search for: nodeset

*facepalm* Now that I'm re-reading the documentation it's obvious that <page/> and @nodeset are for the guest, "This tells the hypervisor that the guest should have its memory allocated using hugepages instead of the normal native page size." Pretty clear there. Thank you SO much for the guidance, I'll return to my tweaking. I'll report back here with my results. On...

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 allocation to the guest fro...

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 "//numatune/memnode[@nodeset]...

On Tue, Feb 10, 2015 at 1:14 AM, Michal Privoznik <mprivozn@redhat.com> wrote: > 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 >> me...

...cpu="28" cpuset="28"/> <vcpupin vcpu="29" cpuset="29"/> <vcpupin vcpu="30" cpuset="30"/> <vcpupin vcpu="31" cpuset="31"/> </cputune> <numatune> <memory mode="strict" nodeset="0-7"/> </numatune> However, this is not enough. This XML pins only vCPUs and not guest memory. So while say vCPU #0 is pinned onto physical CPU #0, the memory for guest NUMA #0 might be allocated at host NUMA #7 (for instance). You need to add: <numatune> <memnode...

...;28' cpuset='28' /><vcpupin vcpu='29' cpuset='29' /><vcpupin vcpu='30' cpuset='30' /><vcpupin vcpu='31' cpuset='31' /></cputune> > <numatune> > <memnode cellid="0" mode="strict" nodeset="0"/> > <memnode cellid="1" mode="strict" nodeset="1"/> > <memnode cellid="2" mode="strict" nodeset="2"/> > <memnode cellid="3" mode="strict" nodeset="3"/> > <memn...

...vcpu='28' cpuset='28' /><vcpupin vcpu='29' cpuset='29' /><vcpupin vcpu='30' cpuset='30' /><vcpupin vcpu='31' cpuset='31' /></cputune> <numatune> <memnode cellid="0" mode="strict" nodeset="0"/> <memnode cellid="1" mode="strict" nodeset="1"/> <memnode cellid="2" mode="strict" nodeset="2"/> <memnode cellid="3" mode="strict" nodeset="3"/> <memnode cellid="4&q...

As I mentioned, I got the instances to launch... but they're only taking HugePages from "Node 0", when I believe my setup should pull from both nodes. [atlas] http://sprunge.us/FSEf [prometheus] http://sprunge.us/PJcR 2015-02-03 16:51:48 root@eanna i ~ # virsh start atlas Domain atlas started 2015-02-03 16:51:58 root@eanna i ~ # virsh start prometheus Domain prometheus started

...gvdata/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 xml: <cpu> <numa> <cell id='0' cpus='0' memory='10...

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?

...gt; <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>prometheus</name> <uuid>dda7d085-701b-4d0a-96d4-584678104fb3</uuid> <m...

...ges-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 xml: > <cpu> > <numa> > &lt...

...;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:83:1a'/> <source type='unix' path='/path/port1' mode=...

...e 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="immediate"/> </memoryBacking> Will it work? Are there any caveats we sh...

.... 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> -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

Hi, All The vm can't start when using numa based on centos 6.5(kernel: kernel-2.6.32-431.17.1.el6.x86_64, qemu-kvm: qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64). My numa setting in vm xml is the following: -------------------- <numatune> <memory mode='strict' nodeset='1'/> </numatune> -------------------- When 'nodeset' sets '0', the vm can start; However, when setting it to 1, it can't start and report the following error: ---------------------------- error: Failed to start domain testbsd error: internal error Process ex...

...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> >> >> >> <interface type='vhostuser'> >> <mac address='52:54:00:3b:83:1a'/> >&gt...

...' /><vcpupin vcpu='28' cpuset='25' /><vcpupin vcpu='29' cpuset='27' /><vcpupin vcpu='30' cpuset='29' /><vcpupin vcpu='31' cpuset='31' /></cputune> <numatune><memory mode='preferred' nodeset='0'/></numatune>) <devices><serial type='pty'><target port='0'/></serial><console type='pty'><target type='serial' port='0'/></console><channel type='pty'><target type='virtio'...

...;/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> > <vcpupin vcpu='0' cpuset='4-7'/> > <vcpupin vcpu='1&...

...to conservatively-allocatables. ... Popped NId 2(%vreg4, GPR64common) , all edge costs added: 2.002748e+01 inf inf inf inf inf inf inf inf inf inf ** selection: 0 llc: ../include/llvm/CodeGen/PBQP/ReductionRules.h:214: llvm::PBQP::Solution llvm::PBQP::backpropagate(GraphT&, StackT, llvm::PBQP::NodeSet&) [with GraphT = llvm::PBQP::Gra ph<llvm::PBQP::RegAlloc::RegAllocSolverImpl>; StackT = std::vector<unsigned int>; llvm::PBQP::NodeSet = std::set<unsigned int>]: Assertion `PushedAsConservativelyAllocatabl eNodes.find(NId) == PushedAsConservativelyAllocatableNodes.end() &&...