[Pkg-libvirt-maintainers] Bug#709081: libvirt-bin: virsh doesn't allow to define LVM pool with custom name.

Guido Günther agx at sigxcpu.org
Mon May 20 17:04:38 UTC 2013


On Mon, May 20, 2013 at 08:54:39PM +0400, Alexey Stupnikov wrote:
> Package: libvirt-bin
> Version: 0.9.12-11
> Severity: important
> 
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>    * What was the outcome of this action?
>    * What outcome did you expect instead?

Please answer the above questions. Add the commands you used, the output
and the pool xml.
 -- Guido

> 
> *** End of the template - remove these lines ***
> I have found that I can' create lvm pool with a name which defers from the LVM VG name.
> I have just tried to create pool and start it. Pool was created with no errors/problems (I used command 'pool-define-as POOL_NAME logical --target /dev/VG'), but when I tried to start it - it fails with the following error:
> 
> error: Failed to start pool lvm_vm
> error: internal error Child process (/sbin/vgchange -aly lvm_vm) status unexpected: exit status 5
> 
> When I created pool with a name as VG name, it started with no errors/problems. I consider it as a bug because XML file of the volume pool has different fields for the pool name and corresponding VG name.
> 

> 
> -- System Information:
> Debian Release: 7.0
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages libvirt-bin depends on:
> ii  adduser             3.113+nmu3
> ii  gettext-base        0.18.1.1-9
> ii  libavahi-client3    0.6.31-2
> ii  libavahi-common3    0.6.31-2
> ii  libblkid1           2.20.1-5.3
> ii  libc6               2.13-38
> ii  libcap-ng0          0.6.6-2
> ii  libdbus-1-3         1.6.8-1
> ii  libdevmapper1.02.1  2:1.02.74-7
> ii  libgcrypt11         1.5.0-5
> ii  libgnutls26         2.12.20-6
> ii  libnetcf1           0.1.9-2
> ii  libnl1              1.1-7
> ii  libnuma1            2.0.8~rc4-1
> ii  libparted0debian1   2.3-12
> ii  libpcap0.8          1.3.0-1
> ii  libpciaccess0       0.13.1-2
> ii  libreadline6        6.2+dfsg-0.1
> ii  libsasl2-2          2.1.25.dfsg1-6
> ii  libudev0            175-7.2
> ii  libvirt0            0.9.12-11
> ii  libxenstore3.0      4.1.4-3+deb7u1
> ii  libxml2             2.8.0+dfsg1-7+nmu1
> ii  libyajl2            2.0.4-2
> ii  logrotate           3.8.1-4
> 
> Versions of packages libvirt-bin recommends:
> ii  bridge-utils    1.5-6
> ii  dmidecode       2.11-9
> ii  dnsmasq-base    2.62-3+deb7u1
> ii  ebtables        2.0.10.4-1
> ii  gawk            1:4.0.1+dfsg-2.1
> ii  iproute         20120521-3+b3
> ii  iptables        1.4.14-3.1
> ii  libxml2-utils   2.8.0+dfsg1-7+nmu1
> ii  netcat-openbsd  1.105-7
> ii  parted          2.3-12
> ii  qemu            1.1.2+dfsg-6a
> ii  qemu-kvm        1.1.2+dfsg-6
> 
> Versions of packages libvirt-bin suggests:
> ii  policykit-1  0.105-3
> pn  radvd        <none>
> 
> -- Configuration Files:
> /etc/libvirt/qemu/networks/default.xml [Errno 2] No such file or directory: u'/etc/libvirt/qemu/networks/default.xml'
> 
> -- no debconf information



More information about the Pkg-libvirt-maintainers mailing list