Host Win11-VM with Win11 works under VB 6.1.x under VB 7.0.x VM freezes after a few minutes

[RonaldMacDonald]

Hello,

I have been using Virtualbox for many years and run several VMs under it (Windwos 10, Windows 11, CentOS, etc.).

One of my most important VMs that runs every day and often for several days at a time is a Windows 11 VM (current kernel and driver, updated from Windows 7->Windows 10->Windows 11) and runs without problems and Virtualbox 6.1.x

As soon as the same VM runs under 7.0.x it freezes with the same settings, etc. I hoped that the error would disappear with the later versions and bug fixes in 7.0.x but unfortunately the behaviour is still the same (since 7.0.0 to 7.0.6).

Of course the latest VirtualboxGuestAdditions are always installed (at the moment the 7.0.6 VirtualboxGuestAddoitions runs in the Win 11 VM under Virtuelbox 6.1.42 without problems) in every Virtualbox version in the Win 11 VM.

I have already tried the settings such as ParaVirtualisation Hyper-V or Default and 3D acceleration on or off (normally off).

In which LOG files do I have to look for the error and could I publish the error here in the hope that someone from the developers reads it and the error is fixed?

Thanks for your help in advance.

Best Regards

Ronald

[scottgus1]

the latest VirtualboxGuestAdditions are always installed

7.0's graphics are under development. Please upgrade to 7.0.6 Virtualbox, Extension Pack if used, and Guest Additions.

If this does not get a stable VM, and you have 3D acceleration turned on, try running the VM with 3D acceleration turned off. If that stabilizes the VM, Please create a ticket in the Bugtracker with the problem description, the manufacturer and model of the host PC's graphics card, the graphics driver version (on the host OS), and a (zipped) VBox.log file.

Please also post the zipped log file here, too.

[RonaldMacDonald]

I know the settings from the old Virtualbox versions and 3D is switched off (has always been under development and never final as far as I know). 7.0.6 is installed and behaviour has been like this since 7.0.0. LOG file is attached and I'll open a ticket for it.

[mpack]

Wrong log. We need the VM log, not the background service log. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[RonaldMacDonald]

Interesting observation: Virtualbox 7.0.6 and the VirtualboxGuestAdditions 6.1.42 run perfectly and stably. Only when the VirtualboxGuestAdditions of 7.0.6 are installed in the Win11 VM, the Win 11 VM becomes unstable.

[scottgus1]

Please note the responses to your previous posts before posting again.

[RonaldMacDonald]

Here is the LOG File.
Systtem: Windows 11
CPU: Intel i7-6820
RAM: 64GB
Graficcards: Intel HD Graphics 530 (Driver Version 31.0.101.2115 (Date: 16.11.2022)) , Nvidia Qua M2000M (Driver Version 31.0.15.2824 (Date: 15.01.2023))

[j77h]

Virtualbox 7.0.6 and the VirtualboxGuestAdditions 6.1.42 run perfectly and stably.

Thank you, this info is very useful.

On Linux it's not advisable to keep a package downgraded for long, *
so it's good to know that it's OK to run the latest Virtualbox.
Using an old version of GA is not a problem, as it doesn't run on the host.

* On Unix/Linux, apps use system libraries, so versions need to stay in sync.

[granada29]

@RonaldMacDonald

You need to download and install (on your host) the Extensions Pack matching your installed version of VirtualBox. Although there is some leeway with Guest Additions, the Extensions MUST match the VirtualBox version. Please do this and post a new log when you have it installed.

Code: Select all   Expand viewCollapse view

00:00:06.827509 VirtualBox VM 7.0.6 r155176 win.amd64 (Jan 11 2023 16:38:38) release log
00:00:06.910137 Installed Extension Packs:
00:00:06.910149   Oracle VM VirtualBox Extension Pack (Version: 6.1.42 r155177; VRDE Module: VBoxVRDP; Crypto Module:  unusable because of 'VBoxExtPackVMRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x30000 got 0x50000'')


[mpack]

00:00:07.261414 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:08.494013 CPUM: Physical host cores: 4

Your i7-6820HQ CPU has 4 cores. So you cannot dedicate 4 cores to the guest and still expect stability. Reduce the VM to 2 cores.

00:00:06.827509 VirtualBox VM 7.0.6 r155176 win.amd64 (Jan 11 2023 16:38:38) release log
...
00:00:06.910149 Oracle VM VirtualBox Extension Pack (Version: 6.1.42 r155177; VRDE Module: VBoxVRDP; Crypto Module: unusable because of 'VBoxExtPackVMRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x30000 got 0x50000'')

Your extension pack version is mismatched. Note Extension Pack, not the same as Guest Additions.

Yes, installing old Guest Additions has the effect of disabling 3D acceleration, which can bypass 3D acceleration problems. But you already have 3D acceleration disabled, so I would not expect any benefit from this. This was a trick using by people have problems early in the 7.0.x branch (i.e. 7.0.0 and 7.0.2). I'm not sure if we still need it with 7.0.6.

You absolutely should NOT be trying to use a 4K graphics mode without 3D acceleration. There is no way software rendering can keep up with that workload. If you want a larger screen then you'll have to select 1920x1028 and use 200% scaling.

00:01:33.126675 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000001a632560000 w=3840 h=2071 bpp=32 cbLine=0x3C00 flags=0x1 origin=0,0

[PeterUK]

I too have this problem and did a post about it.
viewtopic.php?f=2&t=107402

[scottgus1]

7.0's graphics are under development. Please upgrade to 7.0.6 Virtualbox, Extension Pack if used, and Guest Additions.

If this does not get a stable VM, and you have 3D acceleration turned on, try running the VM with 3D acceleration turned off. If that stabilizes the VM, Please create a ticket in the Bugtracker with the problem description, the manufacturer and model of the host PC's graphics card, the graphics driver version (on the host OS), and a (zipped) VBox.log file.

[RonaldMacDonald]

Thank you for the analysis.

I had forgotten the extension pack and now it also works with Guest Additions 7.0.6 in the VM.
I had always switched off 3D acceleration, because historically it was never stable. Even without 3D acceleration, 4K had already worked perfectly with 6.1.x.

I took the idea and switched on 3D acceleration in 7.0.6 and it has worked perfectly so far.

I see things a little differently with the cores, because nothing runs in the host and everything happens in the VM and the host has no problems with utilisation according to the "Resource Monitor" in Win11.

[mpack]

because nothing runs in the host

The opposite is true. VirtualBox is a host app, little of importance runs as guest code.

[RonaldMacDonald]

What I learned from VMware and Hyper-V for VMs:

- RAM is dedicated and you can't have enough in doubt

- CPU can be shared and overprovisioned. Do not allocate too many vCPUs (e.g. Microsoft Domain Controller - 1 vCPU or max.2 vCPUs / 8GB or 16GB RAM).

I thought Virtualbox uses Hyper-V as a paravirtualisation (can be preset) if a Windows host (Windows 11 in my case) is used and a VM with Windows operating system...

I have changed it to 2 CPUs and am watching it.