I've already tried the first solution but it has a big issue: with a
64 bit configuration (dom0 @64bits and kernel @64 bits, xen 3.2 built
from the src.rpm from the xen web site) I can not save nor migrate
domUs running at 32 bits.
I get this error:
[2008-04-28 14:00:16 2283] ERROR (XendCheckpoint:141) Save failed on
domain TEST (2).
Traceback (most recent call last):
line 109, in save
forkHelper(cmd, fd, saveInputHandler, False)
line 351, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 4 2 0 0 0 failed
This is probably due to the different architecture (32 and 64 bits)
from the dom0 to domUs: I suppose, although the documentation says the
opposite, that xen dom0 @64 bits can not handle correctly many
operations. I mean, with 54 bits dom0 I can start/stop a 32 bit domU
but I can not use a very big number of features.
See the faq:
2008/4/29 Rafał Kupka <rkupka+Listy.Xen@xxxxxxxxxxxxx>:
> On Tue, Apr 29, 2008 at 03:49:39PM +0200, Marco Strullato wrote:
> > > > You should use:
> > > > 1) 64bits Xen + 64bits dom0 kernel, userland 64- or 32-bits;
> > > > 2) 64bits Xen + 32bits dom0 kernel, userland 32bits
> > > So you suggest me to install a 64 bit xen version into a 32 bit dom0?
> > > I think it won't run but I'll try.
> > Tried. Dont' work (obviously)
> Did you as well test first solution?
> What Xen & dom0 kernel version have you tried?
> Great software without the knowledge to run it is pretty useless.
> (Linux Gazette #1)
> Xen-users mailing list
Xen-users mailing list