Re: [libvirt] [RFC] Fix https://bugzilla.redhat.com/show_bug.cgi?id=461931

On Fri, Apr 12, 2013 at 5:20 PM, Osier Yang <jyang(a)redhat.com&gt; wrote: > On 12/04/13 16:02, harryxiyou wrote: >> Hi Osier, >> >> From the actual bug messages like fowllowing >> >> Actual results: >> Traceback (most recent call last): >> File "/usr/share/virt-manager/virtManager/createvol.py", line 191, >> in _async_vol_create >> poolobj = self.vol.install(meter=meter) >> File "/usr/lib/python2.5/site-packages/virtinst/Storage.py", line >> 893, in install >> (self.name, str(e))) >> RuntimeError: Couldn't create storage volume >> 'virt-stor-dir-bochs.img': '/usr/bin/qemu-img exited with non-zero >> status 1 and signal 0' >> >> >> It seems that libvirt calls command 'qemu-img' to create a volume of bochs >> but >> it failed. So the problem may no matter with Libvirt itself. I am not >> sure if qemu >> supports to create a volume of bochs. Or something wrong with QEMU? > > You didn't understand meaning of the bug, the root request here is the > capability support for storage driver (like virsh capabilities for the > hypervisor > drivers, e.g. what pool types it supports, what volume types each pool type > supports, even may what operations/APIs the pool type support, ...etc). > Yup, i think these are more deserved for Libvirt storage driver. And it is different from Michal's project. Should i come up with these ideas for GSOC 2013?