Bug 578452 - PV Guest crashed when migration failed
Summary: PV Guest crashed when migration failed
Keywords:
Status: CLOSED DUPLICATE of bug 513335
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-31 11:26 UTC by Yufang Zhang
Modified: 2010-04-01 11:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-01 11:57:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
xend.log from source host (15.40 KB, text/x-log)
2010-03-31 11:26 UTC, Yufang Zhang
no flags Details
xend.log from dst host (5.06 KB, text/plain)
2010-03-31 11:31 UTC, Yufang Zhang
no flags Details

Description Yufang Zhang 2010-03-31 11:26:45 UTC
Created attachment 403709 [details]
xend.log from source host

Description of problem:
Migrating a VM to a remote host will make the guest crash, if another guest with the same name exists on the remote host.

Version-Release number of selected component (if applicable):
xen-3.0.3-105.el5
kernel-xen-2.6.18-194.el5

How reproducible:
Always

Steps to Reproduce:
1. Prepare two hosts with shared storage
2. Start a VM named 'vm' in the destination host
3. Start another VM which is also named as 'vm', try to migrate the VM to the destination host:
# xm li
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0     1833     4 r-----  16876.5
test2                                     28     1023     1 -b----    553.7
vm                                       125      511     4 -b----      7.8

# xm migrate vm -l 10.66.70.157
Error: /usr/lib64/xen/bin/xc_save 24 125 0 0 1 failed
Usage: xm migrate <Domain> <Host>

Migrate a domain to another machine.

Options:

-h, --help           Print this help.
-l, --live           Use live migration.
-p=portnum, --port=portnum
                     Use specified port for migration.
-r=MBIT, --resource=MBIT
                     Set level of resource usage for migration.

# xm li
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0     1833     4 r-----  16886.0
test2                                     28     1023     1 -b----    553.8
vm                                       126      512     1 ----c-      0.4

  
Actual results:
The VM crashed when migration failed.


Expected results:
VM should not crash even migration failed.

Additional info:

Comment 1 Yufang Zhang 2010-03-31 11:31:07 UTC
Created attachment 403711 [details]
xend.log from dst host


Note You need to log in before you can comment on or make changes to this bug.