[SOLVED] QED: pve 3 ignores qed-disks, is it on purpose?

[yarick123]

Dear Proxmox team, thank you for amazing product!

I am experimenting now with QED disk format for qemu. This format cannot be specified in the pve GUI,
this is why I changed the virtual machine configuration file /etc/pve/qemu-server/101.conf this way:

virtio0: local:101/vm-101-disk-1.qed,format=qed,cache=writeback,size=30G

Pve GUI does not show, that this machine has that virtual disk at all:



If I start this machine in pve, it is started also without this disk:

ps waux | grep 101
root      915923  0.3  0.1 1776680 7728 ?        Sl   12:03   0:02 /usr/bin/kvm -id 101 -chardev socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait 
-mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -name vmotcs 
-smp sockets=1,cores=2 -cpu host -nodefaults -boot menu=on -vga cirrus -k en-us -m 1500 -cpu host -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 
-drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2 
-netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,vhost=on 
-device virtio-net-pci,romfile=,mac=00:0C:29:56:DA:FA,netdev=net0,bus=pci.0,addr=0x12,id=net0 -rtc driftfix=slew,base=localtime

But I can start the machine manually, and it works:

/usr/bin/kvm -id 101 -chardev socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait \
-mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/101.vnc,x509,password \
-pidfile /var/run/qemu-server/101.pid -daemonize -name vmotcs -smp sockets=1,cores=2 -cpu host -nodefaults \
-boot menu=on -vga cirrus -k en-us -m 1500 -cpu host -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 \
-drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2 \
-drive file=/var/lib/vz/images/101/vm-101-disk-1.qed,if=none,id=drive-virtio0,format=qed,cache=writeback,aio=native \
-device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 \
-netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,vhost=on \
-device virtio-net-pci,romfile=,mac=00:0C:29:56:DA:FA,netdev=net0,bus=pci.0,addr=0x12,id=net0 \
-rtc driftfix=slew,base=localtime

Could it be possible to allow pve to start virtual machines with disks in QED format?

---

Output of "pveversion -v" on the server is:

pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-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.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

Best
yarick123

 

[dietmar]

we do not support QED (AFAIK this is an experimental format, only used to improve qcow2).

 

[yarick123]

thank you for the quick answer, Dietmar!

You are right - I could not find any information about status of this format. For me it is not clear, if it is stable at all.

Best regards
yarick123