proxmox 2.3 issue

[mlmmilkyway]

hi,


After upgrading from 2.2 to 2.3 any image file on the glusterfs will not start. I move the image to /var/lib/vz/images and so far the Ubuntu images start. So far the windows images do not start.
Tried making a link from /var/lib/vz/images/ to local mounted disk but it will not start either.


qm start 108
kvm: -drive file=/var/lib/vz/images/108/vm-108-disk-1.qcow2,if=none,id=drive-ide0,aio=native,cache=none: could not open disk image /var/lib/vz/images/108/vm-108-disk-1.qcow2: Invalid argument
start failed: command '/usr/bin/kvm -id 108 -chardev 'socket,id=qmp,path=/var/run/qemu-server/108.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/108.vnc,x509,password -pidfile /var/run/qemu-server/108.pid -daemonize -name epscor-terra -smp 'sockets=1,cores=2' -nodefaults -boot 'menu=on' -vga std -no-hpet -k en-us -m 4096 -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'file=/var/lib/vz/template/iso/windows7-64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/108/vm-108-disk-1.qcow2,if=none,id=drive-ide0,aio=native,cache=none' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap108i0,script=/var/lib/qemu-server/pve-bridge' -device 'e1000,mac=5E4:B5:9F:6D:B7,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1


Should an image file located outside /var/lib/vz work? They did under 2.2?


Mark

 

[tom]

try other cache settings for your virtual hard disk, e.g. cache=writethrough

can you create new KVM guests, running on your glusterfs?

 

[mlmmilkyway]

try other cache settings for your virtual hard disk, e.g. cache=writethrough

can you create new KVM guests, running on your glusterfs?

hi,

Thank you, changing the cache to write through worked, the windows systems now start.
Creating new has always worked but any reboot of the proxmox server would cause this issue, images not in /var/lib/vz/images would not start.
The first time I just started over since none of the virtual systems were in use yet. This time I moved the smaller images to the local /var/lib/vz/images folder and those systems started. That is when I decided to seek help.

Mark