Bug#727736: With full log: Wheezy -> testing kernel upgrade won't reboot.
On Sun, Oct 27, 2013 at 12:29:55PM +0100, Bastian Blank wrote:
> On Sun, Oct 27, 2013 at 05:52:46AM +0200, Regid Ichira wrote:
> > Kernel ID aki-b6aa75df
>
> This does not match _any_ of the PV-GRUB versions listed on [1].
>
> Bastian
>
> [1]: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UserProvidedKernels.html
Indeed, aki-b6aa75df is not mentioned. I tried aki-919dcaf8, which
is one of the PV-GRUB versions listed on [1]. It created a
debian-wheezy-installer-amd64-20130613_deb7u1 (ami-29fea140). As
documented at https://wiki.debian.org/Cloud/AmazonEC2DebianInstaller.
I couldn't ssh to it, which might be reasonable if it gave an installer
at the first steps. The AmazonEC2DebianInstaller states I need the
euca2ools.deb. There are 4 images in each region. Half of that are
i386 images. I couldn't find any i386 images in any region. Half of
what is left are Ubuntu related images. There are many of these. I
think that any debian related, in the whole list, is for the installer.
I think the PV-GRUB able aki is irrelevant for our discussion:
1. Qouting http://wiki.xen.org/wiki/PvGrub:
(pv-grub) runs an adapted version of the grub boot loader inside
the created domain itself, and uses the regular domU facilities
to read the disk mounted as root directory, fetch files from
network, etc.; it also eventually loads the PV kernel and
chain-boots it.
In addition, http://wiki.xen.org/wiki/PvGrub has a link to
Xen PVGRUB Howto: http://backdrift.org/xen-pvgrub-howto. Qouting
this Howto:
From the xen wiki: PV-GRUB replaces PyGrub to boot domU images
safely: it runs the regular grub inside the created domain itself
and uses regular domU facilities to read the disk / fetch files
from network etc.; it eventually loads the PV kernel and chain-boots
it.
This means that your domU guests can install and manage their
own kernels as if they were running on regular hardware. Yum,
apt-get and other package management software will let you patch
your virtual machine's kernel without the need to alter any Xen
configuration.
Doesn't all hat means the PV vps can mostly ignore pv-grub as
long as it has a menu.lst file in the right place? I think that
conclusion is also consistent with [1].
2. Both ami-f494e99d and aki-919dcaf8 are created by the Debian AMI
Account (account number 379101102735). ami-f494e99d, which is
mentioned at https://wiki.debian.org/Cloud/AmazonEC2Image/Wheezy,
uses aki-b6aa75df. I think Debian AMI Account people are official
Debian representative. Thus, know what they are doing.
3. I wonder what is the difference between the xen minimal os that is
mentioned in the boot logs, and
PV-GRUB is a paravirtual "mini-OS" that runs a patched
version of GNU GRUB 0.97
which is mentioned in [1]. Xen Minimal OS! is mentioned at the
boot log I posted in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727736#40, which
also shows the content of menu.lst. I think it won't be great
surprise if Xen Minimal OS! and PV-GRUB is the same thing. So
PV-GRUB booted ami-f494e99d, even though aki-b6aa75df is not in [1].
Most of all, which is also in accordabce with the quote of
the http://backdrift.org/xen-pvgrub-howto from above, ami-f494e99d,
which uses aki-b6aa75df, gave me a virtual wheezy machine. I can, and
actually did, apt-get all its packages to the latest testing machine.
I was able to reboot it when it had wheezy's kernel. Actually, before
debian source 3.9 came out, I was able to use the latest debian source
for that time, run a configold, make a self compiled kernel, install it
and reboot the machine to the new self compiled kernel. That ability
was broke by the debian source for 3.9. My conclusion is that there
is an ability to run a wheezy machine, that can not be upgraded to
testing machine. Isn't that a bug in Debian?
Reply to: