virt-manager apparently uses blktap, which we have disabled in our builds, since it's a special kernel-patch/driver.

we could add it to our kernel servers (or make a specific dom0 server build)

but, it's been superseeded to blktap2 (even though no other distro has it yet), (which virt-manager doesn't use anyway).

and there's also qdisk (which is qemu-compatible), but qdisk is highly experimental. (ie: i didn't get it to work)

but, it's deemed more efficient to use lvm directly (then you don't need blktap), except that virt-manager seems to do that anyway (or it's maybe libvirtd that decides this...; whichever one makes the xml file to start up a machine)



i think that: adding blktap would be the easiest way to get things going with virt-manager, but it's not really worth the hassle of getting it in there.

or, we can try to patch virt-manager to either have a "configurable backend type" or we use direct physical devices... (which will be slow if you have file images and fast if you use lvm storage)

well, it's likely that making an xml file and using virsh would likely work, but i don't know enough about libvirt to make such an xml file just yet...

and since i can't install one with virt-manager, i can't use the xml to look at it... (it doesn't show the xml it tries in the logs)

Reproducible: 

Steps to Reproduce: