[Pkg-libvirt-maintainers] Bug#676328: Bug#676328: libvirt-bin: Migration with network disk failed (Invalid relative path)

Guido Günther agx at sigxcpu.org
Wed Jun 6 09:57:18 UTC 2012


Hi,
On Wed, Jun 06, 2012 at 10:00:11AM +0200, Bastian Scholz wrote:
> Package: libvirt-bin
> Version: 0.9.12~rc2-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I use libvirt with kvm and sheepdog for block devices. Since an update from
> 0.9.6-2 to 0.9.11.3-1 (and now for testing 0.9.12~rc2) I cant migrate my
> virtual machines between different hosts.
> With the older Version it works flawlessly.
> 
> # virsh migrate --live virt-name qemu+ssh://server-name/system
> error: Invalid relative path 'virt-name': Invalid argument
> 
> Excerpt from config
>     <disk type='network' device='disk'>
>       <driver name='qemu' type='raw'/>
>       <source protocol='sheepdog' name='virt-name'>
>         <host name='localhost' port='7000'/>
>       </source>
>       <target dev='vda' bus='virtio'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
>     </disk>
> 
> (My virtuall machines and sheepdog vdi names are identic)
> 
> I found a short description of the same problem an the mailing list,
> but I didnt find a solution...

Please see

http://wiki.debian.org/libvirt/Debugging

for necessary logs to look into such kind of problems.
Cheers,
 -- Guido

> 
> https://www.redhat.com/archives/libvirt-users/2012-May/msg00088.html
> 
> -- System Information:
> Debian Release: wheezy/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.2.0-2-amd64 (SMP w/12 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages libvirt-bin depends on:
> ii  adduser             3.113+nmu2
> ii  gettext-base        0.18.1.1-8
> ii  libavahi-client3    0.6.31-1
> ii  libavahi-common3    0.6.31-1
> ii  libblkid1           2.20.1-5
> ii  libc6               2.13-32
> ii  libcap-ng0          0.6.6-1
> ii  libdbus-1-3         1.5.12-1
> ii  libdevmapper1.02.1  2:1.02.67-2
> ii  libgcrypt11         1.5.0-3
> ii  libgnutls26         2.12.19-1
> ii  libnetcf1           0.1.9-2
> ii  libnl1              1.1-7
> ii  libnuma1            2.0.8~rc3-1
> ii  libparted0debian1   2.3-9.1
> ii  libpcap0.8          1.2.1-3
> ii  libpciaccess0       0.13.1-2
> ii  libreadline6        6.2-8
> ii  libsasl2-2          2.1.25.dfsg1-4
> ii  libudev0            175-3.1
> ii  libvirt0            0.9.12~rc2-1
> ii  libxenstore3.0      4.1.2-6
> ii  libxml2             2.7.8.dfsg-9.1
> ii  libyajl2            2.0.4-2
> ii  logrotate           3.8.1-4
> 
> Versions of packages libvirt-bin recommends:
> ii  bridge-utils    1.5-3
> ii  dmidecode       2.11-9
> ii  dnsmasq-base    2.61-1
> ii  ebtables        2.0.9.2-2.1
> ii  gawk            1:4.0.1+dfsg-2
> ii  iproute         20120319-1
> ii  iptables        1.4.13-1.1
> ii  libxml2-utils   2.7.8.dfsg-9.1
> ii  netcat-openbsd  1.105-6
> ii  parted          2.3-9.1
> ii  qemu            1.0.1+dfsg-1
> ii  qemu-kvm        1.0+dfsg-11
> 
> Versions of packages libvirt-bin suggests:
> pn  policykit-1  <none>
> pn  radvd        <none>
> 
> -- no debconf information
> 
> 
> 
> _______________________________________________
> Pkg-libvirt-maintainers mailing list
> Pkg-libvirt-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
> 





More information about the Pkg-libvirt-maintainers mailing list