similar to: Re: [PATCHv2 1 of 2] libxl: extend pCPUs specification for vcpu-pin.

On Wed, 2012-01-25 at 14:35 +0000, Dario Faggioli wrote: > Allow for "^<cpuid>" syntax while specifying the pCPUs list > during a vcpu-pin. This enables doing the following: > > xl vcpu-pin 1 1 0-4,^2 > > and achieving: > > xl vcpu-list > Name ID VCPU CPU State Time(s) CPU Affinity > ... > Squeeze_pv

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

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

[Moving the conversation on @xen-devel and adding Jan, as that seems more appropriate] [Jan, this came up as I''m implementing some NUMA bits in libvirt but, as you see, the core of Jim''s question is purely about Xen] On lun, 2013-07-01 at 16:47 -0600, Jim Fehlig wrote: > On my non-NUMA test machine I have the cell memory reported as > > <memory

On Mon, Oct 17, 2011 at 05:36:27PM +0200, Dario Faggioli wrote: > Hi everyone, > > I''m trying to setup PCI-passthrough for a network card on a testbox. > With HVM, everything seems to work, while if I try with a pv-guest the > domain crashes! > > Here''s the thing: > -- > # xl pci-list-assignable-devices > 0000:07:00.0 > 0000:07:00.1 > >

in _csched_cpu_pick(), as not doing so may result in the domain''s node-affinity mask (as retrieved by csched_balance_cpumask() ) and online mask (as retrieved by cpupool_scheduler_cpumask() ) having an empty intersection. Therefore, when attempting a node-affinity load balancing step and running this: ... /* Pick an online CPU from the proper affinity mask */

Hello, I observed that a configuration where dom0 vcpus were pinned to a set of pcpus in the host using dom0_vcpus_pin and the guests were prevented from running on the dom0 pcpus (here called "exclusively-pinned dom0 vcpus", or xpin) caused the general performance of the guests in a host with around 24 pcpus or more to increase during bootstorms and high density of guests, even

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

Hello everyone, Reposting with after having applied the (minor) fixes suggested by Wei and Jan. Allen, if you can tell us what you think about this, or suggest someone else to ask some feedback to, if you''re no longer involved with VT-d, that would be great! :-) -- As already discussed here [1], dealing with IOMMU faults in interrupt context may cause nasty things to happen, up to

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

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

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

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 :

branch xen-unstable xen branch xen-unstable job build-i386 test xen-build Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git Tree: xen git://xenbits.xen.org/xen.git *** Found and reproduced problem changeset *** Bug is in tree: xen git://xenbits.xen.org/xen.git Bug introduced: ae763e4224304983a1cde2fbb3d6e0c4d60b2688 Bug not present:

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*

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

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

I am newbie to this gdb debugging. now i did the bt in the debugging. In my side still it showing the error. Following are the stacktrace which i got. Kindly refer the following logs for full information: **** [New Thread 0x7f8503695700 (LWP 20012)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007f84f671281e in

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