Re: [libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-25 Thread Daniel P. Berrange
On Mon, May 24, 2010 at 04:05:41PM -0600, Eric Blake wrote: > On 05/14/2010 07:10 AM, Daniel P. Berrange wrote: > > The virDomainGetBlockInfo API allows query physical block > > extent and allocated block extent. These are normally the > > same value unless storing a special format like qcow2 > > i

Re: [libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-24 Thread Eric Blake
On 05/14/2010 07:10 AM, Daniel P. Berrange wrote: > The virDomainGetBlockInfo API allows query physical block > extent and allocated block extent. These are normally the > same value unless storing a special format like qcow2 > inside a block device. In this scenario we can query QEMU > to get the

Re: [libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-18 Thread Eric Blake
On 05/16/2010 03:03 AM, Daniel P. Berrange wrote: >> that means you now propagate that fatal error out of the call, rather >> than falling back on the default. > > Yes, that is the intended behaviour here. If it is a block device + not using > the raw format, then we want the caller to be able to

Re: [libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-16 Thread Daniel P. Berrange
On Fri, May 14, 2010 at 10:39:08AM -0600, Eric Blake wrote: > On 05/14/2010 07:10 AM, Daniel P. Berrange wrote: > > The virDomainGetBlockInfo API allows query physical block > > extent and allocated block extent. These are normally the > > same value unless storing a special format like qcow2 > > i

Re: [libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-14 Thread Eric Blake
On 05/14/2010 07:10 AM, Daniel P. Berrange wrote: > The virDomainGetBlockInfo API allows query physical block > extent and allocated block extent. These are normally the > same value unless storing a special format like qcow2 > inside a block device. In this scenario we can query QEMU > to get the

Re: [libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-14 Thread Daniel Veillard
On Fri, May 14, 2010 at 09:10:01AM -0400, Daniel P. Berrange wrote: > The virDomainGetBlockInfo API allows query physical block > extent and allocated block extent. These are normally the > same value unless storing a special format like qcow2 > inside a block device. In this scenario we can query

Re: [libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-14 Thread Daniel P. Berrange
On Thu, May 13, 2010 at 08:18:24AM -0600, Eric Blake wrote: > On 05/13/2010 05:09 AM, Daniel P. Berrange wrote: > > The virDomainGetBlockInfo API allows query physical block > > extent and allocated block extent. These are normally the > > same value unless storing a special format like qcow2 > > i

[libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-14 Thread Daniel P. Berrange
The virDomainGetBlockInfo API allows query physical block extent and allocated block extent. These are normally the same value unless storing a special format like qcow2 inside a block device. In this scenario we can query QEMU to get the actual allocated extent. Since last time: - Return fatal

Re: [libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-13 Thread Eric Blake
On 05/13/2010 05:09 AM, Daniel P. Berrange wrote: > The virDomainGetBlockInfo API allows query physical block > extent and allocated block extent. These are normally the > same value unless storing a special format like qcow2 > inside a block device. In this scenario we can query QEMU > to get the

[libvirt] [PATCH] Query block allocation extent from QEMU monitor

2010-05-13 Thread Daniel P. Berrange
The virDomainGetBlockInfo API allows query physical block extent and allocated block extent. These are normally the same value unless storing a special format like qcow2 inside a block device. In this scenario we can query QEMU to get the actual allocated extent. * src/qemu/qemu_driver.c: Fill in