root filesystem fails to mount VMware/qemu image created from JeOS

[ubuntu_demon]

I'm using Gutsy. I have created (qcow) qemu images from Feisty alternate installer, Gutsy alternate installer and Gutsy JeOS. All these images fail to mount the root filesystem.

I was able to boot the Fedora 7 image I downloaded from oszoo.org :
http://www.oszoo.org/wiki/index.php/Fedora7.img

I'm experiencing the same problem with kqemu,qemu and kvm :
qemu -m 512 jeos.img -no-acpi -snapshot -std-vga -no-kqemu
qemu -m 512 jeos.img -no-acpi -snapshot -std-vga
kvm -m 512 jeos.img -no-acpi -snapshot -std-vga

The same issue happens with jeos images created by VMware.

This is probably a kernel issue but I'm reporting it to JeOS because you might have to roll out new images when this is fixed. See also :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/33269

[ubuntu_demon (ubuntu-demon)]

I have attached a screenshot where booting the JeOS image fails (I booted without quiet splash).

[Luciano Ramalho (ramalho)]

After installing the CD image with MD5(ubuntu-7.10-jeos-i386.iso)= 341ca65a187c71643079a2f9ee5523b5 on a VMWare Workstation 6.0.2 build-59824, the boot process stops at the same step reported above (https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/1)

When booting in recovery mode, the process stops at this message:

[ 2432.690989] hub 2-0:1.0: 6 ports detected

Then there is a long delay (I estimate 2 or 3 minutes), followed by this:

Done.
        Check root= bootarg cat /proc/cmdline
        or missing modulues, devices: cat /proc/modules ls /dev
ALERT! /dev/disk/by-uuid/0[...snip long uuid...] does not exist. Dropping to a shell!

[Martin Visser (martinvisser99)]

I can confirm this bugs also occurs in Vmware Workstation 6.0.2

[ubuntu_demon (ubuntu-demon)]

to Martin Visser / Luciano Ramalho :

I have changed the bug's description to reflect that it also happens for VMware. Please change the status of this bug to confirmed.

[ubuntu_demon (ubuntu-demon)]

IMHO the following bugs might be related :
https://bugs.launchpad.net/ubuntu-jeos/+bug/163113
https://bugs.launchpad.net/ubuntu/+bug/163140
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/33269

[ubuntu_demon (ubuntu-demon)]

A workaround for this issue :

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316/comments/6

But instead of pressing F6 you need to edit the kernel boot option during boot by pressing "e" in grub.

[Soren Hansen (soren)]

I need a bit more detail here... Did you use the jeos ISO or did you use the jeos image builder script to create your vm?

[Luciano Ramalho (ramalho)]

The ISO image I used was the one with MD5(ubuntu-7.10-jeos-i386.iso)= 341ca65a187c71643079a2f9ee5523b5

I was not aware of that a "JEOS image builder script" existed until you asked, Soren.

Are there docs or at least a readme for JEOS somewhere? I've looked around but could not find that, or a mailing list.

[ubuntu_demon (ubuntu-demon)]

I was also not aware of any docs or scripts.

I also used the ISO with MD5(ubuntu-7.10-jeos-i386.iso)= 341ca65a187c71643079a2f9ee5523b5 to create an image from it.

I created the image like this :
qemu-img create -f qcow jeos.img 10G
qemu -m 512 -cdrom ubuntu-7.10-jeos-i386.iso -boot d jeos.img -no-acpi -std-vga

This is probably a kernel issue. The reason I submitted this bug is that you should probably contact the kernel team and increase the priority of the issue and roll out new iso images when this is fixed.

IMHO the following bugs might be related :
https://bugs.launchpad.net/ubuntu-jeos/+bug/163113
https://bugs.launchpad.net/ubuntu/+bug/163140
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/33269

[ubuntu_demon (ubuntu-demon)]

to Martin Visser / Luciano Ramalho :

Can you confirm that the same workaround works for you ?

1) Press ESC to enter Grub
2) Press "e" to edit the boot options
3) remove "quiet splash"
4) Add: "break=mount"
5) push Enter, push 'b' to boot
6) after a bit you need to type the following:
modprobe ide-generic
exit

Original source of this workaround :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316/comments/6

