[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#656792: linux-image-3.2.0-1-amd64: kernel does not boot since 3.1 under a (strange) Xen anymore

On Sat, 2012-01-28 at 00:29 +0100, Christoph Anton Mitterer wrote:
> Hi.
> Perhaps this helps. According to the ISP the exakt version of the dom0
> kernel is:
> Also they claim there is not Microsoft HyperV or so used at all.

But they probably enabled 'Viridian compatibility mode' which makes
XenServer look more like HyperV, probably to make Windows guests behave
btter.  Linux 3.1 now checks for Xen before HyperV, to avoid being
fooled by this.  That might be a problem if it causes the kernel to
detect different emulated devices.  (I don't know whether it could have
this effect.)

Which drivers are in the initramfs?  Does
/etc/initramfs-tools/initramfs.conf have MODULES=dep (which is
vulnerable to configuration changes) or MODULES=most (which is safer)?


Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: