4 ms·

Rather than using QEMU by itself, it might be advisable to use libvirt..? As somewhat of a newbie to virtualization, that's how I started - googling how to use

Rather than using QEMU by itself, it might be advisable to use libvirt..? As somewhat of a newbie to virtualization, that's how I started - googling how to use libvirt and virsh, and I found a lot of resources that helped me to deploy what I needed... What are your painpoints in particular? I.e. which topics would you like to explore deeper and can't due to poor documentation/resources? We could work on improving the resources.

babuskov 8y ago
> What are your painpoints in particular? I believe his pain point is that with Virtual Box you get a very simple GUI where you can get VM up and running very quickly without having to use Google or read any guides at all.
- BossingAround 8y ago
  For that, I use 'Virtual Machine Manager' [1], which works for me extremely well, and is available for major distros. [1] https://virt-manager.org/ https://virt-manager.org/
- philpem 8y ago
  Well, qemu + libvirt + virt-manager works pretty well. Virt-manager adds a very nice VirtualBox-style GUI front-end to libvirt.
- carlavilla 8y ago
  You can use QtEmu (https://gitlab.com/qtemu https://gitlab.com/qtemu)
qalmakka 8y ago
I personally dislike libvirt a lot, and virsh in particular. I think that it's pointlessly complicated and burdensome to use, and that in general the hypervisor-agnosticabstractions provided by libvirt are nullified by the fact that no backend except Qemu really works well, this making them a pointless exercise in futility.
- jezze 8y ago
  I agree with you whole-heartedly. Instead of running one simple qemu command for each vm you instead have hundreds of lines of xml split into many different files. Files you need to run through libvirts session manager that needs to implements its own pretty pointless state management (this could be handled by systemd instead). If there is a nice feature in qemu you want to use, not only do you need to know how to define it in libvirts xml, it might not even be supported at all.

babuskov 8y ago

> What are your painpoints in particular? I believe his pain point is that with Virtual Box you get a very simple GUI where you can get VM up and running very quickly without having to use Google or read any guides at all.

BossingAround 8y ago
For that, I use 'Virtual Machine Manager' [1], which works for me extremely well, and is available for major distros. [1] https://virt-manager.org/ https://virt-manager.org/
philpem 8y ago
Well, qemu + libvirt + virt-manager works pretty well. Virt-manager adds a very nice VirtualBox-style GUI front-end to libvirt.
carlavilla 8y ago
You can use QtEmu (https://gitlab.com/qtemu https://gitlab.com/qtemu)

qalmakka 8y ago

I personally dislike libvirt a lot, and virsh in particular. I think that it's pointlessly complicated and burdensome to use, and that in general the hypervisor-agnosticabstractions provided by libvirt are nullified by the fact that no backend except Qemu really works well, this making them a pointless exercise in futility.

jezze 8y ago
I agree with you whole-heartedly. Instead of running one simple qemu command for each vm you instead have hundreds of lines of xml split into many different files. Files you need to run through libvirts session manager that needs to implements its own pretty pointless state management (this could be handled by systemd instead). If there is a nice feature in qemu you want to use, not only do you need to know how to define it in libvirts xml, it might not even be supported at all.