public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: chris@versecorp.net
Cc: kvm@vger.kernel.org, rl@brabbel.net
Subject: Re: Hangs
Date: Fri, 21 Nov 2008 20:32:37 +0100	[thread overview]
Message-ID: <20081121193237.GA22203@dmt.cnet> (raw)
In-Reply-To: <20081120171057.GA13638@versecorp.net>

On Thu, Nov 20, 2008 at 09:10:57AM -0800, chris@versecorp.net wrote:
> On Wed, Nov 19, 2008 at 02:43:42PM -0800, chris@versecorp.net wrote:
> > Thanks for the responses,
> > 
> > I'm not sure if my problem is the same as Roland's, but it definitely sounds
> > plausible.  I had been running ntpdate in the host to synchronize time every hour (in a cron job), so it sounds as if we could be seeing the same issue.
> > 
> 
> Actually, with ntpdate taken out of crontab, I'm still seeing periodic
> hangs, so it's either a different problem or I'm hitting it in a
> different manner.
> 
> OK, I installed kvm-79 and kernel 2.6.27.6, and here's the the kvm-stat output 
> with 1 guest hung and 3 more operational:

<snip>

> If I shut down the 3 operational guests leaving just the hung guest, the
> kvm-stat output is all 0s:
> 
>  efer_relo      exits  fpu_reloa  halt_exit  halt_wake  host_stat  hypercall  insn_emul  insn_emul     invlpg   io_exits  irq_exits  irq_windo  largepage  mmio_exit  mmu_cache  mmu_flood  mmu_pde_z  mmu_pte_u  mmu_pte_w  mmu_recyc  mmu_shado  nmi_windo   pf_fixed   pf_guest  remote_tl  request_i  signal_ex  tlb_flush
>          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0

So the guest is not actually running here, which means its
QEMU that its hanging at.

> The hung guest in this case was run with this command:
> 
> sudo /usr/local/bin/qemu-system-x86_64             \
>      -daemonize                                    \
>      -no-kvm-irqchip                               \
>      -hda Imgs/ndev_root.img                       \
>      -m 1024                                       \
>      -cdrom ISOs/ubuntu-8.10-server-amd64.iso      \
>      -vnc :4                                       \
>      -net nic,macaddr=DE:AD:BE:EF:04:04,model=e1000 \
>      -net tap,ifname=tap4,script=/home/chris/kvm/qemu-ifup.sh \
>      >>& Logs/ndev_run.log
> 
> 
> I should also mention that when the guest is hung, I can still switch
> to the monitor with ctrl-alt 2. So, at least it's a little bit alive.

In coma perhaps.

> I've also noticed that the behavior with the hung guest is slightly
> different on kvm-79 than it was earlier. When the guest hangs, the kvm
> process in the host doesn't spin at 100% busy any longer - the guest is
> just unresponsive at both the network and VNC console.

> Also, I've noticed that if I reset the guest from the monitor, the
> guest will boot up again, and I can get through to it on the network,
> but strangely, the mouse and keyboard will still be hung at the
> VNC console (except that I can still switch back and forth to the
> monitor).
>
> Hope some of this helps, let me know if you need to me to provide any
> other troubleshooting info.

$ gdb -p pid-of-qemu

(gdb) info threads

Print the backtrace for every thread with:

(gdb) thread N
(gdb) bt


  reply	other threads:[~2008-11-21 22:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 22:43 Hangs chris
2008-11-20 17:10 ` Hangs chris
2008-11-21 19:32   ` Marcelo Tosatti [this message]
2008-11-21 23:43     ` Hangs Roland Lammel
2008-11-22 17:54     ` Hangs chris
     [not found]       ` <519a8b110811280305v764fade1w9d02f5c9188f56e5@mail.gmail.com>
2008-11-28 12:35         ` Hangs xming
2008-12-02 10:47           ` Hangs xming
2008-12-02 12:09             ` Hangs Avi Kivity
2008-12-02 20:58               ` Hangs chris
2008-12-02 23:01                 ` Hangs xming
2008-12-03  1:20                   ` Hangs chris
2008-12-03  9:13                     ` Hangs xming
2008-12-03 10:44                 ` Hangs Avi Kivity
2008-12-03 17:49                   ` Hangs chris
2008-12-18 18:05                     ` Hangs chris
  -- strict thread matches above, loose matches on Subject: below --
2008-11-14 15:34 Hangs Chris Jones
2008-11-16 16:36 ` Hangs Chris Jones
2008-11-18 21:34 ` Hangs Marcelo Tosatti
2008-11-19 10:57   ` Hangs Roland Lammel
2008-11-19 21:53     ` Hangs Roland Lammel
     [not found]       ` <20081120015600.GB10846@dmt.cnet>
2008-11-21 15:55         ` Hangs Glauber Costa
2008-11-21 20:29           ` Hangs Roland Lammel
2008-11-21 21:01             ` Hangs Daniel P. Berrange
2008-11-21 23:46               ` Hangs Roland Lammel
2008-12-06 23:18                 ` Hangs Roland Lammel
2008-12-09  0:34                   ` Hangs xming

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=20081121193237.GA22203@dmt.cnet \
    --to=mtosatti@redhat.com \
    --cc=chris@versecorp.net \
    --cc=kvm@vger.kernel.org \
    --cc=rl@brabbel.net \
    /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