The AWK script about this checks strings: cx16 lahf popcnt sse4_1 sse4_2 ssse3
I don’t see popcnt on your output. The hypervisor should be configured to pass that capability to the VM (since the host most likely has it).
Since you have RL8, you should be able to run /lib64/ld-linux-x86-64.so.2 --help
Here is example, where host is x86-64-v4, but guest does not get even the x86-64-v2:
I managed to make it work by disabling the “Memory Integrity” option from Windows 11’s Core Isolation. Though I’m not very happy on disabling Windows protections to make this work when other VM’s I have don’t require me to turn off this option.
Prior to this, I also disabled Hyper-V completely as I’ve read online that it helped some people with similar issues but it didn’t work for me.
Is there anything I could do to make RL 9 work in Virtualbox without having to disable the Memory Integrity from Core Isolation ?
I would ask on the VirtualBox forums about this since it seems to be a VirtualBox problem. I would expect you wouldn’t have any issues if using VMware Workstation on Windows.
This can most likely happen as well for any other VM types no matter what the OS is, if Oracle don’t get their act together with VirtualBox. I would never personally use their products, but that’s my personal viewpoint.
I am getting the same issue with the latest iso: Rocky-9.0-20220805.0-x86_64-minimal
I am trying to create a VM on my Hypervisor - KVM host. (with AMD CPU).
Hey all!
Not sure if anyone else has solved this, but I have R9 running in Virtualbox 6.1.38. I noticed that under System/Processor, I had Enable PAE/NX and Netsted VT-x/AMD-V disabled - I vaguely recalling getting this error and this solved it. I had a kernel update come down today in R9 and shutdown the VM and then re-enabled these settings, and everything is working. (Also disabled EFI because I generally leave this off.)
I get the same issue on newest ProxMox VM with default settings in the new KVM-machine and Rocky 9 Minimal. Same settings I always use for different Ubuntu/Debian and other distros.
Edit: Had to change the VM CPU type to Host instead of KVM64. Then both workes. First time I have needed to do that ever…
I get the same kernel panic running Rocky 9 on the qemu-kvm hypervisor. Usually, my cluster manager (ganeti) omits the “-cpu” option when starting a VM instance. This results in:
# grep model /proc/cpuinfo
model : 13
model name : QEMU Virtual CPU version 1.5.3
However, if I supply a specific virtual cpu model that matches the underlying physical processor, like so…
/usr/libexec/qemu-kvm -cpu Westmere ...
…then, Rocky 9 boots normally. In this example, after changing cpu type, /proc/cpuinfo looks like this from inside the viraual host:
# grep model /proc/cpuinfo
model : 44
model name : Westmere E56xx/L56xx/X56xx (Nehalem-C)
This seems to be a manifestation of the new minimum requirement of “AMD and Intel 64-bit architectures (x86-64-v2)” as stated in the release notes.
It would be nice to have a specific list of Rocky 9-compatible processor models, or a way to derive such a list. Does anyone have that info?
@jmcnally can you not use the host option to pass it through by default? I usually always create my VM’s with virt-manager, so the option to copy the host CPU is enabled by default.
When I use:
qemu-kvm -cpu help
one of the options shown is:
x86 host
so I’m assuming you could then just do:
qemu-kvm -cpu host
and you’ll get what the underlying CPU on the server has. At least that is how I understand it.
Hi, in my post I mentioned virt-manager, which is the GUI app for KVM environment - you’ll see the references to KVM, so I know you aren’t running VirtualBox. I believe the qemu-kvm commands that I mentioned should help you in resolving the issue. If you pass the host parameter through via that particular parameter to the VM (-cpu host), then it’ll have the features you need to run Rocky 9 rather than you telling it to be a particular CPU type. I expect the Ganeti commands (not used it so can’t be sure) should give you similar ability to pass through the host CPU, irrespective of what CPU is underneath.
Maybe these links will help:
And this link:
shows lower down what ones are x86-64-v2 Nehalem and upwards
x86-64-v2 (basically an alias to nehalem with generic tuning)
And elsewhere:
With glibc 2.33 or later (Arch Linux, Debian 12, Ubuntu 21.04, Fedora 34, etc.), or patched glibc (RHEL 8), you can see what architecture is supported by your CPU by running: $ /lib/ld-linux-x86-64.so.2 --help
in my case I fixed the error increasing the number of processors. By default VirtualBox configure only one, increasing to two the kernel panic has disappeared.
Having the same issue. Rocky 8.7 loads just fine. But 9.1 keeps dumping with kernel panic.
Tried increasing CPU from 1 to 2, and then to 4, but still get Kernel panic dump.
Also tried bumping RAM - 1GB to 4GB.
Virtual Drive set to 50GB
Tried toggling the ‘Enable PAE/NX’ setting (defaulted to checked)
All with same result.
Using VirtualBox 6.1.38
On Win10, latest patches.
On a new ThinkPad L14 (Intel i7) 64GB RAM
In addition to removing Hyper-V (in “Turn Windows features on or off”), you may try to open cmd as administrator and run “bcdedit /set hypervisorlaunchtype off”, and reboot, before installing Rocky 9.
Thanks for that, but I think that’s already set. Anyway, I’m not going to worry about it now. Was just experimenting, I’ll go with v8 - just excited to see a proper replacement for CentOS.
Had the same problem. Windows 10, VirtualBox 6.1.38, attempted to boot rocky 9.1 iso. Kernel fault. Thanks to the info in this thread, checked cpu extensions, popcnt missing. Open cmd, cd C:\Program Files\Oracle\VirtualBox, run “VBoxManage setextradata VMName VBoxInternal/CPUM/IsaExts/POPCNT 1” and then tried again and that seemed to solve it. Replace VMName with whatever you named your vm.