On 11/11/13 14:52, Teske, Devin wrote: > On Nov 11, 2013, at 12:44 PM, Peter Grehan wrote: > >> Hi Devin, >> >>> Question: >>> Does bhyve set kern.console irrespective of loader.conf values? >> The kernel sets it based on what it determines the console to be. Bhyve influences that by requesting a serial console. This is no different than booting on a headless machine with a serial console. >> > Well, for a headless meachine, I would set console=comconsole,vidconsole > in loader.conf(5), then our Forth code slurps it in via loader.4th + support.4th > routines... > > When boot is executed, I know I can see "kenv console", but hadn't realized > that there were/are a host of others that are slurped into the kernel for later > (very purposeful) fetching. > > So when you say that bhyve requests a serial console... I assume now it's > setting variables... but via raw Forth? C code? loader.conf(5)? I've seen my > menu come up under bhyve, and I noticed that it only has a 5-second count- > down instead of the usual 9 -- but I'm curious how you're exporting the variables. I think you've misunderstood. kern.console isn't set by loader. It reflects the state of the kernel, which decides what to do autonomously based on a number of driver and platform-dependent things including, but not limited to, kenv (loader variables, for instance). -NathanReceived on Mon Nov 11 2013 - 19:56:45 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:44 UTC