From: Avi Kivity <avi@redhat.com>
To: Eric Lacombe <goretux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [x86] - technical questions about HV implementation on Intel VT
Date: Mon, 27 Oct 2008 18:38:03 +0200 [thread overview]
Message-ID: <4905EE6B.9070000@redhat.com> (raw)
In-Reply-To: <200810271529.26821.goretux@gmail.com>
Eric Lacombe wrote:
> Hi,
>
> Thanks for your answer.
> I will eventually add a netconsole, but for now, I find how to bypass my
> problem (getting debug information).
>
> However I come with a new question, related to an unexpected VM-exit.
> The scenario is as follows:
> 1. some setup occur
> 2. vmlaunch is executed by a function F, so the guest is launched. This guest
> (as I explained in my previous mail) executes the end of the function F.
> 3. The end of F, do some "printk" then return to the module init function.
>
> The problem is that I get a VM-exit during the step 3. In fact after the
> first "printk", a vm-exit occurs with exit_reason=2 (triple-fault).
>
> Do you have an idea of what could be the cause of this vm-exit?
>
Almost any emulation error can cause this. Something goes wrong, an
exception is raised, can't be handled due to the same problem (or maybe
another one), triple fault.
You need to print out the entire contents of the vmcs before the last
entry and check it out carefully.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-10-27 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 17:27 [x86] - technical questions about HV implementation on Intel VT Eric Lacombe
2008-10-21 9:05 ` Avi Kivity
2008-10-27 14:29 ` Eric Lacombe
2008-10-27 16:38 ` Avi Kivity [this message]
[not found] <200903241822.11529.goretux@gmail.com>
[not found] ` <200904071926.30643.goretux@gmail.com>
2009-04-14 12:24 ` Eric Lacombe
2009-04-20 17:53 ` Eric Lacombe
2009-04-20 18:22 ` Avi Kivity
2009-04-21 11:16 ` Eric Lacombe
2009-04-29 14:50 ` Eric Lacombe
2009-04-29 16:13 ` Eric Lacombe
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=4905EE6B.9070000@redhat.com \
--to=avi@redhat.com \
--cc=goretux@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.