WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen-3.0.3 migration problems

To: Ryan Worsley <R.C.Worsley@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Xen-3.0.3 migration problems
From: "Ulrich Windl" <ulrich.windl@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 08 Jan 2007 13:27:22 +0100
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 08 Jan 2007 04:27:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4592D0FD.5070209@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Universitaet Regensburg, Klinikum
Priority: normal
References: <537C6C0940C6C143AA46A88946B8541705B38579@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 27 Dec 2006 at 20:01, Ryan Worsley wrote:

> I suggest you research what ports Xen migration occurs on, then check
> that these ports are not being blocked.

Typically "No route to host" does not relate to blocked ports. That would be
"Connection refused" typically... Just my 0.05$...

>
> Ryan.
>
>
>
> Bhatia, Nikhil wrote:
> >
> > 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-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users



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

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-users] Xen-3.0.3 migration problems, Ulrich Windl <=