storage migration virtio failed

[nz_monkey]

I will collect some more info on this. And see if I can come up with an easy way to replicate the problem.

Most of our guests are Windows, but we have had this happen on Linux guests too.
Disks being transferred are in size from 80GB to 10TB.
PVE version is now 3.3 with qemu 2.1.2

 

[mir]

Points 1 & 2 are reasonable where they apply. Points 3 & 4 are, IMO, not. Likewise, risk of storage corruption is also not reasonable. Those are all things that need to be addressed on the software side rather than blaming the user for using too much space or I/O. The average size of disk images is growing pretty fast; we've created our first 1TB+ images recently. That's only going to get more common, and likewise disk I/O's are going up not down.

Please note that I was not blaming anybody I was merely listing issues which I have personally experienced affected the success of live storage migration.

 

[jdw]

Please note that I was not blaming anybody I was merely listing issues which I have personally experienced affected the success of live storage migration.

Sure, sorry if I offended. It's sufficient to say that certain causes of migration failure can & should be addressed by the software, and others (like inferior hardware) really cannot.

 

[spirit]

PVE version is now 3.3 with qemu 2.1.2

Do you have stop/start the vm after proxmox upgrade to 3.3?
because vm don't get new qemu version until the kvm process is restarted.

That's why I have asked to do "info version" in qemu monitor to be sure.

 

[mir]

It looks like 2.1.2 also has made some god things for backup. At least I see increased speed of backup here.

 

[spirit]

Hi,

we have made some bugfix for disk move

can you test:

http://download1.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/qemu-server_3.3-2_amd64.deb

?