Re: [Openstack] Image as Volume Source - Bootable volume issue

2016-04-05 Thread Erdősi Péter
2016. 04. 05. 3:51 keltezéssel, Jagga írta: Ahh. Looks like it is the disk size. It starts working at 5GB. Is this a CentOS thing then instead of how the image creation works. Yes... Debian images works from 2GB i think... Anyways... You can easily check the images with this command: $ *qem

Re: [Openstack] Image as Volume Source - Bootable volume issue

2016-04-04 Thread Jagga
Ahh. Looks like it is the disk size. It starts working at 5GB. Is this a CentOS thing then instead of how the image creation works. Thanks. > On Apr 4, 2016, at 5:10 PM, Erdősi Péter wrote: > > Hy there, > > 2016. 04. 05. 1:51 keltezéssel, Jagga Soorma írta: >> This leads me to believe tha

Re: [Openstack] Image as Volume Source - Bootable volume issue

2016-04-04 Thread Erdősi Péter
Hy there, 2016. 04. 05. 1:51 keltezéssel, Jagga Soorma írta: This leads me to believe that there is something missing within our qcow CentOS 7.x images. Is there something that we need to do to our images so that it can be deployed as a bootable volume? 2 things crossed my mind while reading

[Openstack] Image as Volume Source - Bootable volume issue

2016-04-04 Thread Jagga Soorma
Hi Guys, When creating a bootable volume (volume source - image) within horizon ui by pointing it to one of our images we are getting a Error status without any further details. However, when I try to do the same thing with a cirros image that was downloaded from a external source it works just f