Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Boot ISO image on openstack installed on Ubuntu

Hi,

I am trying to boot-up my own ISO file on openstack Grizzly (which was installed on top of Ubuntu). The steps I am following are as follows:

(1). Create an image, providing "iso" as the input format.

glance image-create --name test_iso_image --disk-format iso --container-format bare --file /opt/stack/devstack/files/images/myimage.iso --property hw_vif_model=e1000 --property hw_disk_bus='ide'

(2). Start an instance with the created image and flavor as "medium".

nova boot test_image --image "7b48108e-9778-41bf-820d-cdadb5517a93" --flavor 3

With this approach, I am finding that the instance is created, but no drive is attached to the image, other than the CDROM. So, the installation stop, complaining that there is no disk to boot into.

The same ISO image, in VMDK format boots up fine. The aim is to boot from the ISO image directly.

I saw posts that this issue was fixed in openstack on XENServer - is this still a problem on openstack on Ubuntu?

Boot ISO image on openstack installed on Ubuntu

Hi,

I am trying to boot-up my own ISO file on openstack Grizzly (which was installed on top of Ubuntu). The steps I am following are as follows:

(1). Create an image, providing "iso" as the input format.

glance image-create --name test_iso_image --disk-format iso --container-format bare --file /opt/stack/devstack/files/images/myimage.iso --property hw_vif_model=e1000 --property hw_disk_bus='ide'

(2). Start an instance with the created image and flavor as "medium".

nova boot test_image --image "7b48108e-9778-41bf-820d-cdadb5517a93" --flavor 3

With this approach, I am finding that the instance is created, but no drive is attached to the image, other than the CDROM. So, the installation stop, stops, complaining that there is no disk to boot into.

The same ISO image, in VMDK format boots up fine. The aim is to boot from the ISO image directly.

I saw posts that this issue was fixed in openstack on XENServer - is this still a problem on openstack on Ubuntu?