From: Peter Lieven <pl@dlhnet.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: qemu-kvm-1.0.1 - unable to exit if vcpu is in infinite loop
Date: Thu, 28 Jun 2012 18:29:35 +0200 [thread overview]
Message-ID: <4FEC866F.5000402@dlhnet.de> (raw)
In-Reply-To: <4FEC76A8.6060100@siemens.com>
On 28.06.2012 17:22, Jan Kiszka wrote:
> On 2012-06-28 17:02, Peter Lieven wrote:
>> On 28.06.2012 15:25, Jan Kiszka wrote:
>>> On 2012-06-28 15:05, Peter Lieven wrote:
>>>> Hi,
>>>>
>>>> i debugged my initial problem further and found out that the problem
>>>> happens to be that
>>>> the main thread is stuck in pause_all_vcpus() on reset or quit commands
>>>> in the monitor
>>>> if one cpu is stuck in the do-while loop kvm_cpu_exec. If I modify the
>>>> condition from while (ret == 0)
>>>> to while ((ret == 0)&& !env->stop); it works, but is this the right fix?
>>>> "Quit" command seems to work, but on "Reset" the VM enterns pause state.
>>> Before entering the wait loop in pause_all_vcpus, there are kicks sent
>>> to all vcpus. Now we need to find out why some of those kicks apparently
>>> don't reach the destination.
>> can you explain shot what exactly these kicks do? does these kicks lead
>> to leaving the kernel mode and returning to userspace?
> Yes. A signal is sent, and KVM returns from the guest to userspace on
> pending signals.
is there a description available how this process exactly works?
thanks
peter
next prev parent reply other threads:[~2012-06-28 16:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 13:05 qemu-kvm-1.0.1 - unable to exit if vcpu is in infinite loop Peter Lieven
2012-06-28 13:25 ` Jan Kiszka
2012-06-28 15:02 ` Peter Lieven
2012-06-28 15:22 ` Jan Kiszka
2012-06-28 16:29 ` Peter Lieven [this message]
2012-06-28 16:32 ` Avi Kivity
2012-06-28 19:27 ` Peter Lieven
2012-07-01 8:19 ` Avi Kivity
2012-07-01 19:18 ` Peter Lieven
2012-07-02 7:05 ` Jan Kiszka
2012-07-02 8:12 ` Peter Lieven
2012-08-06 15:11 ` Stefan Hajnoczi
2012-08-17 13:11 ` Jan Kiszka
2012-08-17 14:36 ` Jan Kiszka
2012-08-17 14:41 ` Jan Kiszka
2012-08-17 15:04 ` Jan Kiszka
2012-08-19 9:42 ` Avi Kivity
2012-08-21 7:21 ` Jan Kiszka
2012-08-21 8:23 ` Stefan Hajnoczi
2012-08-22 12:52 ` Peter Lieven
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=4FEC866F.5000402@dlhnet.de \
--to=pl@dlhnet.de \
--cc=jan.kiszka@siemens.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).