Or also the myth that no OS nor general PC hardware likes odd amount of RAM? But when trying connecting through SPICE I got the very same issues as the libvirt guest, only difference being not hitting openSUSE host’s performance.īoth Windows guests are Windows 10 1703, and both have spice-guest-tools installed (obviously).Ĭould it really be SPICE hits client’s performance, still when VM guest is not even installed locally but in a remote server? Proxmox uses noVNC console for guests by default, and this one works relatively fine for the Windows guest (testing on openSUSE’s Firefox). Now I always blamed laptop’s specifications (Core i3 2.5 GHz, 4 Gb RAM DDR3, 500 Gb SATA HDD, 3 Gb RAM located for guest with ballooning), until I tested connecting to another Windows 10 KVM guest from a Proxmox server (on local LAN), also with 3 Gb RAM ballooning.
After having used Windows 10 KVM guest (locally installed through libvirt) for a longer time and tried few other features -including screenshots, webcam passthrough and snapshots-, I’m concluding VM is “usable”, but not “very usable”.Īt times in general VM is rather slow, constant -albeit rather brief- hangups, not to mention it makes openSUSE host itself kind of unresponsive.
0 kommentar(er)
