From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dmitry Vyukov" <dvyukov@google.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"KVM list" <kvm@vger.kernel.org>,
"Steve Rutherford" <srutherford@google.com>
Subject: Re: How bad is KVM_EXIT_INTERNAL_ERROR?
Date: Wed, 21 Dec 2016 12:00:06 +0100 [thread overview]
Message-ID: <814620bd-e9c8-cd82-df70-31db5e4b8566@redhat.com> (raw)
In-Reply-To: <CACT4Y+Zp5D+PXfvrrAf2xAkr1oM3+omFppBa+0k1G67KbShVDw@mail.gmail.com>
On 21/12/2016 10:41, Dmitry Vyukov wrote:
> Hello,
>
> I am getting some KVM_EXIT_INTERNAL_ERROR/KVM_INTERNAL_ERROR_EMULATION
> while fuzzing KVM. Does it indicate a bug in kvm code?
No, it just indicates something that isn't implemented. Other
KVM_EXIT_INTERNAL_ERROR cases indicate a bug in the userspace code.
If you're running nested virtualization and the nested guest manages to
kill the host, that's bad. Otherwise, they're harmless.
Paolo
> To make it clear, the context is that guest does all kind of weird
> stuff and if it kills itself it is fine. I am just trying to catch bad
> effects on the host.
> As far as I can tell, if qemu gets KVM_EXIT_INTERNAL_ERROR it will
> fail. So for user it will look like qemu misbehaves. E.g. it will not
> auto restart the VM.
> If KVM_EXIT_INTERNAL_ERROR/KVM_INTERNAL_ERROR_EMULATION is OK, are
> other KVM_EXIT_INTERNAL_ERROR error codes worse? Are there any other
> indications that host is affected in a bad way? I mean besides BUGs,
> WARNINGs and crashes of the host kernel.
>
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-12-21 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 9:41 How bad is KVM_EXIT_INTERNAL_ERROR? Dmitry Vyukov
2016-12-21 11:00 ` Paolo Bonzini [this message]
2016-12-21 11:06 ` Dmitry Vyukov
2016-12-21 13:26 ` Paolo Bonzini
2016-12-21 19:05 ` Dmitry Vyukov
2016-12-22 9:05 ` Paolo Bonzini
2016-12-22 10:44 ` Dmitry Vyukov
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=814620bd-e9c8-cd82-df70-31db5e4b8566@redhat.com \
--to=pbonzini@redhat.com \
--cc=dvyukov@google.com \
--cc=kvm@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=srutherford@google.com \
/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