Hello! On Tue, Sep 19, 2006 at 07:33:28AM +0200, Wolfgang Lonien wrote: > Thomas Schwinge wrote: > > Please try either a) linux-image-2.6-xen-* together with
^ That should have been
linux-image-2.6.16-2-xen-*.
> > xen-hypervisor-3.0.2-1-* or b) linux-image-2.6.17-2-xen-* together with
> > xen-hypervisor-3.0-unstable-1-* and report whether that fixes your issue.
>
> I did. I tried both the 2.6.16 (-18) as well as the 2.6.17 linux images
> which are in Etch currently, and both have that same behaviour. Only the
> older 2.6.16 (-17 or -16) kernels did boot the Dom0.
Is that still with xen-hypervisor-3.0-amd64? If yes, then that would be
expected and you should re-read what I wrote (and corrected...) above,
i.e. you need to update your xen-hypervisor package to either
xen-hypervisor-3.0.2-1-* or xen-hypervisor-3.0-unstable-1-* depending on
which version of the Linux kernel you indend to use.
Regards,
Thomas
signature.asc
Description: Digital signature
