Date: Mon, 04 Sep 2023 10:59:22 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 273560] sysutils/edk2: bhyve flavor causes windows VMs to fail to boot after update to 202308 Message-ID: <bug-273560-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273560 Bug ID: 273560 Summary: sysutils/edk2: bhyve flavor causes windows VMs to fail to boot after update to 202308 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: uboot@FreeBSD.org Reporter: madpilot@FreeBSD.org Flags: maintainer-feedback?(uboot@FreeBSD.org) Assignee: uboot@FreeBSD.org Hi! First thanks for your work on this port. Unluckily after upgrading the bhyve flavor package to the latest version (202308), the Windows 10 Pro Virtual machines I have running under bhyve stopped working. They were crashing on boot with error 0xc0000225. I did bl= ame windows for this, but I was also unable to boot the official windows 10 installation media to try recovery or a new installation. The installation media was showing a blue screen, 100% vcpu usage for while and then crashing. Googling around there were indications similar behaviour was showing up als= o on physical machines with buggy UEFI BIOSes. At this point I noticed the edk2 port provided UEFI firmware was recently updated. I have now reverted to the previous version (202202), grabbing the port bef= ore commit 8097dda40a03b8a27a1edf1f31a8af0455a52baf , and the windows VMs are n= ow working fine again without need of any change. I think this regression should be investigated, at least. Maybe upstream already has a fix for this? If any further information is required please ask. Thanks in advance! --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273560-7788>