search for: vcpu1

>5. LTP testing might run very slow in SMP VTI Domain with credit scheduler. If binding VTI >and Xen0 vcpu, this bug won''t be there. Hi keir, In credit scheduler, two vcpus in the same domain may be scheduled on the same CPU. For instance, vcpu0 and vcpu1 are running on the same CPU, vcpu0 is doing spin_lock in guest, then time slice is due, vcpu0 is scheduled out before doing spin_unlock, vcpu1 is scheduled in, vcpu1 is also trying to get the same spin lock, yes vcpu1 can''t get this lock due to this lock has been got by vcpu0, so vcpu1 tig...

...: $ROOT | +- system | +- libvirtd.service | +- libvirt | +- qemu | | | +- vm1 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm2 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm3 | | | +- emulator |...

...pus': Permission denied The same log snippet with 4.5.0-10.el7_6.12 version, everything works well: 2019-08-28 16:13:22.837+0000: 26937: debug : virCgroupDetect:747 : Detected mount/mapping 0:cpu at /sys/fs/cgroup/cpu,cpuacct in /machine.slice/machine-qemu\x2d1\x2dvm12vms\x2d2coreshost1.scope/vcpu1 for pid -1 2019-08-28 16:13:22.837+0000: 26937: debug : virCgroupDetect:747 : Detected mount/mapping 1:cpuacct at /sys/fs/cgroup/cpu,cpuacct in /machine.slice/machine-qemu\x2d1\x2dvm12vms\x2d2coreshost1.scope/vcpu1 for pid -1 2019-08-28 16:13:22.837+0000: 26937: debug : virCgroupDetect:747 : Detect...

Hi, Is anybody know the purpose of this method (xen_evtchn_do_upcall)? When I run a user level application involved in TCP receiving and the SoftIRQ for eth0 on the same CPU core, everything is OK. But if I run them on 2 different cores, there will be xen_evtchn_do_upcall() existing (maybe when the local_bh_disable<http://www.cs.fsu.edu/~baker/devices/lxr/http/ident?i=local_bh_disable>() or

...+- libvirtd.service > | > +- libvirt > | > +- qemu > | | > | +- vm1 > | | | > | | +- emulator > | | +- vcpu0 > | | +- vcpu1 > | | > | +- vm2 > | | | > | | +- emulator > | | +- vcpu0 > | | +- vcpu1 > | | > | +- vm3 > | | > |...

...domain) calculates a domain''s total CPU time from its VCPU times using the code: if ( v->cpu_time > cpu_time ) cpu_time += v->cpu_time; This causes a VCPU''s time to only be counted if it is greater than the current total; so if VCPU0 has 10 seconds and VCPU1 has 5, the total will be 10, but if VCPU0 has 5 and VCPU10 has 10, the total will be 15. Is there a reason for this behavior? It seems more useful and intuitive to always total the VCPU times to obtain the CPU time. The attached patch removes the conditional, so that all VCPU times for a domain a...

...0 to host pcpu1 VM2 vcpu 0 to host pcpu1, VM2 vcpu 1 to host pcpu2 I executed inside the VMs a simple process that consume all available cpu, eg # cat /dev/zero > /dev/null on the host, using 'top', the reported cpu usage per qemu process is : with 1 process in VM1 and 1 process on vcpu1 in VM2 VM1 = 100%, VM2=100% explanation - without contention for pcpu2 shares are to be irrelevant (that's ok!) with 1 process in VM1 and 1 process on vcpu0 in VM2 VM1=33%, VM2=66% explanation - with contention on pcpu2, host cpu usage is partitioned according to shares (that's ok!) w...

...looking into bug [1]#195 and I have a couple of questions on how timer interrupts and virqs are handled. Is it possible for dom0 linux to irq balance timer interrupts to different cpus? That is, if xen sends a VIRQ_TIMER to vcpu0, backed by cpu0, is it possible for that interrupt to be handled by vcpu1, backed by cpu1 ? After putting in some debug code in to timer_interrupt in linux, I can see that when we get a "Time went backwards" message, that shadow->system_timestamp+offset is significantly behind the previous value of processed_system_time, and that the previous value was se...

...to a physical CPU. I found http://www.mail-archive.com/libvir-list at redhat.com/msg04562.html which mentioned some changes to the C API in the Python implementation, and was wondering if my understanding is correct. Say that I have a host system with 16 logical CPU's, 0-15. If I wanted to pin vcpu1 of a domain to CPUs 2 and 4, I would pass: domain.pinVcpu(1, (False, False, True, False, True, False....[and so on til I have 16 things])) In other words, pinVcpu accepts as arguments the vCPU that I wish to act on, and a 16 (or however many CPU's are present on the host) item tuple of True/F...

