[virt-tools-list] Virt-manager doesn't attach Sheepdog storage VDI disk correctly
Dmitriy Slachshyov
slashvdm at yandex.ru
Mon Aug 10 10:08:24 UTC 2015
Cole,
I've repeated the adding process, running --debug flag.
Look at the attached file with debug messages.
On Sun, 09/08/2015 at 13:58 -0400, Cole Robinson wrote:
> On 08/03/2015 04:58 AM, Dmitriy Slachshyov wrote:
> > Hi,
> >
> > Recently, I 've installed libvirt (version 1.2.17) and sucessfully
> > attached
> > working sheepdog storage (version 0.9.2) as a pool.
> > I use virt-manager 1.2.1
> >
> > Everything looks fine. I can create and remove VDI disks in the
> > storage pool
> > without any errors.
> >
> > Everytime, when I try to connect my created VDI disk using virt
> > -manager to any
> > virtual machine, I see that my attached disk is not a disk from
> > sheepdog
> > storage. While connecting VDI storage disk, the disk creates on the
> > local file
> > system (newly created storage with full path $HOME/test).
> >
> > So, I can't attach real VDI disk from sheepdog storage to my
> > virtual machine.
> >
> > As I see, this problem appears because the sheepdog's target path
> > is NULL
> > and/or xml-parsing isn't valid for sheepdog.
> >
> > The commands at bottom of message may help you!
> >
> > # virsh pool-list
> > Name State Autostart
> > -------------------------------------------
> > default active yes
> > $MYUSER active yes # suddenly created
> > storage pool
> > while connecting sheeddog's VDI disk to.
> > LVM active yes
> > sheepdog active yes
> >
> > # virsh pool-dumpxml sheepdog
> > <pool type='sheepdog'>
> > <name>sheepdog</name>
> > <uuid>7333590b-1dcc-46e2-9af6-09c9c96af70a</uuid>
> > <capacity unit='bytes'>19414155264</capacity>
> > <allocation unit='bytes'>25198592</allocation>
> > <available unit='bytes'>19388956672</available>
> > <source>
> > <host name='192.168.100.10'/>
> > <name>sheepdog</name>
> > </source>
> > </pool>
> >
> > # virsh vol-list sheepdog
> > Name Path
> > --------------------------------------------
> > test test
> >
> > # dog vdi list -a 192.168.100.10
> > Name Id Size Used Shared Creation time VDI id
> > Copies Tag
> > test 0 8.0 GB 0.0 MB 0.0 MB 2015-08-02 00:09 7c2b25
> > 2:2
> >
> >
> > Also look at the next issue:
> >
> > - <disk type='file' device='disk'> # It's automatically
> > created by
> > virt-manager
> > + <disk type='network'> # I made it manually
> > and it works
> > <driver name='qemu' type='raw'/>
> > - <source file='$HOME/test'/>
> > + <source protocol="sheepdog" name="test"/>
> > <target dev='hda' bus='ide'/>
> > <address type='drive' controller='0' bus='0' target='0'
> > unit='0'/>
> > </disk>
>
> Thanks for the report. Please provide virt-manager --debug when
> reproducing,
> from app start to app shutdown
>
> - Cole
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: virt-manager.log
Type: text/x-log
Size: 18795 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20150810/c000312e/attachment.bin>
More information about the virt-tools-list
mailing list