| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Strange error in domU after dom0 update
On Thu, Oct 22, 2009 at 09:47:17AM +0200, Andreas Florath wrote:
> 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.
Uh oh.
Is there some reason why you didn't get the latest stable Xen release?
which is Xen 3.4.1.
Also on production you might want to run linux-2.6.18-xen.hg on dom0, or
then the OpenSUSE forward-ported (non pv_ops) dom0 patches for 2.6.31.4.
See: http://wiki.xensource.com/xenwiki/XenDom0Kernels
> 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.
Maybe you should try with LVM or file-backed domU disks first.
> WHY DOES THE BEHAVIOR OF A domU CHANGE WHEN THE dom0 IS EXCHANGED?
Because there's something clearly wrong; the iSCSI connection shouldn't
drop.
Debug that and solve the problem.
> Virtualization is IMHO exactly the abstraction layer which should hide
> such the dependency to any underlaying system.
Exactly.
You also need to have a working dom0 for that.
> 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!
>
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home