09:29:31 <szilard> Hi. I am trying to get 9front iso booting in Bhyve on OmniOS. I have successfully did it 6 months ago, but now it fails to boot.
09:30:52 <szilard> The console shows the iso starts, the 9front bootloader emits some info and then it attempts to start the kernel, but then the zone suddenly stops.
11:53:34 <andyf_> szilard - is there anything in the zone logs? (`zadm log <zone>` is the easiest way if you have zadm installed)
11:57:07 <szilard> I see this: https://pastebin.com/raw/GB1uV9c2
12:51:20 <andyf_> That will do it, the assertion. We need to understand why it tripped and whether bhyve should handle whatever's going on better.
12:56:23 <szilard> I have attempted to remove every optional stuff from the config, but zadm adds most of them back automatically. So I am unable to check which module / config entry triggers the bug.
12:56:56 <szilard> It would be easier to look at the bhyve sources to see what's going on.
12:57:00 <szilard> or dtrace, maybe
12:59:36 <Woodstock> shouldn't this have left a core file?
13:00:24 <szilard> I am looking at the pci_emul.c here:  * Register (or unregister) the MMIO or I/O region associated with the BAR
13:00:29 <szilard>  * register 'idx' of an emulated pci device.
13:00:51 <Woodstock> if you have a core, the stack will tell you which device failed
13:01:01 <szilard> https://github.com/omniosorg/illumos-omnios/blob/1ff0e8f931b4f26568ca7e19bfc9ead2def3aae5/usr/src/cmd/bhyve/common/pci_emul.c#L650
13:01:25 <szilard> Woodstock: where should I look for the core file?
13:01:46 <szilard> /var/cores?
13:02:24 <szilard> I have many /var/cores/core.bhyve.13782
13:04:54 <Woodstock> well, it's probably the newest one?
13:06:05 <szilard> yep
13:06:24 <szilard> deleted all, and bhyve created a new one, so it is definetely new
13:06:29 <szilard> uploading right now
13:06:48 <szilard> core.bhyve.20110 : https://0x0.st/PHsX.20110
13:06:53 <szilard> it is 10Mb
13:10:54 <Woodstock> it's the framebuffer device
13:11:07 <Woodstock> trying to register bar 1, which I presume is the actual framebuffer memory
13:13:55 <szilard> afaik there is a bhyve config option to disable the fb. Or is this the efi fb? I don't really know too much about bhyve inner working.
13:15:25 <szilard> If I disable vnc it doesn't crash, but it gets stuck
13:17:13 <szilard> without vnc it hangs here: https://pastebin.com/raw/6ASdChgc
13:17:29 <szilard> This is the consol output with BHYVE_DEBUG firmware
13:17:49 <szilard> my scrollback buffer is too short to capture everything, sorry
13:18:34 <szilard> in zadm log i see only this 2 lines:
13:18:35 <szilard> root@omnios:/var/cores# zadm log 9front                                         
13:18:35 <szilard> wrmsr to register 0x401(0) on vcpu 0
13:18:36 <szilard> wrmsr to register 0x401(0) on vcpu 1
13:21:24 <szilard> I am trying it with a different OS iso to see if this is a 9front specific bug or not.
13:25:47 <szilard> openbsd 78.iso boots just fine with enabled vnc.
16:53:06 <andyf> Yes, 9front is obviously doing something we don't expect and we should see what we can do about improving things.
16:53:51 <Woodstock> i don't recall the details, but working on vga bios stuff and gpu passthru a while ago i saw similar issues with bar remapping
19:43:40 <szilard> Oh, this is a known issue : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290098
23:36:03 <andyf> https://paste.omnios.org/?c4dae234fa658ea9#2Awf3e4Seakcqnv9qBehimr1BJ6yxV9DG5Z76r3uCdkS
23:36:49 <andyf> Just checking to see if it's possible to disable the bootrom variables with our framework
23:38:30 <andyf> Yes, szilard try `zadm set 9front uefivars=off`
23:46:53 <szilard> andyf: this works. thanks!
23:47:13 <szilard> I have successfully got it booted via vnc
23:50:02 <szilard> https://0x0.st/PHcK.png
23:52:25 <andyf> Great :)
23:52:56 <andyf> We should probably build bhyve with that extra detailed error message always enabled