Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Yesterday, Microsoft finally enabled the upgrade my Windows 10 laptop to Windows 11. I did so without any issues.
I logged into the new Windows 11 and started up Virtual Box and both my VMs came up (FreeBSD 12.2 and Windows Server 2012R2). So far so good.
Overnight three updates for Windows 11 were applied (KB5005537, KB5013628, and KB5023943) and my system rebooted.
I logged in, started up my VMs. The Windows Server 2012R2 started without any issues. FreeBSD 12.2 starts to boot and then gets a 'privilege instruction failure'
I have tried to do a screen grab, but VB immediately starts reboots on the error and tries to bring up FreeBSD - putting me in an infinite loop.
Has anyone seen this before? Anyone know what I should try (remove the Windows 11 patches - and won't they just reinstall?)
I logged into the new Windows 11 and started up Virtual Box and both my VMs came up (FreeBSD 12.2 and Windows Server 2012R2). So far so good.
Overnight three updates for Windows 11 were applied (KB5005537, KB5013628, and KB5023943) and my system rebooted.
I logged in, started up my VMs. The Windows Server 2012R2 started without any issues. FreeBSD 12.2 starts to boot and then gets a 'privilege instruction failure'
I have tried to do a screen grab, but VB immediately starts reboots on the error and tries to bring up FreeBSD - putting me in an infinite loop.
Has anyone seen this before? Anyone know what I should try (remove the Windows 11 patches - and won't they just reinstall?)
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Did you reinstall VirtualBox? You really should, after such a big change to the host OS.
As to what is different about the various VMs, are some using single CPU cores and others multiple? Are the failures all using >1 core?
Another thing to be wary about after a feature update is Windows enabling Hyper-v. While in theory VirtualBox can sometimes tolerate this, in practice the two seldom work well together, and problems when >1 core is configured is one known area of conflict. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).
As to what is different about the various VMs, are some using single CPU cores and others multiple? Are the failures all using >1 core?
Another thing to be wary about after a feature update is Windows enabling Hyper-v. While in theory VirtualBox can sometimes tolerate this, in practice the two seldom work well together, and problems when >1 core is configured is one known area of conflict. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Thinking there was an issue with VirtualBox, I downgraded to 6.1.32 - same error.
Reinstalled 6.1.34 - same error.
Just tried to create a new VM, using the FreeBSD DVD (FreeBSD 12.2) and during boot from DVD hit the same privilege instruction error
FreeBSD has 4 CPUs, 4GB of memory.
Windows 2012R2 has 1 CPU, 4GB of memory
Reinstalled 6.1.34 - same error.
Just tried to create a new VM, using the FreeBSD DVD (FreeBSD 12.2) and during boot from DVD hit the same privilege instruction error
FreeBSD has 4 CPUs, 4GB of memory.
Windows 2012R2 has 1 CPU, 4GB of memory
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Please mark solved.
Required an upgrade to FreeBSD 12.3 (12.2 no longer supported)
Required an upgrade to FreeBSD 12.3 (12.2 no longer supported)
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.3/13.1
Spoke too soon.
It booted to a point and hung.
I have attempted to create new VMs - one for FreeBSD 12.3 and another for FreeBSD13.1 and had the same "privilege instruction failure".
I have screenshots of the failures - but I don't seem to see a way to upload
It booted to a point and hung.
I have attempted to create new VMs - one for FreeBSD 12.3 and another for FreeBSD13.1 and had the same "privilege instruction failure".
I have screenshots of the failures - but I don't seem to see a way to upload
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Please try two processors in the VM.
If that does not work, please provide a log:
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
If that does not work, please provide a log:
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Two CPUs and it booted just fine.scottgus1 wrote:Please try two processors in the VM.
Thank you!
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Great!
Above, you mentioned that a FreeBSD VM had 4 processors and hit the error. Does it do that anymore with 4 processors?
Above, you mentioned that a FreeBSD VM had 4 processors and hit the error. Does it do that anymore with 4 processors?
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
It worked for about 20 minutes, I was typing in the VM and it spontaneously rebooted.scottgus1 wrote:Great!
Above, you mentioned that a FreeBSD VM had 4 processors and hit the error. Does it do that anymore with 4 processors?
It then hung on reboot.
Attaching log file
- Attachments
-
- jhbuild-2022-06-01-13-28-27.zip
- (29.54 KiB) Downloaded 5 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
The log doesn't show anything egregiously wrong in the Virtualbox 'hardware'. The only thing I see is that host Hyper-V is enabled. Try turning it off as an experiment, see the "Attempting" link above.
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
In looking at the settings, I don't see anything checked w/relation to Hyper-Vscottgus1 wrote:The log doesn't show anything egregiously wrong in the Virtualbox 'hardware'. The only thing I see is that host Hyper-V is enabled. Try turning it off as an experiment, see the "Attempting" link above.
I am running WSL, not sure if that requires Hyper-V
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Are these the Windows Features?heymanj wrote:In looking at the settings, I don't see anything checked w/relation to Hyper-V
WSL2 does.heymanj wrote: am running WSL, not sure if that requires Hyper-V
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Yesscottgus1 wrote:Are these the Windows Features?heymanj wrote:In looking at the settings, I don't see anything checked w/relation to Hyper-V
scottgus1 wrote:WSL2 does.heymanj wrote: am running WSL, not sure if that requires Hyper-V
Code: Select all
PS C:\Users\Jerrold Heyman> wsl -l -v
NAME STATE VERSION
* Ubuntu-20.04 Running 2
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Did you read the tutorial?
Re: Virtual Box 6.1.34, Windows 11, and FreeBSD 12.2
Is there a specific one?scottgus1 wrote:Did you read the tutorial?
I've used https://docs.microsoft.com/en-us/windows/wsl/install as my instructions, when I did the installation on Window10.
I'm wondering if any of my problem(s) are related to upgrading to Windows11 rather than a clean installation.