Public bug reported:
Please report to https://bugzilla.redhat.com/show_bug.cgi?id=659262 for more
information.
This Bug has a patch as in:
http://www.redhat.com/archives/libvir-list/2010-December/msg00103.html
Description of problem:
If you do not specify the type of the disk in the <driver> subelement of domain
xml, virsh automatically inserts type raw, without testing for the real type of
the image.
Version-Release number of selected component (if applicable):
virsh 0.8.3
( Debian-backports 0.8.3-4~bpo50+1 )
How reproducible:
Everytime
Steps to Reproduce:
1.
Create a domain from a xml which disks have no <driver> element:
(SNIP /tmp/one-7050.xml)
<disk type='file' device='disk'>
<source file='/var/lib/one/7035/images/disk.0'/>
<target dev='hda'/>
<model type='virtio'/>
</disk>
(SNIP)
$ onevm create /tmp/one-7035.xml
2.
Dump the xml of the domain:
$ onevm dumpxml one-7035
(SNIP)
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/var/lib/one/host1/images/disk.0'/>
<target dev='hda' bus='ide'/>
<alias name='ide0-0-0'/>
<address type='drive' controller='0' bus='0' unit='0'/>
</disk>
(SNIP)
Actual results:
<driver name='qemu' type='raw'/>
AND domain cannot boot from the disk
Expected results:
<driver name='qemu' type='qcow2'/> # or nothing at all
AND domain would boot as a charm.
Additional info:
This would be not a problem by manual generation of the domain xml file, since
we could simply insert it.
The problem will treat bad if we have a VMM generating this xml automatically..
as it is our fall, as we are using opennebula for this.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684127
Title:
virsh adds automatically type='raw' to a disk session
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
