2014-02-21 19:24:08 +04:00
|
|
|
QA output created by 082
|
|
|
|
|
|
|
|
|
|
=== create: Options specified more than once ===
|
|
|
|
|
|
|
|
|
|
Testing: create -f foo -f qcow2 TEST_DIR/t.qcow2 128M
|
|
|
|
|
Formatting 'TEST_DIR/t.qcow2', fmt=qcow2 size=134217728 encryption=off cluster_size=65536 lazy_refcounts=off
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2
|
|
|
|
|
image: TEST_DIR/t.qcow2
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 196K
|
|
|
|
|
cluster_size: 65536
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: false
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o cluster_size=4k -o lazy_refcounts=on TEST_DIR/t.qcow2 128M
|
|
|
|
|
Formatting 'TEST_DIR/t.qcow2', fmt=qcow2 size=134217728 encryption=off cluster_size=4096 lazy_refcounts=on
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2
|
|
|
|
|
image: TEST_DIR/t.qcow2
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 16K
|
|
|
|
|
cluster_size: 4096
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: true
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o cluster_size=4k -o lazy_refcounts=on -o cluster_size=8k TEST_DIR/t.qcow2 128M
|
|
|
|
|
Formatting 'TEST_DIR/t.qcow2', fmt=qcow2 size=134217728 encryption=off cluster_size=8192 lazy_refcounts=on
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2
|
|
|
|
|
image: TEST_DIR/t.qcow2
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 28K
|
|
|
|
|
cluster_size: 8192
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: true
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o cluster_size=4k,cluster_size=8k TEST_DIR/t.qcow2 128M
|
|
|
|
|
Formatting 'TEST_DIR/t.qcow2', fmt=qcow2 size=134217728 encryption=off cluster_size=8192 lazy_refcounts=off
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2
|
|
|
|
|
image: TEST_DIR/t.qcow2
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 28K
|
|
|
|
|
cluster_size: 8192
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: false
|
|
|
|
|
|
|
|
|
|
=== create: help for -o ===
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o help TEST_DIR/t.qcow2 128M
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o ? TEST_DIR/t.qcow2 128M
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o cluster_size=4k,help TEST_DIR/t.qcow2 128M
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o cluster_size=4k,? TEST_DIR/t.qcow2 128M
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o help,cluster_size=4k TEST_DIR/t.qcow2 128M
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o ?,cluster_size=4k TEST_DIR/t.qcow2 128M
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o cluster_size=4k -o help TEST_DIR/t.qcow2 128M
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o cluster_size=4k -o ? TEST_DIR/t.qcow2 128M
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o backing_file=TEST_DIR/t.qcow2,,help TEST_DIR/t.qcow2 128M
|
|
|
|
|
Formatting 'TEST_DIR/t.qcow2', fmt=qcow2 size=134217728 backing_file='TEST_DIR/t.qcow2,help' encryption=off cluster_size=65536 lazy_refcounts=off
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o backing_file=TEST_DIR/t.qcow2,,? TEST_DIR/t.qcow2 128M
|
|
|
|
|
Formatting 'TEST_DIR/t.qcow2', fmt=qcow2 size=134217728 backing_file='TEST_DIR/t.qcow2,?' encryption=off cluster_size=65536 lazy_refcounts=off
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o backing_file=TEST_DIR/t.qcow2, -o help TEST_DIR/t.qcow2 128M
|
|
|
|
|
qemu-img: Invalid option list: backing_file=TEST_DIR/t.qcow2,
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o backing_file=TEST_DIR/t.qcow2 -o ,help TEST_DIR/t.qcow2 128M
|
|
|
|
|
qemu-img: Invalid option list: ,help
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o backing_file=TEST_DIR/t.qcow2 -o ,, -o help TEST_DIR/t.qcow2 128M
|
|
|
|
|
qemu-img: Invalid option list: ,,
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 -o help
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
|
|
|
|
|
|
|
|
|
Testing: create -o help
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
|
|
|
|
|
=== convert: Options specified more than once ===
|
|
|
|
|
|
|
|
|
|
Testing: create -f qcow2 TEST_DIR/t.qcow2 128M
|
|
|
|
|
Formatting 'TEST_DIR/t.qcow2', fmt=qcow2 size=134217728 encryption=off cluster_size=65536 lazy_refcounts=off
|
|
|
|
|
|
|
|
|
|
Testing: convert -f foo -f qcow2 TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2.base
|
|
|
|
|
image: TEST_DIR/t.qcow2.base
|
|
|
|
|
file format: raw
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 0
|
|
|
|
|
|
|
|
|
|
Testing: convert -O foo -O qcow2 TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2.base
|
|
|
|
|
image: TEST_DIR/t.qcow2.base
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 196K
|
|
|
|
|
cluster_size: 65536
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: false
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o cluster_size=4k -o lazy_refcounts=on TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2.base
|
|
|
|
|
image: TEST_DIR/t.qcow2.base
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 16K
|
|
|
|
|
cluster_size: 4096
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: true
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o cluster_size=4k -o lazy_refcounts=on -o cluster_size=8k TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2.base
|
|
|
|
|
image: TEST_DIR/t.qcow2.base
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 28K
|
|
|
|
|
cluster_size: 8192
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: true
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o cluster_size=4k,cluster_size=8k TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2.base
|
|
|
|
|
image: TEST_DIR/t.qcow2.base
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 28K
|
|
|
|
|
cluster_size: 8192
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: false
|
|
|
|
|
|
|
|
|
|
=== convert: help for -o ===
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o help TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o ? TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o cluster_size=4k,help TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o cluster_size=4k,? TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o help,cluster_size=4k TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o ?,cluster_size=4k TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o cluster_size=4k -o help TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o cluster_size=4k -o ? TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o backing_file=TEST_DIR/t.qcow2,,help TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
qemu-img: Could not open 'TEST_DIR/t.qcow2.base': Could not open backing file: Could not open 'TEST_DIR/t.qcow2,help': No such file or directory
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o backing_file=TEST_DIR/t.qcow2,,? TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
qemu-img: Could not open 'TEST_DIR/t.qcow2.base': Could not open backing file: Could not open 'TEST_DIR/t.qcow2,?': No such file or directory
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o backing_file=TEST_DIR/t.qcow2, -o help TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
qemu-img: Invalid option list: backing_file=TEST_DIR/t.qcow2,
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o backing_file=TEST_DIR/t.qcow2 -o ,help TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
qemu-img: Invalid option list: ,help
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o backing_file=TEST_DIR/t.qcow2 -o ,, -o help TEST_DIR/t.qcow2 TEST_DIR/t.qcow2.base
|
|
|
|
|
qemu-img: Invalid option list: ,,
|
|
|
|
|
|
|
|
|
|
Testing: convert -O qcow2 -o help
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
|
|
|
|
|
|
|
|
|
Testing: convert -o help
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
|
|
|
|
|
=== amend: Options specified more than once ===
|
|
|
|
|
|
|
|
|
|
Testing: amend -f foo -f qcow2 -o lazy_refcounts=on TEST_DIR/t.qcow2
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2
|
|
|
|
|
image: TEST_DIR/t.qcow2
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 128M (134217728 bytes)
|
|
|
|
|
disk size: 196K
|
|
|
|
|
cluster_size: 65536
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: true
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o size=130M -o lazy_refcounts=off TEST_DIR/t.qcow2
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2
|
|
|
|
|
image: TEST_DIR/t.qcow2
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 130M (136314880 bytes)
|
|
|
|
|
disk size: 196K
|
|
|
|
|
cluster_size: 65536
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: false
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o size=8M -o lazy_refcounts=on -o size=132M TEST_DIR/t.qcow2
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2
|
|
|
|
|
image: TEST_DIR/t.qcow2
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 132M (138412032 bytes)
|
|
|
|
|
disk size: 196K
|
|
|
|
|
cluster_size: 65536
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: true
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o size=4M,size=148M TEST_DIR/t.qcow2
|
|
|
|
|
|
|
|
|
|
Testing: info TEST_DIR/t.qcow2
|
|
|
|
|
image: TEST_DIR/t.qcow2
|
|
|
|
|
file format: qcow2
|
|
|
|
|
virtual size: 148M (155189248 bytes)
|
|
|
|
|
disk size: 196K
|
|
|
|
|
cluster_size: 65536
|
|
|
|
|
Format specific information:
|
|
|
|
|
compat: 1.1
|
|
|
|
|
lazy refcounts: true
|
|
|
|
|
|
|
|
|
|
=== amend: help for -o ===
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o help TEST_DIR/t.qcow2
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o ? TEST_DIR/t.qcow2
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o cluster_size=4k,help TEST_DIR/t.qcow2
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o cluster_size=4k,? TEST_DIR/t.qcow2
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o help,cluster_size=4k TEST_DIR/t.qcow2
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o ?,cluster_size=4k TEST_DIR/t.qcow2
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o cluster_size=4k -o help TEST_DIR/t.qcow2
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o cluster_size=4k -o ? TEST_DIR/t.qcow2
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <cyliu@suse.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-06-30 10:29:58 +04:00
|
|
|
nocow Turn off copy-on-write (valid only on btrfs)
|
2014-02-21 19:24:08 +04:00
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o backing_file=TEST_DIR/t.qcow2,,help TEST_DIR/t.qcow2
|
|
|
|
|
|
|
|
|
|
Testing: rebase -u -b -f qcow2 TEST_DIR/t.qcow2
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o backing_file=TEST_DIR/t.qcow2,,? TEST_DIR/t.qcow2
|
|
|
|
|
|
|
|
|
|
Testing: rebase -u -b -f qcow2 TEST_DIR/t.qcow2
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o backing_file=TEST_DIR/t.qcow2, -o help TEST_DIR/t.qcow2
|
|
|
|
|
qemu-img: Invalid option list: backing_file=TEST_DIR/t.qcow2,
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o backing_file=TEST_DIR/t.qcow2 -o ,help TEST_DIR/t.qcow2
|
|
|
|
|
qemu-img: Invalid option list: ,help
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o backing_file=TEST_DIR/t.qcow2 -o ,, -o help TEST_DIR/t.qcow2
|
|
|
|
|
qemu-img: Invalid option list: ,,
|
|
|
|
|
|
|
|
|
|
Testing: amend -f qcow2 -o help
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
compat Compatibility level (0.10 or 1.1)
|
|
|
|
|
backing_file File name of a base image
|
|
|
|
|
backing_fmt Image format of the base image
|
|
|
|
|
encryption Encrypt the image
|
|
|
|
|
cluster_size qcow2 cluster size
|
2014-09-10 13:05:49 +04:00
|
|
|
preallocation Preallocation mode (allowed values: off, metadata, falloc, full)
|
2014-02-21 19:24:08 +04:00
|
|
|
lazy_refcounts Postpone refcount updates
|
|
|
|
|
|
|
|
|
|
Testing: convert -o help
|
|
|
|
|
Supported options:
|
|
|
|
|
size Virtual disk size
|
|
|
|
|
*** done
|