Bug#727736: With full log: Wheezy -> testing kernel upgrade won't reboot.
I terminated the prevoius instance, and started from scratch.
1. Searching for an AMI: looking at public, 32-bit images and the Debian
platform. There are 93 images available. Looks like there are 2 or
3 for Wheezy. Choosing
AMI ID ami-f494e99d
AMI Name debian-wheezy-i386-20130705
Owner 379101102735
Source 379101102735/debian-wheezy-i386-20130705
Status available
State Reason -
Platform Debian
Architecture i386
Image Type machine
Description Debian 7.1a (Wheezy) Base
Root Device Name /dev/sda1
Root Device Type ebs
RAM disk ID -
Kernel ID aki-b6aa75df
Product Codes -
Block Devices /dev/sda1=snap-df83078f:8:true:standard
and launch it.
2. Using a size of 30GB and without implicit deletion on termination.
It is running.
As an aside: there is
https://wiki.debian.org/Cloud/AmazonEC2Image/Wheezy
3. vps is running and can be connected by ssh.
4. root@ip-vps:~# shutdown -r now
successfuly reboots the machine. And so does Amazon API.
5. root@ip-vps:~# aptitude -R safe-upgrade linux-image-686-pae
Resolving dependencies...
The following NEW packages will be installed:
linux-image-3.10-3-686-pae{a}
The following packages will be upgraded:
initramfs-tools linux-image-686-pae
The following packages are RECOMMENDED but will NOT be installed:
busybox busybox-static firmware-linux-free libc6-i686
2 packages upgraded, 1 newly installed, 0 to remove and 134 not upgraded.
Need to get 24.3 MB of archives. After unpacking 87.5 MB will be used.
linux-image-3.10-3-686-pae is now installed. Grub is set to boot
it by default. Rebooting from inside the vps.
6. It takes a few minutes to see that Amazon API reports a running
Instant State and 1/2 checks for Status checks. The machine does not
respond to the network. The boot log follows. I hope the deletion
of many empty lines, and ncurses codes interfering with copy-paste
didn't remove important information.
ll now restart.
[1670414.627648] xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping
[1670414.992956] Disabling non-boot CPUs ...
[1670414.992974] Restarting system.
Xen Minimal OS!
start_info: 0xa01000(VA)
nr_pages: 0x26700
shared_inf: 0x7de2a000(MA)
pt_base: 0xa04000(VA)
nr_pt_frames: 0x9
mfn_list: 0x967000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: root=/dev/sda1 ro 4
stack: 0x946780-0x966780
MM: Init
_text: 0x0(VA)
_etext: 0x61e05(VA)
_erodata: 0x76000(VA)
_edata: 0x7b6b4(VA)
stack start: 0x946780(VA)
_end: 0x966d34(VA)
start_pfn: a10
max_pfn: 26700
Mapping memory range 0xc00000 - 0x26700000
setting 0x0-0x76000 readonly
skipped 0x1000
MM: Initialise page allocator for b3e000(b3e000)-0(26700000)
MM: done
Demand map pfns at 26701000-36701000.
Heap resides at 36702000-76702000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x26701000.
Initialising scheduler
Thread "Idle": pointer: 0x36702008, stack: 0xbf0000
Initialising xenbus
Thread "xenstore": pointer: 0x36702478, stack: 0x26600000
Dummy main: start_info=0x966880
Thread "main": pointer: 0x367028e8, stack: 0x26610000
"main" "root=/dev/sda1" "ro" "4"
vbd 2049 is hd0
******************* BLKFRONT for device/vbd/2049 **********
backend at /local/domain/0/backend/vbd/1400/2049
Failed to read /local/domain/0/backend/vbd/1400/2049/feature-barrier.
Failed to read /local/domain/0/backend/vbd/1400/2049/feature-flush-cache.
62914560 sectors of 0 bytes
**************************
oting '3.10-3-686-pae'
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-3.10-3-686-pae root=/dev/xvda1 ro
initrd /boot/initrd.img-3.10-3-686-pae
ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: unknown compression format
xc_dom_bzimageloader.c:394: panic: xc_dom_probe_bzimage_kernel: unknown compression format
ERROR Invalid kernel: xc_dom_find_loader: no loader found
xc_dom_core.c:536: panic: xc_dom_find_loader: no loader found
xc_dom_parse_image returned -1
Error 9: Unknown boot failure
Press any key to continue...
Reply to: