From: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Christoffer Dall <cd2436-WLbs8XpHrcb2fBVCVOL8/A@public.gmane.org>
Cc: kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andreas Nilsson <apn2107-WLbs8XpHrcb2fBVCVOL8/A@public.gmane.org>
Subject: Re: Exception handling between QEMU and KVM
Date: Wed, 01 Jul 2009 18:02:59 +0300 [thread overview]
Message-ID: <4A4B7AA3.6000400@redhat.com> (raw)
In-Reply-To: <7d08b87d0907010659v6e0efac1va906991402589ab7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 07/01/2009 04:59 PM, Christoffer Dall wrote:
> OK, my question is this:
>
> If I want to tell QEMU to quit from within the KVM_RUN ioctl in a way
> that causes QEMU to exit gracefully (e.g. free any allocated memory
> etc.) what is the way to do that?
>
Have KVM_RUN return -ESOMETHING, qemu should abort when it sees that.
> I have tried setting EXIT_REASON to both KVM_EXIT_EXCEPTION and
> KVM_EXIT_SHUTDOWN, but QEMU stays in the execution loop and
> re-executes the machine over and over.
>
> Is this some logic that has to be done architecture specifically in
> kvm_arch_post_run(...) or ?
>
I don't remember exactly. It also depends on what version of the source
you're looking at.
> And yes, any exceptions should be handled in KVM, but in the case of
> an unrecoverable error I'm left with reporting this to the user and
> end the QEMU process, right?
>
Yes. Current sources pause the vm so you can inspect guest state via
the monitor.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-07-01 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 3:28 Exception handling between QEMU and KVM Christoffer Dall
[not found] ` <7d08b87d0906302028q4bd7c9efifd399be9529fdc5b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-01 6:28 ` Alexander Graf
2009-07-01 9:00 ` Avi Kivity
[not found] ` <4A4B25A0.70800-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-01 13:59 ` Christoffer Dall
[not found] ` <7d08b87d0907010659v6e0efac1va906991402589ab7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-01 15:02 ` Avi Kivity [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=4A4B7AA3.6000400@redhat.com \
--to=avi-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=apn2107-WLbs8XpHrcb2fBVCVOL8/A@public.gmane.org \
--cc=cd2436-WLbs8XpHrcb2fBVCVOL8/A@public.gmane.org \
--cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.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