search for: eanna

I've been having intermittent network issues on my Host - they go away when I stop and disable libvirtd and then reboot. They do not go away if I just stop libvirtd and don't reboot. I'm at a loss as to where to start with my troubleshooting, and being a relative n00b to libvirt, I'd love any pointers. Regards, Richard

...te period of time 2. continue even if I shutdown libvirtd and the two guests - a reboot is REQUIRED 3. do NOT occur if I leave libvirtd disabled and NEVER start it Which, on review, seems it might have something to do with the KVM kernel module - so I'm copying that mailing list as well. root@eanna i ~ # pacman -Qi linux Name : linux Version : 3.18.6-1 Description : The Linux kernel and modules Architecture : x86_64 ... Build Date : Fri 06 Feb 2015 11:46:13 PM PST Install Date : Thu 19 Mar 2015 03:58:50 PM PDT Install Reason : Explicitly installed Install Script :...

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

Yeah, Dominique, your wiki was one of the many docs I read through before/during/after starting down this primrose path... thanks for writing it. I'm an Arch user, and I couldn't find anything to indicate qemu, as its compiled for Arch, will look in /etc/default/qemu-kvm. And now that I've got the right page size, the instances are starting... The reason I want to use the page element

...ls, 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_nod...

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

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

...uot; with def->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...