[Xen-devel] Xen-3.0.3 migration problems

["Bhatia, Nikhil" <bhatia@xxxxxxxx>]

Hello Xen Users and Developers,

 

I am running 3 guest domains on a node. Following is the information:

 

[root@dmz02 fedora]# xm list

Name                                      ID Mem(MiB) VCPUs State   Time(s)

Domain-0                                   0      255     4 r-----     66.2

vcl-dmz02                                  1      256     1 -b----      1.1

vcn-dmz02                                  6      256     1 -b----      0.3

vcs-dmz02                                  7      256     1 -b----      0.3

 

I am trying to perform live migration using the command:

 

(dmz03.ornl.gov is also running Xen-3.0.3 and is running 3 guest domains of it’s own)

 

xm migrate --live vcs-dmz02 dmz03.ornl.gov

Error: can't connect: No route to host

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.

 

 

 

So, apparently dmz03.ornl.gov cannot be seen from dmz02.ornl.gov. However, when I run “ping”, I GET THE FOLLOWING OUTPUT:

 

[root@dmz02 fedora]# ping dmz03.ornl.gov

PING dmz03.ornl.gov (160.91.40.231) 56(84) bytes of data.

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=0 ttl=64 time=0.142 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=1 ttl=64 time=0.099 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=2 ttl=64 time=0.104 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=3 ttl=64 time=0.099 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=4 ttl=64 time=0.098 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=5 ttl=64 time=0.099 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=6 ttl=64 time=0.122 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=7 ttl=64 time=0.098 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=8 ttl=64 time=0.099 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=9 ttl=64 time=0.098 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=10 ttl=64 time=0.098 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=11 ttl=64 time=0.098 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=12 ttl=64 time=0.102 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=13 ttl=64 time=0.099 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=14 ttl=64 time=0.099 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=15 ttl=64 time=0.098 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=16 ttl=64 time=0.097 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=17 ttl=64 time=0.098 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=18 ttl=64 time=0.098 ms

64 bytes from dmz03.ornl.gov (160.91.40.231): icmp_seq=19 ttl=64 time=0.097 ms

 

Can someone please suggest what the problem might be?

 

 

Thanks,

Nikhil

 

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