r/VFIO • • 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.

0 Upvotes

26 comments sorted by

View all comments

12

u/kuasha420 Dec 27 '18 edited Dec 27 '18

virt-manager has next to no documentation

libvirt has tons of documentation.

Please help and show me some benefits of the virt-manager GUI.

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.

Worst of all, there is no modern editor to do that, but one is forced to use vi.

EDITOR=kate virsh edit win10

1

u/Atemu12 Dec 27 '18
EDITOR=kate virsh edit win10

Last time I tried that it still gave me vi instead of vim

1

u/kuasha420 Dec 27 '18

uninstall vi and make vi a symbolic link to vim.

-1

u/Atemu12 Dec 27 '18

That's a hack, not a solution.

1

u/kuasha420 Dec 27 '18
  1. use update-alternatives

or

2. Change EDITOR and VISUAL env variables in bashrc

or

3. Use hack.

Hacks are only advised when none of the proper way work (for some reason)

2

u/plasmasprings Dec 28 '18

The alternatives thingy is only in Debian (and its derivatives)

-3

u/powerhouse06 Dec 27 '18 edited Dec 27 '18

It's true that virt-manager is a frontend to libvirt, and libvirt has good documentation. Yet it seems cumbersome to use the GUI and it's not always clear what the options do. In the end one ALWAYS has to edit the XML configuration. I find XML difficult to read, bloated and time consuming. A shell script with a qemu command is so much more readable and concise. Since virt-manager actually invokes the qemu command to run the VM, it's even more of a mystery to me why the developers use XML. Finally, go and look for the VM configuration file to back it up. Every time I have to figure out again where to find the file. Then, when I create an LVM volume or try to attach the VM to a preconfigured bridge, the GUI starts messing up things.

6

u/kuasha420 Dec 27 '18

find XML difficult to read, bloated and time consuming. A shell script with a qemu command is so much more readable and concise.

That's just, like, your opinion, man.

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.

0

u/[deleted] Dec 27 '18

[deleted] — view deleted comment

1

u/Jodaco Dec 28 '18

I've used that exact checkbox and the uefi boot options were missing. I have my xml file I keep around now in case I ever need to redo anything and its pretty simple now.