From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: SMP reboot issue
Date: Wed, 10 Oct 2007 12:26:12 +0200 [thread overview]
Message-ID: <470CA8C4.1020208@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A02364257-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Dong, Eddie wrote:
> SMP reboot failed with various phenomena such as user level
> "unhandled vm exit: 0x80000021 ..." when rebooting SMP RHEL5U
> or "execption 8 (0)..." when rebooting XP etc. The reason is that
> we are not correctly reset VCPU. create_vcpu does some initialization
> work which should be part of reset job. So reset_vcpu can't do full
> VCPU reset and thus cause AP reboot failure.
> The best approach is to re-org above 2 functions to make it
> clear that everything will be re-initialized in vcpu_reset. create_vcpu
> probably only allocate memory and do initialization only for those
> communicating with user level data structure. while leave others
> including MMU reset to vcpu_reset. For now, let us
> use this small patch to fix current issue: GUEST_CR3 in VMCS is
> not correctly reseted due to enter_rmode issue.
> With this I get XPSP2 acpi SMP guest reboot successfully
> and also SMP Linux RHEL5U.
> thanks, eddie
>
>
>
Applied, thanks,
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-10-10 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 6:26 SMP reboot issue Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02364257-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-10 10:26 ` 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=470CA8C4.1020208@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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