[Xen-bugs] [Bug 328] New: Unable to access migrated domain

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=328

           Summary: Unable to access migrated domain
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dbarrera@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx,pl@xxxxxxxxxx


I migrated a domain from machine A to machine B. I see the domain in machine B
when I do an xm list:

lamb22:/tmp/xen-unstable.hg # xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       245    0      1  r-----    545.4
vm3                1       127    1      1  -b----      0.3

I am unable, however, to access the migrated domain:

lamb22:/tmp/xen-unstable.hg # xm console 1
xenconsole: xs_get_domain_path(): No such file or directory
lamb22:/tmp/xen-unstable.hg #

or,

lamb22:/tmp/xen-unstable.hg # xm console vm3
xenconsole: xs_get_domain_path(): No such file or directory
lamb22:/tmp/xen-unstable.hg #

I cannot either ssh or ping the guest domain:

lamb22:/tmp/xen-unstable.hg # ping vm3
PING vm3.ltc.austin.ibm.com (9.3.191.28) 56(84) bytes of data.

--- vm3.ltc.austin.ibm.com ping statistics ---
18 packets transmitted, 0 received, 100% packet loss, time 16999ms


So, I am unable to verify whether the migrated domain is viable.

The machine is SLES 9 SP2 based build, 512MB of RAM (enough mem to receive
migrated domain), non-PAE build. Previously, it was crashing on migration.

changeset:   7344:ffbee4415bf7
tag:         tip
user:        emellor@ewan
date:        Wed Oct 12 06:04:45 2005 +0100
summary:     Explicitly state which architectures are going to use /usr/lib64,
to allow for

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs