search for: memorybacking

...ize=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. > > Looking at tests/qemuxml2argvdata/qemuxml2argv-hugepages-pages.args, I > see several instances of "-object memory-backend-file...", so look at > the counterpart .xml file for some examples: > > <memoryBacking> > <hugepages> > <page size='2048' unit='KiB' nodeset='1'/> > <page size='1048576' unit='KiB' nodeset='0,2-3'/> > </hugepages> > </memoryBacking> > > Thank you. I use this...

...eter? this is my xml: <cpu> <numa> <cell id='0' cpus='0' memory='1048576' memAccess='shared'/> <cell id='1' cpus='1' memory='1048576' memAccess='shared'/> </numa> </cpu> <memoryBacking> <hugepages> <page size="2" unit="M" nodeset="0,1"/> </hugepages> <!--nosharepages/--> <!--locked/--> </memoryBacking> <interface type='vhostuser'> <mac address='52:54:00:3b:...

...> this memAccess='shared' is exactly what you need in order for the > share='on' to be appended. I wonder why it's not there. What libvirt > version are you using? -bash-4.2# virsh --version 1.2.7 > >> </numa> >> </cpu> >> <memoryBacking> >> <hugepages> >> <page size="2" unit="M" nodeset="0,1"/> >> </hugepages> >> <!--nosharepages/--> >> <!--locked/--> >> </memoryBacking> >> >> >> <interf...

...#39;1' memory='1048576' memAccess='shared'/> this memAccess='shared' is exactly what you need in order for the share='on' to be appended. I wonder why it's not there. What libvirt version are you using? > </numa> > </cpu> > <memoryBacking> > <hugepages> > <page size="2" unit="M" nodeset="0,1"/> > </hugepages> > <!--nosharepages/--> > <!--locked/--> > </memoryBacking> > > > <interface type='vhostuser'> &gt...

...n type='kvm' id='2'> > <name>atlas</name> > <uuid>d9991b1c-2f2d-498a-9d21-51f3cf8e6cd9</uuid> > <memory unit='KiB'>16777216</memory> > <currentMemory unit='KiB'>16777216</currentMemory> > <memoryBacking> > <hugepages> > <page size='2048' unit='KiB' nodeset='0'/> > </hugepages> > <nosharepages/> > </memoryBacking> > <!-- no numa pining --> > </domain> > > > <domain type='k...

...much since that is only a > snapshot > > - when running a guest you can have 1gb free now, and 10 mb free 2 min > > later. > > > > Any ideas? > > There is one option I see, use -mem-prealloc. Either you can passthrough > it onto qemu commandline [1] or use locked memoryBacking [2]. I advocate > for the latter though. Not only it will allocate all the memory at qemu > startup it will also lock it so it won't get swapped off. > > Michal > > 1: http://libvirt.org/drvqemu.html#qemucommand > 2: http://libvirt.org/formatdomain.html#elementsMemoryBackin...

Hi, I want to use virsh to create a VM with the qemu parameter '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. How to write the XML file?

...terdag 31 januari 2015 0:33 > Aan: libvirt-users@redhat.com > Onderwerp: [libvirt-users] HugePages - can't start guest that requires them > > > Hello All, > > I'm trying to enable hugepages, I've turned off THP (Transparent Huge > Pages), and enabled hugepages in memoryBacking, and set my 2MB > hugepages count via sysctl. > > I'm getting "libvirtd[5788]: Failed to autostart VM 'atlas': internal > error: Unable to find any usable hugetlbfs mount for 16777216 KiB" > where atlas is one of my guests and 16777216 KiB is the amount of >...

First I'll quickly summarize my understanding of how to configure numa... In "//memoryBacking/hugepages/page[@nodeset]" I am telling libvirt to use hugepages for the guest, and to get those hugepages from a particular host NUMA node. In "//numatune/memory[@nodeset]" I am telling libvirt to pin the memory allocation to the guest from a particular host numa node. In "//nu...

...when running a guest you can have 1gb free now, and 10 mb free 2 min > >>> later. > >>> > >>> Any ideas? > >> > >> There is one option I see, use -mem-prealloc. Either you can passthrough > >> it onto qemu commandline [1] or use locked memoryBacking [2]. I advocate > >> for the latter though. Not only it will allocate all the memory at qemu > >> startup it will also lock it so it won't get swapped off. > >> > >> Michal > >> > >> 1: http://libvirt.org/drvqemu.html#qemucommand > >&g...

