Kernel panic booting Alma 9.2 and 9.3 on 9.3 VM with defaults
I'm trying to get a VM of Alma 9 running on a fully updated Alma 9 host. It's really simple: 1) I start virt-manager 2) Add machine, default settings, click "next... next..." * Local install media /home/AlmaLinux-9.3-x86_64-minimal.iso [X] Automatically detect from installation media/source * 1536 memory, 2 CPUs (default) * 20 GB storage (default) * Name: almalinux9 (default) 3) When it boots, I choose "Install AlmaLinux...." 4) Kernel panics! See attached screenshot result. What am I missing? Hopefully useful information to follow, screenshot attached. Host has 16 GB RAM and the following cpu. processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz stepping : 3 microcode : 0x28 cpu MHz : 3955.493 cache size : 8192 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_unknown bogomips : 7183.66 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management:
What CPU model are you using for the VM? AlmaLinux 9 requires x86_64v2 so you generally need to use host passthrough and not "kvm64" which is often the default. On Tue, Feb 13, 2024 at 12:34 PM Benjamin Smith <yesthatguy@gmail.com> wrote:
I'm trying to get a VM of Alma 9 running on a fully updated Alma 9 host. It's really simple:
1) I start virt-manager
2) Add machine, default settings, click "next... next..." * Local install media /home/AlmaLinux-9.3-x86_64-minimal.iso [X] Automatically detect from installation media/source * 1536 memory, 2 CPUs (default) * 20 GB storage (default) * Name: almalinux9 (default)
3) When it boots, I choose "Install AlmaLinux...."
4) Kernel panics! See attached screenshot result.
What am I missing? Hopefully useful information to follow, screenshot attached.
Host has 16 GB RAM and the following cpu.
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
stepping : 3
microcode : 0x28
cpu MHz : 3955.493
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_unknown
bogomips : 7183.66
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management: _______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
On 13/02/2024 20:30, Jonathan Wright wrote:
What CPU model are you using for the VM? AlmaLinux 9 requires x86_64v2 so you generally need to use host passthrough and not "kvm64" which is often the default.
On Tue, Feb 13, 2024 at 12:34 PM Benjamin Smith <yesthatguy@gmail.com> wrote:
I'm trying to get a VM of Alma 9 running on a fully updated Alma 9 host. It's really simple:
1) I start virt-manager
2) Add machine, default settings, click "next... next..." * Local install media /home/AlmaLinux-9.3-x86_64-minimal.iso [X] Automatically detect from installation media/source * 1536 memory, 2 CPUs (default) * 20 GB storage (default) * Name: almalinux9 (default)
3) When it boots, I choose "Install AlmaLinux...."
4) Kernel panics! See attached screenshot result.
What am I missing? Hopefully useful information to follow, screenshot attached.
Host has 16 GB RAM and the following cpu.
processor: 7
vendor_id: GenuineIntel
cpu family: 6
model: 60
model name: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
stepping: 3
microcode: 0x28
cpu MHz: 3955.493
cache size: 8192 KB
physical id: 0
siblings: 8
core id: 3
cpu cores: 4
apicid: 7
initial apicid: 7
fpu: yes
fpu_exception: yes
cpuid level: 13
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_unknown
bogomips: 7183.66
clflush size: 64
cache_alignment: 64
address sizes: 39 bits physical, 48 bits virtual
power management:
The physical CPU has AVX so it is x86-64-v2, actually it is a x86-64-v3 as it has AVX2, so I do not think that is the problem. Did you set the CPU type in virt-manager? If you are unsure use pass through as your physical CPU does have the features The screenshot is too small, as in there is relevant information missing, can you send the full screenshot including the part above that is missing, that might help us understand the problem
Hi Jonathan, Thanks for the info about x86_64v2. Picking this up after putting it down for a bit... (I'm getting married soon! =) In my case, neither of these worked. I have tried several CPU configurations (somewhat randomly) to no avail, including: * Copy host CPU configuration did not work * Hypervisor Default * Clear CPU configuration * host-model * host-passthrough * kvm64 * qemu64 * Opteron_G1 * Westmere I also tried copying over the cpu config XML from an Alma9 instance running on a xeon server "Broadwell-IBRS" and that didn't work either. This morning I poked around various Google searches and found this page referencing the X86_64v2 requirement of RHEL 9: https://www.reddit.com/r/linux/comments/uuojiv/rhel_9support_dropped_for_int... and searching that took me to: https://www.qemu.org/docs/master/system/i386/cpu.html which, when comparing to the list of CPU models shown in the virt-manager UI (which doesn't actually seem to exactly match the list of CPUs actually supported by the hypervisor!? Ugh!) I settled on "Nehalem" as a likely workable CPU type, which did, indeed, install and boot. (Wahoo! My QA environment can now be built!) Leaving this out there for future searches... On my system, AlmaLinux 9.3 under qemu works with the Nehalem processor in virt-manager on a 4th Gen i7 Host running AlmaLinux 9.3. On Tue, Feb 13, 2024 at 11:30 AM Jonathan Wright <jonathan@almalinux.org> wrote:
What CPU model are you using for the VM? AlmaLinux 9 requires x86_64v2 so you generally need to use host passthrough and not "kvm64" which is often the default.
On Tue, Feb 13, 2024 at 12:34 PM Benjamin Smith <yesthatguy@gmail.com> wrote:
I'm trying to get a VM of Alma 9 running on a fully updated Alma 9 host. It's really simple:
1) I start virt-manager
2) Add machine, default settings, click "next... next..." * Local install media /home/AlmaLinux-9.3-x86_64-minimal.iso [X] Automatically detect from installation media/source * 1536 memory, 2 CPUs (default) * 20 GB storage (default) * Name: almalinux9 (default)
3) When it boots, I choose "Install AlmaLinux...."
4) Kernel panics! See attached screenshot result.
What am I missing? Hopefully useful information to follow, screenshot attached.
Host has 16 GB RAM and the following cpu.
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
stepping : 3
microcode : 0x28
cpu MHz : 3955.493
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_unknown
bogomips : 7183.66
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management: _______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
Actually, it is an x86-64-v3 with AVX2, so I don't think that is the issue; the hardware CPU has AVX, therefore it is x86-64-v2. Have you used virt-manager to configure the CPU type? The characteristics are present in your physical CPU, so use pass through if you're not sure. Please provide us the complete screenshot, including the missing area above, so that we can better understand the problem. The current screenshot is too small and does not include all necessary information.
participants (4)
-
Benjamin Smith -
Jonathan Wright -
percynicholson9＠gmail.com -
Toshaan Bharvani | VanTosh