Oneiric's x64 cloud image [20111124] won't boot (wrong kernel, buggy /etc/fstab, buggy /etc/network/interfaces)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Fix Released
|
Critical
|
Unassigned |
Bug Description
This report is against the latest (as of now, 2011-11-27, 02:01 GMT-2) Oneiric's x64 cloud image, available on http://
I tried to launch an instance on my Eucalyptus cloud, but I wouldn't boot. I started digging, and found many issues with this image.
#####
(1) Wrong Kernel
(a) Symptom.
The kernel said it couldn't find /dev/sda1: VFS: Cannot open root device "sda1" or unknown-block(0,0).
(b) Analysis.
Somehow I noticed that the kernel that came in the tarball was the "-generic" one, and not the "-virtual" one (as is the case with Natty, for example, which works fine). The file is called "oneiric-
(c) Solution.
I removed the -generic kernel packages, installed the -virtual kernel packages (`apt-get purge linux-image-generic linux-image-
Then I removed the kernel that came in the tarball ball (oneiric-
The boot would now find /dev/sda1, as expected.
(2) Broken /etc/fstab
(a) Symptom.
At the end of the output from the virtual machine, I'd see "mount: mount point ext4 does not exist", and it wouldn't finish the boot sequence
(b) Analysis.
The file /etc/fstab is malformed. The contents of the file are:
LABEL=cloudimg-
That's all. It is obviously missing the mount point (/), as one would expect from the error message. Comparing it to Natty's cloud image fstab, it seems to be missing /proc as well.
(c) Solution.
Replace the contents of the file with:
proc /proc proc nodev,noexec,nosuid 0 0
LABEL=cloudimg-
(3) Broken /etc/network/
(b) Analysis.
The file /etc/network/
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
(c) Solution.
Add the following configuration for eth0 (copied from Natty), at the end of /etc/network/
# The primary network interface
auto eth0
iface eth0 inet dhcp
#####
After all these fixes, the instance finally managed to boot. Apparently it is working. However, there might be more bugs I couldn't detect (and that would not interfere with the boot sequence).
I urge you to fix this image, and to double check it.
Oh, and ***please make it easier to report bugs***. I lost more than 1 hour only to find this form (even asking at #ubuntu-server and #launchpad). It's really disgusting when you want to help and the system makes it extremelly difficult to help.
Changed in ubuntu: | |
importance: | Medium → Critical |
milestone: | none → precise-alpha-1 |
Confirming per IRC conversation seen in #ubuntu-server