<tt> > I'm facing a weird situation, trying to migrate from one storage > pool (on VLET1, SWRAID1,SATA) to another (on VLET3, HWRAID1,SAS) > (all servers VLET1,2,3 on ubuntu 10.10) </tt> <tt>->each server has /srv/VMs exported as nfs-pool, nfs-pool2 and nfs-pool3 respectively</tt> <tt> > </tt> <tt>I run the VM ISPConfigLET2 on VLET1, and live migrate it to VLET3 (like this, I get the host properly defined on VLET3). The disk image, shared with NFS, resides physically on VLET1.</tt> <tt> > 1. I stop all running VM instances > 2. On VLET3, I have an NFS share of VLET1 mounted > 3. On VLET3, I issue: cp /mnt/nfs/ISPConfigLET2.qcow2 /srv/VMs/ > 4. On VLET3 and VLET1, I virsh edit ISPConfigLET2 to use the newly created copied /srv/VMs/ISPConfigLET2.qcow2 residing on pool nfs-pool3 </tt> <tt>->see XML further down</tt> <tt>> </tt> <tt>The VM refuses to run with the different storage pool selected: the VM starts on VLET1 (using the image served over nfs from VLET3), but a boot error comes up</tt> <tt>> -> it gets mounted read-only apparently; it doesn't work. </tt> <tt>dmesg:</tt> <tt>... (many times same error message)</tt> <tt>[ 20.967377] ata1.00: status: { DRDY ERR }</tt> <tt>[ 20.967379] ata1.00: error: { ABRT }</tt> <tt>[ 20.971640] ata1.00: configured for PIO0</tt> <tt>[ 20.971648] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE</tt> <tt>[ 20.971651] sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]</tt> <tt>[ 20.971654] Descriptor sense data with sense descriptors (in hex):</tt> <tt>[ 20.971656] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00</tt> <tt>[ 20.971661] 02 77 97 3f</tt> <tt>[ 20.971663] sd 0:0:0:0: [sda] Add. Sense: No additional sense information</tt> <tt>[ 20.971666] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 02 77 97 3f 00 00 08 00</tt> <tt>[ 20.971672] end_request: I/O error, dev sda, sector 41391935</tt> <tt>[ 20.971684] ata1: EH complete</tt> <tt>[ 20.971744] JBD: Detected IO errors while flushing file data on sda1</tt> <tt>[ 20.971761] __journal_remove_journal_head: freeing b_committed_data</tt> <tt>[ 20.971769] __journal_remove_journal_head: freeing b_committed_data</tt> <tt>[ 20.971777] __journal_remove_journal_head: freeing b_committed_data</tt> <tt>[ 20.971798] __journal_remove_journal_head: freeing b_committed_data</tt> <tt>[ 20.971801] __journal_remove_journal_head: freeing b_committed_data</tt> <tt>[ 20.971845] journal commit I/O error</tt> <tt>> When > using rsync or scp instead of cp, there's no difference... I really don't > understand what's going on... Who has a clue please?? </tt> <tt>When trying to start the VM on VLET3, the VM hangs immediately at boot, with following messags in /var/log/messages:</tt> <tt>Mar 14 21:21:30 VLET3 kernel: [255777.604342] type=1400 audit(1300134090.205:39): apparmor="STATUS" operation="profile_load" name="libvirt-02f97acb-d586-4eb9-9f59-e1df7a3cd647" pid=29124 comm="apparmor_parser"</tt> <tt>Mar 14 21:21:30 VLET3 libvirtd: 21:21:30.803: warning : qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed</tt> <tt>Mar 14 21:21:30 VLET3 kernel: [255778.193514] device vnet0 entered promiscuous mode</tt> <tt>Mar 14 21:21:30 VLET3 kernel: [255778.193540] br0: new device vnet0 does not support netpoll (disabling)</tt> <tt>Mar 14 21:21:30 VLET3 kernel: [255778.195370] br0: port 2(vnet0) entering learning state</tt> <tt>Mar 14 21:21:30 VLET3 kernel: [255778.195374] br0: port 2(vnet0) entering learning state</tt> <tt>Mar 14 21:21:45 VLET3 kernel: [255793.206140] br0: port 2(vnet0) entering forwarding state</tt> <tt>> Did the host version change, I had a problem on an older system > where the disk was type raw even though it was qcow2, on a newer > lucid host system I had to change it to explicitly state qcow2 then > it was fine?</tt> <tt>> > -- > Dave </tt> <tt>->It is mentioned correctly in the host's XML:</tt> <tt><domain type='kvm'></tt> <tt> <name>ISPConfigLET2</name></tt> <tt> <uuid>101682a8-5969-4ac0-b7dd-53fddd207365</uuid></tt> <tt> <memory>524288</memory></tt> <tt> <currentMemory>524288</currentMemory></tt> <tt> <vcpu>1</vcpu></tt> <tt> <os></tt> <tt> <type arch='i686' machine='pc-0.12'>hvm</type></tt> <tt> <boot dev='hd'/></tt> <tt> </os></tt> <tt> <features></tt> <tt> <acpi/></tt> <tt> </features></tt> <tt> <clock offset='utc'/></tt> <tt> <on_poweroff>destroy</on_poweroff></tt> <tt> <on_reboot>restart</on_reboot></tt> <tt> <on_crash>destroy</on_crash></tt> <tt> <devices></tt> <tt> <emulator>/usr/bin/kvm</emulator></tt> <tt> <disk type='file' device='disk'></tt> <tt> <driver name='qemu' type='qcow2'/></tt> <tt> <source file='/var/lib/libvirt/images/nfs-pool3/ispconfig2.qcow2'/></tt> <tt> <target dev='hda' bus='ide'/></tt> <tt> <address type='drive' controller='0' bus='0' unit='0'/></tt> <tt> </disk></tt> <tt> <controller type='ide' index='0'></tt> <tt> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/></tt> <tt> </controller></tt> <tt> <interface type='bridge'></tt> <tt> <mac address='00:0c:29:9a:6b:a4'/></tt> <tt> <source bridge='br0'/></tt> <tt> <target dev='vnet0'/></tt> <tt> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/></tt> <tt> </interface></tt> <tt> <input type='mouse' bus='ps2'/></tt> <tt> <graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1'/></tt> <tt> <video></tt> <tt> <model type='cirrus' vram='9216' heads='1'/></tt> <tt> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/></tt> <tt> </video></tt> <tt> <memballoon model='virtio'></tt> <tt> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/></tt> <tt> </memballoon></tt> <tt> </devices></tt> <tt></domain></tt> <tt>"Serge E. Hallyn" <serge.hallyn@ubuntu.com> wrote on 14/03/2011 14:27:04: > From: "Serge E. Hallyn" <serge.hallyn@ubuntu.com></tt> <tt>> To: jurgen.depicker@let.be</tt> <tt>> Cc: ubuntu-server@lists.ubuntu.com</tt> <tt>> Date: 14/03/2011 14:27</tt> <tt>> Subject: Re: troubles copying qcow2 VM images</tt> <tt>> > Quoting jurgen.depicker@let.be (jurgen.depicker@let.be): > > Dear all, > > > > I'm facing a weird situation, trying to migrate from one storage pool (on > > VLET1, SWRAID1,SATA) to another (on VLET3, HWRAID1,SAS) > > (all servers VLET1,2,3 on ubuntu 10.10) > > > > 1. I stop all running VM instances > > 2. On VLET3, I have an NFS share of VLET1 mounted > > 3. On VLET3, I issue: cp /mnt/nfs/VM1.qcow2 /srv/VMs/ > > 4. I reconfigure VM1 to use the newly created copied /srv/VMs/VM1.qcow2 > > > > -> it gets mounted read-only apparently; it doesn't work. When using > > rsync instead of cp, there's no difference... I really don't understand > > what's going on... Who has a clue please?? > > Can you sha1sum {/mnt/nfs,/srv/VMs/}/VM1.qcow2? My guess is this is an > NFS bug with large file xfer corruption. > > -serge </tt> <tt>Great, I didn't think of that one before! I thought that was it, but, unfortunately, I ran sha1sum on VLET1 and VLET3's copies, and both give the same checksum.</tt> <tt>I really really don't understand this... Is there some 'magic' associated with qcow2 images, so you need to copy them in a special way? But since the sha1sums are identical...</tt> <tt>The funny thing is, most of these images were VMWare images which I converted. They were first stored on other systems, and I could copy the qcow2 images to VLET1 and they all worked fine. But now it seems impossible to move them... Kind regards, </tt> <tt> J�rgen </tt>