On Wed, May 08, 2013 at 01:18:17PM +0800, yuxh wrote:
I have to consult you a qemu-img's problem.
Is this reasonable to create a file which is larger than the
available size of the fs by qemu-img cmd ?
When I use qemu-img create a file which is larger than the available
size of the fs,
On 05/09/2013 03:44 PM, Stefan Hajnoczi wrote:
On Wed, May 08, 2013 at 01:18:17PM +0800, yuxh wrote:
I have to consult you a qemu-img's problem.
Is this reasonable to create a file which is larger than the
available size of the fs by qemu-img cmd ?
When I use qemu-img create a file which is
Hello all,
I have to consult you a qemu-img's problem.
Is this reasonable to create a file which is larger than the available
size of the fs by qemu-img cmd ?
When I use qemu-img create a file which is larger than the available
size of the fs, the creation is completed succesfully.
I think it's the system admin to be responsible for the risk of over
provisioning. We have host sparse file[1] (as your example) for
preallocated image (for example, -f raw), as well as sparse image (as
supported in qcow2, vmdk, etc.). There are cases that host file system
is extended or the vm
Thank you for your reply. I agreed what you said.
And do you think we shall print a prompt to user when the size user
specified is larger than available space ?
On 05/08/2013 02:36 PM, Fam Zheng wrote:
I think it's the system admin to be responsible for the risk of over
provisioning. We have
On Wed, 05/08 15:34, yuxh wrote:
Thank you for your reply. I agreed what you said.
And do you think we shall print a prompt to user when the size user
specified is larger than available space ?
Might be nice, but it's hard to define available space, and available
space at creating time
On 05/08/2013 04:20 PM, Fam Zheng wrote:
On Wed, 05/08 15:34, yuxh wrote:
Thank you for your reply. I agreed what you said.
And do you think we shall print a prompt to user when the size user
specified is larger than available space ?
Might be nice, but it's hard to define available space,
