kernel-packages team mailing list archive
Mailing list archive
[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 doing to do that, but I can try to squeeze it in while I'm
waiting for other stuff to run, etc. We're upgrading our infrastructure
to 16.04 and, for now, I'm just staying away from the r3 instances, but
it will be important for us to support them at some point.
I believe I may have misspoken about r3 supporting PV. c3 supports both
PV and HVM. r3 only supports HVM.
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
HVM/SSD Xenial AWS AMI doesn't launch on r3.large
Status in linux package in Ubuntu:
Status in linux source package in Xenial:
**NOTE** The additional information attached to this bug report is for
my laptop and does not apply to this bug report. Using ubuntu-bug, I'm
not sure how to control this. Using the debian bug tool, I would have
just edited the file....
If you attempt to launch an ec2 instance using
IMAGE ami-c1cb23ac 099720109477/ubuntu/images-testing/hvm-ssd
available public x86_64 machine
on an instance of type r3.large, the kernel doesn't boot. You get
output such as the attached log (kernel-ami-c1cb23ac.log).
You get essentially the same result if you try to launch an image from
ami-840910ee which is the AMI you get from http://cloud-
images.ubuntu.com/locator/ with the search string "16.04 hvm us-east
ssd" and picking the latest version.
HVM is supposed to work on r3.large. We have used this successfully
with Ubuntu 12.04, 14.04, and 15.10 and also with CentOS 5, 6, and 7.
r3.large is supposed to work with both HVM and PV. We have no problems
with this AMI on m4 or c4 instances which only support HVM.
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
USER PID ACCESS COMMAND
/dev/snd/controlC0: ejb 14140 F.... pulseaudio
Date: Tue May 17 11:06:11 2016
InstallationDate: Installed on 2016-04-22 (24 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
docker0 no wireless extensions.
enp0s3 no wireless extensions.
lo no wireless extensions.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=/dev/mapper/jblin0-root_16_04 ro quiet splash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: innotek GmbH
dmi.board.vendor: Oracle Corporation
dmi.chassis.vendor: Oracle Corporation
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to: