Win11 guest on win11 host with 3D support freezes on boot

[schulzki]

Hi, I try to run a win11 guest on my Win11 dev PC (16gb RAM, I7, GF1650, latest win updates and graphic drivers installed)

I use virtualbox 7.0.4 r154605 (Qt5.15.2) and the W11 dev image from Microsoft.
latest guest additions did not work (wouldn't boot afterwards), so I used guest additions 6.1.40

Everything works, but I can't switch on 3D support (which I really need). The vb machine will consistently freeze during boot (same with or without guest additions installed)
Actually, the machine seems to be alive, but it is not advancing anymore. It is stuck repeating the same line in the logfile over and over:

Code: Select all

VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0

letting it run longer will only add more of these messages until I eventually shut it down.
Attached the logfile, hope somebody can help, thanks a lot!

[mpack]

00:00:09.991669 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:10.081329 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:10.081344 NEM: info: Found optional import vid.dll!VidGetHvPartitionId.
00:00:10.081349 NEM: info: Found optional import vid.dll!VidGetPartitionProperty.
00:00:10.081422 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[schulzki]

Thanks for the quick reply! I followed the guides and now the quoted messages are not in the log anymore (Also the turtle is gone ).
However, the problem remains, still stuck on boot with 3D switched on.

Maybe some other ideas? I attached a new logfile.

[mpack]

It looks like you made quite a lot of changes beyond disabling Hyper-v. It looks like you also upgraded to VirtualBox v7. I believe 3D acceleration works very differently in VirtualBox v7, but you neglected to install the v7 GAs (you still have 6.1.40 Guest Additions in there).

So, I would update the GAs. I would also reduce the VM CPU allocation to the guest to 2 cores.

Personally I would have let v7 go through a few more interactions before I jumped to it. But I have no concrete reason for that, so you may as well stick with it now.

Your log has a huge number of these lines:

00:01:14.255342 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:19.285059 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:24.300919 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:29.328202 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:34.371487 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:39.391734 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0

... which I don't recognize. Let's see if they go away when the GAs are updated.

Note: in fact you shouldn't update the 6.1.40 GAs. Instead you uninstall the old ones, then install the new ones. I suspect that uninstalling the GAs causes it to restore any modified system DLLs, which will be necessary since the new 3D engine uses a different method.