Windows 10 vm slow performance

[kokoticek]

Using latest Proxmox release.

Server has CPU Xeon 4 cores 3 GHz and 10 Gb RAM.
Testing from a client with i3 2.53 GHz, 4 Gb RAM, using virt-viewer on Fedora.

I have been using a Windows 10 KVM guest for a while already, always on local network. VM has 3 Gb ballooning RAM and spice-guest-tools installed.
If using default novnc VM works acceptable.
But if using SPICE VM is rather slow in general, with constant short hangups that can make VM kind of unresponsive.

If it was, say a VM installed locally through libvirt, slow VM would make sense given client's specs. But this is not the case.

Is Spice affecting client's performance, still when VM guest is not even installed locally but in a server?
Or any other ideas?
Thanks.

 

[kokoticek]

Excuse me, any ideas?
I'm still not able to debug this...

 

[Ashley]

Is the VM itself sluggish or the Spice Console?

Have you tried RDP directly to the Windows VM? Is the performance the same then or does the slowness go away?

 

[kokoticek]

As I already posted, if using default novnc VM works ok, just with its slight lags.

Haven't tried RDP, but already given this I would think it's the Spice console the one making it sluggish and unresponsive at times, when it should be the exact opposite!

 

[killmasta93]

whats ur FSYNC? when you mean acceptable as in regular? or eh not so bad but could be better?

 

[kokoticek]

Could it be SPICE client (virt-viewer), despite being *just* the client, is actually also dependent of client PC's hardware itself for performance?