(add your name here) |
(Advanced aspects) |
||
| Line 17: | Line 17: | ||
=== Who's available === | === Who's available === | ||
[[User:Crobinso|Cole Robinson]] and [[User:Kwolf|Kevin Wolf]] are your hosts for today. | [[User:Crobinso|Cole Robinson]] and [[User:Kwolf|Kevin Wolf]] (IRC nick kwolf, GMT+2h) are your hosts for today. | ||
The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion: | The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion: | ||
| Line 36: | Line 36: | ||
# [[QA:Testcase qemu-img convert from raw to qcow2]] | # [[QA:Testcase qemu-img convert from raw to qcow2]] | ||
# [[QA:Testcase qemu-img create snapshot]] | # [[QA:Testcase qemu-img create snapshot]] | ||
=== Advanced aspects === | |||
If you want to play a bit more with qcow2 and the test cases suggested above are not enough for you, there are some additional features that cannot be accessed with the management tools (so they are not top priority to be tested), but you still can use them by invoking qemu-img and qemu manually. | |||
When creating images with qemu-img, you can change some default options using the -o parameter. For example you could create a fairly non-standard image using <code>qemu-img create -f qcow2 -o encryption,cluster_size=32k,backing_file=base.vmdk image.qcow2 10G</code>. To get an overview of the supported options, you can use <code>qemu-img create -f qcow2 -o ?</code>. | |||
The following list contains some suggestions on what you could test: | |||
* Encrypted images (<code>-o encryption</code>) | |||
* Varying cluster sizes (<code>-o cluster_size=size</code> where size is between 512 and 64k). Smaller cluster can save some space on almost empty disks, larger clusters are faster usually. | |||
* Backing files (<code>-o backing_file=file</code>). The new image is based on the given backing file and only differences are saved into the qcow2 file. Try usinh different formats for the backing file, it doesn't need to be qcow2. | |||
* Commit back the changes from a qcow2 image to its backing file (<code>qemu-img commit</code> or the <code>commit</code> command in the qemu monitor) | |||
* Compressed images: When converting an image, you can have the resulting qcow2 image compressed (<code>qemu-img convert -O qcow2 -c ...</code>) | |||
* Combine things: Snapshots on an encrypted image with a compressed backing file... | |||
=== Issues that were identified === | === Issues that were identified === | ||
Revision as of 16:01, 16 September 2009
| DATE | TIME | WHERE |
| Thursday Sep 17, 2009 | All day | #fedora-test-day (webchat) |
What to test?
This part of today's Fedora Test Day will focus on testing virt-manager, libvirt and qemu-kvm support for the qcow2 image format.
This is related to the KVM qcow2 Performance feature in Fedora 12. If we're to advertise the format's improved performance, we better test that people can use the format!
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test qcow2 support and provide feedback.
Who's available
Cole Robinson and Kevin Wolf (IRC nick kwolf, GMT+2h) are your hosts for today.
The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion:
- add your name here
What's needed to test
- A fully updated Fedora 12 Rawhide machine. See instructions on the main test day page.
- At least one guest image installed before the test day (suggested reading - Virtualization_Quick_Start)
Test Cases
Things to test, roughly in dependency order:
- QA:Testcase virt-install using qcow2
- QA:Testcase virt-manager install using qcow2
- QA:Testcase qemu-img convert from raw to qcow2
- QA:Testcase qemu-img create snapshot
Advanced aspects
If you want to play a bit more with qcow2 and the test cases suggested above are not enough for you, there are some additional features that cannot be accessed with the management tools (so they are not top priority to be tested), but you still can use them by invoking qemu-img and qemu manually.
When creating images with qemu-img, you can change some default options using the -o parameter. For example you could create a fairly non-standard image using qemu-img create -f qcow2 -o encryption,cluster_size=32k,backing_file=base.vmdk image.qcow2 10G. To get an overview of the supported options, you can use qemu-img create -f qcow2 -o ?.
The following list contains some suggestions on what you could test:
- Encrypted images (
-o encryption) - Varying cluster sizes (
-o cluster_size=sizewhere size is between 512 and 64k). Smaller cluster can save some space on almost empty disks, larger clusters are faster usually. - Backing files (
-o backing_file=file). The new image is based on the given backing file and only differences are saved into the qcow2 file. Try usinh different formats for the backing file, it doesn't need to be qcow2. - Commit back the changes from a qcow2 image to its backing file (
qemu-img commitor thecommitcommand in the qemu monitor) - Compressed images: When converting an image, you can have the resulting qcow2 image compressed (
qemu-img convert -O qcow2 -c ...) - Combine things: Snapshots on an encrypted image with a compressed backing file...
Issues that were identified
| Tester | Description | Bug references | Status |
| #XXXXX | ASSIGNED |