Hi all, I am working with libvirt and I am trying to set cpu affinity. Now I can always use      virsh vcpupin <domain_name> <vcpu> <pcpu> to pin vcpus to pcpus. I want to do it using Python API. Now, there is function pinVcpu which is supposed to do that. But this is not working. For example I gave      dom.pinVcpu(0,1) but still my vcpu affinity is for all the pcpus. The

...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 core usage of the 2 VMs by manipulating the cpu_shares parameter (or other parameters) so that 'top' at the h...

Hi Peeyush, If we want to pin vcpu1 of a domain to CPUs 3 and 4, we need to pass: dom.pinVcpu(1, (False, False, False, True, True, False....[and so on, til number of logical CPUs of host])) Can you please check this? Regards, Saurabh Deochake [NTT DATA] On Fri, Jul 19, 2013 at 11:45 AM, Peeyush Gupta <gpeeyush@ymail.com>...

...8/smp_affinity [root@rac10box2 ~]# cat /proc/irq/48/smp_affinity 0002 [root@rac10box2 ~]# cat /proc/interrupts |grep mpt 48: 342051 0 0 0 0 0 0 0 0 0 0 0 PCI-MSI-edge mpt2sas0-msix0 After change affinity to vcpu1, interrupt still happen on vcpu0. And sometimes we got "/No irq handler for vector (irq -1)/" and panic. qemu-dm.log shows error: pt_msixctrl_reg_write: guest enabling MSI-X, disable MSI-INTx translation pci_intx: intx=1 pt_msi_disable: Unmap msi with pirq 4f pt_msix_update_one: Update m...

...w MB per vcpu. shadow_memory = 8 name = "winHVMDomain" vcpus=1 #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5 #cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3 vif = [ ''type=ioemu, bridge=eth0'' ] disk = [ ''file:/root/xen.img,hda,w'', ''file:/root/win.iso,cdrom,r'' ] device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' boot="cda" vnc=1 vn...

...; # List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5 #cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3 # Number of Virtual CPUS to use, default is 1 #vcpus = 1 #---------------------------------------------------------------------------- # Define network interfaces. # By default, no network interfaces are configured. You may have one created # with sensible defaults using an empty v...

...List of which CPUS this domain is allowed to use, default Xen picks > #cpus = "" # leave to Xen to pick > #cpus = "0" # all vcpus run on CPU0 > #cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5 > #cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3 > > # Number of Virtual CPUS to use, default is 1 > #vcpus = 1 > > #---------------------------------------------------------------------------- > # Define network interfaces. > > # By default, no network interfaces are configured. You may have one > created...

...List of which CPUS this domain is allowed to use, default Xen picks +#cpus = "" # leave to Xen to pick +#cpus = "0" # all vcpus run on CPU0 +#cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5 +#cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3 + +# Optionally define mac and/or bridge for the network interfaces. +# Random MACs are assigned if not given. +#vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] +# type=ioemu specify the NIC is an ioemu device not netfront +vif = [ '...

...vcpu. shadow_memory = 8 name = "winHVMDomain" vcpus=1 #cpus = ""         # leave to Xen to pick #cpus = "0"        # all vcpus run on CPU0 #cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5 #cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3 vif = [ ''type=ioemu, bridge=eth0'' ] disk = [ ''file:/root/xen.img,hda,w'', ''file:/root/win.iso,cdrom,r'' ] device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' boot="cda" vnc=1...

...) XenPage 00000be9: caf=80000002, taf=e8000002 (XEN) VCPU information and callbacks for domain 0: (XEN) VCPU0: CPU0 [has=T] flags=0 upcall_pend = 00, upcall_mask = 00 dirty_cpus={0} cpu_affinity={0} (XEN) 100 Hz periodic timer (period 10 ms) (XEN) Notifying guest (virq 1, port 0, stat 0/-1/0) (XEN) VCPU1: CPU1 [has=F] flags=2 upcall_pend = 00, upcall_mask = 01 dirty_cpus={} cpu_affinity={0-31} (XEN) 100 Hz periodic timer (period 10 ms) (XEN) Notifying guest (virq 1, port 0, stat 0/-1/0) (XEN) General information for domain 1: (XEN) refcnt=3 nr_pages=264159 xenheap_pages=5 dirty_cpus={1} (XEN) handl...

I am currently looking at a bug report[1] which is happening when a Xen PVM guest with multiple VCPUs is running a high IO database load (a test script is available in the bug report). In experimenting it seems that this happens (or is getting more likely) when the number of VCPUs is 8 or higher (though I have not tried 6, only 2 and 4), having autogroup enabled seems to make it more likely, too