Bug 750482

Summary: VM status change to down when migrating
Product: Red Hat Enterprise Linux 6 Reporter: cshao <cshao>
Component: qemu-kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: abaron, acathrow, apevec, bazulay, bsarathy, gouyang, iheim, juzhang, leiwang, mburns, michen, mkenneth, mkhusid, moli, tburke, virt-maint, ycui, ykaul
Target Milestone: rc   
Target Release: 6.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-02 07:59:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
vdsm.log+rhevm.log none

Description cshao 2011-11-01 09:51:40 UTC 
Description of problem:
VM status change to down when migrating.
RHEV-M event: Migration of VM migrate failed. Error: Lost connection with qemu process.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.2-20111026.2.el6
vdsm-4.9-110.el6.x86_64
rhevm-3.0.0_0001-50.el6.x86_64
qemu-kvm-0.12.1.2-2.204.el6.x86_64
libvirt-0.9.4-20.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H in two same model machines.
2. Register RHEV-H to RHEV-M, approve RHEV-H in same cluster.
3. Create new NFS domain and create VM.
4. VM status is "up".
5. Migrate VM.
6. VM status change to "migrating from".
7. VM status change to "down".
  
Actual results:
VM status change to down when migrating, VM can up successful by click run button.

Expected results:
VM live migration can successful.

Additional info:
Comment 2 cshao 2011-11-01 09:55:21 UTC 
Created attachment 531094 [details]
vdsm.log+rhevm.log
Comment 3 Ying Cui 2011-11-01 10:12:09 UTC 
RHEV-M build is IC146
Comment 8 Dor Laor 2011-11-02 07:59:04 UTC 

*** This bug has been marked as a duplicate of bug 749806 ***