natty kernel does not boot on ec2 t1.micro
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Stefan Bader | ||
Natty |
Fix Released
|
High
|
Stefan Bader |
Bug Description
This bug has been split off of bug 669496.
instances of size t1.micro on EC2 do not boot with the natty kernel.
This is true both of i386 and amd64.
I've just tested with instances of:
us-east-1 ami-dece38b7 ebs/ubuntu-
us-east-1 ami-d4ce38bd ebs/ubuntu-
There is no console output past the grub messages.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.37-8-virtual x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CurrentDmesg:
Date: Tue Dec 7 18:27:29 2010
Ec2AMI: ami-d4ce38bd
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: m1.large
Ec2Kernel: aki-427d952b
Ec2Ramdisk: unavailable
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: root=LABEL=
ProcModules: acpiphp 19089 0 - Live 0xffffffffa0000000
SourcePackage: linux
tags: | added: kernel-series-unknown |
tags: |
added: regression-release removed: regression-update |
Changed in linux (Ubuntu Natty): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Natty): | |
milestone: | natty-alpha-2 → natty-alpha-3 |
Not the solution yet, unfortunately, but looking at bug #667796, we found that XEN_MAX_ DOMAIN_ MEMORY limits the memory a domU is reporting. Looking at Natty, this has actually changed to a fixed config option of 128GB. But this went with a quite big change to the mmu code and only changing the value back to 70 is not enough to make it work again. But at least the following commit may be a start to look at:
commit 58e05027b530ff0 81ecea68e38de8d 59db8f87e0
Author: Jeremy Fitzhardinge <email address hidden>
Date: Fri Aug 27 13:28:48 2010 -0700
xen: convert p2m to a 3 level tree
Make the p2m structure a 3 level tree which covers the full possible
physical space.
The p2m structure contains mappings from the domain's pfns to system-wide
mfns. The structure has 3 levels and two roots. The first root is for
the domain's own use, and is linked with virtual addresses. The second
is all mfn references, and is used by Xen on save/restore to allow it to
update the p2m mapping for the domain.
At boot, the domain builder provides a simple flat p2m array for all the to_machine( )
initially present pages. We construct the two levels above that using
the early_brk allocator. After early boot time, set_phys_
will allocate any missing levels using the normal kernel allocator
(at GFP_KERNEL, so it must be called in a normal blocking context).
Because the early_brk() API requires us to pre-reserve the maximum amount XEN_MAX_ DOMAIN_ MEMORY
of memory we could allocate, there is still a CONFIG_
config option, but its only negative side-effect is to increase the
kernel's apparent bss size. However, since all unused brk memory is
returned to the heap, there's no real downside to making it large.