Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-13 Thread Stefan Hajnoczi
On Sat, Mar 04, 2017 at 12:15:00AM +0200, Nir Soffer wrote: > On Sat, Mar 4, 2017 at 12:02 AM, John Snow wrote: > > > > > > On 03/03/2017 04:38 PM, Nir Soffer wrote: > >> On Fri, Mar 3, 2017 at 3:51 PM, Stefan Hajnoczi > >> wrote: > >>> > >>> RFCv1: > >>>

Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-07 Thread Daniel P. Berrange
On Tue, Mar 07, 2017 at 01:11:44PM +0100, Alberto Garcia wrote: > On Tue 07 Mar 2017 11:36:54 AM CET, Daniel P. Berrange wrote: > >> The creation scenario is: > >> > >> $ qemu-img max-size -O qcow2 --size 5G > >> 196688 > > > > Hmm, so that appears to be indicating the amount of physical

Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-07 Thread Alberto Garcia
On Tue 07 Mar 2017 11:36:54 AM CET, Daniel P. Berrange wrote: >> The creation scenario is: >> >> $ qemu-img max-size -O qcow2 --size 5G >> 196688 > > Hmm, so that appears to be indicating the amount of physical space > that a qcow2 image would take up before any data has been written to > it.

Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-07 Thread Daniel P. Berrange
On Fri, Mar 03, 2017 at 09:51:46PM +0800, Stefan Hajnoczi wrote: > RFCv1: > * Publishing patch series with just raw support, no qcow2 yet. Please review >the command-line interface and let me know if you are happy with this >approach. > > Users and management tools sometimes need to

Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-03 Thread Nir Soffer
On Sat, Mar 4, 2017 at 12:15 AM, Nir Soffer wrote: > On Sat, Mar 4, 2017 at 12:02 AM, John Snow wrote: >> >> >> On 03/03/2017 04:38 PM, Nir Soffer wrote: >>> On Fri, Mar 3, 2017 at 3:51 PM, Stefan Hajnoczi wrote: RFCv1: *

Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-03 Thread Nir Soffer
On Sat, Mar 4, 2017 at 12:02 AM, John Snow wrote: > > > On 03/03/2017 04:38 PM, Nir Soffer wrote: >> On Fri, Mar 3, 2017 at 3:51 PM, Stefan Hajnoczi wrote: >>> >>> RFCv1: >>> * Publishing patch series with just raw support, no qcow2 yet. Please >>>

Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-03 Thread John Snow
On 03/03/2017 04:38 PM, Nir Soffer wrote: > On Fri, Mar 3, 2017 at 3:51 PM, Stefan Hajnoczi wrote: >> >> RFCv1: >> * Publishing patch series with just raw support, no qcow2 yet. Please >> review >>the command-line interface and let me know if you are happy with this

Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-03 Thread Nir Soffer
On Fri, Mar 3, 2017 at 3:51 PM, Stefan Hajnoczi wrote: > > RFCv1: > * Publishing patch series with just raw support, no qcow2 yet. Please review >the command-line interface and let me know if you are happy with this >approach. > > Users and management tools

Re: [Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-03 Thread John Snow
On 03/03/2017 08:51 AM, Stefan Hajnoczi wrote: > RFCv1: > * Publishing patch series with just raw support, no qcow2 yet. Please review >the command-line interface and let me know if you are happy with this >approach. > > Users and management tools sometimes need to know the size

[Qemu-devel] [RFC 0/4] qemu-img: add max-size subcommand

2017-03-03 Thread Stefan Hajnoczi
RFCv1: * Publishing patch series with just raw support, no qcow2 yet. Please review the command-line interface and let me know if you are happy with this approach. Users and management tools sometimes need to know the size required for a new disk image so that an LVM volume, SAN LUN, etc