Christian, thank you for pointing me in the right direction. Adding
filter = [ "a|/dev/disk/by-path/pci-*|" ]
to /etc/lvm/lvm.conf solved this issue. (There is no need to restart any
service after changing this file. ;))
You can find the thread on the mailing list under this link:
I now used:
filter =[ "a|/dev/disk/by-path/virtio-pci-*|" ]
Now it really is the same way on creation and query.
$ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0
Physical volume "/dev/disk/by-path/virtio-pci-:00:07.0" successfully
created.
$ sudo pvdisplay
This is again a case of please read all characters carefully :-)
definition from xml:
(gdb) p def->source.devices[i].path
$4 = 0x7f5204008e30 "/dev/disk/by-path/virtio-pci-:00:07.0"
compared against the array it built with the lvm tools
(gdb) p thisSource->devices[0]
$7 = {nfreeExtent = 0,
lvm2 - config option intentionally starting safe, how to use it is outlined =>
invalid
libvirt - IMHO it should now work, need to debug more and wait for the
mentioned upstream discussion => incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That is in fact a LVM limitation of the default config that is targetted
at low multi-scanning and general compatibility with older setups.
You'll find in /etc/lvm/lvm.conf a disabled line like:
# filter = [ "a|.*/|" ]
That means that it will consider /dev/* but not more - in particular not
Error on starting the device:
error : virStorageBackendLogicalMatchPoolSource:692 : unsupported
configuration: cannot find any matching source devices for logical volume group
'testpool1'
That error from the log matches the error in the UI of virsh.
The reason is that even thou it was
6 matches
Mail list logo
