When running Ubuntu as an Eucalyptus VM instance, module acpiphp is not available to be loaded, complicating the use EBS volume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Tim Gardner | ||
Jaunty |
Fix Released
|
Wishlist
|
Stefan Bader | ||
Karmic |
Fix Released
|
Undecided
|
Tim Gardner |
Bug Description
SRU justification:
Impact: When an Ubuntu AMI is being run as an instance in Eucalyptus, using an EBS volume requires that the acpiphp module be loaded. Unfortunately, the kernel and modules are not installed in the root filesystem, which mean the acpiphp module is not available to be loaded in the first place.
Fix: Add the module to the list of modules for the virtual package.
Testcase: See below
---
I can think of two ways to work-around the problem:
- Install linux-image-$(uname -r) inside the instance, and load acpiphp in /etc/modules or somesuch. The drawback is that doing this have a pretty important footprint in term of disk (115 MB) and network download.
- Upload to the cloud an initramfs image that have the acpiphp module in it. The drawback is that doing so needs to be documented, and it make creating/
Having the kernel built with CONFIG_
Just to clarify, this is not a problem on EC2, or when running as an instance on an Eucalyptus cloud that use the Xen hypervisor. This problem is specific to running Eucalyptus with KVM, which is the default on Ubuntu. In that case, EBS volumes show up as block devices attached through virtual SCSI controller being hot-plugged, and that is why we need to have the acpiphp module loaded (or a kernel compiled with CONFIG_
Related branches
Changed in eucalyptus (Ubuntu): | |
status: | New → Confirmed |
description: | updated |
Changed in linux (Ubuntu): | |
status: | New → In Progress |
Changed in linux (Ubuntu Jaunty): | |
assignee: | nobody → Stefan Bader (stefan-bader-canonical) |
importance: | Undecided → Wishlist |
status: | New → Fix Committed |
Changed in linux (Ubuntu Karmic): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
milestone: | none → karmic-alpha-5 |
I found this also to be a problem simply when running jaunty as a qemu or kvm guest. Note, that the config for linux-image-virtual (linux- image-2. 6.28-11- virtual) does have CONFIG_ HOTPLUG_ PCI_ACPI= m, the module is just not included in the -virtual package.