I’ve been running RL9 under VirtualBox for a long time with no issues.
Thought I’d try spinning up an RL10 VM to check it out. Have tried three different ISOs (DVD, minimal, gnome) and all get a kernel panic when I try to boot. I’ve tried various VirtualBox settings to no avail.
Additionally, I get a message that i9-14900K is deprecated which is disturbing because it’s a pretty new processor (and it’s what I’m running).
I also tried spinning up my RL9 VM and running:
/lib64/ld-linux-x86-64.so.2 --help | grep x86-64
It reports:
This program interpreter self-identifies as: /lib64/ld-linux-x86-64.so.2
x86-64-v4
x86-64-v3
x86-64-v2 (supported, searched)
VirtualBox is now updated to the latest.
Hyper-V was already off.
I turned off Core Isolation (Memory Integrity). Kernel-mode stack protection was already off.
Rebooted the machine.
I tried changing some of the VBox settings (most notably enabled EFI). Got it to where it no longer kernel panics, but it halts with the message:
Fatal glibc error: CPU does not support x86-64-v3
If I turn EFI back off, a message about a TPM error flies by and then it kernel panics.
Your processor won’t be the problem, it’ll be your system settings somewhere. I have the generation before yours (13900KF). In fact, VirtualBox added the extensions needed for v3 to work in 7.1.0, so you shouldn’t be having trouble.
What I would do next is look through your VM’s vbox.log file and see if it mentions anything about VT-x or “fall back to NEM”. You can find these logs by right clicking your VM in and clicking “show in explorer”
00:00:02.433059 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
So I found to enable VT-x you do this:
VBoxManage modifyvm “RockyLinux 10” --nested-hw-virt on
After I did that, the checkbox to enable nested VT-x (under System/Processor) showed up, so I’m pretty sure I enabled it correctly.
But attempting to run the VM results in exactly the same as before. If EFI is disabled, I get a kernel panic. If EFI is enabled, I get Fatal glibc error: CPU does not support x86-64-v3
After running the above vboxmanage command, if I examine the log file it once again says:
00:00:02.439489 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
So I don’t understand why VT-x is not available but it shows up as active in the settings for the VM.
I don’t have nested virtualization on myself, so I don’t think that’s necessary. And your log doesn’t mention Hyper-V? Hyper-V is usually the fallback in these situations, but if it’s off and you’re still running into this issue, something else may be getting in the way… and I’m sure you also have virtualization turned on in your BIOS too, so that wouldn’t be it.
It’s likely I’m forgetting what you may need to turn off or on… but I found this for you. Apologies if you’ve found this before.
Maybe this can help you. I’m hitting a blank in my mind of what else you could potentially do (and my windows 11 install is a couple years old, so that doesn’t help matters with remembering how I’ve set it up…)
There are only two lines in the log that reference hyper-v:
00:00:02.476883 NEM: Disable Hyper-V if you need X2APIC for your guests!
00:00:02.476965 NEM: NEMR3Init: Snail execution mode is active!
00:00:02.476965 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode.
00:00:02.476965 NEM: To see VirtualBox run at max speed you need to disable all Windows features
00:00:02.476965 NEM: making use of Hyper-V. That is a moving target, so google how and carefully
00:00:02.476965 NEM: consider the consequences of disabling these features.
There’s also this:
00:00:02.476980 CPUM: No hardware-virtualization capability detected
00:00:02.476982 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x7
00:00:02.477596 CPUM: Warning! Can’t turn on nested VT-x/AMD-V when NEM is used! (later)
I read through the link you provided (again!), and I suspect I have some windows service running that is interfering.
I do have a green turtle in my status bar, so that’s some kind of clue.
while the hardware under VirtualBox is i9-14900K. The i9-14900K and i5-11400 do support x86-64-v3. The issue is not the hardware, but what the hypervisor allows the VM to use. In other words, the config of the VirtualBox (or of the Windows-VirtualBox combo).
There’s something to be followed up with about this.
lscpu | grep Virtual reports “full”
on a bare metal machine lscpu | grep Virtual reports:
VT-x
So somehow VirtualBox is not allowing VT-x through. In VirtualBox settings, under SystemProcessor, Enable Nested VT-V and AMD-V is checked.
I have tried both:
VboxManage modifyvm --nested-hw-virt on
and editing the .vbox file to manually add
NestedHWVirt enabled=“true”/ (with brackets around it)
