|  |  | 
  
    |  |  | 
 
  |   |  | 
  
    |  |  | 
  
    |  |  | 
  
    |   xen-users
[Xen-users] Re: Problem in migration (xen-unstable) 
| Hello xen-users  , xenybody here?
On 11/10/05, Mark Ryden <markryde@xxxxxxxxx> wrote:
> Hello,
>
> I am trying to migrate domainU from machine A to machine B.
> On both machines there is xen-unstable from this week.
>
> The migration fails, and this is the error I get:
> Error: can't connect: Connection refused
>
> More details:
> I am trying to migrate a domain from machine A to machine B.
>
> On machine A , on which I issue the "xm migrate" command,
> xm list shows:
>
> Name                              ID Mem(MiB) VCPUs State  Time(s)
> Domain-0                           0       58     1 r-----   137.1
> katz                               3       19     1 -b----    65.9
>
> and the command I issue is:
>  xm migrate 3 192.168.0.199
>  where 192.168.0.199 is on the same subnet as I am and 192.168.0.199 runs
>  also Xen. (both machines are on the same hub and of course I verified
>  that there is a ping between them).
>
>
> ifconfig shows the following interfaces on machine A:
> eth0,lo,peth0,vif0.0,vif1.0,vif2.0,vif3.0,xenbr0.
>
> the vif* interfaces do not have an IP address in them ; the eth0 of
> course has the right IP address (maybe
> this is the problem ? in such a case , what **exactly**
> should I do to set the vif*  addresses and which of them should
> I set (or all)? )
>
> For example
> (vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2712 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11376 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:517584 (505.4 KiB)  TX bytes:1371081 (1.3 MiB)
>
> xen-unstabel version:
> hg tip on machine A shows:
> changeset:   7701:abbe3df33774
> ...
> ....
> date:        Tue Nov  8 19:39:58 2005 +0100
>
> I want to add tha saving adomain DOES work: tried : xm save 3
> /work/domain3.save and it finished it's worked
> with no errors and created the saced domain file.
>
> Any ideas?
>
> Mark R.
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 | 
 |  | 
  
    |  |  |