virtio2: hotplug problem - adding drive failed: Invalid parameter 'detect-zeroes'

clgies

Active Member
Oct 18, 2018
11
0
41
55
Hi folks,

adding a new virtual hard drive to an existing VM


Bildschirmfoto 2020-06-19 um 13.14.58.png

fails in the Proxmox backend with error message

Parameter verification failed. (400)
virtio2: hotplug problem - adding drive failed: Invalid parameter 'detect-zeroes'

Bildschirmfoto 2020-06-19 um 12.51.11.png

Any idea how to fix this error? Any help is welcome :)

Thank you very much.

Best regards,
Claus

Report:

qm config 233
bootdisk: virtio0
cores: 4
description: ext%3A 89.146.239.233%0Aint%3A 192.168.58.233%0A
ide2: none,media=cdrom
keyboard: en-us
memory: 8192
name: web01
net0: virtio=52:28:4B:A0:5E:F3,bridge=vmbr0
onboot: 1
ostype: l26
sockets: 1
virtio0: local-ssd:233/vm-233-disk-1.qcow2,format=qcow2,size=10G
virtio1: local-ssd:233/vm-233-disk-2.qcow2,format=qcow2,size=25G


lsblk (on vm)
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 10G 0 disk
├─vda1 254:1 0 9.6G 0 part /
├─vda2 254:2 0 1K 0 part
└─vda5 254:5 0 466M 0 part [SWAP]
vdb 254:16 0 25G 0 disk
└─vdb1 254:17 0 25G 0 part /.........
sr0 11:0 1 1024M 0 rom



pvesm status
local dir 1 132908400 46467864 86440536 35.46%
local-ssd dir 1 242549120 134780776 95447576 59.04%
 
Which version of PVE are you running? (i.e. please post the output of 'pveversion -v')
 
Hi Stefan,

the output:

proxmox-ve-2.6.32: 3.4-185 (running kernel: 2.6.32-20-pve)
pve-manager: 3.4-16 (running version: 3.4-16/40ccc11c)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-44-pve: 2.6.32-173
pve-kernel-2.6.32-48-pve: 2.6.32-185
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-43-pve: 2.6.32-166
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-20
qemu-server: 3.4-9
pve-firmware: 1.1-6
libpve-common-perl: 3.0-27
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-35
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-28
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
As I thought from your screenshot, you're using a *very* outdated version of PVE. Please update your node to the newest version, we do not provide support for PVE 2/3 anymore.