| Perhaps you have something eating into RAM of the host. I had my host freezing when I forgot to limit memory utilization in the ZFS. It does not matter what eats into your host RAM - since qemu is just a regular userspace process, it's memory needs (ie those of the guest system) are not "prioritized" as more essential than any other userspace process. If your host does not have enough memory, then the more you allocate in qemu (or libvirt) to the guest system, the more probability that qemu will run out of RAM, effectively freezing the guest OS. At least, this is what it would appear to be (it might be simply swapping, but that slows down guest execution speed by orders of magnitude, so it is effectively frozen) B.
Very very very things. If i set more than 2GB Memory Ram in Virt-Manager for the Guest, i have artefacts and freeze. If I set 2GB like actually, the guest works perfectly. So i don't know if it will be good for gaming even if i set Windows swap to 10GB ... 2016-10-07 19:43 GMT+02:00 Jayme Howard <g.pr...@gmail.com>:
| ||
_______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
