[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee:

[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

Yes, I am able to boot an r3.large instance using this kernel, and I see the correct number of CPUs. My procedure, in case anyone else wants to reproduce it, was to boot up from the latest test AMI (ami-c1cb23ac), sudo dpkg -i ./linux-headers-4.4.0-21* linux-image-* as downloaded from your link,

[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

I will test it and post results here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582776 Title: HVM/SSD Xenial AWS AMI doesn't launch on r3.large To manage notifications about this bug go to:

[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

That commit also fixes bug 1573231. I have a test kernel already built for that bug if you want to test it. It can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1573231/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

OK, looks like we need at least: commit 56402d63eefe22179f7311a51ff2094731420406 Author: Thomas Gleixner Date: Fri May 6 20:48:16 2016 +0200 x86/topology: Handle CPUID bogosity gracefully Joseph reported that a XEN guest dies with a division by 0 in the

[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

I wonder how AWS manages to get that odd (literally) number of CPUs. >From the dmesg: smpboot: Allowing 15 CPUs, 13 hotplug CPUs >From that it looks like possible=15 and num_processors=2 in prefill_possible_,map(). And possible is assigned to nr_cpu_ids after printing the line above. Confirmed

[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

** Tags added: kernel-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582776 Title: HVM/SSD Xenial AWS AMI doesn't launch on r3.large To manage notifications about this bug go to:

[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

I know it works on c4 and m4 instance types. Those are the only other ones I've tried. To test this kernel on r3, I'd probably have to launch an instance on m4, upgrade the kernel from above, create a new AMI, and try running that on r3. I'm in major crunch right now, so I can't stop what I'm

[Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large

Would it be possible for you to test the 16.04 kernel against other instance types to see if the bug happens with them as well? The latest 16.04 kernel can be downloaded from: https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa/+build/9734451 With this kernel, you need to