KVM causing high CPU load since 2.6.26

2009-10-04 Thread Risanecek
Hello virtualists, Avi asked me to bring this issue to the ML, so here it is: Searching for solutions to a persistant problem with our KVM hosts, I stumbled across Avis post [REGRESSION] High, likely incorrect process cpu usage counters with kvm and 2.6.2[67] dated Sun, 31 Aug 2008 08:43:41

Heads up: More user-unaccessible x86 states?

2009-10-04 Thread Jan Kiszka
Hi, while preparing new IOCTLs to let user space query set the yet unaccessible NMI states (pending and masked) I also came across the interrupt shadow masks. Unless I missed something I would say that we so far break them in the rare case that a migration happens right while any of them is

Re: Heads up: More user-unaccessible x86 states?

2009-10-04 Thread Avi Kivity
On 10/04/2009 10:59 AM, Jan Kiszka wrote: Hi, while preparing new IOCTLs to let user space query set the yet unaccessible NMI states (pending and masked) I also came across the interrupt shadow masks. Unless I missed something I would say that we so far break them in the rare case that a

Re: [PATCH v2 2/4] KVM: introduce xinterface API for external interaction with guests

2009-10-04 Thread Avi Kivity
On 10/02/2009 10:19 PM, Gregory Haskins wrote: What: xinterface is a mechanism that allows kernel modules external to the kvm.ko proper to interface with a running guest. It accomplishes this by creating an abstracted interface which does not expose any private details of the guest or its

Re: [PATCH v2 3/4] KVM: add io services to xinterface

2009-10-04 Thread Avi Kivity
On 10/02/2009 10:19 PM, Gregory Haskins wrote: We want to add a more efficient way to get PIO signals out of the guest, so we add an xioevent interface. This allows a client to register for notifications when a specific MMIO/PIO address is touched by the guest. This is an alternative interface

Re: [PATCH v2 4/4] KVM: add scatterlist support to xinterface

2009-10-04 Thread Avi Kivity
On 10/02/2009 10:19 PM, Gregory Haskins wrote: This allows a scatter-gather approach to IO, which will be useful for building high performance interfaces, like zero-copy and low-latency copy (avoiding multiple calls to copy_to/from). The interface is based on the existing scatterlist

Re: Heads up: More user-unaccessible x86 states?

2009-10-04 Thread Jan Kiszka
Avi Kivity wrote: On 10/04/2009 10:59 AM, Jan Kiszka wrote: Hi, while preparing new IOCTLs to let user space query set the yet unaccessible NMI states (pending and masked) I also came across the interrupt shadow masks. Unless I missed something I would say that we so far break them in the

Re: Heads up: More user-unaccessible x86 states?

2009-10-04 Thread Avi Kivity
On 10/04/2009 12:50 PM, Jan Kiszka wrote: Avi Kivity wrote: On 10/04/2009 10:59 AM, Jan Kiszka wrote: Hi, while preparing new IOCTLs to let user space query set the yet unaccessible NMI states (pending and masked) I also came across the interrupt shadow masks. Unless I missed

Re: kvm guest: hrtimer: interrupt too slow

2009-10-04 Thread Michael Tokarev
Marcelo Tosatti wrote: Michael, Can you please give the patch below a try please? (without acpi_pm timer or priority adjustments for the guest). Sure. I'll try it out in a hour or two, while I can experiment freely because it's weekend. But I wonder... [] hrtimer: interrupt too slow,

PATCH: kvm-userspace: ksm support

2009-10-04 Thread Izik Eidus
From a8ca226de8efb4f0447e4ef87bf034cf18996745 Mon Sep 17 00:00:00 2001 From: Izik Eidus iei...@redhat.com Date: Sun, 4 Oct 2009 14:01:31 +0200 Subject: [PATCH] kvm-userspace: add ksm support Calling to madvise(MADV_MERGEABLE) on the memory allocations. Signed-off-by: Izik Eidus iei...@redhat.com

Re: PATCH: kvm-userspace: ksm support

2009-10-04 Thread Avi Kivity
On 10/04/2009 02:16 PM, Izik Eidus wrote: From a8ca226de8efb4f0447e4ef87bf034cf18996745 Mon Sep 17 00:00:00 2001 From: Izik Eidusiei...@redhat.com Date: Sun, 4 Oct 2009 14:01:31 +0200 Subject: [PATCH] kvm-userspace: add ksm support Calling to madvise(MADV_MERGEABLE) on the memory allocations.

buildbot failure in qemu-kvm on default_x86_64_debian_5_0

2009-10-04 Thread qemu-kvm
The Buildbot has detected a new failure of default_x86_64_debian_5_0 on qemu-kvm. Full details are available at: http://buildbot.b1-systems.de/qemu-kvm/builders/default_x86_64_debian_5_0/builds/94 Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/ Buildslave for this Build: b1_qemu_kvm_1

buildbot failure in qemu-kvm on default_i386_out_of_tree

2009-10-04 Thread qemu-kvm
The Buildbot has detected a new failure of default_i386_out_of_tree on qemu-kvm. Full details are available at: http://buildbot.b1-systems.de/qemu-kvm/builders/default_i386_out_of_tree/builds/33 Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/ Buildslave for this Build: b1_qemu_kvm_2

Re: [PATCH 1/2] KVM: x86: Refactor guest debug IOCTL handling

2009-10-04 Thread Avi Kivity
On 10/03/2009 12:31 AM, Jan Kiszka wrote: Much of so far vendor-specific code for setting up guest debug can actually be handled by the generic code. This also fixes a minor deficit in the SVM part /wrt processing KVM_GUESTDBG_ENABLE. Applied both, thanks. -- error compiling committee.c:

