Description of problem:
The memory usage of the virt-launcher process on virt-launcher pod is growing and may lead to OOMKilled pods:

> # VM started:
> qemu 10 0.1 0.2 2002312 60872 ? Sl 22:15 0:04 /usr/bin/virt-launcher --qemu-timeout 253s --name vm-fedora --uid 6b181371-7c41-4783-8f8f-a

> # 12hrs
> qemu 10 0.1 0.2 2002312 67952 ? Sl May16 0:58 /usr/bin/virt-launcher --qemu-timeout 253s --name vm-fedora --uid 6b181371-7c41-4783-8f8f-a

> # 48hrs
> qemu 10 0.1 0.2 2002312 70528 ? Sl May16 3:06 /usr/bin/virt-launcher --qemu-timeout 253s --name vm-fedora --uid 6b181371-7c41-4783-8f8f-a

> # And after 5 days it has exceeded the 75MB limit:
> qemu 10 0.1 0.3 2002312 77364 ? Sl May16 9:28 /usr/bin/virt-launcher --qemu-timeout 253s --name vm-fedora --uid 6b181371-7c41-4783-8f8f-a

Version-Release number of selected component (if applicable):
4.11

How reproducible:

Steps to Reproduce:
1. run VM with stress for a long time
2. check memory
3.

Actual results:
Memory usage of virt-launcher is growing and may exceed the limit

Expected results:
Memory usage is under the limit

Additional info: