From: Andreas Florath <xen@flonatel.org>
To: Xen-devel <xen-devel@lists.xensource.com>
Subject: Strange error in domU after dom0 update
Date: Thu, 22 Oct 2009 09:47:17 +0200 [thread overview]
Message-ID: <20091022094717.fk8pkqy6o80kgg0w@webmail.flonatel.org> (raw)
Hello!
I'm currently running some domUs on some dom0s. Everything is Debian
Lenny which comes with Xen-3.2.1 and kernel 2.6.26. The domUs are
running without any problems.
Now I want to use live migration - which does not really work with
Debian Lenny as dom0. Pulled xen-unstable c/s 20346 with
linux-2.6-pvops (2.6.31.4) and installed it on an extra box.
But: it is not possible to start any of the known-to-run-very-well
domUs on it. The domUs use a iSCSI based root file system. They
connect to the iSCSI-target, start to boot - but at some (random)
point during boot, they loose the iSCSI connection with a timeout and
therefore stop running.
WHY DOES THE BEHAVIOR OF A domU CHANGE WHEN THE dom0 IS EXCHANGED?
Virtualization is IMHO exactly the abstraction layer which should hide
such the dependency to any underlaying system.
Yes - it is reproducible: started the domUs hundreds of times on
Xen-3.2.1 boxes without any problems; tried to start the domUs on the
xen-unstable system tens of times always with problem described above.
I'm really stuck with this. Any help, remark, question, idea is welcome!
Kind regards - Andreas
next reply other threads:[~2009-10-22 7:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 7:47 Andreas Florath [this message]
2009-10-22 11:01 ` Strange error in domU after dom0 update Pasi Kärkkäinen
2009-10-22 11:55 ` Andreas Florath
2009-10-22 21:08 ` Jeremy Fitzhardinge
2009-10-23 11:28 ` Andreas Florath
2009-10-23 16:01 ` Andreas Florath
2009-10-27 14:44 ` Andreas Florath
2009-10-27 18:29 ` Jeremy Fitzhardinge
2009-10-29 11:14 ` Andreas Florath
2009-10-29 22:11 ` Jeremy Fitzhardinge
2009-10-30 9:24 ` Andreas Florath
2009-10-30 11:11 ` Steven Smith
2009-11-02 8:59 ` xen
2009-11-03 10:29 ` Andreas Florath
2009-11-03 22:52 ` Jeremy Fitzhardinge
2009-11-04 9:04 ` Steven Smith
2009-11-04 21:04 ` Jeremy Fitzhardinge
2009-11-05 12:22 ` Steven Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091022094717.fk8pkqy6o80kgg0w@webmail.flonatel.org \
--to=xen@flonatel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.