Because they are for different use cases. I use QEMU+KVM on desktop for games and 3D CAD software, because of its undeniable performance advantage. But on work laptop, I use VirtualBox to test my software on different platforms. On VirtualBox it’s relatively easy to initialize a VM, configure network, file sharing and device passthrough, and its snapshot feature allows me recreate the same environment for troubleshooting
I just looked them up and maybe you are right. But QEMU definitely lacks a GUI config tool that is both easy to use and allows for advanced features like snapshots. So far the only ones I know is GNOME Boxes and Virt Manager, and neither is as good as providing handy ways to configure as VirtualBox. I could probably just write the XML config or QEMU command by the documentation, but next time it could be a different scenario so I have to investigate the docs and maybe a few more forum posts. In VirtualBox, the buttons that do everything for me are always there
It literally does everything you mentioned, including allowing you to edit the XML files manually to reach advanced or obscure features that are not exposed.
Because they are for different use cases. I use QEMU+KVM on desktop for games and 3D CAD software, because of its undeniable performance advantage. But on work laptop, I use VirtualBox to test my software on different platforms. On VirtualBox it’s relatively easy to initialize a VM, configure network, file sharing and device passthrough, and its snapshot feature allows me recreate the same environment for troubleshooting
All this is true using Virt-Manager… Especially if you use the qemu-guest-agent.
I just looked them up and maybe you are right. But QEMU definitely lacks a GUI config tool that is both easy to use and allows for advanced features like snapshots. So far the only ones I know is GNOME Boxes and Virt Manager, and neither is as good as providing handy ways to configure as VirtualBox. I could probably just write the XML config or QEMU command by the documentation, but next time it could be a different scenario so I have to investigate the docs and maybe a few more forum posts. In VirtualBox, the buttons that do everything for me are always there
Let me say it louder for the people in the back: https://virt-manager.org/
It literally does everything you mentioned, including allowing you to edit the XML files manually to reach advanced or obscure features that are not exposed.
Last time I tried Virt manager, I couldn’t figure out bridge networks and ended up corrupted the XML config for the VM. Skill issue for me I guess
im a networking idiot so apologies if this doesnt work for your needs
if you leave the NAT virtual NIC and add a 2nd one, type MACVTAP, make device name your real NIC (ento1 for me).
Now you can access guest on your host and on other LAN devices without needing a bridge
(Spent yesterday figuring this out)