Ubuntu

ubuntu jeos 7.10 - can't boot using vmware server

Bug #163227 reported by Savvas Radevic on 2007-11-16

This bug report is a duplicate of: Bug #164716: linux-virtual kernel images need LSI scsi driver for VMware ESX. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu JeOS	Won't Fix	Undecided	Unassigned
	Ubuntu	Invalid	Undecided	Unassigned

Bug Description

I used:
VMware Server Console 1.0.4 build-56528
Ubuntu JeOS 7.10

The problem occurs after a successful installation of the ubuntu jeos on a virtual machine.
It shows the usplash screen and after some seconds it leads to something with initramfs and debian busybox.

md5sum is correct on the ISO image (I use the iso emulation).
I tried both recovery and normal bootup, both fail. Attached screenshots below.
Maybe it got *too* slimmed down? :)

See original description

Revision history for this message

Savvas Radevic (medigeek) wrote on 2007-11-16:

screenshots after normal and recovery bootup Edit (140.6 KiB, application/zip)

it said it couldn't find the disk

Savvas Radevic (medigeek) on 2007-11-17

description:

updated

Revision history for this message

Savvas Radevic (medigeek) wrote on 2007-11-17:

I've finally detected what's wrong, it doesn't detect SCSI hard drives. I think that's the one because when I switched to IDE, it worked!

Revision history for this message

Soren Hansen (soren) wrote on 2007-11-19:

That's correct. The special kernel in the JeOS ISO does not support the SCSI controller vmware emulates.

Changed in ubuntu-jeos:
status:	New → Won't Fix

Revision history for this message

Eugene San (eugenesan) wrote on 2007-11-19:

I am too confirm the issue.
It's strange that OS for Virtual Appliance wont boot on Virtual Machine :-)
Also installer fails to create devices on target while LVM is used.

Revision history for this message

Savvas Radevic (medigeek) wrote on 2007-11-20:

VMware shouldn't use SCSI as a default option for hard disks then

Revision history for this message

Jason Fiset (jasonfiset) wrote on 2007-11-20:

How do you expect to push out a virtual appliance that will run on ESX? ESX does not support IDE disks for boot environment - only SCSI. This will need to be fixed. The reason why VMware server is using SCSI by default is to maintain compatibility with ESX server. This won't make it far in the Enterprise datacenter if it only works with IDE disks.

Revision history for this message

Jason Fiset (jasonfiset) wrote on 2007-11-20:

I *have* been able to get this VM to boot by just changing this line in my .vmx file:

from:

scsi0.virtualDev = "lsilogic"

to:

scsi0.virtualDev = "buslogic"

My question is, how hard would it be to add support for LSI? The standard Ubuntu 7.10 installer works properly with LSI and LSI is the preferred interface from a performance perspective on VMware and would be more supportable in an ESX environment which is where ISVs would want to develop appliances. The initrd image and maybe the installed kernel would have to support LSI in order for this to work.

Revision history for this message

Eugene San (eugenesan) wrote on 2007-11-20:

I fully support Jason's opinion.
I think it was a huge mistake to release a product in such a condition.
If you ask me, I wouldn't even call it Virtual Appliance, it's not working on near 85% of virtual machine setups.
Steps to correct the situation must be taken NOW, no workaround can be accepted in that case.
If only i knew where to forward our words....

Revision history for this message

Savvas Radevic (medigeek) wrote on 2007-11-20:

well, as you can see, soren hansen rejected it and from the status I think he's not willing to fix it...
Is anyone else willing to attempt to do the plumbing? :)

Revision history for this message

Onno Benschop (onno-itmaze) wrote on 2007-12-03:

#10

For those coming across this bug, during creation of a new VM you can choose "Custom" rather than "Typical" and select the buslogic adapter.

Note that for me, even though the .iso had a correct md5, the integrity check failed.
Also, the CDROM needs to be IDE, because the VM won't boot from SCSI alone.

Revision history for this message

Richard Hansen (rhansen) wrote on 2008-01-20:

#11

It looks like this will be fixed in Hardy -- see bug #164716