Re: [Qemu-devel] Guest freezes Refined TSC clocksource calibration ...

2011-10-02 Thread Mulyadi Santosa
Hi. :) On Sat, Oct 1, 2011 at 19:16, Onkar N Mahajan kern...@gmail.com wrote: Compiled 3.1.0-rc3+ from source (see attached config file) and updated the host(fc14) kernel ; So host is now running 3.1.0-rc3+ Now I also want to try to boot FC14 guest with this updated kernel , like this

Re: [Qemu-devel] Guest freezes Refined TSC clocksource calibration ...

2011-10-02 Thread Dor Laor
On 10/02/2011 09:24 AM, Mulyadi Santosa wrote: Hi. :) On Sat, Oct 1, 2011 at 19:16, Onkar N Mahajankern...@gmail.com wrote: Compiled 3.1.0-rc3+ from source (see attached config file) and updated the host(fc14) kernel ; So host is now running 3.1.0-rc3+ Now I also want to try to boot

Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: Questions about duplicate memory work

2011-10-02 Thread Avi Kivity
On 09/29/2011 09:46 PM, Robin Lee Powell wrote: On Thu, Sep 29, 2011 at 02:22:43PM -0300, Marcelo Tosatti wrote: On Wed, Sep 28, 2011 at 05:14:47PM -0700, Robin Lee Powell wrote: Please post the contents of /proc/meminfo and /proc/zoneinfo when this is happening. I

Re: [PATCH] KVM: x86: Use do_div for tsc deadline calculation

2011-10-02 Thread Avi Kivity
On 09/30/2011 02:50 PM, Jan Kiszka wrote: Required on i386 hosts. Thanks, applied. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: [PATCH] virtio-net: Read MAC only after initializing MSI-X

2011-10-02 Thread Michael S. Tsirkin
On Mon, Sep 19, 2011 at 05:19:49PM +0930, Rusty Russell wrote: On Mon, 19 Sep 2011 09:01:50 +0300, Michael S. Tsirkin m...@redhat.com wrote: On Mon, Sep 19, 2011 at 01:05:17PM +0930, Rusty Russell wrote: On Sat, 20 Aug 2011 23:00:44 +0300, Michael S. Tsirkin m...@redhat.com wrote:

Re: [PATCH] virtio-net: Read MAC only after initializing MSI-X

2011-10-02 Thread Michael S. Tsirkin
On Wed, Sep 28, 2011 at 09:30:51PM +0300, Sasha Levin wrote: On Mon, 2011-09-19 at 17:19 +0930, Rusty Russell wrote: On Mon, 19 Sep 2011 09:01:50 +0300, Michael S. Tsirkin m...@redhat.com wrote: On Mon, Sep 19, 2011 at 01:05:17PM +0930, Rusty Russell wrote: On Sat, 20 Aug 2011

[PATCH] KVM: Fix tsc deadline timer without irqchip_in_kernel()

2011-10-02 Thread Avi Kivity
vcpu-arch.apic may be NULL. Signed-off-by: Avi Kivity a...@redhat.com --- arch/x86/kvm/x86.c |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 83b839f..aa11707 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@

Re: [PATCH] qemu-kvm: device assignment: add 82599 PCIe Cap struct quirk

2011-10-02 Thread Michael S. Tsirkin
On Wed, Sep 28, 2011 at 08:20:33PM -0400, Donald Dutile wrote: commit f9c29774d2174df6ffc20becec20928948198914 changed the PCIe Capability structure version check from if 2 fail, to if ==1, size=x, if ==2, size=y, else fail. Turns out the 82599's VF has an errata where it's PCIe Cap struct

Re: how to assign a pci device to guest [with qemu.git upstream]?

2011-10-02 Thread Avi Kivity
On 09/29/2011 08:28 AM, Ren, Yongjie wrote: Now you'll be on the master branch (and it should track upstream master properly). Oh, thanks a lot. I didn't notice the qemu.git is using the 'memory/queue' branch by default. I've switched it to the 'master' tree. It seems device assignment

Re: qemu-kvm: Remaining relevant bits in kvm/

2011-10-02 Thread Avi Kivity
On 09/29/2011 08:10 PM, Marcelo Tosatti wrote: On Wed, Sep 28, 2011 at 05:05:57PM +0200, Jan Kiszka wrote: Hi all, in order to reduce the diff between qemu-kvm.git and upstream, getting rid of the kvm subdirectory would be nice. What bits there are actually still in use today? From

Re: [PATCH v3 1/6] iommu/core: split mapping to page sizes as supported by the hardware

2011-10-02 Thread Ohad Ben-Cohen
(sorry for the late response; we had a big holiday here and I was forced away from my keyboard :) On Tue, Sep 27, 2011 at 9:14 PM, Roedel, Joerg joerg.roe...@amd.com wrote: No. I suggest a simpler and shorter algorithm using the bit helpers. Ok, fair enough. I've revised the patches and

Re: [PATCH] KVM: Fix tsc deadline timer without irqchip_in_kernel()

2011-10-02 Thread Jan Kiszka
On 2011-10-02 11:51, Avi Kivity wrote: vcpu-arch.apic may be NULL. Signed-off-by: Avi Kivity a...@redhat.com --- arch/x86/kvm/x86.c |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 83b839f..aa11707 100644 ---

Re: [PATCH] KVM: Fix tsc deadline timer without irqchip_in_kernel()

