xen_emul_unplug=unnecessary on kernel cmdline is required in ec2 hvm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Under bug 684875 I added a cmdline option to the EC2 HVM instances [1]:
xen_
This flag is required to get the instance to boot on EC2 HVM instances. With bug 684875 fixed, we expected that this would no longer be necessary. However, I've tested today and it is still necessary with
$ uname -r
2.6.37-12-virtual
$ dpkg -S /boot/vmlinuz-
linux-image-
I'll attach console logs.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-
Regression: No
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.37-12-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
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg: [ 20.210048] eth0: no IPv6 routers present
Date: Mon Jan 17 15:42:24 2011
Ec2AMI: ami-f442b39d
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: cc1.4xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Xen HVM domU
PciMultimedia:
ProcEnviron:
LANG=en_US.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.45
RfKill:
SourcePackage: linux
dmi.bios.date: 04/14/2010
dmi.bios.vendor: Xen
dmi.bios.version: 3.4.2
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: dmi:bvnXen:
dmi.product.name: HVM domU
dmi.product.
dmi.sys.vendor: Xen
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
I modified grub to have an additional boot option called 'CUSTOM-TEST' and booted into that.
$ ent="Ubuntu, with Linux $(uname -r)" custom. cfg emul_unplug= unnecessary, ,' /boot/grub/ custom. cfg CUSTOM- TEST entry=Ubuntu, with Linux 2.6.37-12-virtual custom. cfg $linux_ gfx_mode d0de-4c19- b130-794dbd905a 44 2.6.37- 12-virtual root=UUID= f7ac8333- d0de-4c19- b130-794dbd905a 44 ro vt.handoff=7 console=ttyS0 img-2.6. 37-12-virtual
$ cust="CUSTOM-TEST"
$ sed -n -e "s/${ent}/${cust}/" \
-e "/^menuentry '${cust}'/,/}/p" \
< /boot/grub/grub.cfg | sudo tee /boot/grub/
$ sudo sed -i 's,xen_
$ sudo grub-set-default "${ent}"
$ sudo grub-reboot "${cust}"
$ sudo update-grub
$ grep -v "^#" /boot/grub/grubenv
saved_entry=
prev_saved_
$ cat /boot/grub/
menuentry 'CUSTOM-TEST' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=
insmod part_msdos
insmod ext2
set root='(hd2,msdos1)'
search --no-floppy --fs-uuid --set=root f7ac8333-
linux /boot/vmlinuz-
initrd /boot/initrd.
}
$ sudo reboot
The above does a "boot once" into that custom test kernel, so that subsequent reboots will go back into working kernel.