On 08/15/2015 02:21 AM, Dmitriy Slachshyov wrote: > On Tue, 11/08/2015 at 10:02 -0400, Cole Robinson wrote: >> Can you provide XML for a _working_ volume after it's been defined? > No, unfortunately I can't to get working XML. Every time when I try to > create a volume from XML-file through the `virsh vol-create` command, I > get another XML-output when I type `virsh vol-dumlxml` after successful > creation of volume. > > As I guess, the reason is in the libvirt only! > >> The example XML from the link you provide, which is what we have in >> our >> testsuite, has some confusing bits: >> >> - If specifies <key> but that's a readonly field. So I'm interested >> to see >> what libvirt outputs for a working volume > I'am also interested to see that! I am not a maintainer of sheepdog > > >> - The volume path is 'sheepdog:myvol'. Is 'sheepdog:' just a protocol >> specified, like http://, or does it reference the pool name? >> - Also, from looking at the libvirt code, it seems <target><path> is >> readonly >> as well, so whatever virt-manager specifies is just thrown out. So >> I'm curious >> to see what libvirt spits out for a working volume >> >> Also please put all this in a bug report. Starting tomorrow I'm > > How can I put a request to a bug report? > Please file a virt-manager upstream bug as described here: https://virt-manager.org/bugs/ I'll get to it when I can >> offline for >> two weeks, I want to make sure this info doesn't get lost in the mail >> shuffle >> when I come back > > > Look at attached output as a possible evidence: > Thanks, that info looks interesting, but I guess I'll probably need to set up a sheepdog server to figure out the root issue, I think libvirt needs a bug fix. Thanks, Cole _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
