search for: socket_ids

Hi, All The vm can't start when using numa based on centos 6.5(kernel: kernel-2.6.32-431.17.1.el6.x86_64, qemu-kvm: qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64). My numa setting in vm xml is the following: -------------------- <numatune> <memory mode='strict' nodeset='1'/> </numatune> -------------------- When 'nodeset' sets '0', the

Hi, I have been trying to find out CPU topology using libvirt. I understand that I can find out the number of cores/sockets/ threads etc through getCapabilities() function. What I am wondering is that is there any function that can provide me the exact topology like how many sockets, how many sockets per core and number of threads per core, if applicable or may be info about numa cells.  Is there

Hi all, I have been trying to find out cpu topology using libvirt. When I do 'virsh capabilites', I find this inside <topology> tag: <topology>       <cells num='1'>         <cell id='0'>           <memory unit='KiB'>3908488</memory>           <cpus num='4'>             <cpu id='0' socket_id='0'

Tried to migrate a few VMs from existing system to an older host that we threw in the rack to facilitate some server reshuffling. Migration complained about lack of capabilities (which I expected its an older server) but when I looked at what I should throw into the xml file I got a core2duo when it should have been at least Penryn or something (Xeon E5345) Of course the VMs work fine with

Test libvirt-users-request@redhat.com schrieb: >Send libvirt-users mailing list submissions to > libvirt-users@redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/libvirt-users >or, via email, send a message with subject or body 'help' to > libvirt-users-request@redhat.com > >You can reach the

On Mon, May 22, 2017 at 05:03:21PM -0700, W Kern wrote: >Tried to migrate a few VMs from existing system to an older host that we >threw in the rack to facilitate some server reshuffling. > >Migration complained about lack of capabilities (which I expected its an >older server) but when I looked at what I should throw into the xml file >I got a core2duo when it should have been

On Tue, Sep 17, 2013 at 05:41:12PM +0800, Peeyush Gupta wrote: > Hi all, > > I have been trying to find out cpu topology using libvirt. When > I do 'virsh capabilites', I find this inside <topology> tag: > > > <topology> >       <cells num='1'> >         <cell id='0'> >           <memory

...ic void signal_int_handler(int signo set_xen_guest_handle(info.cpu_to_node, cpu_to_node); info.max_cpu_index = MAX_NR_CPU - 1; - ret = xc_topologyinfo(xc_handle, &info); - if ( !ret ) + if ( cx_cap && !xc_topologyinfo(xc_handle, &info) ) { uint32_t socket_ids[MAX_NR_CPU]; uint32_t core_ids[MAX_NR_CPU]; @@ -461,7 +457,7 @@ static void signal_int_handler(int signo if ( cpu_to_socket[j] == socket_ids[i] ) break; } - printf("Socket %d\n", socket_ids[i]); +...

... to be more precise in naming, and also to match Linux. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- 2009-07-10.orig/xen/arch/ia64/linux-xen/perfmon.c 2009-05-27 13:54:05.000000000 +0200 +++ 2009-07-10/xen/arch/ia64/linux-xen/perfmon.c 2009-07-15 10:02:08.000000000 +0200 @@ -7313,7 +7313,7 @@ xenpfm_context_create(XEN_GUEST_HANDLE(p goto out; /* XXX fmt */ -

I hope this question isn't considered too off topic for this list, I am trying to reach the libvirt-sandbox developers, but I could not find a libvirt-sandbox specific mailing list, and it seemed to me that libvirt-sandbox was a part of libvirt itself. I am trying to port libvirt-sandbox to run on a CentOS 6.5 system. This wasn't too hard but, I had to do the following: I have used the

Hi everyone, Using the QEMU hypervisor, when a live disk snapshot is requested through libvirt, the request can fail if the underyling qemu binary lacks the snapshotting support. In python, we have something like libvirtError: Operation not supported: live disk snapshot not supported with this QEMU binary I'd like to detect ahead of time if the underlying QEMU can or cannot do

Hi, I tried to run domsuspend command on my PowerPC board but failed. # virsh dompmsuspend sdk --target mem error: Domain sdk could not be suspended error: argument unsupported: QEMU guest agent is not configured It seemed that support suspend-to-mem only from capabilities. # virsh capabilities <capabilities> <host>

...: [%020"PRIu64" ms]\n", + cxstat->cc3/1000000UL, cxstat->cc6/1000000UL, + cxstat->cc7/1000000UL); printf("\n"); } @@ -458,6 +462,9 @@ break; } printf("Socket %d\n", socket_ids[i]); + res = cxstat_end[j].pc2 - cxstat_start[j].pc2; + printf("\tPC2\t%"PRIu64" ms\t%.2f%%\n", res / 1000000UL, + 100UL * res / (double)sum_cx[j]); res = cxstat_end[j].pc3 - cxstat_start[j].pc3;...

Since the image pointed to may (and generally will) live in boot services memory (which we add to the global memory pool long before ACPI tables get looked at), we should prevent Dom0 from trying to retrieve the image data. The alternatives would be to - not add boot services memory to the global pool at all, or - defer adding boot services memory until Dom0 indicates it is safe to do so, or -

Since the image pointed to may live in boot services memory (which we add to the global memory pool long before ACPI tables get looked at), we should prevent Dom0 from trying to retrieve the image data in that case. The alternatives would be to - not add boot services memory to the global pool at all, or - defer adding boot services memory until Dom0 indicates it is safe to do so, or - find and