kernel panic when creating VMs (centos 9 stream ISO)

[scottharwell]

Another circumstance where this can arise is when running CentOS Stream or RHEL 9 containers under a VM running in Proxmox. For instance, running a CentOS Stream 9 container on RHEL 8 or CentOS 8 (or any other RHEL 8 derivative) will generate the same error within the container itself. Changing the CPU for the host VM appears to fix those container issues as well.

 

[Robson Rissato]

Yes, exactly, I also did this test. thankful

 

[alebeta]

A better fix would be to apply the cpu args, so the kvm64 can have similar flags than the host cpu.

 

[ramblurr]

I'm encountering this issue with the latest 2022-04-19 centos stream 9 image as well (CentOS-Stream-GenericCloud-9-20220419.0.x86_64.qcow2).

passing `--cpu cputype=host` when creating the vm worked for me as well.

I'm also curious, what is he effect of choosing `host`? Are there drawbacks? What happens when the vm is migrated to a different host?

 

[alebeta]

Hi @ramblurr

the effects depend on what are you doing with proxmox and your configuration.

What I can tell you is: If you have a cluster and each node in the cluster have dfferent cpus, when live migrating, you can find some problems related with cpu.

Other than that I believe it is fine. But for sure other members of the forum can share more from their experience

 

[TheFlipside]

Red Hat changed the requirements for the release version 9 which therefore also effects all distributions which are derivatives from the RHEL source.

https://developers.redhat.com/blog/...-9-for-the-x86-64-v2-microarchitecture-level#

There are updates required for the KVM64 set to be able to support the x86-64-v2 instructions by default.

 

[markus-r]

I just tried with the newly released AlmaLinux 9. Same behavior.

 

[jterry]

Hello,

I've tried AlmaLinux 9.0 today and had this problem.

The Processor Type -> host workaround worked for me.

 

[Baulder]

I've tried OracleLinux 9 today and had this problem.

The Processor Type -> host workaround not working for me.

My CPU is Intel Xeon E5410. May be this CPU does not contains the x86-64-v2 instructions

 

[BAMBR]

Hello all, if add cpu with instruction on cpu-models.conf, all worked normal.
my example:
cpu-model: avx+sse
flags +fpu;+de;+pse;+tsc;+msr;+pae;+mce;+cx8;+apic;+sep;+mtrr;+pge;+mca;+cmov;+pat;+pse36;+clflush;+mmx;+fxsr;+sse;+sse2;+syscall;+nx;+pdpe1gb;+rdtscp;+lm;+pni;+pclmulqdq;+ssse3;+cx16;+sse4_1;+sse4_2;+movbe;+popcnt;+aes;+xs
ave;+rdrand;+lahf_lm;+abm;+fsgsbase;+bmi1;+smep;+bmi2;+adx;+smap;+clflushopt;+xsaveopt;+xgetbv1;+arat;+hypervisor;+avx
phys-bits host
hidden 0
hv-vendor-id proxmox
reported-model kvm64

 

[mount]

It worked for me on Proxmox VE 6.2

/etc/pve/virtual-guest/cpu-models.conf
cpu-model: rhel9
flags +ssse3;+sse4_1;+sse4_2;+popcnt
phys-bits host
hidden 0
hv-vendor-id proxmox
reported-model kvm64

# qm set 100 --cpu=custom-rhel9

 

[jameswang]

i've just tried that now too, it seems to work fine with the host CPU type, thanks for checking!


no idea, but it works with the CPU type set to host.

if you have similar issues in different hypervisors then it might be a bug on centos' end (would make sense to report it to them if that's the case)

FYI, I had same problem when tried to install Rocky 9 on PVE 7.2 (change CPU type to 'host' fixed it). I tried the same ISO on ESXi 5.5 and was able to install it.

 

[fabiobasso]

What does it mean when we choose the host option in CPU/Type?

 

[vuanhson]

What does it mean when we choose the host option in CPU/Type?

Directly pass instructions to host cpu instead via KVM

 

[axsa]

As would be expected, same results with Rocky Linux 9.0. Change of CPU to Host works.

 

[User_Zero]

Directly pass instructions to host cpu instead via KVM

Noob question, but is there a downside to doing this?

 

[Deepen Dhulla]

does not work if configured like this centos 9 stream
View attachment 34154


but that's how it works
View attachment 34155

I believe that the problem is in the default( kvm64) of the proxmox

Works after changing vCPU type for VM as 'host' (last option in CPU List)
Also there in https://bugzilla.redhat.com/show_bug.cgi?id=2060839

 

[scornelissen]

As suggested on bugzilla, the type 'max' does also work. This is still an Qemu emulated CPU and not a host passthrough CPU.

 

[mpatzwah]

same Problem with Rocky Linux 9 (min or DVD Iso)
Same Solution works (CPU: Host)
Kind regrads Marco

 

[n0bie]

same problem.. ubuntu 22, rocky 9..
any idea? yes we can switch to host..but in this case we need kvm64.. any idea?