LOG is LIMITED due to character limitation.
Any help is appreciated, since I need this VM to work :( Now when I want to start the machine again (doesnt matter if I use vagrant up or directly inside the Oracle VM Virtual Box) I receive a Kernel panic - not syncing: Attempted to kill init! error. Loop (for some debugging) which got the machine stuck. That said - VMs in VirtualBox should work when the Windows Hypervisor is enabled, but any seriously complicated software has bugs, and this is an entirely different code path than when VirtualBox uses its own hypervisor code which isn't possible when Microsoft's is active.I am using vagrant with virtualbox and everything worked fine. Memory integrity in the Device Guard area), see e.g. The usual reasons why it is enabled (without you having enabled Hyper-V) is that your Windows 11 config uses the HVCI feature (a.k.a.
the log showsĠ0:00:02.591516 HM: HMR3Init: Attempting fall back to NEM: VT-x is not availableĠ0:00:02.647880 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.Ġ0:00:02.647936 NEM: WHvCapabilit圜odeHypervisorPresent is TRUE, so this might work. Your Windows 11 install has the hypervisor itself enabled somehow.
0 kommentar(er)
