[SOLVED] RHEL-based os stuck druing installation/boot

K

kmw

New Member
Jul 24, 2024
5
1
3
I'm using Proxmox 8.3.5 (kernel: 6.8.12-9-pve) with the no-subscription and pvetest repositories added. I received updates while pvetest was still enabled, and after discovering that QEMU 9.2 is available even with the no-subscription repository, I removed pvetest. After the update, I noticed that VMs running other OSes are working fine, but only RHEL-based OSes (CentOS, Rocky Linux) are freezing during installation and booting.

How can I resolve this issue? I believe the updated packages from pvetest might be causing the problem.

Bash: 
# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-9-pve)
pve-manager: 8.3.5 (running version: 8.3.5/dac3aa88bac3f300)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8: 6.8.12-9
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.12-8-pve: 6.8.12-8
proxmox-kernel-6.8.12-7-pve-signed: 6.8.12-7
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
amd64-microcode: 3.20240820.1~deb12u1
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.2.0
libpve-network-perl: 0.10.1
libpve-rs-perl: 0.9.2
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.4-1
proxmox-backup-file-restore: 3.3.4-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.7
pve-cluster: 8.0.10
pve-container: 5.2.4
pve-docs: 8.3.1
pve-edk2-firmware: 4.2025.02-1
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-3
pve-ha-manager: 4.0.6
pve-i18n: 3.4.0
pve-qemu-kvm: 9.2.0-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2

Bash: 
# uname -r
6.8.12-9-pve
 
Please show us VM configuration, also check that CPU model set for this VM is not kvm64/qkvm64. Minimal CPU to work with EL-8 distributions is x86-64-v2
 
momus said:
Please show us VM configuration, also check that CPU model set for this VM is not kvm64/qkvm64. Minimal CPU to work with EL-8 distributions is x86-64-v2
Click to expand...

The CPU type is host, and I'm using a 5600G CPU, so it doesn't seem to be a cpu issue
1742459262618.png
 
Hi,
please share the output of qm config 101. What ISOs are you using for installation? Does the installation work fine with the exact same configuration if you downgrade the QEMU package apt install pve-qemu-kvm=9.0.2-4?

The OVMF/EDK2 firmware package was also recently upgraded, so the issue might also be related to that.
 
fiona said:
Hi,
please share the output of qm config 101. What ISOs are you using for installation? Does the installation work fine with the exact same configuration if you downgrade the QEMU package apt install pve-qemu-kvm=9.0.2-4?

The OVMF/EDK2 firmware package was also recently upgraded, so the issue might also be related to that.
Click to expand...

i'm using Rocky Linux 9.5(iso: Rocky-9.5-x86_64-dvd.iso), and I assume that is likely the case
I'll test it now

Bash: 
# qm config 101
agent: 1
bios: ovmf
boot: order=scsi0
cores: 4
cpu: host
efidisk0: local-lvm:vm-101-disk-0,efitype=4m,size=4M
machine: q35
memory: 16384
meta: creation-qemu=9.0.2,ctime=1732180962
name: Rocky9.5
net0: virtio=BC:24:11:4A:A4:B5,bridge=vmbr0
numa: 0
ostype: l26
scsi0: local-lvm:vm-101-disk-1,iothread=1,size=128G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=9606b926-d995-4e75-866f-de5f9e96b8b0
sockets: 1
tags: minecraft
vga: virtio
vmgenid: 93388f3f-ab51-4dd8-9e2f-c08146476fb4


+ I tired it, but the stuck issue still occurs even after the installation

Bash: 
# pveversion -v | grep qemu
libproxmox-backup-qemu0: 1.5.1
pve-qemu-kvm: 9.0.2-4
qemu-server: 8.3.8
 
Last edited:
kmw said:
+ I tired it, but the stuck issue still occurs even after the installation

Bash: 
# pveversion -v | grep qemu
libproxmox-backup-qemu0: 1.5.1
pve-qemu-kvm: 9.0.2-4
qemu-server: 8.3.8
Click to expand...
What if you use the pre-enrolled-keys setting for the EFI disk?

What if you downgrade the OVMF firmware package: apt install pve-edk2-firmware=4.2023.08-4 pve-edk2-firmware-ovmf=4.2023.08-4 pve-edk2-firmware-legacy=4.2023.08-4 ?
 
  • Like
Reactions: Kingneutron
fiona said:
What if you downgrade the OVMF firmware package: apt install pve-edk2-firmware=4.2023.08-4 pve-edk2-firmware-ovmf=4.2023.08-4 pve-edk2-firmware-legacy=4.2023.08-4 ?
Click to expand...
The issue was resolved successfully after running the command, thanks for the help! :)
 
  • Like
Reactions: Kingneutron
You must log in or register to reply here.
Top Bottom