From: Gleb Natapov <gleb@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: No kernel interface to reset a VCPU
Date: Fri, 25 Sep 2009 20:13:56 +0300 [thread overview]
Message-ID: <20090925171356.GB30416@redhat.com> (raw)
In-Reply-To: <4ABCD915.5090503@siemens.com>
On Fri, Sep 25, 2009 at 04:52:05PM +0200, Jan Kiszka wrote:
> Hi all,
>
> looks to me like there is no way to properly reset the boot processor.
> The current pattern used by qemu[-kvm] is to reload all registers with
> their reset values. But that does not affect the internal VCPU states
> the KVM keeps in the kernel. They are only reset during VCPU setup or
> after receiving a SIPI (and the latter only helps with secondary CPUs).
>
Userspace should have access to internal VCPU states too, otherwise
migration will not work.
> So the only way around it with the current kernel interface is to
> destroy/recreate the BSP on reset, right? /me is looking into such an
> approach now.
I don't think destroying/recreating vcpu will work. I don't remember
exact details though.
>
> We stumbled over inconsistent VCPU states with our internal qemu-kvm
> tree. We have a legacy watchdog emulation here that triggered but failed
> to bring up the system again. I wasn't able to create a similar case
> with a standard environment yet, but I think it is not unrealistic for
> qemu-kvm as well. Hacking kvm_arch_vcpu_reset() into KVM that triggers
> on the right register values "solved" the issue here.
>
Can you find the root cause of the problem? As I said above qemu should
have full access to vcpu state for proper migration support. Not that
kvm_vcpu_reset()/kvm_apic_reset()/kvm_ioapic_reset()/kvm_pit_reset() is
bad idea. Actually I want to add them one day.
--
Gleb.
next prev parent reply other threads:[~2009-09-25 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 14:52 No kernel interface to reset a VCPU Jan Kiszka
2009-09-25 17:13 ` Gleb Natapov [this message]
2009-09-25 18:54 ` Jan Kiszka
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=20090925171356.GB30416@redhat.com \
--to=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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).