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/
Home Products Support Community News


[Xen-users] IP address

Subject: [Xen-users] IP address
From: Dakshina Dasari <Dakshina.Dasari@xxxxxxx>
Date: Fri, 09 Dec 2005 10:42:18 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 09 Dec 2005 05:11:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200512081054.06134.michael.mey@xxxxxx>
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>
References: <E1Ek276-0008Nf-00@xxxxxxxxxxxxxxxxx> <200512081054.06134.michael.mey@xxxxxx>
Reply-to: Dakshina.Dasari@xxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221
A very basic question --Do i need to allocate a static IP for each of the domains I create ???

Michael Mey wrote:
On Wednesday 07 December 2005 17:25, Steven Hand wrote:

I had this exact same problem with 2.0.7.  I had done a little
investigation and found scheduled_work gets called to schedule the
shutdown in the user domain kernel, but the shutdown work that gets
scheduled never actually gets called.  I'm glad someone else is
seeing this same problem now :-) Like you, it worked a number of
times in a row, then would fail, and it didn't seem to matter if
there was really any load going on or not.

At least one issue with live migration in 2.0.7 is fixed in the
the 2.0-testing tree (cset 3513:80a8b005b669 if you want to just
apply the patch directly)

This doesn't explain the situation where your domain dies tho; do
you have any console information from the domain in question?

The only thing I have is some syslog output of the domU, but there's not more than this usual lines:
Dec  6 15:47:16 debian1 kernel: Xen reported: 2806.425 MHz processor.
Dec  6 15:51:12 debian1 kernel: Xen reported: 2806.429 MHz processor.
Dec  6 15:54:54 debian1 kernel: Xen reported: 2806.425 MHz processor.

and the log file of my i/o testing script, but these are only md5 checksums. The script writes several times a dummy text into a file on the hd and finally builds a md5 checksum of the file for integrity test.
That logfile is fine, it's always the same md5.

Is there a possibility to further investigate what is happening with domU?

The funny thing is, yesterday afternoon I started a new testrun, this time using a ramdisk as storage for the i/o test. That domU is still running (after approx. 350 migrations). So it seems to me as if there is a problem with storage during migration, which sometimes occurs earlier, sometimes later.

The fibre channel adapters and the san is tested and works 100% correctly, so this shouldn't be the reason.




Xen-users mailing list

Xen-users mailing list