search for: numa_info

...9;>9175040</memory> > Which is 8960, if divided by 1024, so at least it''s consistent. However... > The machine has 8G of memory, running xen 4.3 rc6, with dom0_mem=1024M. ''xl > info --numa'' says > > total_memory : 8190 > ... > numa_info : > node: memsize memfree distances > 0: 8960 7116 10 > > Why is the node memsize > total_memory? Mmm... Interesting question. I really never paid attention to this... Jan (or anyone else), is that something known and/or expected? I went c...

...opology : cpu: core socket node 0: 0 0 0 1: 0 0 0 2: 1 0 0 3: 1 0 0 4: 2 0 0 5: 2 0 0 6: 3 0 0 7: 3 0 0 numa_info : node: memsize memfree distances 0: 4590 442 10 xen_major : 4 xen_minor : 2 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler :...

...0 > > 1: 0 0 0 > > 2: 1 0 0 > > 3: 1 0 0 > > 4: 2 0 0 > > 5: 2 0 0 > > 6: 3 0 0 > > 7: 3 0 0 > > numa_info : > > node: memsize memfree distances > > 0: 4590 442 10 > > xen_major : 4 > > xen_minor : 2 > > xen_extra : .1 > > > Mmm... I have to admit that the most of the testing I did whe...

...node > 0: 0 0 0 > 1: 0 0 0 > 2: 1 0 0 > 3: 1 0 0 > 4: 2 0 0 > 5: 2 0 0 > 6: 3 0 0 > 7: 3 0 0 > numa_info : > node: memsize memfree distances > 0: 4590 442 10 > xen_major : 4 > xen_minor : 2 > xen_extra : .1 > Mmm... I have to admit that the most of the testing I did when working on the patch for libvirt...

hi i want to install libvirt-1.1.2 in xen -4.2.1. i installed int he following manner: 1. downloaded source from libvirt/org (libvirt-1.1.2) 2. untarred & run ./configure --with-xen=yes --with-libxl=yes 3. then make and make install. i also enabled the (xend-unix-server yes) in xend config file. i run libvirtd -v and getting the followning error: root@boss[libexec]#libvirtd -v

hi i want to install libvirt-1.1.2 in xen -4.2.1. i installed int he following manner: 1. downloaded source from libvirt/org (libvirt-1.1.2) 2. untarred & run ./configure --with-xen=yes --with-libxl=yes 3. then make and make install. i also enabled the (xend-unix-server yes) in xend config file. i run libvirtd -v and getting the followning error: root@boss[libexec]#libvirtd -v

...0 0 >> > 2: 1 0 0 >> > 3: 1 0 0 >> > 4: 2 0 0 >> > 5: 2 0 0 >> > 6: 3 0 0 >> > 7: 3 0 0 >> > numa_info : >> > node: memsize memfree distances >> > 0: 4590 442 10 >> > xen_major : 4 >> > xen_minor : 2 >> > xen_extra : .1 >> > >> Mmm... I have to admit that the m...

...> 2: 1 0 0 > > 3: 1 0 0 > > 4: 2 0 0 > > 5: 2 0 0 > > 6: 3 0 0 > > 7: 3 0 0 > > numa_info : > > node: memsize memfree distances > > 0: 4590 442 10 > > xen_major : 4 > > xen_minor : 2 > > xen_extra : .1 > > > Mmm.....

On ven, 2013-09-27 at 12:56 +0530, cooldharma06 wrote: > root@boss[libexec]#libvirtd -v > 2013-09-27 07:24:46.501+0000: 29517: info : libvirt version: 1.1.2 > 2013-09-27 07:24:46.501+0000: 29517: error : libxlCapsInitHost:86 : > internal error: Failed to get node physical info from libxenlight > 2013-09-27 07:24:46.501+0000: 29517: error : > libxlStateInitialize:1362 : cannot

On ven, 2013-09-27 at 12:56 +0530, cooldharma06 wrote: > root@boss[libexec]#libvirtd -v > 2013-09-27 07:24:46.501+0000: 29517: info : libvirt version: 1.1.2 > 2013-09-27 07:24:46.501+0000: 29517: error : libxlCapsInitHost:86 : > internal error: Failed to get node physical info from libxenlight > 2013-09-27 07:24:46.501+0000: 29517: error : > libxlStateInitialize:1362 : cannot

...> 3: 1 0 0 >> > > 4: 2 0 0 >> > > 5: 2 0 0 >> > > 6: 3 0 0 >> > > 7: 3 0 0 >> > > numa_info : >> > > node: memsize memfree distances >> > > 0: 4590 442 10 >> > > xen_major : 4 >> > > xen_minor : 2 >> > > xen_extra...

...0 > > > 3: 1 0 0 > > > 4: 2 0 0 > > > 5: 2 0 0 > > > 6: 3 0 0 > > > 7: 3 0 0 > > > numa_info : > > > node: memsize memfree distances > > > 0: 4590 442 10 > > > xen_major : 4 > > > xen_minor : 2 > > > xen_extra : .1 > >...

...0 sharing_used_memory : 0 free_cpus : 0 cpu_topology : cpu: core socket node 0: 0 0 0 1: 1 0 0 2: 2 0 0 3: 3 0 0 4: 4 0 0 5: 5 0 0 numa_info : node: memsize memfree distances 0: 51200 0 10 xen_major : 4 xen_minor : 2 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler :...

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding

Hi all, This is the second take of a patch that I submitted some time ago for allowing specifying vcpu pinning taking NUMA nodes into account. IOW, something like this: * "nodes:0-3": all pCPUs of nodes 0,1,2,3;  * "nodes:0-3,^node:2": all pCPUS of nodes 0,1,3;  * "1,nodes:1-2,^6": pCPU 1 plus all pCPUs of nodes 1,2    but not pCPU 6; v1 was a single patch, this is