kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
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: Sun, 08 May 2011 21:06:18 -0600	[thread overview]
Message-ID: <4DC75A2A.70406@gmail.com> (raw)
In-Reply-To: <20110508190637.GB7918@nik-comp.lan>



On 05/08/11 13:06, Nikola Ciprich wrote:
> OK,
> I see.. the problem is, that I'm trying to hunt down bug causing hangs
> when 2.6.32 guests try to run tcpdump - this seems to be reproducible even on latest 2.6.32.x, and seems like it depends on kvm-clock..
> So I was thinking about bisecting between 2.6.32 and latest git which doesn't seem to suffer this problem but hitting another (different) problem in 2.6.32 complicates thinks a bit :(
> If somebody would have some hint on how to proceed, I'd be more then grateful..
> cheers

Have you tried enabling gdbserver in the qemu monitor and then attaching
gdb to the guest once it hangs?

David

  reply	other threads:[~2011-05-09  3:06 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 [this message]
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

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=4DC75A2A.70406@gmail.com \
    --to=dsahern@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=nikola.ciprich@linuxbox.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).