Comment 1 for bug 1005551

Revision history for this message
Stefan Bader (smb) wrote : Re: [Bug 1005551] [NEW] Quantal does not boot on EC2

On 28.05.2012 16:25, Ben Howard wrote:
> Public bug reported:
>
> Quantal stopped booting on EC2 around 2012-05-25.
>
> ben@padfoot:~$ ec2-get-console-output -i i-75727213
> Required parameter 'INSTANCE' missing (-h for usage)
> ben@padfoot:~$ ec2-get-console-output i-75727213
> i-75727213
> 2012-05-28T14:17:49+0000
> Xen Minimal OS!
> start_info: 0xb10000(VA)
> nr_pages: 0x6a400
> shared_inf: 0x001a5000(MA)
> pt_base: 0xb13000(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: 0x61e65(VA)
> _erodata: 0x76000(VA)
> _edata: 0x7b6d4(VA)
> stack start: 0x946780(VA)
> _end: 0x966d34(VA)
> start_pfn: b1f
> max_pfn: 6a400
> Mapping memory range 0xc00000 - 0x6a400000
> setting 0x0-0x76000 readonly
> skipped 0x1000
> MM: Initialise page allocator for e6c000(e6c000)-0(6a400000)
> MM: done
> Demand map pfns at 6a401000-7a401000.
> Heap resides at 7a402000-ba402000.
> Initialising timer interface
> Initialising console ... done.
> gnttab_table mapped at 0x6a401000.
> Initialising scheduler
> Thread "Idle": pointer: 0x7a402008, stack: 0x6a030000
> Initialising xenbus
> Thread "xenstore": pointer: 0x7a402478, stack: 0x6a040000
> Dummy main: start_info=0x966880
> Thread "main": pointer: 0x7a4028e8, stack: 0x6a050000
> "main" "root=/dev/sda1" "ro" "4"
> vbd 2049 is hd0
> ******************* BLKFRONT for device/vbd/2049 **********
>
>
> backend at /local/domain/0/backend/vbd/126/2049
> Failed to read /local/domain/0/backend/vbd/126/2049/feature-barrier.
> Failed to read /local/domain/0/backend/vbd/126/2049/feature-flush-cache.
> 16777216 sectors of 0 bytes
> **************************
> vbd 2050 is hd1
> ******************* BLKFRONT for device/vbd/2050 **********
>
>
> backend at /local/domain/0/backend/vbd/126/2050
> Failed to read /local/domain/0/backend/vbd/126/2050/feature-barrier.
> Failed to read /local/domain/0/backend/vbd/126/2050/feature-flush-cache.
> 312705024 sectors of 0 bytes
> **************************
> vbd 2051 is hd2
> ******************* BLKFRONT for device/vbd/2051 **********
>
>
> backend at /local/domain/0/backend/vbd/126/2051
> Failed to read /local/domain/0/backend/vbd/126/2051/feature-barrier.
> Failed to read /local/domain/0/backend/vbd/126/2051/feature-flush-cache.
> 1835008 sectors of 0 bytes
> **************************
> [H[J Booting 'Ubuntu quantal (development branch), memtest86+'
>
> root (hd0)
> Filesystem type is ext2fs, using whole disk

> kernel /boot/memtest86+.bin

^Huh?!?

>
> xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> 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...
>
> ** Affects: ubuntu
> Importance: Undecided
> Assignee: Canonical Kernel Team (canonical-kernel-team)
> Status: New
>
>
> ** Tags: cloud-images ec2
>