Bug 700701

Summary: Migration progress stuck with qcow2 image ENOSPAC during installation
Product: Red Hat Enterprise Linux 5 Reporter: Min Deng <mdeng>
Component: kvmAssignee: Juan Quintela <quintela>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 5.7CC: bcao, gcosta, juzhang, kwolf, michen, mkenneth, owasserm, quintela, rhod, syeghiay, tburke, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 682653 Environment:
Last Closed: 2011-11-02 09:51:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 682653    
Bug Blocks: 580946, 580948, 580949    
Attachments:
Description Flags
It is convenient for developer to catch the migration time. none

Comment 1 Min Deng 2011-04-29 10:19:21 UTC 
Please ignore the 'Notes' in above comments and already tried the issue with following kernel&kvm on AMD host again.
-------------------------------------------------------------
kernel&kvm version
2.6.18-256.el5&kvm-83-231.el5
-------------------------------------------------------------
Additional,
1.Use iscsi and had better have the source and destination connect to a third-party server
2.create a lvm about 156M and begin migration at a time (please see attachment)
-log info
From source host-
/usr/libexec/qemu-kvm -rtc-td-hack -usbdevice tablet -no-hpet -drive file=/dev/migrate/deng1,if=virtio,boot=on,werror=stop,cache=none,format=qcow2,media=disk -cpu qemu64,+sse2 -smp 4 -m 4G -net nic,macaddr=00:12:24:57:a8:2e,model=virtio,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -uuid `uuidgen` -vnc :2 -boot dc -balloon none -monitor stdio -drive file=/opt/RHEL5.6-Server-20110106.0-x86_64-DVD.iso,if=ide,werror=stop,cache=none,format=raw,media=cdrom -notify all
QEMU 0.9.1 monitor - type 'help' for more information
(qemu) 
(qemu) 
(qemu) 
(qemu) migrate -d tcp:10.66.9.101:1234
# VM is stopped due to disk write error: virtio0: Invalid argument

(qemu) migration_notify_done
info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
(qemu) info migrate
Migration status: active
transferred ram: 162 kbytes
remaining ram: 4213732 kbytes
total ram: 4214796 kbytes
Comment 2 Min Deng 2011-04-29 10:23:29 UTC 
Created attachment 495748 [details]
It is convenient for developer to catch the migration time.
Comment 3 Glauber Costa 2011-05-16 19:48:57 UTC 
*** Bug 700706 has been marked as a duplicate of this bug. ***
Comment 4 Dor Laor 2011-08-07 09:47:30 UTC 
*** Bug 700706 has been marked as a duplicate of this bug. ***
Comment 5 Dor Laor 2011-08-07 09:48:09 UTC 
*** Bug 704441 has been marked as a duplicate of this bug. ***
Comment 6 Ronen Hod 2011-10-31 10:12:54 UTC 
Min,
We did not fix it for 5.8, but now that I read it again. Line #5 in your description says that it does not exist in 5.7. If it is true, then we should have closed it already.
Comment 7 Ronen Hod 2011-11-02 09:51:12 UTC 
Well, looking at its duplicates, it seems to be relevant to 5.7 too.
Anyhow, we decided to close it for the following reasons:
1. Since we didn't make it for 5.8 dev-freeze and it doesn't look like a trivial fix, we gave up on 5.8.
2. Since there is no data corruption, we decided not to drag it further to 5.9