Hello, I'm suffering a problem with windows server 2022 on proxmox VE, no hyperV installed.
The machine was recently updated from WS2008R2, and we had 0 problems before.
The machine only hangs for a while while doing lots of iops, always when using windows disk optimizer. maybe syncing with google drive for the first time. Maybe in 10-15 minutes comes back, it depends on the load. No IO delay on the hypervisor, maximum was 3.15% this week.
It looses connectivity, qemu tools drop comunication, the machine display on the hypervisor doesn't work, but it's working by itselft after a while it recovers conectivity and it doesn't restart.
It has two disks, one conected to a ZFS NVME RAID1 for the OS, and another to an LVM RAID1 for DATA.
Moved the data disk to another pool, made no differece.
Tried the disks with native and io_uring Async IO, made no difference.
Reduced read/write limits and op/s on disks, made no difference.
Tried with several proxmox kernel 5.13 and 5.15, made no difference.
Tried change cpu type to KVM, made no difference
Syslog only throws this related to the VM:
pvedaemon[2320607]: VM 105 qmp command failed - VM 105 qmp command 'guest-network-get-interfaces' failed - got timeout
The machine was recently updated from WS2008R2, and we had 0 problems before.
The machine only hangs for a while while doing lots of iops, always when using windows disk optimizer. maybe syncing with google drive for the first time. Maybe in 10-15 minutes comes back, it depends on the load. No IO delay on the hypervisor, maximum was 3.15% this week.
It looses connectivity, qemu tools drop comunication, the machine display on the hypervisor doesn't work, but it's working by itselft after a while it recovers conectivity and it doesn't restart.
It has two disks, one conected to a ZFS NVME RAID1 for the OS, and another to an LVM RAID1 for DATA.
Moved the data disk to another pool, made no differece.
Tried the disks with native and io_uring Async IO, made no difference.
Reduced read/write limits and op/s on disks, made no difference.
Tried with several proxmox kernel 5.13 and 5.15, made no difference.
Tried change cpu type to KVM, made no difference
¿KB5015446 installed on 27/01/2022, could this be the problem?
proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve) pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4) pve-kernel-helper: 7.3-3 pve-kernel-5.15: 7.3-1 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.83-1-pve: 5.15.83-1 pve-kernel-5.15.74-1-pve: 5.15.74-1 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-2-pve: 5.13.19-4 ceph-fuse: 16.2.9-pve1 corosync: 3.1.7-pve1 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown: not correctly installed ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve2 libproxmox-acme-perl: 1.4.3 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.3-1 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.3-2 libpve-guest-common-perl: 4.2-3 libpve-http-server-perl: 4.1-5 libpve-storage-perl: 7.3-2 libqb0: 1.0.5-1 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.2-1 lxcfs: 5.0.3-pve1 novnc-pve: 1.3.0-3 openvswitch-switch: 2.15.0+ds1-2+deb11u2 proxmox-backup-client: 2.3.2-1 proxmox-backup-file-restore: 2.3.2-1 proxmox-mini-journalreader: 1.3-1 proxmox-offline-mirror-helper: 0.5.0-1 proxmox-widget-toolkit: 3.5.3 pve-cluster: 7.3-2 pve-container: 4.4-2 pve-docs: 7.3-1 pve-edk2-firmware: 3.20220526-1 pve-firewall: 4.2-7 pve-firmware: 3.6-3 pve-ha-manager: 3.5.1 pve-i18n: 2.8-2 pve-qemu-kvm: 7.1.0-4 pve-xtermjs: 4.16.0-1 qemu-server: 7.3-3 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.8.0~bpo11+2 vncterm: 1.7-1 zfsutils-linux: 2.1.9-pve1
agent: 1,fstrim_cloned_disks=1
balloon: 0
bios: ovmf
boot: c
bootdisk: scsi0
cores: 8
cpu: host
efidisk0: NVME_WDS500GB:vm-105-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: none,media=cdrom
machine: pc-q35-7.1
memory: 16384
name: WS2022
net0: virtio=52:54:00:bc:bd:80,bridge=vmbr0,tag=10
net1: virtio=52:54:00:2e:90:8e,bridge=vmbr1
net2: virtio=0E:37:E5:E2:CB:04,bridge=vmbr5
net3: virtio=26:F4:01:76:74:4B,bridge=vmbr4
numa: 0
onboot: 1
ostype: win11
parent: autoweekly230205030006
protection: 1
scsi0: NVME_KINGSTON1TB:vm-105-disk-0,backup=0,discard=on,iops_rd=1000,iops_rd_max=1500,iops_wr=1000,iops_wr_max=1500,iothread=1,mbps_rd=250,mbps_rd_max=350,mbps_wr=250,mbps_wr_max=350,size=114695M,ssd=1
scsi1: RAID1VD1:vm-105-disk-0,backup=0,discard=on,iops_rd=500,iops_rd_max=1000,iops_wr=500,iops_wr_max=1000,iothread=1,mbps_rd=100,mbps_rd_max=150,mbps_wr=100,mbps_wr_max=150,size=1T
scsi2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=10311389-3929-4670-bc8e-d044149eda7e
sockets: 1
startup: order=6,up=30
tpmstate0: NVME_KINGSTON1TB:vm-105-disk-1,size=4M,version=v2.0
vga: qxl,memory=128
balloon: 0
bios: ovmf
boot: c
bootdisk: scsi0
cores: 8
cpu: host
efidisk0: NVME_WDS500GB:vm-105-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: none,media=cdrom
machine: pc-q35-7.1
memory: 16384
name: WS2022
net0: virtio=52:54:00:bc:bd:80,bridge=vmbr0,tag=10
net1: virtio=52:54:00:2e:90:8e,bridge=vmbr1
net2: virtio=0E:37:E5:E2:CB:04,bridge=vmbr5
net3: virtio=26:F4:01:76:74:4B,bridge=vmbr4
numa: 0
onboot: 1
ostype: win11
parent: autoweekly230205030006
protection: 1
scsi0: NVME_KINGSTON1TB:vm-105-disk-0,backup=0,discard=on,iops_rd=1000,iops_rd_max=1500,iops_wr=1000,iops_wr_max=1500,iothread=1,mbps_rd=250,mbps_rd_max=350,mbps_wr=250,mbps_wr_max=350,size=114695M,ssd=1
scsi1: RAID1VD1:vm-105-disk-0,backup=0,discard=on,iops_rd=500,iops_rd_max=1000,iops_wr=500,iops_wr_max=1000,iothread=1,mbps_rd=100,mbps_rd_max=150,mbps_wr=100,mbps_wr_max=150,size=1T
scsi2: local:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=10311389-3929-4670-bc8e-d044149eda7e
sockets: 1
startup: order=6,up=30
tpmstate0: NVME_KINGSTON1TB:vm-105-disk-1,size=4M,version=v2.0
vga: qxl,memory=128
Syslog only throws this related to the VM:
pvedaemon[2320607]: VM 105 qmp command failed - VM 105 qmp command 'guest-network-get-interfaces' failed - got timeout
Last edited: