search for: numastat

...39;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 to the guest. Yes, i can see the hugepages via numastat -m and hugetlbfs is mounted via /dev/hugepages and there is a dir structure /dev/hugepages/libvirt/qemu (it's empty). HugePages is big enough to accommodate the 16G i'm allocating... and changing the perms on that directory structure to 777 doesn't work either. Any help is much apprec...

...rtd[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 to the guest. > > Yes, i can see the hugepages via numastat -m and hugetlbfs is mounted > via /dev/hugepages and there is a dir structure > /dev/hugepages/libvirt/qemu (it's empty). > > HugePages is big enough to accommodate the 16G i'm allocating... and > changing the perms on that directory structure to 777 doesn't work > eit...

...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 2015-02-03 16:52:53 root@eanna i ~ # numastat -m Per-node system memory usage (in MBs): Node 0 Node 2 Total --------------- --------------- --------------- MemTotal 32113.93 32238.27 64352.20 MemFree 7030.30 7175.87 14206...

...aring it to the number > of nodesets in "//memoryBacking//hugepages". I think this means that I > misunderstand what the nodeset is for in that element... > > Of note is the fact that my host has non-contiguous NUMA node numbers: > 2015-02-09 08:53:06 > root@eanna i ~ # numastat > node0 node2 > numa_hit 216225024 440311113 > numa_miss 0 795018 > numa_foreign 795018 0 > interleave_hit 15835 15783 > local_node 2...

*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.

...> <page size='16777216' unit='KiB' nodeset='0'/> This means you want the guest's memory to be allocated from 16GiB hugepages. You probably wanted to put this there: <page size='2' unit='MiB' ... >Yes, i can see the hugepages via numastat -m and hugetlbfs is mounted >via /dev/hugepages and there is a dir structure >/dev/hugepages/libvirt/qemu (it's empty). > >HugePages is big enough to accommodate the 16G i'm allocating... and >changing the perms on that directory structure to 777 doesn't work >either....

...39;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 to the guest. Yes, i can see the hugepages via numastat -m and hugetlbfs is mounted via /dev/hugepages and there is a dir structure /dev/hugepages/libvirt/qemu (it's empty). HugePages is big enough to accommodate the 16G i'm allocating... and changing the perms on that directory structure to 777 doesn't work either. Any help is much apprec...

...39;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 to the guest. Yes, i can see the hugepages via numastat -m and hugetlbfs is mounted via /dev/hugepages and there is a dir structure /dev/hugepages/libvirt/qemu (it's empty). HugePages is big enough to accommodate the 16G i'm allocating... and changing the perms on that directory structure to 777 doesn't work either. Any help is much apprec...

...10500 11694 61,50 10,00 0,00 71,50 8 smbd 16:30:26 10500 11694 64,00 10,00 0,00 74,00 8 smbd 16:30:28 10500 11694 63,50 10,00 0,00 73,50 8 smbd 16:30:30 10500 11694 67,50 11,50 0,00 79,00 8 smbd root at storiq-111:~# numastat -p 11694 Per-node process memory usage (in MBs) for PID 11694 (smbd) Node 0 Node 1 Total --------------- --------------- --------------- Huge 0.00 0.00 0.00 Heap 0.2...

...>> of nodesets in "//memoryBacking//hugepages". I think this means that I >> misunderstand what the nodeset is for in that element... >> >> Of note is the fact that my host has non-contiguous NUMA node numbers: >> 2015-02-09 08:53:06 >> root@eanna i ~ # numastat >> node0 node2 >> numa_hit 216225024 440311113 >> numa_miss 0 795018 >> numa_foreign 795018 0 >> interleave_hit 15835 15783 >>...

...f->cpu->ncells, and comparing it to the number of nodesets in "//memoryBacking//hugepages". I think this means that I misunderstand what the nodeset is for in that element... Of note is the fact that my host has non-contiguous NUMA node numbers: 2015-02-09 08:53:06 root@eanna i ~ # numastat node0 node2 numa_hit 216225024 440311113 numa_miss 0 795018 numa_foreign 795018 0 interleave_hit 15835 15783 local_node 214029815 221903122 other...

...0 10,00 0,00 71,50 8 smbd > 16:30:26 10500 11694 64,00 10,00 0,00 74,00 8 > smbd 16:30:28 10500 11694 63,50 10,00 0,00 73,50 > 8 smbd 16:30:30 10500 11694 67,50 11,50 0,00 > 79,00 8 smbd > > root at storiq-111:~# numastat -p 11694 > Per-node process memory usage (in MBs) for PID 11694 (smbd) > Node 0 Node 1 Total > --------------- --------------- --------------- > Huge 0.00 0.00 0.00 > Heap...

...memory technology devices (flash) -mono.txt +admin-guide/mono.rst - how to execute Mono-based .NET binaries with the help of BINFMT_MISC. namespaces/ - directory with various information about namespaces @@ -340,7 +340,7 @@ nommu-mmap.txt - documentation about no-mmu memory mapping support. numastat.txt - info on how to read Numa policy hit/miss statistics in sysfs. -oops-tracing.txt +admin-guide/oops-tracing.rst - how to decode those nasty internal kernel error dump messages. padata.txt - An introduction to the "padata" parallel execution API @@ -378,7 +378,7 @@ ptp/ - dire...

...memory technology devices (flash) -mono.txt +admin-guide/mono.rst - how to execute Mono-based .NET binaries with the help of BINFMT_MISC. namespaces/ - directory with various information about namespaces @@ -340,7 +340,7 @@ nommu-mmap.txt - documentation about no-mmu memory mapping support. numastat.txt - info on how to read Numa policy hit/miss statistics in sysfs. -oops-tracing.txt +admin-guide/oops-tracing.rst - how to decode those nasty internal kernel error dump messages. padata.txt - An introduction to the "padata" parallel execution API @@ -378,7 +378,7 @@ ptp/ - dire...

...memory technology devices (flash) -mono.txt +admin-guide/mono.rst - how to execute Mono-based .NET binaries with the help of BINFMT_MISC. namespaces/ - directory with various information about namespaces @@ -340,7 +340,7 @@ nommu-mmap.txt - documentation about no-mmu memory mapping support. numastat.txt - info on how to read Numa policy hit/miss statistics in sysfs. -oops-tracing.txt +admin-guide/oops-tracing.rst - how to decode those nasty internal kernel error dump messages. padata.txt - An introduction to the "padata" parallel execution API @@ -378,7 +378,7 @@ ptp/ - dire...

...memory technology devices (flash) -mono.txt +admin-guide/mono.rst - how to execute Mono-based .NET binaries with the help of BINFMT_MISC. namespaces/ - directory with various information about namespaces @@ -340,7 +340,7 @@ nommu-mmap.txt - documentation about no-mmu memory mapping support. numastat.txt - info on how to read Numa policy hit/miss statistics in sysfs. -oops-tracing.txt +admin-guide/oops-tracing.rst - how to decode those nasty internal kernel error dump messages. padata.txt - An introduction to the "padata" parallel execution API @@ -378,7 +378,7 @@ ptp/ - dire...