Please excuse me for my approximate English.
(I am French)
But I use automatic translation.
Hello to all,
My problem is very similar to "fth0"
However, the circumstances are different.
Here's how the problem looks for me :
I have a lab made up of different guests: Windows 11 and other Windows, Linux …
My host is Windows 11 Professional.
1) On my old MSI laptop
I had VirtualBox version 6 installed.
I upgrade, without difficulty, to VB 7.0.0 then to VB 7.0.2
All my virtual machines are working including Windows 11.
For information, I am attaching the "Vbox.log" log file of a VM Windows 11 Pro: « win11pro-1-guest-2022-10-28.zip »
2) On my new HP laptop
I still have Windows 11 Professional as a host
And I directly installed VirtualBox version 7.0.2
Then I installed my new lab by copying the files of each VM to my new PC and operating, under VirtualBox, by adding machines.
By testing the first Windows 11 VM mentioned in 1) of my presentation, I obtain after a few minutes an "Aborted" state.
Attached is the "Vbox.log" file: « win11pro(add)-2022-10-29.zip »
So I try another way:
I create a Windows 11 Pro virtual machine starting from an ISO image « Win11_22H2_French_x64v1.iso »
This time I get a total freeze.
Nothing works anymore. I have to shut down the machine abruptly.
See the attached "Vbox.log" file: « win11pro-2-guest-2022-10-29.zip »
If, with my old MSI laptop, everything worked fine with the same Windows 11 Pro host and the same VirtualBox version 7.0.2, I conclude that the problem could be a hardware incompatibility with my new HP laptop:
Network interface?
(Note however my Linux VMs are working ; only Windows VMs seem affected)
I don't know what to look for in the logs.
Maybe you could help me?
That's why I am attaching my logs.
Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
- Attachments
-
- win11pro(add)-2022-10-29.zip
- (38.86 KiB) Downloaded 5 times
-
- win11pro-2-guest-2022-10-29.zip
- (38.87 KiB) Downloaded 5 times
-
- win11pro-1-guest-2022-10-28.zip
- (38.77 KiB) Downloaded 3 times
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
I know that I sometimes have problems, but I didn't know so far that I am a problem. SCNR What did you try to say?nonsolum wrote:My problem is very similar to "fth0"
Regarding your hosts, on the new HP laptop Microsofts hypervisor (Hyper-V) is running, which means that VirtualBox cannot use the hardware virtualization (Intel VT-x) itself. According to reports by other users, VirtualBox 7.0.2 seems to have problems in that case.
Re: Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
My apologies fth0.
But my English is really bad.
I thought we had a similar problem, but I was wrong.
It seems to be something else.
In fact, I have partially solved the problem :
I updated my network interface driver.
It's about:
Intel wireless-AC 9560
And as a result I have all my Windows guests accessible.
Is there really a cause and effect relationship?
But I still find myself with my Linux guests, which in turn become inaccessible.
I don't understand why.
Concerning Hyper-V I don't understand why the logs refer to it
Hyper-V is not activated on my system.
Perhaps you can explain?
Thank you for your help.
But my English is really bad.
I thought we had a similar problem, but I was wrong.
It seems to be something else.
In fact, I have partially solved the problem :
I updated my network interface driver.
It's about:
Intel wireless-AC 9560
And as a result I have all my Windows guests accessible.
Is there really a cause and effect relationship?
But I still find myself with my Linux guests, which in turn become inaccessible.
I don't understand why.
Concerning Hyper-V I don't understand why the logs refer to it
Hyper-V is not activated on my system.
Perhaps you can explain?
Thank you for your help.
- Attachments
-
- kali-linux-2022.3-virtualbox-amd64.log.zip
- (17.94 KiB) Downloaded 3 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
Yes, it is. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).nonsolum wrote:Hyper-V is not activated on my system.
Re: Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
Thank you fth0
I have read the topic with interest:
HMR3Init: Attempting fall back to NEM (Hyper-V is active)
viewtopic.php?f=25&t=99390
Indeed, when I look at the logs of my virtual machines, I find :
I note the comment made in Scottgus1's topic
viewtopic.php?f=25&t=99390
« You might notice in the guest window's Status Bar the green turtle The choice of animal is appropriate:
Your guest is running, just really slow.
Or it might guru-meditate or crash. Or guest OS's won't properly hash their update files or ISOs. »
Before going further into the analysis of my problem.
I must recall the situation.
I have two cases:
1) The Windows guests.
I was able to create them without any problem.
But the guests are very, very, slow.
And when the mouse points to the "green turtle of the guest window's Status Bar"
I get the following pop-up window:
The presence of Hyper-V is mentioned although it is not activated in the "Windows Features".
2) The Linux guests
I was unable to install the Linux guests from an ISO image.
I get a "...Kernel Panic..."
However, I was able to install Kali Linux from a VirtualBox pre-built image.
And there when I point the mouse on the green turtle of the guest window's Status Bar,
I get the following pop-up window:
KVM (Kernel-based Vitual Machine) is a virtualisation tool for Linux.
I don't know more about it.
But I would like to understand why KVM is involved at this stage.
Conclusions:
It appears that, at the very least, I need to fix the problem of Hyper-V running on my Windows 11 Pro host in the background.
viewtopic.php?f=25&t=99390
"To turn Hyper-V off completely, do this:"
I followed Scottgus1's advice
But I can't get it to work.
I'll keep looking and report back in a later post.
I have read the topic with interest:
HMR3Init: Attempting fall back to NEM (Hyper-V is active)
viewtopic.php?f=25&t=99390
Indeed, when I look at the logs of my virtual machines, I find :
Code: Select all
« 00:00:03.886077 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.964809 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work... »
viewtopic.php?f=25&t=99390
« You might notice in the guest window's Status Bar the green turtle The choice of animal is appropriate:
Your guest is running, just really slow.
Or it might guru-meditate or crash. Or guest OS's won't properly hash their update files or ISOs. »
Before going further into the analysis of my problem.
I must recall the situation.
I have two cases:
1) The Windows guests.
I was able to create them without any problem.
But the guests are very, very, slow.
And when the mouse points to the "green turtle of the guest window's Status Bar"
I get the following pop-up window:
Code: Select all
...
Paravirtualisation interface: Hyper-V
...
2) The Linux guests
I was unable to install the Linux guests from an ISO image.
I get a "...Kernel Panic..."
However, I was able to install Kali Linux from a VirtualBox pre-built image.
And there when I point the mouse on the green turtle of the guest window's Status Bar,
I get the following pop-up window:
Code: Select all
...
paravirtualisation interface: KVM
...
I don't know more about it.
But I would like to understand why KVM is involved at this stage.
Conclusions:
It appears that, at the very least, I need to fix the problem of Hyper-V running on my Windows 11 Pro host in the background.
viewtopic.php?f=25&t=99390
"To turn Hyper-V off completely, do this:"
I followed Scottgus1's advice
But I can't get it to work.
I'll keep looking and report back in a later post.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
The 10.5. Paravirtualization Providers (configured under System > Acceleration > Paravirtualization Interface as Default) are correct in both cases and have nothing to do with the Windows hypervisor (Hyper-V) on the host OS. So you can concentrate on getting rid of the latter.
Re: Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
Hello everyone,
I'm back.
I followed the recommendations of scottgus1:
viewtopic.php?f=25&t=99390
But I still have the "green turtle". ☹
Here is how I did it:
1) I checked if Hyper-V was not enabled .
It is not.
2) I entered the following commands:
3) Shutdown and disconnection
4) after reboot:
Finally
I still have the same problems:
- Very slow Windows guests
(the green turtle)
- Linux guests: impossible to install them from an ISO image
I don't know what to do
Thank you for your help.
I'm back.
I followed the recommendations of scottgus1:
viewtopic.php?f=25&t=99390
But I still have the "green turtle". ☹
Here is how I did it:
1) I checked if Hyper-V was not enabled .
It is not.
2) I entered the following commands:
Code: Select all
PS C:\Users\hjg> bcdedit /set hypervisorlaunchtype off
L’opération a réussi.
PS C:\Users\hjg> DISM /Online /Disable-Feature:Microsoft-Hyper-V
Outil Gestion et maintenance des images de déploiement
Version : 10.0.22621.1
Version de l’image : 10.0.22621.755
Désactivation de la ou des fonctionnalités
[==========================100.0%==========================]
L’opération a réussi.
PS C:\Users\hjg>
4) after reboot:
Code: Select all
PS C:\Users\hjg> bcdedit
Gestionnaire de démarrage Windows
---------------------------------
identificateur {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale fr-FR
inherit {globalsettings}
default {current}
resumeobject {6dc4c6c2-4d23-11ed-b5c8-d1ffd2a6686d}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Chargeur de démarrage Windows
-----------------------------
identificateur {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 11
locale fr-FR
inherit {bootloadersettings}
recoverysequence {6dc4c6c4-4d23-11ed-b5c8-d1ffd2a6686d}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {6dc4c6c2-4d23-11ed-b5c8-d1ffd2a6686d}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Off
PS C:\Users\hjg>
I still have the same problems:
- Very slow Windows guests
(the green turtle)
- Linux guests: impossible to install them from an ISO image
I don't know what to do
Thank you for your help.
Re: Guest Windows 11 under VB 7.0.2 Hardware incompatibility?
Hello,
The green turtle does not appear anymore.
All my virtual machines are now operational:
- Windows guests are running at normal speed
- Linux guests can be installed from an ISO image
I solved the problem by modifying a registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity
Set to 0:
Enabled REG_DWORD 0
EnabledBootld REG_DWORD 0
WasEnbledBy REG_DWORD 0
I have been inspired by scottgus1
viewtopic.php?f=25&t=99390
and by InfoSecDr
viewtopic.php?f=6&t=105887&p=517076#p517076
Observations :
1- On my system I have the registry key mentioned above, but it may look different on another OS.
As a reminder, I have for OS:
Édition Windows 11 Professionnel
Version 22H2
Installé le 16/10/2022
Build du système d’exploitation 22621.755
Expérience Windows Feature Experience Pack 1000.22636.1000.0
2- I don't know if the change to the key has any other effect on the operation of my OS.
There may be collateral damage.
3- I don't know if it is necessary to use the preliminary commands to reach this result:
> bcdedit /set hypervisorlaunchtype off
and
> DISM /Online /Disable-Feature:Microsoft-Hyper-V
Thanks to the whole community for their help
Good luck to all
The green turtle does not appear anymore.
All my virtual machines are now operational:
- Windows guests are running at normal speed
- Linux guests can be installed from an ISO image
I solved the problem by modifying a registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity
Set to 0:
Enabled REG_DWORD 0
EnabledBootld REG_DWORD 0
WasEnbledBy REG_DWORD 0
I have been inspired by scottgus1
viewtopic.php?f=25&t=99390
and by InfoSecDr
viewtopic.php?f=6&t=105887&p=517076#p517076
Observations :
1- On my system I have the registry key mentioned above, but it may look different on another OS.
As a reminder, I have for OS:
Édition Windows 11 Professionnel
Version 22H2
Installé le 16/10/2022
Build du système d’exploitation 22621.755
Expérience Windows Feature Experience Pack 1000.22636.1000.0
2- I don't know if the change to the key has any other effect on the operation of my OS.
There may be collateral damage.
3- I don't know if it is necessary to use the preliminary commands to reach this result:
> bcdedit /set hypervisorlaunchtype off
and
> DISM /Online /Disable-Feature:Microsoft-Hyper-V
Thanks to the whole community for their help
Good luck to all