On Mon, Jan 18, 2016 at 04:19:58PM +, Richard W.M. Jones wrote:
> On Mon, Jan 18, 2016 at 03:33:25PM +, Richard W.M. Jones wrote:
> > I tried another workaround which was to get virt-resize to fsync the
> > output file before closing the libvirt connection, but that doesn't
> > work for
On Tue, Jan 19, 2016 at 12:31:48PM +0100, Kashyap Chamarthy wrote:
> On Mon, Jan 18, 2016 at 04:19:58PM +, Richard W.M. Jones wrote:
> > On Mon, Jan 18, 2016 at 03:33:25PM +, Richard W.M. Jones wrote:
> > > I tried another workaround which was to get virt-resize to fsync the
> > > output
On Tue, Jan 19, 2016 at 01:39:41PM +, Richard W.M. Jones wrote:
> On Tue, Jan 19, 2016 at 12:31:48PM +0100, Kashyap Chamarthy wrote:
> > On Mon, Jan 18, 2016 at 04:19:58PM +, Richard W.M. Jones wrote:
> > > On Mon, Jan 18, 2016 at 03:33:25PM +, Richard W.M. Jones wrote:
> > > > I tried
On Tue, Jan 19, 2016 at 01:43:58PM +, Daniel P. Berrange wrote:
> I don't think it does. Passing GRACEFUL flag means libvirt will try
> /less/ hard to kill QEMU, so it is /more/ likely that you will get
> the
>
> "Failed to terminate process 1275 with SIGTERM: Device or resource busy"
>
>
On Tue, Jan 19, 2016 at 01:48:10PM +, Richard W.M. Jones wrote:
> On Tue, Jan 19, 2016 at 01:43:58PM +, Daniel P. Berrange wrote:
> > I don't think it does. Passing GRACEFUL flag means libvirt will try
> > /less/ hard to kill QEMU, so it is /more/ likely that you will get
> > the
> >
> >
On Tue, Jan 19, 2016 at 01:39:41PM +, Richard W.M. Jones wrote:
[...]
> The problem with this theory is we are passing the
> VIR_DOMAIN_DESTROY_GRACEFUL flag, so that would indicate that this
> flag is buggy.
>
> I think what we need is a test case, so here goes. Note you must run
> these
On Tue, Jan 19, 2016 at 03:39:22PM +0100, Kashyap Chamarthy wrote:
> Upstream OpenStack Nova employs a similar suggestion (calling the
> virDomainDestroy() API about 3 more times) proposed by Dan in this
> thread:
>
> http://git.openstack.org/cgit/openstack/nova/commit/?id=3907867 --
>
I didn't file a bug about this because it's not really clear what the
bug is. Anyway, here goes ...
$ virt-builder fedora-23 -o /dev/sdX
[ 2.3] Downloading: http://libguestfs.org/download/builder/fedora-23.xz
[ 3.0] Planning how to build this image
[ 3.0] Uncompressing
[ 18.1] Resizing
On Mon, Jan 18, 2016 at 03:33:25PM +, Richard W.M. Jones wrote:
> I tried another workaround which was to get virt-resize to fsync the
> output file before closing the libvirt connection, but that doesn't
> work for reasons I don't understand so far - still studying this.
I worked out what
