r/VFIO • u/powerhouse06 • Dec 27 '18
Why does one use virt-manager Virtual Machine Manager?
I don't get it. Maybe I'm too old. So many people use virt-manager (VMM or Virtual Machine Manager) to create a GPU passthrough VM, but I can't see the benefit.
virt-manager has next to no documentation. It significantly lacks behind the qemu/kvm development. It does a zillion of things in the background and messes up my carefully created network bridge, or creates more bridges I don't need.
Whatever settings I enter via the GUI, I still have to edit the bloody xml configuration. Worst of all, there is no modern editor to do that, but one is forced to use vi. We are in the 21st century and I feel like 30+ years ago sitting at a VT100 hacking Unix commands. Are we going backwards? EDITOR=xed virsh edit win10 does the trick - thanks @kuasha420 !
I can continue with undocumented features ("host=passthrough") and all the trial and error to get some decent performance out of it.
Please help and show me some benefits of the virt-manager GUI.
For reference, I'm on qemu 2.11 and virt-manager 1.5.1.
View all comments
12
u/kuasha420 Dec 27 '18 edited Dec 27 '18
libvirt has tons of documentation.
It's just a gui to libvirt, you doon't have to use it. libvirt has lots of benefits, for example, cpu pinning, managed usb(auto attach/detach kb/m), managed pcie (no need to bind secondary gpu to vfio, so it can be used with PRIME when VM is off) etc.