3 ms·
Indeed. Instead of contributing a patch to qemu with better defaults, or even support for config files, someone wrote tens of thousands of lines of complex code
by ori_b 8y ago
Indeed. Instead of contributing a patch to qemu with better defaults, or even support for config files, someone wrote tens of thousands of lines of complex code.
People forget that software is malleable. Bend it to your needs, instead of adding fragile wrapper layers.
- LukeShu 8y agolibvirt-the-software is tens of thousands of lines of complex code that doesn't really add much. libvirt-the-project does contribute patches in to qemu, and a lot of the reason that libvirt-the-software doesn't add much of value is because libvirt-the-project worked to get capabilities in to upstream qemu. The libvirt team definitely does view qemu as malleable, and bends it to their needs. The problem is that the libvirt authors contributing to qemu look at qemu as a machine-interface (to be consumed by libvirt), not as a human-interface. Many of the more poorly documented or otherwise difficult-for-humans flags were contributed by the libvirt team. And they're useful! They make it so qemu can do things it couldn't do before. But they're also kinda the reason qemu is difficult to use without libvirt.
- JoshuaRLi 8y agoGood observations! I can't say I like it when a wrapper (loosely said here) starts to exert too much influence over what it wraps.