Status: io-error on first boot of any new VM

Code:
Jul 09 15:38:45 Proxmox pvedaemon[148408]: <root@pam> starting task UPID:Proxmox:00026343:0059F620:62C984E5:vncproxy:108:root@pam:
Jul 09 15:38:45 Proxmox pvedaemon[156483]: starting vnc proxy UPID:Proxmox:00026343:0059F620:62C984E5:vncproxy:108:root@pam:
Jul 09 15:37:24 Proxmox kernel: CIFS: VFS: \\172.16.0.11 Error -512 sending data on socket to server
Jul 09 15:32:38 Proxmox pvedaemon[148048]: <root@pam> successful auth for user 'root@pam'
Jul 09 15:32:28 Proxmox pveproxy[155438]: worker exit
 
Please share the configuration for the affected VMs (using qm config <ID>) and the output of pveversion -v.
 
qm config

Code:
root@Proxmox:~# qm config 103
bios: ovmf
boot: order=sata0;ide2
cores: 2
ide2: local:iso/linuxmint-19.1-xfce-64bit.iso,media=cdrom,size=1885696K
memory: 4096
meta: creation-qemu=6.2.0,ctime=1657730263
name: Test
net0: e1000=12:93:5B:45:92:C0,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: Backup_Monolith:103/vm-103-disk-0.qcow2,aio=native,size=32G
smbios1: uuid=2ff341a4-f614-4ede-bbf6-5e4836ce3e2e
sockets: 1
vmgenid: 105f2bf7-68fb-4522-9065-175873f39ac0

... and there is pveversion -v

Code:
root@Proxmox:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.39-1-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-6
pve-kernel-helper: 7.2-6
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-5
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.4.128-1-pve: 5.4.128-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-3
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1


I hope this will help you and thanks for the replies
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!