Opened 3 years ago
Last modified 3 years ago
#20807 new defect
echec de l'ouverture de session pour la machine virtuelle XP
| Reported by: | mas421 | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.32 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
bonjour, je rencontre un pb à l'ouverture de session suite à la mise à jour de Virtual box 6.1.32
comment corriger cela, svp merci?
"Échec de l'ouverture de session pour la machine virtuelle XP.
Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
Code d'erreur : E_FAIL (0x80004005) Composant : ConsoleWrap Interface : IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"
Attachments (1)
Change History (3)
by , 3 years ago
| Attachment: | Capture d'écran 2022-02-03 13.53.22.png added |
|---|
comment:1 by , 3 years ago
comment:2 by , 3 years ago
@klaus:
You can find a VBox.log file from a similar case of a forum user in Error message "Not in a hypervisor partition". Reading the forum thread again, I noticed that the forum user "restored the OS image with version 6.1.30" to solve the issue, so it was possibly more than just reverting the VirtualBox update. Do you know a combination of installed Windows features that can lead to this error combination?
VBox.log would tell us a lot more than the screenshot... don't we emphasize the importance of getting the log file enough in the instructions for creating a new ticket? Rhetoric question.
Suspect that your PC simply has VT-x/AMD-V disabled in the BIOS, i.e. the 2nd part of the message is more likely. Can happen e.g. after BIOS upgrades. You can fix this by changing the BIOS settings.