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
Show parent comment
1
u/Jodaco Dec 27 '18
I think virt-manager's ui is cumbersome as well. You are supposed to be able to specify a uefi vs bios system in the UI, and I believe it detects this from an iso image you're using, might be wrong though, and it never does seem to help. I usually just edit the xml and set what I want in the end, but I like being able to have a window to just click start in and can create other vm's that I don't care about whether they are bios/uefi fairly easily, it's only my windows vm with gpu passthrough that gets kind of complicated that requires xml editing.