Hello All, I'm trying to enable hugepages, I've turned off THP (Transparent Huge Pages), and enabled hugepages in memoryBacking, and set my 2MB hugepages count via sysctl. I'm getting "libvirtd[5788]: Failed to autostart VM 'atlas': internal error: Unable to find any usable hugetlbfs mount for 16777216 KiB" where atlas is one of my guests and 16777216 KiB is the amount of memory I'm trying to give...

...se hard_limit of <memtune> element to pin the memory. However, from the discussion in the spec it seems that there is no way to determine a good enough value and that hard_limit should not be used at all. What should be used then? There is a suggestion to use something like this: <memoryBacking> <hugepages> <page size="2" unit="M" nodeset="1"/> </hugepages> <nosharepages/> <locked/> <source type="file"/> <access mode="shared"/> <allocation mode="...

...path=/mnt/huge,share=on -numa node,memdev=mem'. >> Looking at tests/qemuxml2argvdata/qemuxml2argv-hugepages-pages.args, I >> see several instances of "-object memory-backend-file...", so look at >> the counterpart .xml file for some examples: >> >> <memoryBacking> >> <hugepages> >> <page size='2048' unit='KiB' nodeset='1'/> >> <page size='1048576' unit='KiB' nodeset='0,2-3'/> >> </hugepages> >> </memoryBacking> >> &...

...rom both XMLs] <domain type='kvm' id='2'> <name>atlas</name> <uuid>d9991b1c-2f2d-498a-9d21-51f3cf8e6cd9</uuid> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <hugepages> <page size='2048' unit='KiB' nodeset='0'/> </hugepages> <nosharepages/> </memoryBacking> <!-- no numa pining --> </domain> <domain type='kvm' id='3'> <name>prometh...

...t;> snapshot >>> - when running a guest you can have 1gb free now, and 10 mb free 2 min >>> later. >>> >>> Any ideas? >> >> There is one option I see, use -mem-prealloc. Either you can passthrough >> it onto qemu commandline [1] or use locked memoryBacking [2]. I advocate >> for the latter though. Not only it will allocate all the memory at qemu >> startup it will also lock it so it won't get swapped off. >> >> Michal >> >> 1: http://libvirt.org/drvqemu.html#qemucommand >> 2: http://libvirt.org/formatdoma...

Hi all, I am running KVM on a 3.18 kernel. The system runs and Atom processor with 2Gb RAM. Using KVM you obviously can over allocate your resources: say you have 4 guests each configured with 1GB ram. Running all four at the same time, depending on the workload, can crash the system - I get a kernel trace when this happens. But let's consider a simpler case: one guest with 1.5 Gb RAM,

...> <uuid>925e4f9b-2c27-406d-bdd9-f3e0b44f28bb</uuid> <title>PCVIRTdra - PC voor dra</title> <description></description> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <hugepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-utopic'>hvm</type>...

...3c41db850d5cde8de8208b">service</nova:project> > </nova:owner> > </nova:instance> > </metadata> > <memory unit='KiB'>2097152</memory> > <currentMemory unit='KiB'>2097152</currentMemory> > <memoryBacking> > <hugepages> > <page size='2048' unit='KiB' nodeset='0'/> > </hugepages> > </memoryBacking> > <vcpu placement='static'>2</vcpu> > <cputune> > <shares>4096</shares>...

...er 2015 R2 <domain type='kvm' id='146'> <name>CmsrvAPP2</name> <uuid>02c5daef-662a-85ba-7291-485118badc64</uuid> <memory unit='KiB'>3149824</memory> <currentMemory unit='KiB'>3149824</currentMemory> <memoryBacking> <hugepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>...

On 09.02.2015 18:19, G. Richard Bellamy wrote: > First I'll quickly summarize my understanding of how to configure numa... > > In "//memoryBacking/hugepages/page[@nodeset]" I am telling libvirt to > use hugepages for the guest, and to get those hugepages from a > particular host NUMA node. No, @nodeset refers to guest NUMA nodes. > > In "//numatune/memory[@nodeset]" I am telling libvirt to pin the > memory all...