search for: vcpu0

Add self pause ability, which is required by vcpu0/dom0 when running on a AP. This can''t be satisfied by existing interface, since the new flag also serves as a sync point. Signed-off-by Kevin Tian <kevin.tian@intel.com> diff -r d5315422dbc8 xen/common/domain.c --- a/xen/common/domain.c Mon May 14 18:35:31 2007 -0400 +++ b/xen/comm...

On Wed, Oct 15, 2014 at 01:49:55PM +0000, VONDRA Alain wrote: > If I do kill -9, do I get a core dump ? I'm not sure, but ... > Killall does nothing the process is still alive... > Each time I got this hang, I find only umount -f /tmp/xxxx to force > qemu-img to stop. Are you sure this couldn't be an NFS server problem? Any message or errors in 'dmesg'? Any kernel

....461031] nfs: server 192.203.100.247 not responding, still trying > [475748.461034] nfs: server 192.203.100.247 not responding, still trying These are a problem, if they are coincident with qemu-img hanging. Use 'dmesg -w' to check. > And a lot of : > [785084.263606] kvm [12719]: vcpu0 unhandled rdmsr: 0x345 > [785084.269594] kvm [12719]: vcpu0 unhandled wrmsr: 0x40 data 0 > [785084.269999] kvm [12719]: vcpu0 unhandled wrmsr: 0x60 data 0 > [785084.270406] kvm [12719]: vcpu0 unhandled wrmsr: 0x41 data 0 > [785084.270826] kvm [12719]: vcpu0 unhandled wrmsr: 0x61 data 0...

...or KVM. On my brand new System ;-), but also with my older System. I have big problems with KVM guests "slow slow slow", the DomU's are also CentOS 7 virt-manager is also broken with the 7.1 The "old" Bug in the Kernel is really bad, I have several hundreds log from the vcpu0 Problem. thank's for a answer, -- mit freundlichen Gr?ssen / best regards, G?nther J. Niederwimmer

...00.247 not responding, still trying [475748.461028] nfs: server 192.203.100.247 not responding, still trying [475748.461031] nfs: server 192.203.100.247 not responding, still trying [475748.461034] nfs: server 192.203.100.247 not responding, still trying And a lot of : [785084.263606] kvm [12719]: vcpu0 unhandled rdmsr: 0x345 [785084.269594] kvm [12719]: vcpu0 unhandled wrmsr: 0x40 data 0 [785084.269999] kvm [12719]: vcpu0 unhandled wrmsr: 0x60 data 0 [785084.270406] kvm [12719]: vcpu0 unhandled wrmsr: 0x41 data 0 [785084.270826] kvm [12719]: vcpu0 unhandled wrmsr: 0x61 data 0 [785084.271231] kvm...

When using the 4.3.0-3/4.3.0-3+b1 xen packages from the Debian archive, things work fine. However, when we compile the xen=4.3.0-3 source package ourselves, we run into an issue launching an HVM. As soon as the HVM bios is loaded, VCPU0 gets a triple fault and the HVM is destroyed (this is with "loglvl=all guest_loglvl=all hvm_debug=3" boot options). (XEN) HVM1: Multiprocessor initialisation: (XEN) HVM1: - CPU0 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM1: Writing SMBIOS tables ... (XEN) HVM...

...] nfs: server 192.203.100.247 > not responding, still trying [475748.461034] nfs: server > 192.203.100.247 not responding, still trying These are a problem, if they are coincident with qemu-img hanging. Use 'dmesg -w' to check. > And a lot of : > [785084.263606] kvm [12719]: vcpu0 unhandled rdmsr: 0x345 > [785084.269594] kvm [12719]: vcpu0 unhandled wrmsr: 0x40 data 0 > [785084.269999] kvm [12719]: vcpu0 unhandled wrmsr: 0x60 data 0 > [785084.270406] kvm [12719]: vcpu0 unhandled wrmsr: 0x41 data 0 > [785084.270826] kvm [12719]: vcpu0 unhandled wrmsr: 0x61 dat...

