virt-clone fails with: Unknown driver 'iso'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* unable to use util storage users (like virt-clone) to process iso files
through qemu-img
* an example is "virt-clone -o test-vm -n cloned-vm --auto-clone"
* Fix by backporting upstream fix
[Test Case]
* UVT Based test
$ uvt-simplestrea
$ uvt-kvm create test-vm release=xenial arch=amd64
$ virsh destroy test-vm
$ virt-clone -o test-vm -n cloned-vm --auto-clone
[Regression Potential]
* This fix is upstream a while now, so it should be fairly safe.
In general any user of virStorageBacke
be affected (that is the function we change the behavior).
It's purpose is to convert a volume to a qemu-img call (to clone it).
Without the fix some image types fail.
- users cloning type iso today fail, this is fixed by the change
- the change does not effect other types than "iso"
- there is only one user of this function (in the same file, so not too
much alternative ways to invoke we have to consider).
[Other Info]
* n/a
----
Cloning a uvt VM fails with error: Unknown driver 'iso'
To reproduce:
uvt-simplestrea
uvt-kvm create test-vm release=xenial arch=amd64
virsh destroy test-vm
virt-clone -o test-vm -n cloned-vm --auto-clone
Which results in:
WARNING The requested volume capacity will exceed the available pool space when the volume is fully allocated. (8192 M requested capacity > 3898 M available)
Allocating 'cloned-vm.qcow' | 8.0 GB 00:00:01
ERROR Couldn't create storage volume 'test-vm-
'
Upsttream fix: https:/ /www.redhat. com/archives/ libvir- list/2017- March/msg00259. html