Re: NMI Injection to Guest

2009-07-25 Thread Gleb Natapov
On Sat, Jul 25, 2009 at 10:46:39PM +0200, Jiaqing Du wrote: > Hi list, > > I'm trying to extend OProfile to support guest profiling. One step of > my work is to push an NMI to the guest(s) when a performance counter > overflows. Please correct me if the following is not correct: > > counter overf

NMI Injection to Guest

2009-07-25 Thread Jiaqing Du
Hi list, I'm trying to extend OProfile to support guest profiling. One step of my work is to push an NMI to the guest(s) when a performance counter overflows. Please correct me if the following is not correct: counter overflow --> NMI to host --> VM exit --> "int $2" to handle NMI on host --> ...

Re: Timeout of network interface with OpenBSD 4.5 VM

2009-07-25 Thread Daniel Bareiro
Hi Chris. On Friday, 24 July 2009 08:03:29 -0400, Chris Dukes wrote: > http://zeniv.linux.org.uk/~pakrat/obsd45 > > 3 configs, 3 kernels. > All work on a Core2 Duo T7300 running 2.6.27-7-generic (From ubuntu > intrepid) crammed onto a laptop that's mostly running hardy. > The OpenBSD virtual ma

serial port again

2009-07-25 Thread Michael Tokarev
Finally, I'm trying to use serial port in a kvm guest. And as in my previous attempt, it does not quite work. qemu-kvm-0.10.5, 2.6.27.latest guest, 2.6.30.latest host. Running pppd over real serial/model lines for now. Dialing into kvm virtual machine from another location, kvm pppd acts as dia

Very high memory usage with KVM

2009-07-25 Thread Daniel Bareiro
Hi all! I have an installation with Ubuntu Hardy Heron server amd64 with KVM-62 from Ubuntu repositories installed on an HP Proliant DL380 G5 with two Xeon E5405 quadcore processors and 16 GiB of RAM which has six VMs with the following configuration of memory: Hostname | RAM =

Re: [PATCH v2 6/6] remove kvm_mmio_read and kvm_mmio_write

2009-07-25 Thread Marcelo Tosatti
On Tue, Jul 21, 2009 at 06:13:12PM -0400, Glauber Costa wrote: > all they did was to call a qemu function. Call this function instead. > > Signed-off-by: Glauber Costa > --- > qemu-kvm-x86.c |7 +-- > qemu-kvm.c | 34 -- > 2 files changed, 9 insertio

Re: [PATCH] qemu-kvm: fix error handling in msix vector add

2009-07-25 Thread Marcelo Tosatti
On Thu, Jul 23, 2009 at 04:34:13PM +0300, Michael S. Tsirkin wrote: > When adding a vector fails, the used counter should > not be incremented, otherwise on vector change we will > try to update the routing entry. > > Signed-off-by: Michael S. Tsirkin Applied, thanks. > --- > hw/msix.c | 10

Re: Host latency peaks due to kvm-intel

2009-07-25 Thread Avi Kivity
On 07/24/2009 12:41 PM, Jan Kiszka wrote: Jan (who is now patching his guest to avoid wbinvd where possible) Is there ever a case where it is required? What about under a hypervisor (i.e. check the hypervisor enabled bit). -- Do not meddle in the internals of kernels, for they are subt

Re: slow guest performance with build load, looking for ideas

2009-07-25 Thread Avi Kivity
On 07/16/2009 03:20 PM, Jes Sorensen wrote: It's really just a standard Intel or Supermicro motherboard in a box that has been painted purple (or blue/green now I guess), so it really shouldn't have extra numa factors compared to other Nehalem systems. Have you been transferred to marketing? -

Re: Host latency peaks due to kvm-intel

2009-07-25 Thread Avi Kivity
On 07/25/2009 12:55 PM, Jan Kiszka wrote: Avi Kivity wrote: On 07/24/2009 12:41 PM, Jan Kiszka wrote: I vaguely recall that someone promised to add a feature reporting facility for all those nice things, modern VM-extensions may or may not support (something like or even an extension

Re: Host latency peaks due to kvm-intel

2009-07-25 Thread Jan Kiszka
Avi Kivity wrote: > On 07/24/2009 12:41 PM, Jan Kiszka wrote: >> I vaguely recall that someone promised to add a feature reporting >> facility for all those nice things, modern VM-extensions may or may not >> support (something like or even an extension of /proc/cpuinfo). What is >> the state of th

Re: Host latency peaks due to kvm-intel

2009-07-25 Thread Avi Kivity
On 07/24/2009 12:41 PM, Jan Kiszka wrote: I vaguely recall that someone promised to add a feature reporting facility for all those nice things, modern VM-extensions may or may not support (something like or even an extension of /proc/cpuinfo). What is the state of this plan? Would be specifically