2011-10-02 Thread Avi Kivity
On 10/02/2011 06:28 PM, Jan Kiszka wrote: @@ -615,9 +617,12 @@ static void update_cpuid(struct kvm_vcpu *vcpu) if (boot_cpu_data.x86_vendor == X86_VENDOR_INTEL best-function == 0x1) { best-ecx |= bit(X86_FEATURE_TSC_DEADLINE_TIMER); -

Re: [PATCH] KVM: Fix tsc deadline timer without irqchip_in_kernel()

2011-10-02 Thread Jan Kiszka
On 2011-10-02 18:30, Avi Kivity wrote: On 10/02/2011 06:28 PM, Jan Kiszka wrote: @@ -615,9 +617,12 @@ static void update_cpuid(struct kvm_vcpu *vcpu) if (boot_cpu_data.x86_vendor == X86_VENDOR_INTEL best-function == 0x1) { best-ecx |=

Re: [PATCH] KVM: Fix tsc deadline timer without irqchip_in_kernel()

2011-10-02 Thread Avi Kivity
On 10/02/2011 06:33 PM, Jan Kiszka wrote: On 2011-10-02 18:30, Avi Kivity wrote: On 10/02/2011 06:28 PM, Jan Kiszka wrote: @@ -615,9 +617,12 @@ static void update_cpuid(struct kvm_vcpu *vcpu) if (boot_cpu_data.x86_vendor == X86_VENDOR_INTEL best-function == 0x1) {

Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Avi Kivity
On 10/02/2011 02:45 AM, Robin Lee Powell wrote: I'm afraid clocksource=hpet didn't help much; after about 24 hours up, tcpdump hung the machine for for about 10 seconds. That may or may not be better than usual; I haven't been timing things precisely. My suspicion is that it's slightly better,

Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Robin Lee Powell
On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote: On 10/02/2011 02:45 AM, Robin Lee Powell wrote: I'm afraid clocksource=hpet didn't help much; after about 24 hours up, tcpdump hung the machine for for about 10 seconds. That may or may not be better than usual; I haven't been timing

Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Avi Kivity
On 10/02/2011 07:07 PM, Robin Lee Powell wrote: On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote: On 10/02/2011 02:45 AM, Robin Lee Powell wrote: I'm afraid clocksource=hpet didn't help much; after about 24 hours up, tcpdump hung the machine for for about 10 seconds. That may or

Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Robin Lee Powell
On Sun, Oct 02, 2011 at 07:12:42PM +0200, Avi Kivity wrote: On 10/02/2011 07:07 PM, Robin Lee Powell wrote: On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote: On 10/02/2011 02:45 AM, Robin Lee Powell wrote: I'm afraid clocksource=hpet didn't help much; after about 24 hours up,

Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Avi Kivity
On 10/02/2011 07:13 PM, Robin Lee Powell wrote: On Sun, Oct 02, 2011 at 07:12:42PM +0200, Avi Kivity wrote: On 10/02/2011 07:07 PM, Robin Lee Powell wrote: On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote: On 10/02/2011 02:45 AM, Robin Lee Powell wrote: I'm afraid

Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Robin Lee Powell
On Sun, Oct 02, 2011 at 07:21:08PM +0200, Avi Kivity wrote: On 10/02/2011 07:13 PM, Robin Lee Powell wrote: On Sun, Oct 02, 2011 at 07:12:42PM +0200, Avi Kivity wrote: On 10/02/2011 07:07 PM, Robin Lee Powell wrote: On Sun, Oct 02, 2011 at 07:06:35PM +0200, Avi Kivity wrote: On

Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Avi Kivity
Well, any messages? None I can find. I'll try again later today and double check. Please do. Alternatively, detailed instructions to reproduce? Start a VM. Wait a few days. Run tcpdump. The system locks up for 30+ seconds. How do you detect the lockup? Are you at the

Re: ethtool

2011-10-02 Thread Lucas Meneghel Rodrigues
On 10/01/2011 12:30 AM, pradeep wrote: Hello Amos, Lmr Couple of networking tests like ethtool, file_transfer..etc are not doing cleaning properly. Huge files are not getting deleted after the test. So guest running out of space for next tests. I will investigate Pradeep, thanks for

Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Robin Lee Powell
On Sun, Oct 02, 2011 at 03:38:29PM -0400, Avi Kivity wrote: Well, any messages? None I can find. I'll try again later today and double check. Please do. Oct 2 19:53:01 vrici dbus: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Oct 2 19:53:01

Re: Dirty page tracking in EPT

2011-10-02 Thread Nai Xia
Hi, On Sunday 02 October 2011 17:43:23 Prateek Sharma wrote: Hello , I came across the dirty-page tracking patch here: [https://lkml.org/lkml/2011/6/21/169] . There is some mention of dirty-bit tracking not working with EPT. Can someone please clarify this? Does this patch only work

Re: Dirty page tracking in EPT

2011-10-02 Thread Prateek Sharma
On Mon, Oct 3, 2011 at 9:04 AM, Nai Xia nai@gmail.com wrote: Hi, On Sunday 02 October 2011 17:43:23 Prateek Sharma wrote: Hello ,     I came across the dirty-page tracking patch here: [https://lkml.org/lkml/2011/6/21/169] . There is some mention of dirty-bit tracking not working with

Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: [kvm] Re: tcpdump locks up kvm host for a while.

2011-10-02 Thread Nikola Ciprich
When I run tcpdump on a *guest*, the entire guest completely freezes up; no response even to hitting enter on the console. virsh list also locks up whenever it tries to print state about that VM (but the others work fine), as does any other operation that touches the state of that VM. The