vbox 7.0.12 vboxSVGA with 3d "on" hangs on win 11 22h2 host

[hrdwrkr]

Host: Lenovo Laptop full info below. Display: Intel(R) Iris(R) Xe Graphics Full info below.

Vbox log is zipped and attached.

Virtual console Screen shot is attached. NOTE: The 5 dots seen in the screenshot are NOT CHANGING. The display is hung but the underlying OS is still running. Behavior might reflect a hang in an interrupt handler. When hung, there is no response to any keyboard/mouse input.

Using Display|Graphics controller selection "VBoxVGA" there is no problem. Switching to "VBoxSVGA" encounters several hangs at various times. The "3D" setting does not change the outcome. The log attached is a hang during a guest OS initiated reboot of the VM.

HOST MACHINE: OS Name Microsoft Windows 11 Pro Version 10.0.22621 Build 22621 OS Manufacturer Microsoft Corporation System Manufacturer LENOVO System Model 21CD000QUS System Type x64-based PC System SKU LENOVO_MT_21CD_BU_Think_FM_ThinkPad X1 Yoga Gen 7 Processor 12th Gen Intel(R) Core(TM) i5-1250P, 1700 Mhz, 12 Core(s), 16 Logical Processor(s) BIOS Version/Date LENOVO N3AET71W (1.36 ), 1/31/2023 SMBIOS Version 3.4 Embedded Controller Version 1.17 BIOS Mode UEFI BaseBoard Manufacturer LENOVO BaseBoard Product 21CD000QUS BaseBoard Version SDK0T76530 WIN Platform Role Mobile Secure Boot State On Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "10.0.22621.1413" Time Zone Eastern Daylight Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 15.7 GB Available Physical Memory 2.92 GB Total Virtual Memory 26.7 GB Available Virtual Memory 7.45 GB Page File Space 11.0 GB Page File C:\pagefile.sys Kernel DMA Protection On Virtualization-based security Running Virtualization-based security Required Security Properties Base Virtualization Support Virtualization-based security Available Security Properties Base Virtualization Support, Secure Boot, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization Virtualization-based security Services Configured Hypervisor enforced Code Integrity, Secure Launch, SMM Firmware Measurement Virtualization-based security Services Running Hypervisor enforced Code Integrity, Secure Launch, SMM Firmware Measurement Windows Defender Application Control policy Enforced Windows Defender Application Control user mode policy Off Device Encryption Support Elevation Required to View A hypervisor has been detected. Features required for Hyper-V will not be displayed.

DISPLAY: Name Intel(R) Iris(R) Xe Graphics PNP Device ID PCI\VEN_8086&DEV_46A6&SUBSYS_22E617AA&REV_0C\3&11583659&1&10 Adapter Type Intel(R) Iris(R) Xe Graphics Family, Intel Corporation compatible Adapter Description Intel(R) Iris(R) Xe Graphics Adapter RAM 1.00 GB (1,073,741,824 bytes) Installed Drivers <>,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_4f565bf362d7d0bd\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_4f565bf362d7d0bd\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_4f565bf362d7d0bd\igd12umd64.dll Driver Version 31.0.101.4502 INF File oem106.inf (iADLPD_w10_DS section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1200 x 60 hertz Bits/Pixel 32 Memory Address 0x3C000000-0x3CFFFFFF Memory Address 0x0000-0xFFFFFFF I/O Port 0x0000FFC0-0x0000FFFF IRQ Channel IRQ 4294967241 Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_4F565BF362D7D0BD\IGDKMDN64.SYS (31.0.101.4502, 48.26 MB (50,603,416 bytes), 7/20/2023 9:43 AM)

[hrdwrkr]

VBox log - zipped

[hrdwrkr]

Screen shot of hung virtual display

[boxer01]

If you are updating from a previous version of VBox, then please see my comments about safe mode for installation in the ticket #21697.

[NathanV]

I am seeing the same thing in 7.0.14, sometimes the display freezes during the boot, always within a couple minutes. Dropping down to VGA is the only work-around I have found

[boxer01]

Is this issue still present in the current version?