Another new-KDE annoyance. I have 20+ QEMU VMs (just converted from VirtualBox) and all but the KDE ones start the spice-vdagent app upon user login. Spice installs its user startup .desktop file in /etc/xdg/autostart, but for some unknown reason it will not run on KDE unless I open a terminal and manually run it. Note, this is not about the spice-vdagentd.service; this starts, along with the listening socket, just fine. It’s just the userspace spice-vdagent that won’t.
Any ideas??? I ran into similar problems with VMware’s open-vm-tools; that one was never solved.
I use virtualbox a lot and vmware. I always have issues with qemu for one reason or another. One i don’t like is it’s too difficult to get the screen size working i want. On vmware or v-box it is a always correct and done very easily on boot. The screen size matches my monitor size and or adjust appropriately on the fly.
Another issue is getting it to work sometimes without black screen.
I’ve used all (3) at various times, even paid for VMware WS Pro, but I always end up back with QEMU. Other than KDE issues with starting services (or phantom services), the only other problem I’ve ever encountered with QEMU is that xfwm4 does not like to resize the desktop, at least not until a user logs off/on again. In my experience, VMware’s support is not good, and VirtualBox’s documentation is full of features that were sunsetted/abandoned without updating.
Overall, these are all good systems; can’t imagine how hard it must be to maintain something that needs to work with so many different OS’s from gods-know how many years ago.
For me, the original reason was learning, kinda like I tried (and failed) to build a working Gentoo system. Now I have (3) Gentoo systems working and would switch there if EOS/Arch ever kicked the bucket.
QEMU’s interface is definitely lacking compared to the other 2.