Re: [PATCH 2/2] KVM: x86: Preserve guest single-stepping on register

2009-10-04 Thread Avi Kivity
On 10/03/2009 12:31 AM, Jan Kiszka wrote: Give user space more flexibility /wrt its IOCTL order. So far updating the rflags via KVM_SET_REGS ignored potentially set single-step flags. Now they will be kept. kvm_rip_write(vcpu, regs-rip); - kvm_x86_ops-set_rflags(vcpu,

Re: Q: Stopped VM still using host cpu CPU ?

2009-10-04 Thread Avi Kivity
On 10/01/2009 12:32 PM, Daniel Schwager wrote: Hi, we are running some stopped (sending stop via kvm-monitor socket) vm's on our system. My intention was to pause (stop) the vm's and unpause (cont) them on demand (very fast, without time delay, within 2 seconds ..). After 'stop'ing, the vm's

Re: Q: Stopped VM still using host cpu CPU ?

2009-10-04 Thread Avi Kivity
On 10/01/2009 01:47 PM, Daniel Schwager wrote: If i send a signal STOP/CONT (kill -STOPpid or kill -CONTpid) to the KVM-process, it looks like the kvm does not (sure ;-) use any host CPU usage. - Are there some side effects using this approach ? (e.g. with networking, ...) The

Re: KVM: x86: disable paravirt mmu reporting

2009-10-04 Thread Avi Kivity
On 10/02/2009 12:28 AM, Marcelo Tosatti wrote: Disable paravirt MMU capability reporting, so that new (or rebooted) guests switch to native operation. Paravirt MMU is a burden to maintain and does not bring significant advantages compared to shadow anymore. Applied, thanks. -- error

RE: Q: Stopped VM still using host cpu CPU ?

2009-10-04 Thread Daniel Schwager
After 'stop'ing, the vm's still using CPU-load, like the top will tell PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 25983 root 20 0 495m 407m 1876 R 8.9 2.5 228:09.15 qemu-system-x86 It shouldn't do that. ok. How long is this after the 'stop'? 30

Re: Q: Stopped VM still using host cpu CPU ?

2009-10-04 Thread Avi Kivity
On 10/04/2009 05:21 PM, Daniel Schwager wrote: How long is this after the 'stop'? 30 seconds or 2 days ... the process takes CPU all the time Can you take an oprofile run to see where it's spending its time? -- error compiling committee.c: too many arguments to function -- To

Re: [PATCH 04/47] KVM: x86: Disallow hypercalls for guest callers in rings 0

2009-10-04 Thread Avi Kivity
On 09/30/2009 08:58 AM, Jan Lübbe wrote: Hi! On Wed, 2009-08-26 at 13:29 +0300, Avi Kivity wrote: From: Jan Kiszkajan.kis...@siemens.com So far unprivileged guest callers running in ring 3 can issue, e.g., MMU hypercalls. Normally, such callers cannot provide any hand-crafted MMU command

Re: Heads up: More user-unaccessible x86 states?

2009-10-04 Thread Jan Kiszka
Avi Kivity wrote: On 10/04/2009 12:50 PM, Jan Kiszka wrote: Avi Kivity wrote: On 10/04/2009 10:59 AM, Jan Kiszka wrote: Hi, while preparing new IOCTLs to let user space query set the yet unaccessible NMI states (pending and masked) I also came across the interrupt shadow masks.

Re: [PATCH 2/2] KVM: x86: Preserve guest single-stepping on register

2009-10-04 Thread Jan Kiszka
Avi Kivity wrote: On 10/03/2009 12:31 AM, Jan Kiszka wrote: Give user space more flexibility /wrt its IOCTL order. So far updating the rflags via KVM_SET_REGS ignored potentially set single-step flags. Now they will be kept. kvm_rip_write(vcpu, regs-rip); -

Re: docs on storage pools?

2009-10-04 Thread Cole Robinson
Richard Wurman wrote: So far I've been using files and/or LVM partitions for my VMs -- basically by using virt-manager and modifying existing XML configs and just copying my VM files to be reused. I'm wondering how KVM storage pools work -- at first I thought it was something like KVM's

[PATCH 11/21] i8254.c: Add pr_fmt(fmt)

2009-10-04 Thread Joe Perches
Add pr_fmt(fmt) pit: fmt Strip pit: prefixes from pr_debug Signed-off-by: Joe Perches j...@perches.com --- arch/x86/kvm/i8254.c | 12 +++- 1 files changed, 7 insertions(+), 5 deletions(-) diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c index 82ad523..fa83a15 100644 ---

[PATCH 00/21] pr_dbg, pr_fmt

2009-10-04 Thread Joe Perches
One possible long term goal is to stop adding #define pr_fmt(fmt) KBUILD_MODNAME : fmt to source files to prefix modulename to logging output. It might be useful to eventually have kernel.h use a standard #define pr_fmt which includes KBUILD_MODNAME instead of a blank or empty define.

buildbot failure in qemu-kvm on disable_kvm_x86_64_out_of_tree

2009-10-04 Thread qemu-kvm
The Buildbot has detected a new failure of disable_kvm_x86_64_out_of_tree on qemu-kvm. Full details are available at: http://buildbot.b1-systems.de/qemu-kvm/builders/disable_kvm_x86_64_out_of_tree/builds/34 Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/ Buildslave for this Build:

Re: kvm guest: hrtimer: interrupt too slow

2009-10-04 Thread Marcelo Tosatti
On Sun, Oct 04, 2009 at 04:01:02PM +0400, Michael Tokarev wrote: Marcelo Tosatti wrote: Michael, Can you please give the patch below a try please? (without acpi_pm timer or priority adjustments for the guest). Sure. I'll try it out in a hour or two, while I can experiment freely because