Heavy screen flickering VirtualBox 7.1.0 CentOS guest 5.14.0-505.el9.x86_64

[pravinlpatel]

I am running VirtualBox 7.1.0 CentOS guest 5.14.0-505.el9.x86_64 and facing Heavy screen flickering. Any guidance ?

[multiOS]

The probable cause of the problem is this:

00:00:06.465075 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:06.561496 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:06.561527 NEM: info: Found optional import vid.dll!VidGetHvPartitionId.
00:00:06.561542 NEM: info: Found optional import vid.dll!VidGetPartitionProperty.
00:00:06.561626 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
......
00:00:06.564557 NEM: NEMR3Init: Snail execution mode is active!
00:00:06.564557 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode.
00:00:06.564558 NEM: To see VirtualBox run at max speed you need to disable all Windows features
00:00:06.564558 NEM: making use of Hyper-V. That is a moving target, so google how and carefully
00:00:06.564558 NEM: consider the consequences of disabling these features.
00:00:06.564558 NEM:
00:00:06.564676 CPUM: No hardware-virtualization capability detected

See viewtopic.php?t=99390 for possible workarounds.

[pravinlpatel]

Issue still not resolved. Not sure what to do next

----Following is disabled from Windows Feature but issue still persist.

Containers
Hyper-V
Virtual Machine Platform
Windows Hypervisor Platform
Windows Sandbox
Windows subsystem for Linux
-- Disabled credential guard

-- Ran following

bcdedit /set hypervisorlaunchtype off

-- restart

[multiOS]

I will check through the new log to see if anything else jumps out.

Meanwhile, if the VM using Wayland, please try switching to an X11 session.

[multiOS]

Unfortunately the new log is still showing similar warnings about being unable to access to VT-x support directly:

00:00:24.353393 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:24.503751 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
00:00:24.595169 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:24.595239 NEM: info: Found optional import vid.dll!VidGetHvPartitionId.
00:00:24.595285 NEM: info: Found optional import vid.dll!VidGetPartitionProperty.
00:00:24.595532 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

00:00:24.601528 NEM: Adjusting APIC configuration from X2APIC to APIC max mode. X2APIC is not supported by the WinHvPlatform API!
00:00:24.601567 NEM: Disable Hyper-V if you need X2APIC for your guests!
00:00:24.601658 PGM: Enabling NEM mode
00:00:24.602287 NEM:
00:00:24.602288 NEM: NEMR3Init: Snail execution mode is active!
00:00:24.602289 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode.
00:00:24.602289 NEM: To see VirtualBox run at max speed you need to disable all Windows features
00:00:24.602290 NEM: making use of Hyper-V. That is a moving target, so google how and carefully
00:00:24.602290 NEM: consider the consequences of disabling these features.
00:00:24.602291 NEM:
00:00:24.602427 CPUM: No hardware-virtualization capability detected

The log uploaded is incomplete. If the VM was shut down when it was taken then it may have been truncated because it exceeded the upload size limit. Please try again with a 'zipped' log which might yield further information.

[Boxy]

viewtopic.php?t=99390

Some report this command was needed also:

DISM /Online /Disable-Feature:Microsoft-Hyper-V

[pravinlpatel]

Logs extracted when VM is running. Maybe Virtualbox can further developed to perform sanity check before installation to understand steps needs to be completed before installation.