[Martin Visser (martinvisser99)]

No, this doesn't help. The disk was created as SCSI (which is the default in Vmware), so I am not sure why adding an IDE kernel module would help (besides this module was already loaded). The related original source seems to be related to booting in ISO cdrom (presumablly IDE attached) so I don't know why that would be related.

[ubuntu_demon (ubuntu-demon)]

to Martin Visser :

Did you actually try it ? Can't hurt to try. It works for my case (qemu/kvm/kqemu). I can boot the JeOS image I created like this https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/9 with this workaround. But I don't know what kind of disk qemu/kvm emulates.

You should also try the same approach but use the scsi module you need instead of ide-generic.

[ubuntu_demon (ubuntu-demon)]

In my explanation of how I created the QEMU image : https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/9
I forgot to mention this workaround I needed : https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316/comments/7

Because bug #120316 affects JeOS too. Should I report it as a seperate bug against JeOS ?

[Martin Visser (martinvisser99)]

I had tried this, hence my comment. There is no scsi-generic module,
the closest is scsi_mod, but this had the same (NULL) effect.

On Nov 20, 2007 10:29 PM, ubuntu_demon <email address hidden> wrote:
> to Martin Visser :
>
> Did you actually try it ? Can't hurt to try. It works for my case
> (qemu/kvm/kqemu). I can boot the JeOS image I created like this
> https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/9 with this
> workaround. But I don't know what kind of disk qemu/kvm emulates.
>
> You should also try the same approach but use the scsi module you need
> instead of ide-generic.
>
>
> --
> root filesystem fails to mount VMware/qemu image created from JeOS
> https://bugs.launchpad.net/bugs/163113
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards, Martin

Martin Visser

[Luciano Ramalho (ramalho)]

I can confirm that the JEOS installation works if the hard disk is set to IDE when creating the virtual machine in VMWare Workstation 6.

This should be documented somewhere (at least in a README file), because the UI for vm creation has SCSI as the default and recommended choice.

[ubuntu_demon (ubuntu-demon)]

To create the image I did this :
https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/9
To detect the cd-rom I needed this workaround (for a different bug) :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316/comments/7

To be able to workaround this bug and boot the image I created I needed to modprobe ide-generic right before mounting :
https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/10

For VMware setting the harddisk to IDE solves the problem according to https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/15

So what other information is needed ? Why is this bug marked as incomplete ?

[Dan Kegel (dank)]

We had a similar problem recently with vmware and
vmware player booted the original Dapper images from
www.thoughtpolice.co.uk fine, but when we replaced the kernel with
vanilla kernels 2.6.21.1 or 2.6.22.10, booting failed after a long delay and the error
"can't find volume group ubuntu".

Fortunately, http://gentoo-wiki.com/HOWTO_Install_Gentoo_on_VMware
suggests replacing "lsilogic" with "buslogic" in the .vmx file
(just use a text editor). Worked for me, maybe it'll work for you, too.

[markba (mark-baaijens)]

I can confirm that following workaround for prevent JeOS into busybox is working for me:
https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/10

1) Press ESC to enter Grub
2) Press "e" to edit the boot options
3) remove "quiet splash"
4) Add: "break=mount"
5) push Enter, push 'b' to boot
6) after a bit you need to type the following:
modprobe ide-generic
exit

I tried to add ide-generic to /etc/modules, resulting in a corrupt image: it does not boot anymore, even not in busybox.

[jonatanfan (jonatanfan)]

Solved it permanently (hopefully) on an edubuntu 7.10 server installed in qemu using this:
https://lists.ubuntu.com/archives/ubuntu-users/2006-August/091245.html

vi /etc/mkinitramfs-tools/modules
and add the line 'ide-generic'
apt-get install --reinstall linux-image-2.6.22-14-generic

[Greek Ordono (grexk)]

Replacing "lsilogic" to "buslogic" as suggested at https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/17, seems to solved this problem temporarily.

[markba (mark-baaijens)]

In my workaround wich worked (https://bugs.launchpad.net/ubuntu-jeos/+bug/163113/comments/18), I forgot to mention that I was using qemu.

Is there still information missing (as this bug is marked as incomplete), otherwise this bug can be confirmed?