Auto-resize Guest Display is not work on WindowsThinPC

[wangxw]

I use a laptop with a resolution of 2880x1800 and Windows11 host. The client system ThinPC has Guest Adde installed. The resolution can only be set to 1280x720,and Auto-resize Guest Display is not work.
if use Win10 for guest , Auto-resize Guest Display is work.

VirtualBox version is 7.0.8

[mpack]

Please provide a VM log file. 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.

[wangxw]

VBox.zip

(50.85 KiB) Downloaded 30 times

[mpack]

Try increasing the graphics RAM well beyond your current 18MB. Max it out (128MB). Plus you should enable 3D acceleration.

I note also that Hyper-v is enabled on your host, so VirtualBox performance is likely to be poor, and potentially unstable.

00:00:15.251264 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:15.277374 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:15.277383 NEM: info: Found optional import vid.dll!VidGetHvPartitionId.
00:00:15.277385 NEM: info: Found optional import vid.dll!VidGetPartitionProperty.
00:00:15.277430 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

If you want to get rid of Hyper-v then see: HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[wangxw]

Thank you, the Auto-resize issue has been resolved. But the Hyper-v issue you mentioned has not been resolved.

I used an administrator cmd to execute: bcdedit/set hypervisorlaunchtype off
There are still corresponding alarm logs. May I know how to solve it or what tutorials I can recommen

My Host OS is Win11 Home Edition

VBox-20230628.7z

(29.62 KiB) Downloaded 31 times

VBox-20230628.7z

(29.62 KiB) Downloaded 31 times

In addition, what information is in the log that needs to be paid attention to at runtime, and what are the key points that virtualbox logs should focus on.

[wangxw]

I saw the following logs:

Code: Select all

00:00:11.225444 ********************* End of CFGM dump **********************
00:00:11.225759 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support
00:00:11.225838 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x7
00:00:11.227822 CPUM: Matched host CPU INTEL 0x6/0xba/0x2 Intel_Atom_Unknown with CPU DB entry 'Intel Pentium N3530 2.16GHz' (INTEL 0x6/0x37/0x8 Intel_Atom_Silvermont)
00:00:11.227873 CPUM: MXCSR_MASK=0xffff (host: 0xffff)
00:00:11.227905 CPUM: Microcode revision 0x0000410E

This indicates that vt-x has already worked correctly, right?
I turned off the memory integrity setting.

[mpack]

I used an administrator cmd to execute: bcdedit/set hypervisorlaunchtype off

And then followed that with a full boot from power down, right? Because "bcdedit" is the "Boot Configuration Data Editor", whose work only applies during the next full system boot.

As far as I know, "Memory Integrity" relies on Hyper-v so is implicitly disabled if the underlying Hyper-v feature is disabled. However I have never enabled any of those features so I'm not sure about it. We go by what users report, that info being encapsulated in the FAQ.

[fth0]

As far as I know, "Memory Integrity" relies on Hyper-v so is implicitly disabled if the underlying Hyper-v feature is disabled.

The latter is not true any more. See my post in HMR3Init: Attempting fall back to NEM (Hyper-V is active) for the details.

[wangxw]

thanks, it`s work.