-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crash with virtio-net + UEFI #164
Comments
I'm getting the same issue when running OpenBSD 6.5 using UEFI and the virtio-net interface.
Like @adaugherity if I use the e1000 interface it works. Oddly, I can occasionally get it to work but only if I have another Here is the script I used for OpenBSD 6.5
Here are the boot messages of one of the successful times it booted. |
same here:
|
hum maybe related to this was raised upstream a while ago: |
This seems to fix the crash while loading the driver on install at least :) EDIT: Actually I was confusing this with a "similar" issue get with the block driver but the GHI is originaly for virtio-net |
I can confirm @Autonomic's report that virtio-net+UEFI works if another VM is already running using e1000. Tested with both openSUSE Leap 15.1 and OpenBSD 6.6. However... that only applies to booting from disk or cd. If the UEFI attempts to boot from the network, it crashes in the same way! I discovered this by trying to figure out why my openSUSE VM would only boot from CD, not its hard disk, when using EFI. Turns out it was installed in BIOS mode and lacks an EFI System Partition, so that explains it. If I remove the CD from the VM config, it attempts to boot the hard disk (which fails), and then falls back to network booting... which crashes xhyve. |
When using virtio-net with an UEFI firmware (-f bootrom), hyperkit crashes on an assertion. See the related bug on xhyve: machyve/xhyve#164 The complete details are not clear to me, but it seems that during boot, the firmware reads on the interface but doesn't provide big enough read buffers. It seems that the space for VLAN headers is missing. This patch drops the related reads, so normal booting can occur. Network boot probably doesn't work, though.
When using virtio-net with an UEFI firmware (-f bootrom), hyperkit crashes on an assertion. See the related bug on xhyve: machyve/xhyve#164 The complete details are not clear to me, but it seems that during boot, the firmware reads on the interface but doesn't provide big enough read buffers. It seems that the space for VLAN headers is missing. This patch drops the related reads, so normal booting can occur. Network boot probably doesn't work, though. Signed-off-by: Antoine Martin <[email protected]>
When using virtio-net with an UEFI firmware (bootrom), xhyve crashes on an assertion. See the related bug machyve#164 The complete details are not clear to me, but it seems that during boot, the firmware reads on the interface but doesn't provide big enough read buffers. It seems that the space for VLAN headers is missing. This patch drops the related reads, so normal booting can occur. Network boot probably doesn't work, though. Signed-off-by: Antoine Martin [email protected]
When using virtio-net with an UEFI firmware (bootrom), xhyve crashes on an assertion. See the related bug machyve#164 The complete details are not clear to me, but it seems that during boot, the firmware reads on the interface but doesn't provide big enough read buffers. It seems that the space for VLAN headers is missing. This patch drops the related reads, so normal booting can occur. Network boot probably doesn't work, though. Signed-off-by: Antoine Martin [email protected]
I tried to see if I could use UEFI to load GRUB 2 from within the guest, to avoid having to copy the kernel/initrd from the guest to host after every kernel patch. Unfortunately, xhyve immediately crashes:
(FIRMWARE=BHYVE_UEFI.fd copied from FreeBSD, of course; I was previously using
-f kexec,$KERNEL,$INITRD,"$CMDLINE"
instead of-l bootrom,$FIRMWARE
.)If I change virtio-net to e1000, then everything works properly, at least with a serial console. I'm having issues with VNC but that's unrelated to vmnet.
The text was updated successfully, but these errors were encountered: