search for: vcpuinfo

Hi All, I am new to libvirt. Please explain about the units (which is bytes or KB or MB) and uses of DomainJobInfo and DomainBlockInfo methods. Like getMemRemaining(), getDataRemaining() etc. Using libvirt version is libvirt-0.5.1. Thank you Regards, Rathidevi

Dear All, I would like to know what functions and classes are implemented in the ESX(i) driver ? i am trying to use virsh to retrieve some simple information such as vcpuinfo domain, but it is not working, so I would like to know what functions are implemented in libvirt ESX(i) driver. Also i checked the http://libvirt.org/drvesx.html and nothing is mentioned there. Thank You, Regards, Sherif -------------- next part -------------- An HTML attachment was scrubbed... UR...

Hi,        Is it possible to get the CPU usage of a guest through a virsh command? I have tried almost all the commands (vcpuinfo, cpu-stats, etc.) that gets the details of a guest cpu, but it only returns the cpu time. Is there any command that returns the cpu usage (just like the graph that virt-manager displays) of a guest? Or do I have to create a program using libvirt API? Thanks in advance. regards, Marco

...ount 1 error: Operation not supported: qemu didn't unplug the vCPUs properly So I tried another way: log into the running VM, and "echo 0 > /sys/devices/system/cpu/cpu1/online", after that I can find only one processor in the vm through '/proc/cpuinfo', but in virsh, the vcpuinfo still shows: virsh # vcpuinfo 3 VCPU: 0 CPU: 0 State: running CPU time: 13.5s CPU Affinity: yyyy VCPU: 1 CPU: 1 State: running CPU time: 6.9s CPU Affinity: yyyy So the question is: is there any method I can't find y...

...se a VM running 2 endless loop threads to use the 2 cores ? In my case the VM running reports (cat /roc/cpuinfo) that it has 2 vcpus but it uses only 1 core (at a time) because the 'top' at the host shows 100%cpu (out of total 200%) used by the endless loop application Also virsh vcpuinfo <vm> shows only 1 CPU and 1 vcpu any idea ? thanks Zvi Dubitzky Email:dubi at il.ibm.com

Hi. Can anyone confirm if vcpupin works correctly with kvm? If set I pin a vcpu it shows up correctly via vcpuinfo, but querying via taskset shows the cpu is not pinned. Thanks, -Geoff -- ---- Geoff Galitz, ggalitz at shutterstock.com WebOps Engineer, Europe Shutterstock Images http://wwww.shutterstock.com/

...vmhost ~]# virsh nodeinfo CPU model: x86_64 CPU(s): 4 CPU frequency: 1600 MHz CPU socket(s): 1 Core(s) per socket: 4 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 5904548 kB and this is what virsh thinks my vm has: [root at vmhost ~]# virsh vcpuinfo xp VCPU: 0 CPU: 2 State: running CPU time: 521.3s CPU Affinity: yyyy [root at vmhost ~]# But, the vm reports it not only as a 286 but also claims not to have the right drivers for it. How can I make the vm see it as a 686 or something like that?

The series introduces auto-generation of the type definitions used in the libxl interface followed by auto-generation of a destructor function for each type. In the future it may be possible to use the related data structures for other purposes, for example auto-generation of the functions to marshal between C and language binding data types. tools/_libxl_types.h should be identical both before

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

On 06/01/2013 03:16 PM, Dennis Chen wrote: > On 05/29/2013 04:28 AM, Eric Blake wrote: >> On 05/28/2013 02:24 PM, Eric Blake wrote: >> >>>> So the question is: is there any method I can't find yet to change the >>>> vcpu count of a running vm dynamically? >>> Wait for newer qemu and libvirt, or else pitch in and help write >>> patches.

...ocess running on the host . Each VM runs the same process (2 threads endless loop ). Still both VM1 and VM2 get equal share of the 2 cores - running top utility at the host shows each is consuming 100% CPU. At each VM console cat /proc/cpuinfo shows 2 cores assigned to the VM. At the host : virsh vcpuinfo <vm1/2> shows each has 2 vcpus (0 an 1 )but actually a single separate CPU is used for either vcpu0 or vcpu1 at each VM at any check point in time (this is reasonable as it does not say what portion of the core cycles is used by each VM) . Can anyone explain that and how to bias the cor...

...lug, this will fail for you (it works for xen:// URI though). > > So I tried another way: log into the running VM, and "echo 0 > > /sys/devices/system/cpu/cpu1/online", after that I can find only one > processor in the vm through '/proc/cpuinfo', but in virsh, the vcpuinfo > still shows: That's not hot-unplug from qemu's perspective. That's just disabling the use of the cpu from within the guest (and in fact, that's what the new qemu 1.5 guest agent commands do, where we are still working on how best to wire that up into libvirt). > So the qu...

...-virt-type kvm --name Ubuntu13 --ram 1024 --cdrom=/home/peeyush/Downloads/ubuntu-13.04-desktop-i386.iso --cpuset=0,2 --disk path=/var/lib/libvirt/guest.qcow2,size=10,format=qcow2 Now, according to virt-install man page, my VM's cpu affinity should be set to pcpu 0 and 2 . But when I did virsh vcpuinfo $VM, it shows that the affinity is to all cpus. I checked the xml file of my VM and it has the cpuset attribute, but still my VM is running on all cpus.   ~Peeyush Gupta

...cpuacct 0 0 > > # cat /proc/self/cgroup > 7:cpuacct:/ > 3:cpuset:/ > 2:memory:/ > 1:cpu:/ > > virsh # vcpucount CLA-0 > maximum config 3 > maximum live 3 > current config 3 > current live 3 > > virsh # vcpuinfo CLA-0 > VCPU: 0 > CPU: 0 > State: running > CPU time: 5.7s > CPU Affinity: yyyyyyyy > > virsh # vcpupin CLA-0 --current > VCPU: CPU Affinity > ---------------------------------- > 0: 0-7 > 1: 0-7 > 2: 0-7 > > #...

Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl:

The following series implements libxl_domain_config_init as per the libxl API requirement that each type has an init function. The first function does this in an open coded manner and is proposed for Xen 4.2. The second function is RFC only since it moves the definition of this type into the IDL and makes the required infrastructure updates to enable this. I think this is more 4.3 material at

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

...+} diff --git a/tools/ocaml/libs/xl/genwrap.py b/tools/ocaml/libs/xl/genwrap.py index ea978bf..aab65f3 100644 --- a/tools/ocaml/libs/xl/genwrap.py +++ b/tools/ocaml/libs/xl/genwrap.py @@ -286,6 +286,7 @@ if __name__ == ''__main__'': "domain_config", "vcpuinfo", "event", + "device_usb" ] for t in blacklist: -- 1.7.9.5

This patch adds a new option for xen config files for directly mapping hardware io memory into a vm. Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 013270d..428da21 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -496,6 +496,17 @@ is given in hexadecimal and may either a span e.g.

...path, nb); - libxl_ptr_add(ctx, ret); + libxl_ptr_add(gc, ret); return ret; } diff -r 7b144fe8c528 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Wed Aug 11 14:39:44 2010 +0100 +++ b/tools/libxl/xl_cmdimpl.c Thu Aug 12 15:22:56 2010 +0100 @@ -3267,7 +3267,7 @@ static void print_vcpuinfo(uint32_t tdom void vcpulist(int argc, char **argv) { - libxl_dominfo *dominfo; + libxl_dominfo *dominfo, *domlist; libxl_vcpuinfo *vcpuinfo, *list = NULL; libxl_physinfo physinfo; int nb_vcpu, nb_domain, nrcpus; @@ -3279,7 +3279,7 @@ void vcpulist(int argc, char **argv)...