similar to: Re: [libvirt] [PATCH 1/4] libxl: implement NUMA capabilities reporting

Displaying 20 results from an estimated 1000 matches similar to: "Re: [libvirt] [PATCH 1/4] libxl: implement NUMA capabilities reporting"

2013 Sep 30
3
Re: (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
hi, thanks for your response. i cleaned that above one and installed in this following steps: * sudo apt-get install gcc make pkg-config libxml2-dev libgnutils-dev libdevmapper-dev libcurl4-gnutls-dev python-dev libpciaccess-dev libxen-dev libnl-dev * ./configure = --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-xen=yes --with-libxl=yes * make * make install now i am getting the
2013 Sep 30
2
Re: (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
On lun, 2013-09-30 at 11:27 +0530, cooldharma06 wrote: > hi, > Hi, > thanks for your response. > > > i cleaned that above one and installed in this following steps: > > > * sudo apt-get install gcc make pkg-config libxml2-dev libgnutils-dev > libdevmapper-dev libcurl4-gnutls-dev python-dev libpciaccess-dev > libxen-dev libnl-dev > Oh, so you are on
2013 Sep 30
6
Re: (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
hi, i am using debian flavor called BOSS. *uname -a* Linux boss 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux i installed XEN-4.2.1 from the source. *virsh # version* error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to '/usr/local/var/run/libvirt/libvirt-sock': No such file or directory * * *root@boss[src]#libvirtd -v*
2012 Jul 04
53
[PATCH 00 of 10 v3] Automatic NUMA placement for xl
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
2019 Dec 13
0
[PATCH RFC v4 01/13] ACPI: NUMA: export pxm_to_node
On 12.12.19 22:43, Rafael J. Wysocki wrote: > On Thursday, December 12, 2019 6:11:25 PM CET David Hildenbrand wrote: >> Will be needed by virtio-mem to identify the node from a pxm. >> >> Cc: "Rafael J. Wysocki" <rjw at rjwysocki.net> >> Cc: Len Brown <lenb at kernel.org> >> Cc: linux-acpi at vger.kernel.org >> Signed-off-by: David
2020 Mar 02
0
[PATCH v1 01/11] ACPI: NUMA: export pxm_to_node
Will be needed by virtio-mem to identify the node from a pxm. Acked-by: "Rafael J. Wysocki" <rafael at kernel.org> Cc: Len Brown <lenb at kernel.org> Cc: linux-acpi at vger.kernel.org Signed-off-by: David Hildenbrand <david at redhat.com> --- drivers/acpi/numa/srat.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/acpi/numa/srat.c
2020 Mar 02
1
[PATCH v1 01/11] ACPI: NUMA: export pxm_to_node
On Mon 02-03-20 14:49:31, David Hildenbrand wrote: > Will be needed by virtio-mem to identify the node from a pxm. No objection to export the symbol. But it is almost always better to add the export in the patch that actually uses it. The intention is much more clear that way. > Acked-by: "Rafael J. Wysocki" <rafael at kernel.org> > Cc: Len Brown <lenb at
2013 Oct 01
1
Re: (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
hi, i found something im my log: (libvirtd.log) i dont know about this. but it may be helpful for you. So i am forwarding this. 2013-09-26 11:43:58.507+0000: 10718: error : virDriverLoadModule:78 : failed to load module /usr/local/lib/libvirt/connection-driver/libvirt_driver_libxl.so /usr/lib/libxenlight.so.2.0: undefined symbol: xs_check_watch 2013-09-26 11:43:58.790+0000: 10729: error :
2013 Oct 04
7
Re: (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
cooldharma06 wrote: > hi, > > i found something im my log: (libvirtd.log) > > i dont know about this. but it may be helpful for you. So i am > forwarding this. > > 2013-09-26 11:43:58.507+0000: 10718: error : virDriverLoadModule:78 : > failed to load module > /usr/local/lib/libvirt/connection-driver/libvirt_driver_libxl.so > /usr/lib/libxenlight.so.2.0: undefined
2013 Sep 27
5
(Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
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
2013 Sep 27
5
(Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
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
2006 Sep 29
4
[PATCH 4/6] xen: export NUMA topology in physinfo hcall
This patch modifies the physinfo hcall to export NUMA CPU and Memory topology information. The new physinfo hcall is integrated into libxc and xend (xm info specifically). Included in this patch is a minor tweak to xm-test''s xm info testcase. The new fields in xm info are: nr_nodes : 4 mem_chunks : node0:0x0000000000000000-0x0000000190000000
2009 Aug 28
2
[PATCH] x86/numa: fix c/s 20120 (Fix SRAT check for discontig memory)
That change converted the (wrong) assumption of contiguous nodes'' memory to a similarly wrong one of assuming discontiguous memory (i.e. each node having separate E820 table entries). The code ought to be able to deal with both, though, and I hope this change makes it so. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- 2009-08-24.orig/xen/arch/x86/srat.c 2009-08-28
2013 Oct 07
2
Re: (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
hi, i removed all libvirt things form my system and i installed libvirt-0.9.12 frm my repository. then i installed libvirt-1.1.2 from the source with following commands. ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-xen=yes --with-libxl=yes make make install now its works with XM. but with xl its not working... i attached the corresponding screenshots also. kindly
2013 Oct 05
3
Re: (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
hi, i prepared my xen-4.2.1 document with this mail. kindly refer the below attachment. i installed libvirt 1.1.1 like this it giving the following error: ./autogen.sh --system --with-xen=yes make /daemon/libvirtd -d then i checked with the virsh ->version virsh # version error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to
2013 Sep 27
1
Re: (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
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
2013 Sep 27
1
Re: [libvirt-users] (Xen + libvirt) Installing and workin with xen -4.2.1 and libvirt 1.1.2
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
2013 Sep 17
1
[PATCH] xen: numa-sched: leave node-affinity alone if not in "auto" mode
If the domain''s NUMA node-affinity is being specified by the user/toolstack (instead of being automatically computed by Xen), we really should stick to that. This means domain_update_node_affinity() is wrong when it filters out some stuff from there even in "!auto" mode. This commit fixes that. Of course, this does not mean node-affinity is always honoured (e.g., a vcpu
2012 Jul 26
3
[PATCH v8] Some automatic NUMA placement documentation
About rationale, usage and (some small bits of) API. Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> --- Changes from v7: * avoid referring to 4.2 release as "upcoming". * libxl placement disabling key explicitly mentioned. * Limit of max 16 NUMA nodes explicitly mentioned. Changes from v6: * text updated to
2005 Dec 16
3
[PATCH] 0/7 xen: Add basic NUMA support
The patchset will add basic NUMA support to Xen (hypervisor only). We borrowed from Linux support for NUMA SRAT table parsing, discontiguous memory tracking (mem chunks), and cpu support (node_to_cpumask etc). The hypervisor parses the SRAT tables and constructs mappings for each node such as node to cpu mappings and memory range to node mappings. Using this information, we also modified the