proxmox-ve 8.2.0 and ocfs2 - iso CD/DVD Drive problem

[PaulKo]

Hello all,

After upgrade ( pve-manager 8.1.11 > 8.2.2), there is a problem with mounting ISO files to a running VM, or it is impossible to start the VM if the ISO file is mounted.
The files are on the ocfs2 filesystem.

scsi0: Storage:105/vm-105-disk-1.qcow2,aio=native,cache=none,discard=on,iothread=1,size=80G,ssd=1

if you try to change the iso file:



VM does not start:

kvm: -drive file=/Storage/template/iso/virtio-win-0.1.248.iso,if=none,id=drive-ide2,media=cdrom,aio=io_uring: Could not read image for determining its format: Operation not supported
TASK ERROR: start failed: QEMU exited with code 1

I think the problem is related to the 'aio=io_uring'.
Manually editing the VM config ( 'aio=native,cache.direct=on' or 'aio=threads' ) allows you to start a VM with a mounted ISO:

proxmox-ve: 8.2.0 (running kernel: 6.8.4-2-pve)
pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.4-2
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5: 6.5.13-5
proxmox-kernel-6.5.13-4-pve-signed: 6.5.13-4
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.6
libpve-cluster-perl: 8.0.6
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.1
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.2.1
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.4.0-3
proxmox-backup-client: 3.2.2-1
proxmox-backup-file-restore: 3.2.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.6
pve-container: 5.0.11
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.0
pve-firewall: 5.0.5
pve-firmware: 3.11-1
pve-ha-manager: 4.0.4
pve-i18n: 3.2.2
pve-qemu-kvm: 8.1.5-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve2

 

[bbgeek17]

I'd recommend booting to an older Kernel and making sure that VM works without modification there. If it does, it would point toward a potential Kernel issue. If you are still experiencing an issue with the previous Kernel, then one of the userland package upgrades could be the culprit. I.e. something related to OCFS got pulled in as part of Debian 12.5 base.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[PaulKo]

Thanks for the tip! Indeed, there is no problem with the kernel 6.5.13-5-pve. Mounting the iso occurs without errors.

 

[bbgeek17]

Thanks for the tip! Indeed, there is no problem with the kernel 6.5.13-5-pve. Mounting the iso occurs without errors.

I guess your next step is to report it to the PVE Devs. They may see it here, but submitting to https://bugzilla.proxmox.com is a more reliable way.

You'd then want to decide whether 6.5+io_uring is preferable to 6.8+native in the short term.

Since OCFS is not an officially supported PVE storage configuration, it is probably not part of their normal QA. So, it's not surprising that something like this may have slipped in.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Deawon1]

Hello all,

After upgrade ( pve-manager 8.1.11 > 8.2.2), there is a problem with mounting ISO files to a running VM, or it is impossible to start the VM if the ISO file is mounted.
The files are on the ocfs2 filesystem.

scsi0: Storage:105/vm-105-disk-1.qcow2,aio=native,cache=none,discard=on,iothread=1,size=80G,ssd=1

View attachment 67077

if you try to change the iso file:

View attachment 67078

VM does not start:

kvm: -drive file=/Storage/template/iso/virtio-win-0.1.248.iso,if=none,id=drive-ide2,media=cdrom,aio=io_uring: Could not read image for determining its format: Operation not supported
TASK ERROR: start failed: QEMU exited with code 1

I think the problem is related to the 'aio=io_uring'.
Manually editing the VM config ( 'aio=native,cache.direct=on' or 'aio=threads' ) allows you to start a VM with a mounted ISO:

proxmox-ve: 8.2.0 (running kernel: 6.8.4-2-pve)
pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.4-2
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5: 6.5.13-5
proxmox-kernel-6.5.13-4-pve-signed: 6.5.13-4
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.6
libpve-cluster-perl: 8.0.6
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.1
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.2.1
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.4.0-3
proxmox-backup-client: 3.2.2-1
proxmox-backup-file-restore: 3.2.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.6
pve-container: 5.0.11
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.0
pve-firewall: 5.0.5
pve-firmware: 3.11-1
pve-ha-manager: 4.0.4
pve-i18n: 3.2.2
pve-qemu-kvm: 8.1.5-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve2

- Shutdown the VM
- Add "aio=threads" to your qm.conf
- Start the VM