From: Avi Kivity <avi@redhat.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Jan Kiszka <jan.kiszka@web.de>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] kvm: guest can not startup due to triple fault
Date: Mon, 18 Oct 2010 16:19:50 +0200 [thread overview]
Message-ID: <4CBC5786.9000107@redhat.com> (raw)
In-Reply-To: <AANLkTikKf1XnbWXm6TqSeQe_fUVjeSR0J8DTvcEy3xcP@mail.gmail.com>
On 10/18/2010 04:15 PM, Dave Young wrote:
> On Mon, Oct 18, 2010 at 10:13 PM, Avi Kivity<avi@redhat.com> wrote:
> > On 10/18/2010 04:11 PM, Dave Young wrote:
> >>
> >> On Mon, Oct 18, 2010 at 10:06 PM, Avi Kivity<avi@redhat.com> wrote:
> >> > On 10/18/2010 03:58 PM, Dave Young wrote:
> >> >>
> >> >> >
> >> >> > Please patch hardware_setup() to show the value of
> >> >> > boot_cpu_has(X86_FEATURE_NX).
> >> >>
> >> >> It's 0
> >>
> >> Please wait, I reply too quick, actually it boots two times fine then
> >> one time fail.
> >
> > What boots fine? The guest?
>
> Yes the guest
>
That makes some sort of wierd sense. First kvm samples X86_FEATURE_NX,
sees that it has the feature, reports it to qemu, qemu runs the guest,
NX gets disabled in between, the guest tries to enable NX, kvm kills it.
Second time round, kvm reports that NX is not available, qemu does not
enable it, neither does the guest, and everyone is happy.
Please confirm that when the guest does boot, it boots without NX in
/proc/cpuinfo.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-10-18 14:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 8:54 [BUG] kvm: guest can not startup due to triple fault Dave Young
2010-10-17 8:56 ` Dave Young
2010-10-17 9:34 ` Avi Kivity
2010-10-17 10:14 ` Dave Young
2010-10-17 12:15 ` Avi Kivity
2010-10-18 4:43 ` Dave Young
2010-10-18 7:14 ` Jan Kiszka
2010-10-18 8:55 ` Avi Kivity
2010-10-18 8:58 ` Avi Kivity
2010-10-18 12:26 ` Steven Rostedt
2010-10-18 12:27 ` Avi Kivity
2010-10-18 9:15 ` Avi Kivity
2010-10-18 12:58 ` Dave Young
2010-10-18 13:26 ` Avi Kivity
2010-10-18 13:45 ` Dave Young
2010-10-18 13:46 ` Avi Kivity
2010-10-18 13:50 ` Avi Kivity
2010-10-18 13:58 ` Dave Young
2010-10-18 14:06 ` Avi Kivity
2010-10-18 14:11 ` Dave Young
2010-10-18 14:13 ` Avi Kivity
2010-10-18 14:15 ` Dave Young
2010-10-18 14:17 ` Dave Young
2010-10-18 14:19 ` Avi Kivity [this message]
2010-10-18 14:25 ` Dave Young
2010-10-18 14:28 ` Avi Kivity
2010-10-18 18:47 ` H. Peter Anvin
2010-10-19 1:19 ` Dave Young
2010-10-19 2:59 ` H. Peter Anvin
2010-10-19 6:55 ` Dave Young
2010-10-19 8:57 ` Avi Kivity
2010-10-19 11:52 ` Dave Young
2010-10-19 14:56 ` H. Peter Anvin
2010-10-19 15:04 ` Avi Kivity
2010-10-19 15:31 ` H. Peter Anvin
2010-10-18 13:51 ` Dave Young
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=4CBC5786.9000107@redhat.com \
--to=avi@redhat.com \
--cc=hidave.darkstar@gmail.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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