После обновления до Windows 11 перестал работать VT-x в VirtualBox.
00:00:05.852762 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available 00:00:05.966704 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap. 00:00:05.966717 NEM: info: Found optional import vid.dll!VidGetHvPartitionId. 00:00:05.966722 NEM: info: Found optional import vid.dll!VidGetPartitionProperty. 00:00:05.966788 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work... 00:00:05.966793 NEM: WHvCapabilityCodeExtendedVmExits = 0x0000000000007fff [пропущено для краткости] 00:00:05.968227 NEM: Adjusting APIC configuration from X2APIC to APIC max mode. X2APIC is not supported by the WinHvPlatform API! 00:00:05.968230 NEM: Disable Hyper-V if you need X2APIC for your guests! 00:00:05.968455 NEM: 00:00:05.968456 NEM: NEMR3Init: Snail execution mode is active! 00:00:05.968456 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode. 00:00:05.968456 NEM: To see VirtualBox run at max speed you need to disable all Windows features 00:00:05.968456 NEM: making use of Hyper-V. That is a moving target, so google how and carefully 00:00:05.968456 NEM: consider the consequences of disabling these features. 00:00:05.968456 NEM: 00:00:05.968487 CPUM: No hardware-virtualization capability detected
В Windows 10 эта часть лога выглядела так:
00:00:08.088362 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support 00:00:08.088503 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x1f
"Грязное" исправление выглядит так: bcdedit /set hypervisorlaunchtype off
. После этого перезагрузился и теперь VirtualBox работает как и прежде. Скорее всего есть более правильный способ выключить такое поведение, но разбираться пока времени нет.
Комментариев нет:
Отправить комментарий