Hi Vish,
I would like you to review this patch
https://review.openstack.org/#/c/35460/.
I think this approach takes the least effort to fix this issue.
When we boot an instance from a volume, nova can get the volume
information by _get_volume. kerel_id and ramdisk_id are already in the
volume
On Mon, Jul 1, 2013 at 11:14 AM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
On Jul 1, 2013, at 3:35 AM, Sheng Bo Hou sb...@cn.ibm.com wrote:
Hi Mate,
First, thanks for answering.
I was trying to find the way to prepare the bootable volume.
Take the default image downloaded by
Hi,
I just proposed a patch for the boot_from_volume_exercise.sh to get rid
of --image. To be honest, I did not look at the various execution paths.
My initial thought is that boot from volume means you boot from volume.
If you only have a kernel + ramdisk image, I simply assumed that you
can't
On 1 July 2013 20:18, Mate Lakat mate.la...@citrix.com wrote:
Hi,
I just proposed a patch for the boot_from_volume_exercise.sh to get rid
of --image. To be honest, I did not look at the various execution paths.
My initial thought is that boot from volume means you boot from volume.
If you
On Jul 1, 2013, at 3:35 AM, Sheng Bo Hou sb...@cn.ibm.com wrote:
Hi Mate,
First, thanks for answering.
I was trying to find the way to prepare the bootable volume.
Take the default image downloaded by devstack, there are three images:
cirros-0.3.0-x86_64-uec,
Hi Cinder folks,
I am currently fixing the bugs related to booting the instance from the
volume. I found there are bugs both in Nova and
Cinder.
Cinder: https://bugs.launchpad.net/cinder/+bug/1159824
Nova: https://bugs.launchpad.net/nova/+bug/1191069
For the volumes created from the image, I
