From: Marcelo Tosatti <mtosatti@redhat.com>
To: Amos Kong <kongjianjun@gmail.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: Fwd: Guest hangs when I do general operation.
Date: Tue, 7 Sep 2010 18:39:10 -0300 [thread overview]
Message-ID: <20100907213910.GA16686@amt.cnet> (raw)
In-Reply-To: <AANLkTim8OyHmV1oEKBS2F6NafSApjj=1G_zYOO7v5uMi@mail.gmail.com>
On Tue, Sep 07, 2010 at 10:43:38AM +0800, Amos Kong wrote:
> ---------- Forwarded message ----------
> From: Amos Kong <kongjianjun@gmail.com>
> Date: Tue, Sep 7, 2010 at 7:49 AM
> Subject: Guest hangs when I do general operation.
> To: 王箫 <sirouni@gmail.com>
>
>
> kvm upstream: 43e413f7db1a4a90671dda0b1d6c1f8cb30673ed KVM: Whitespace
> changes to remove differences wrt kvm-updates/2.6.37
> qemu upstream: cb93bbdd7db92e50ff5e60a346b23df68acae46b Fix OpenBSD
> linker warning
>
> # ./x86_64-softmmu/qemu-system-x86_64 ~/win7-32.qcow2 -m 1024 -vnc :0
> -usbdevice tablet -cpu qemu64 -snapshot -enable-kvm -bios pc-bios/bios.bin
>
> Guest hangs when I do general operation.
> It's fine when using upstream qemu-kvm. this problem only occurred
> one time when I debug by gdb, after execute 'continue', guest runs
> normally.
>
> debug msg of (qemu + kvm)
> (gdb) c
> Continuing.
>
> Program received signal SIGUSR2, User defined signal 2.
> 0x00007fc7d4d7bfb3 in select () at ../sysdeps/unix/syscall-template.S:82
> 82 ../sysdeps/unix/syscall-template.S: No such file or directory.
> in ../sysdeps/unix/syscall-template.S
> (gdb) bt
Try "handle SIGUSR2 nostop" in gdb before executing qemu-kvm.
prev parent reply other threads:[~2010-09-08 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimdYgbQ_+03mEpLjhnH=BE_jBOdCOikxNkAxs47@mail.gmail.com>
2010-09-07 2:43 ` [Qemu-devel] Fwd: Guest hangs when I do general operation Amos Kong
2010-09-07 17:55 ` Blue Swirl
2010-09-08 2:51 ` Amos Kong
2010-09-07 21:39 ` Marcelo Tosatti [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=20100907213910.GA16686@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kongjianjun@gmail.com \
--cc=kvm@vger.kernel.org \
--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).