Open Stack

Lars,
   Thanks that helped, just curious, why does it need to use libguestfs ?
Why can't it just use qemu-img resize to check ?
Also in my devstack setup i see that my Nova VM is stuck at this step.. so
it looks like nova libvirt driver debug says "Creating image" in the n-cpu
log
and then it stuck there which causes my Instance state to be 'spawning' for
ever.. Any idea if/why libguestfs can never return or cause nova instance
to hang at BUILD/Spawning status ?

I am on F20+devstack combo

thanx,
deepak



On Tue, Jun 10, 2014 at 7:57 PM, Lars Kellogg-Stedman <lars at redhat.com>
wrote:

> On Tue, Jun 10, 2014 at 06:03:14PM +0530, Deepak Shetty wrote:
> > When i use m1.tiny flavour
> > I see that qemu process does not have -vnc and instance name is
> guestfs-XXX
> > and uses libguestfs stuff
>
> Prior to booting your instance, Nova uses libguestfs to check the image
> to see whether it can be dynamically resized or not.  Libguests starts
> up a qemu instance, which is what you are seeing.
>
> This guestfs-XXX instance should disappear once Nova has finished
> inspecting the image and you should see the normal Nova instance with
> the -vnc flag, etc.
>
> --
> Lars Kellogg-Stedman <lars at redhat.com> | larsks @ irc
> Cloud Engineering / OpenStack          | "   "  @ twitter
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140611/f2e68b46/attachment.html>