re: how do I preset ddb's LINES to zero
> > try "options DB_MAX_LINE=0" in your kernel? > > Right. Unfortunately that fails the "without having to rebuild the > kernel" requirement :-) another option would be to use say, gdb :-), to change the value of the "db_max_line" variable from default of 24 to 0, and then boot that modified kernel... if you find the boot to ddb is problematic.
Re: how do I preset ddb's LINES to zero
On Fri, 15 Dec 2023 at 22:59, matthew green wrote: > > Andrew Cagney writes: > > > > thanks, I'll add that (it won't help with my immediate problem of a > > > > panic during boot though) > > > > > > From DDB command prompt "set $lines = 0" ... > > > > Um, the test framework's VM is stuck waiting for someone to hit the > > space bar :-) > > > > I guess I could modify my pexpect script to do just that, but I was > > kind of hoping I could do something like add ddb.lines=0 to the boot > > line. > > try "options DB_MAX_LINE=0" in your kernel? Right. Unfortunately that fails the "without having to rebuild the kernel" requirement :-) > we have poor boot-command line support if you compare against > say what linux can do. booting directly to ddb is sufficient for my needs. thanks
Re: VirtIO MMIO for amd64
On 2/23/22 20:26, el16095 wrote: Firecracker informs VMs about MMIO devices by appending to the boot command line a string like this "virtio_mmio.device=4K@0xd000:5" ([virtio_mmio.]device=@:). So, from what I understand I'd need to write glue code that takes this information and uses it to setup the MMIO devices on the VM side the way Firecracker expects it to; and then attach virtio through that, right? FYI I'm on it, based on Colin Percival's work here https://github.com/freebsd/freebsd-src/blob/main/sys/dev/virtio/mmio/virtio_mmio_cmdline.c I'm getting some results but Firecracker uses MMIO v2 and we only have v1 so there's still quite some work to do. -- Emile `iMil' Heitor | https://imil.net
