All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: Zachary Amsden <zamsden@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, kvm@vger.kernel.org
Subject: Re: 2.6.32 guest with paravirt clock enabled hangs on 2.6.37.6 host (w qemu-kvm-0.13.0)
Date: Mon, 9 May 2011 21:27:32 +0200	[thread overview]
Message-ID: <20110509192732.GD2202@nik-comp.lan> (raw)
In-Reply-To: <4DC832B5.6000205@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

> That's a pretty wide range to be bisecting, and I think we know for a  
> fact there were some kvmclock related bugs in that range.
thats true, I might try to pick those that seem related and see if it
helpts..
>
> If you are looking for something causing problems with tcpdump, I'd  
> suggest getting rid of kvmclock in your testing and using TSC instead;  
that's the problem, I can't reproduce the problems without kvm-clock
enabled, so it must be related to it somehow..

> if you're looking to verify that kvmclock related changed have been  
> backported to -stable, rather than bisect and run into bugs, it would  
> probably be faster to check the commit logs for arch/x86/kvm/x86.c and  
> make sure you're not missing anything from me or Glauber that has been  
> applied to the most recent branch.
yup, I'll try and report...
thanks for the hints!
n.


>
> Zach
>

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2011-05-09 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08 18:33 2.6.32 guest with paravirt clock enabled hangs on 2.6.37.6 host (w qemu-kvm-0.13.0) Nikola Ciprich
2011-05-08 18:41 ` Nikola Ciprich
2011-05-08 18:53 ` Michael Tokarev
2011-05-08 19:06   ` Nikola Ciprich
2011-05-09  3:06     ` David Ahern
2011-05-09 17:32     ` Zachary Amsden
2011-05-09 18:25       ` Nikola Ciprich
2011-05-09 18:30         ` Zachary Amsden
2011-05-09 19:27           ` Nikola Ciprich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110509192732.GD2202@nik-comp.lan \
    --to=nikola.ciprich@linuxbox.cz \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=zamsden@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.