On 25/10/24 22:49, Mark Johnston wrote:
On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
Hi,
I've recently updated my current machines to git commit
525a177c165740fc697df3de5b92e58b3b41477c (Sun Oct 20 22:43:41 2024 -0800)
and just have Windows 10 VMs fail to start in bhyve with the
On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
> Hi,
>
> I've recently updated my current machines to git commit
> 525a177c165740fc697df3de5b92e58b3b41477c (Sun Oct 20 22:43:41 2024 -0800)
> and just have Windows 10 VMs fail to start in bhyve with the error in the
> subject.
>
> I'v
Hi,
I've recently updated my current machines to git commit
525a177c165740fc697df3de5b92e58b3b41477c (Sun Oct 20 22:43:41 2024
-0800) and just have Windows 10 VMs fail to start in bhyve with the
error in the subject.
I've been unable to recover them with usual tricks (automatic recovery,
ch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282241
--- Comment #6 from Andrew Turner ---
It's probably coming from acpi_ged0 as it has some events that look like they
are triggered on battery status change.
You could try setting debug.acpi.ged_defer to 1 to see if that works around the
iss
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282241
Zhenlei Huang changed:
What|Removed |Added
CC||and...@freebsd.org,
