The permanent fix for this is likely in PV-GRUB. See:
https://patchwork.kernel.org/patch/727511/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686692
Title:
natty kernel does not boot on ec2 t1.micr
This bug was fixed in the package linux - 2.6.38-1.27
---
linux (2.6.38-1.27) natty; urgency=low
[ Andy Whitcroft ]
* ubuntu: AUFS -- update aufs-update to track new locations of headers
* ubuntu: AUFS -- update to c5021514085a5d96364e096dbd34cadb2251abfd
* SAUCE: ensure root
This was fix-released by Stefan in 2.6.38-1.28. Alpha2 boots in amd64
in t1.micro. We've opened bug 710754 to address the i386 issue.
** Changed in: linux (Ubuntu Natty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu Natty)
Milestone: natty-alpha-2 => natty-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686692
Title:
natty kernel does not boot on ec2 t1.micro
--
ubuntu-b
I'm still unable to boot i386 instances. I tested
us-east-1 ami-5c3fcf35 canonical ebs/ubuntu-natty-daily-i386-server-20110131
It resulted in no console output and unreachable instance in t1.micro.
So, i386 is still broken on t1.micro (the same ami does boot on
m1.small).
However, x86_64 is fu
** Changed in: linux (Ubuntu Natty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686692
Title:
natty kernel does not boot on ec2 t1.micro
--
ubuntu-bug
With that patch applied I was able to successfully boot t1.micro
instances with a 2.6.37 kernel:
ubuntu@ip-10-112-5-120:~$ uname -a
Linux ip-10-112-5-120 2.6.37-12-virtual #26+686692v2 SMP Thu Jan 20 11:30:38
UTC 2011 x86_64 GNU/Linux
ubuntu@ip-10-112-5-120:~$ echo $(wget -q -O-
http://169.254.1
Ok, so it was the right place but a completely wrong explanation. The
problem is not that the last part of pointers is missed but that it is
not. The problem is that the kernel is given a flat array of address
pointers by the domain constructor along with the number of pointer in
that array. With r
<3>[0.00] smb: pfn=266ff calling set_pte(c1fe77f8, 6b3003)
<3>[0.00] smb: pfn=26700 calling set_pte(c1fe7800, 3)
<1>[0.00] BUG: unable to handle kernel NULL pointer dereference at
(null)
This was seen with some annotation. Basically pfn_pte for the last pfn
returns an in
I think I see the issue now. When xen sets up the p2m tree, it does a
loop from 0 to max_pfn-1, incrementing by the number of p2m mappings in
the leaf. If max_pfn is a multiple of 4M this works out. But if not, we
need an additional leaf being initialized (which is only partially
used).
I need to
One further step finally. Using 'on_crash = "coredump-destroy"' and
after creating /var/xen/dump, I was able to extract the following from
the dump file:
<6>[0.00] ACPI in unprivileged domain disabled
<3>[0.00] max_pfn used = 26700(2670)
<3>[0.00] Xen: map base 0 + 26f0
name = "NattyServerMicro32"
kernel = "/root/boot/pv-grub-hd0-V1.01-i386.gz"
memory = 616
vcpus = 1
disk = [ 'file:/root/amis/natty-server-uec-i386.img,sda1,w' ]
vif = [ '' ]
Not sure the vif really would work like this. I seem to have problems
getting the boot completed (currently got the cloud-in
@Stefan,
just for reference, could you attach your xen config for this instance ? I'd
like to recreate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686692
Title:
natty kernel does not boot on e
Some updates here: the good news is that I am able to reproduce this on
a local CentOS based installation. Bad news so far is that the DomU
crashes so quickly that I get no output at all, even when directly
attaching to the console on "xm create".
But at least I found a lead. The crashes happen if
** Also affects: linux (Ubuntu Natty)
Importance: High
Assignee: Stefan Bader (stefan-bader-canonical)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686692
Title:
na
** Tags added: regression-release
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686692
Title:
natty kernel does not boot on ec2 t1.micro
--
ubuntu-bugs mailing l
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 valu
** Tags added: kernel-series-unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686692
Title:
natty kernel does not boot on ec2 t1.micro
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: "log of amd64 instance t1.micro"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/686692/+attachment/1758791/+files/console-t1-micro-amd64.log
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Attachment added: "log of i386 instance t1.micro"
https://bugs.launchpad.net/bugs/686692/+attachment/1758782/+files/console-t1-micro-i386.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/68669
20 matches
Mail list logo