...rent source) will pull in this regression since seabios-1.7.4 is now in the Debian repositories. ________________________________________ From: Moyer, Keith Sent: Monday, February 03, 2014 9:57 AM To: pkg-xen-devel at lists.alioth.debian.org Subject: 4.3.0-3 fresh build - hvmloader Triple fault on VCPU0 When using the 4.3.0-3/4.3.0-3+b1 xen packages from the Debian archive, things work fine. However, when we compile the xen=4.3.0-3 source package ourselves, we run into an issue launching an HVM. As soon as the HVM bios is loaded, VCPU0 gets a triple fault and the HVM is destroyed (this is with...

>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...

Hi all, I have installed a CentOS-8 server to accomplish some tests using kvm guests ? All these guests are centos8 also. When these guests starts, I always see errors like: [ 589.687915] kvm [2133]: vcpu0, guest rIP: 0xffffffff81a5bc98 disabled perfctr wrmsr: 0xc2 data 0xffff [ 596.210773] kvm [2201]: vcpu0, guest rIP: 0xffffffffb885bc98 disabled perfctr wrmsr: 0xc2 data 0xffff Is this a bug? I am not using virt-manager to create guests configuration ? Any idea? Kernel release is: 4.18.0-80.11....

...m trying to retrieve this layout : $ROOT | +- system | +- libvirtd.service | +- libvirt | +- qemu | | | +- vm1 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm2 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm3 | | | +...

Xen/MCE: vMCE injection In our test for win8 guest mce, we find a bug that no matter what SRAO/SRAR error xen inject to win8 guest, it always reboot. The root cause is, current Xen vMCE logic inject vMCE# only to vcpu0, this is not correct for Intel MCE (Under Intel arch, h/w generate MCE# to all CPUs). This patch fix vMCE injection bug, injecting vMCE# to all vcpus. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> diff -r 133664c6bfb4 xen/arch/x86/cpu/mcheck/vmce.c --- a/xen/arch/x86/cpu/mcheck/vmce....

.../* Shouldn''t return */ + while(1); + } + + if (!freeze_domains()) + { + pmprintk(XENLOG_ERR, "Failed to freeze domains\n"); + return -EINVAL; + } + + if (current->processor == 0) { + int ret; + + pmprintk(XENLOG_INFO, "vcpu0 on cpu0, sleep direclty\n"); + ret = enter_state(acpi_sinfo.sleep_state); + thaw_domains(); + return ret; + } + + pmprintk(XENLOG_INFO, "vcpu0 on cpu%d, pause self and notify cpu0\n", + current->processor); + cpu_raise_softirq(0, PM_SOFTIRQ); +...

I''m just doing some testing on the gplpv drivers with different ways of handling interrupts, and I''m trying a scheme where each xen device (eg vbd/vif) driver attaches to the same IRQ as the pci driver, and each handles it in sequence. In testing though, I noticed the following when logging what each ISR is doing: 60.32381439 - evtchn event on port 5 60.32384109 - port 5

...1] nfs: server 192.203.100.247 > not responding, still trying [475748.461034] nfs: server > 192.203.100.247 not responding, still trying These are a problem, if they are coincident with qemu-img hanging. Use 'dmesg -w' to check. > And a lot of : > [785084.263606] kvm [12719]: vcpu0 unhandled rdmsr: 0x345 > [785084.269594] kvm [12719]: vcpu0 unhandled wrmsr: 0x40 data 0 > [785084.269999] kvm [12719]: vcpu0 unhandled wrmsr: 0x60 data 0 > [785084.270406] kvm [12719]: vcpu0 unhandled wrmsr: 0x41 data 0 > [785084.270826] kvm [12719]: vcpu0 unhandled wrmsr: 0x61 dat...

...m0_getdomaininfo_t for a 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...

I''ve been 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 p...

...ries are not being created for our domains and hence the comamnd "cpu-stats <domain>" is failing. Below is the snippet of logs collected with debug logs enabled for libvirt. 2013-08-21 15:03:35.162+0000: 1273: error : virCgroupMakeGroup:708 : Make group /machine/anusha.libvirt-qemu/vcpu0 2013-08-21 15:03:35.162+0000: 1273: error : virCgroupMakeGroup:729 : Makecontroller /dev/cgroup_cpu/machine/anusha.libvirt-qemu/vcpu0/ 2013-08-21 15:03:35.162+0000: 1273: error : virCgroupMakeGroup:745 : Failed to create controller cpu for group Where anusha --> is the domain which was created...

...nters related to cpu and memory usage related to KVM guests hosted by the host where this code runs. I noticed that depending on the O.S. running on the host , these counters are not found at the same location : CentOS 7 : ls /sys/fs/cgroup/cpuacct/machine.slice/machine-qemu\\x2drhel6.0.scope/vcpu0 cgroup.clone_children cgroup.procs cpuacct.usage cpu.cfs_period_us cpu.rt_period_us cpu.shares notify_on_release cgroup.event_control cpuacct.stat cpuacct.usage_percpu cpu.cfs_quota_us cpu.rt_runtime_us cpu.stat tasks ]# RHEL6 : ls /cgroup/cpuacct/libvirt/qemu/VM_Orion-1/v...

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