Description of problem: Setting up a host with drdb on top of lvm, then handling these devices as block devices to kvm has several advantages, but one big disadvantage: libvirt does not know anything about drbd, as does virt-manager. It is not possible to define a pool of drbd for example Version-Release number of selected component (if applicable): libvirt 0.8.8 virt-manager 0.8.6 How reproducible: Allways Steps to Reproduce: 1. install libvirt, virtmanager 2. create lvm block devices with same size on two hosts 3. configure a drbd 4. create a new VM, assign the created lvm-device 5. change the lvm device to the created drbd, by editing the domains config file ("virsh edit <domain>". Search for /dev/<your vg>/<your lv>. Replace with /dev/drbd/by-res/<your drbd-name> 6. start the domain. It'll use the drbd. Actual results: Expected results: Additional info: Would be nice if virt-manager and libvirt know about drbd's.
I don't really know anything about drbd, but any feature requests like this usually start at the libvirt level. Reassigning
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I still don't know what this entails, but either way probably best suited for the upstream tracker
Libvirt supports several distributed block stores now: ceph/rbd, gluster, sheepdog. Tracking drbd support here isn't going to yield any results unfortunately, someone needs to show up and provide the patches. So closing this as DEFERRED