3 ms·
On the contrary, I haven't manually touched a QEMU/KVM config in a few years because of the above tooling and Proxmox. I think there was a handful of times I ne
by 0x1ch 2y ago
On the contrary, I haven't manually touched a QEMU/KVM config in a few years because of the above tooling and Proxmox. I think there was a handful of times I needed to add manual additions.
- topspin 2y agoWell, I got past being dazzled by QEMU machine config files years ago. They're actually rather simple. Once you grasp dealing with QEMU at that level its a short, and possibly dubious step, to just CLI-ing everything. The GUI tools are efficient for picking up on new capabilities as QEMU/KVM evolves with time. I've been known to just start VMs from the CLI directly, for experimental purposes. The tooling everyone uses (Proxmox, virt-*, etc.) obscures the fact that spawning a VM is just a command with a bunch of switches. I suppose that familiarity for me came from using QEMU to emulate other archs on x86 for embedded development purposes: launching ARM VMs, for example.