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

[Xen-users] Migration only works one way (seemingly depending on machine

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Migration only works one way (seemingly depending on machine's boot time)
From: Dominik Klein <dk@xxxxxxxxxxxxxxxx>
Date: Tue, 13 Mar 2007 10:50:27 +0100
Delivery-date: Tue, 13 Mar 2007 02:49:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20070103)
Hi

I have two completely identical machines running opensuse 10.2. domU (also opensuse 10.2) is running on Root NFS.

When trying to migrate this domU from machine 1 to machine 2, it works perfectly. When trying to migrate back to machine 1, I can see the domU in "xm list" on machine 1, but cannot connect to it with "xm console" nor ssh. The network interface is created, but says "NO-CARRIER" and xentop shows 100% CPU usage for this domU.

When trying to migrate this domU from machine 2 to machine 1 without having migrated it earlier, this fails in the same way. Migration also fails using xm save, copying the file manually and restoring the file on the other machine.

Now the (at least to me) really strange thing: After a reboot of machine 2, the whole procedure is the other way around. I am able to migrate from machine 2 to machine 1, but not from machine 1 to machine 2 - independant of wether the vm has been migrated before or not.

This is reproducable. The machine with less uptime can migrate virtual machines to the other machine. The other way never works.

I compared /etc using diff -r and it showed no difference except for hostname, ip addresses and stuff you'd expect to be different.

Any ideas?

Regards
Dominik

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