On 01/15/2014 10:36 PM, Piotr Karbowski wrote:
Hello,
On 01/15/2014 11:03 AM, Michael S. Tsirkin wrote:
Could you explain how you measure that exactly?
I check the resident memory (RES) of qemu-system-x86_64 proces.
Yes, this should not happen.
One interesting thing to try would be switc
Hello,
On 01/15/2014 11:03 AM, Michael S. Tsirkin wrote:
Could you explain how you measure that exactly?
I check the resident memory (RES) of qemu-system-x86_64 proces.
Yes, this should not happen.
One interesting thing to try would be switching device type from
virtio-net to e1000.
This
On Fri, Jan 10, 2014 at 12:00:31AM +0100, Piotr Karbowski wrote:
> Hello,
>
> kernel 3.12.5, qemu-1.7.0.
>
> With vhost=on, qemu shortly after start uses all its assigned memory
> (2G for example), without vhost-net enabled it does not go to more
> than 200 MB on my idling test virtual machine.
On Fri, Jan 10, 2014 at 12:00:31AM +0100, Piotr Karbowski wrote:
> kernel 3.12.5, qemu-1.7.0.
>
> With vhost=on, qemu shortly after start uses all its assigned memory
> (2G for example), without vhost-net enabled it does not go to more
> than 200 MB on my idling test virtual machine. 100% reproduc
Hello,
kernel 3.12.5, qemu-1.7.0.
With vhost=on, qemu shortly after start uses all its assigned memory (2G
for example), without vhost-net enabled it does not go to more than 200
MB on my idling test virtual machine. 100% reproducable. I think its not
how it should be.
Full command:
/usr/bi
