qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu hangs on windows
Date: Wed, 23 Jul 2008 18:46:06 +0200	[thread overview]
Message-ID: <fb249edb0807230946j53efb654x541997fa659f70e1@mail.gmail.com> (raw)
In-Reply-To: <566555.11493.qm@web94803.mail.in2.yahoo.com>

2008/7/22 sathish kumar <sathishs_45@yahoo.com>:
> Thanks for the response.
>
> i tried according to your suggestion.
>
> Still it hangs.

So that's a different problem than I had. Is your guest kernel hanging
or is all of qemu hanging? (as in ctrl-alt-2 doesn't work anymore). Is
it always reproducible and always hangs in the same place? If so then
just connect gdb and the backtrace should tell you what's wrong.

Regards

  reply	other threads:[~2008-07-23 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22  4:31 [Qemu-devel] Qemu hangs on windows sathish kumar
2008-07-23 16:46 ` andrzej zaborowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-21 12:31 sathish kumar
2008-07-22  2:04 ` andrzej zaborowski

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=fb249edb0807230946j53efb654x541997fa659f70e1@mail.gmail.com \
    --to=balrogg@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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).