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

[Adam Seering <aseering@xxxxxxxxx>]

Hi,
	I'm having this same problem.  The relocation service is enabled on  
both machines; neither has a firewall (sure, I care about  
security...), and there is no firewall between them.
	For a live migration, do the dom0 kernels and the source/target PC's  
hardware have to be the same?  I'm migrating from a stock Debian Etch- 
based Xen AMD64 system on a Pentium D 8xx (no HVM) to a Fedora Core 6  
Xen AMD64 system on a Pentium D 9xx, with HVM support enabled.
Adam


On Dec 28, 2006, at 6:32 AM, Nico Kadel-Garcia wrote:

> Ian Pratt wrote:
> > > xm migrate --live vcs-dmz02 dmz03.ornl.gov
> > >
> > > Error: can't connect: No route to host
> > >
> > > Usage: xm migrate <Domain> <Host>
> >
> > Have you edited /etc/xen/xend-config.sxp on both hosts to enable the
> > relocation service?
> >
> > Best,
> > Ian
> Does it need to be on both hosts? And do there need to be image  
> files *already* in place on the target host in /var/lib/xen/ 
> images/? And what if you've been using LVM managed disk partitions  
> for your working Xen images?
> Unfortunately, I'm finding the documentation for Xen troublesomely  
> poor.
> _______________________________________________
> 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