Displaying 4 results from an estimated 4 matches for "elementsmemorytuning".
2013 Aug 09
0
Re: libvirt possibly ignoring cache=none ?
...qemu/i-000009fa:
> memory.limit_in_bytes: 13215727616
> memory.usage_in_bytes: 12998287360
>
You can get rid of these problems by setting your own memory limits.
The defaults limit get set only if there is no <memtune> setting in the
domain XML: http://libvirt.org/formatdomain.html#elementsMemoryTuning
> The 4G difference is the cache. That's why I'm so interested in what
> is consuming the cache on a VM which should be caching in guest only.
>
> Regards,
>
> Brano Zarnovican
>
Hope this helps,
Martin
2018 Aug 01
3
LXC Memory Limits wont work
Hello,
iam currently trying to run LXC Containers with libvirt
but the memory limit doesn't want to work
in the container i see the full 32GB from the Host OS
iam pretty sure that iam missing a configline in the xml
lxc-template ~ # free -m
total used free shared buff/cache
available
Mem: 32108 626 31396 249 85
2011 Oct 05
1
Performance tuning questions for mail server
...the guest and host.
Load on the server is regularly above 20, yet the processors generally
are idle and the host is still responsive.
Should the concentration of the performance tuning be done on the
guest or the host? I've read through the information at
http://libvirt.org/formatdomain.html#elementsMemoryTuning but I don't
know how the settings apply to my configuration and which ones apply
to my hardware.
I've included my libvirt xml config below. It was built using
virt-manager on fedora15. There appears to be quite a few other
options that are available and not provided by virt-manager that I...
2013 Aug 08
3
Re: libvirt possibly ignoring cache=none ?
On Thu, Aug 8, 2013 at 9:39 AM, Martin Kletzander <mkletzan@redhat.com> wrote:
> At first let me explain that libvirt is not ignoring the cache=none.
> This is propagated to qemu as a parameter for it's disk. From qemu's
> POV (anyone feel free to correct me if I'm mistaken) this means the file
> is opened with O_DIRECT flag; and from the open(2) manual, the O_DIRECT