[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

Hi Ben.

On Sat, 2012-01-28 at 05:05 +0000, Ben Hutchings wrote:
> 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.)
I'll as them

> 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)?
It is "dep", but that shouldn't matter here, should it?
Cause the detected modules are the same as in the (still booting) 3.0.x
kernel (I've compared the initramfs with lsinitramfs).
And if I remember correctly, I even tried it with =most, when I first
stumbled across this when 3.1 came out.


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply to: