Re: [Xen-users] Debian Etch 4.0 domU will not boot

["Andrew W." <andrewinet@xxxxxxxxx>]

Henning,

Thank you for the reply.  I discovered this on my own, one day after
posting to the list.  The last time I did a Xen deployment, it was on
an FC5 box, back when there were separate Dom0 and DomU kernels.  In
fact, I had much grief back then because I was running a kernel on the
DomU that did not match the Dom0 and it took me a long time to
discover that was the problem.  Now it seems that in this case,
running a proper DomU kernel that *does not* match the Dom0 is
*required*.  Any idea when this became normal, what architectural
changes necessitated it, and most importantly, why it doesn't seem to
be documented but is rather a foregone conclusion these days?

Regards,

Andrew Wang


On 7/9/07, Henning Sprang <henning_sprang@xxxxxx> wrote:
> Andrew W. wrote:
> > Hi all.  In CentOS 5 with kernel 2.6.18-8.1.4.el5xen and a file-backed
> > disk, I am unable to successfully boot Debian Etch.
>
> Yes, the fedora/redhat Kernel is patched in a way that only Fedora
> guests work well with it.
>
> Get a debian xen Kernel (fetch it from your guest, which you probably
> bootstrapped with debootstrap), and initrd, and try to start the domain
> with it.
>
> I played ariund with this a lot,  but using the Debian Kernel(or, if you
> rather like that, one from the xensource binary xen packages) was the
> only thing that worked nicely and reliably.
>
> Similar for running Suse on Fedora/Redhat. I got Suse working with a lot
> of tweaking, but using the guest's native Xen Kernel is a match easier
> and better solution.
>
> Henning
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users