Unable to use io_uring

[Unsocial4161]

Hello,

when I try to start an VM I get the following error:

swtpm_setup: Not overwriting existing state file.
kvm: -drive file=/var/lib/vz/template/iso/SERVER_EVAL_x64FRE_en-us.iso,if=none,id=drive-scsi0,media=cdrom,aio=io_uring: Unable to use io_uring: failed to init linux io_uring ring
stopping swtpm instance (pid 4305) due to QEMU startup error
TASK ERROR: start failed: QEMU exited with code 1

Can someone help me fix this?

 

[Folke]

Hey,
has something recently changed on your system, or is this a new installation?
Could you post the output of pveversion -v?

 

[Unsocial4161]

Sure, this is a new installation on new hardware

proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph-fuse: 17.2.7-pve2
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.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.1.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.4
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-3
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.2-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

 

[Folke]

Thanks!

Nothing suspicious here, could you check if the error message is complete, usually there should be a reason attached after failed to init linux io_uring ring.
Could you also look if there are any log messages in dmesg around the time that you tried to start the VM?

 

[Unsocial4161]

I only get this output:

root@proxmox:~# qm start 100
swtpm_setup: Not overwriting existing state file.
kvm: -drive file=/var/lib/vz/template/iso/virtio-win.iso,if=none,id=drive-ide0,media=cdrom,aio=io_uring: Unable to use io_uring: failed to init linux io_uring ring
stopping swtpm instance (pid 16378) due to QEMU startup error
start failed: QEMU exited with code 1

The dmesg output you can find here: https://privatebin.net/?95c0cb95f4e56a2b#3nu4KWAJLHt6t7jKVhPZDChTnmPtGcNhTUSxvfizvv39

 

[Folke]

Also, nothing that jumps out to be the issue :/
Could you post the config of the vm?

Meanwhile, you could run sudo debsums -a | grep FAILED (might need to install debsums) to check if there is any data corruption.

 

[Unsocial4161]

The config is:

agent: 1
bios: ovmf
boot: order=virtio0;ide0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
efidisk0: local-zfs:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide0: local:iso/virtio-win.iso,media=cdrom,size=612812K
ide2: local:iso/SERVER_EVAL_x64FRE_en-us.iso,media=cdrom,size=4925874K
machine: pc-q35-8.1
memory: 4096
meta: creation-qemu=8.1.2,ctime=1705919669
name: DC01
net0: virtio=BC:24:11:24:06:1D,bridge=vmbr0
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=d1c1b47e-c56f-4ad7-abc9-f4dd97dff265
sockets: 1
tpmstate0: local-zfs:vm-100-disk-1,size=4M,version=v2.0
virtio0: local-zfs:vm-100-disk-2,size=64G
vmgenid: efd13031-a5ad-4ff4-8705-713a34c6d4d0

And the output of debsums:

/etc/issue                                                                FAILED
/etc/fwupd/remotes.d/lvfs.conf                                            FAILED
/etc/initramfs-tools/initramfs.conf                                       FAILED
/etc/security/limits.conf                                                 FAILED
/etc/lvm/lvm.conf                                                         FAILED
/usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js                FAILED
/etc/apt/sources.list.d/pve-enterprise.list                               FAILED
/etc/kernel/postrm.d/zz-systemd-boot                                      FAILED
/etc/initramfs/post-update.d/systemd-boot                                 FAILED
/etc/kernel/postinst.d/zz-systemd-boot                                    FAILED
/etc/tuned/active_profile                                                 FAILED
/etc/modprobe.d/tuned.conf                                                FAILED
/etc/tuned/profile_mode                                                   FAILED

I suppose this shouldn't look like this. Is there a way to recover or do I have to reinstall?

 

[Folke]

The config is:

Unfortunately, I wasn't able to reproduce your error with this config, so it's probably a system specific issue.

I suppose this shouldn't look like this. Is there a way to recover or do I have to reinstall?

No reinstallation might not be needed, most of these are configuration files, it would make sense that some of those get changed over time.
But judging from the files that have changed, you already did a couple of modifications to your system. I'm especially unsure about tuned, since it messes with some core settings of linux, it could be possible that that clashes with kvm.

I would try to revert the changes you made to the base system (+ reboot) and see if you are able to start vm's again. If not, a reinstallation would be the next step.

 

[fiona]

Hi,
what is the output of sysctl -a | grep io_uring?

 

[Unsocial4161]

Hey,
I have reinstalled Proxmox on my system and have not made any modifications. So everything works fine for now.
The script I used for the previous installation was: https://github.com/TommyTran732/Linux-Setup-Scripts/blob/main/Proxmox-8.sh maybe you can look in to it and tell me what caused the issue? I think it cloud have been the "ia32_emulation=0" kernal flag.

 

[fiona]

Hey,
I have reinstalled Proxmox on my system and have not made any modifications. So everything works fine for now.
The script I used for the previous installation was: https://github.com/TommyTran732/Linux-Setup-Scripts/blob/main/Proxmox-8.sh maybe you can look in to it and tell me what caused the issue? I think it cloud have been the "ia32_emulation=0" kernal flag.

Hmm, I don't think that flag should affect io_uring setup. That said, the way to install Proxmox on top of Debian is documented here: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm

If you think it's a bug in that script, feel free to contact the author.