public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Young <hidave.darkstar@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	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: Tue, 19 Oct 2010 19:52:00 +0800	[thread overview]
Message-ID: <20101019115200.GA2524@darkstar> (raw)
In-Reply-To: <4CBD5D8F.6020505@redhat.com>

On Tue, Oct 19, 2010 at 10:57:51AM +0200, Avi Kivity wrote:
>  On 10/19/2010 08:55 AM, Dave Young wrote:
> >>  OK.  Please install msr-tools on your system, and give us the outputs of:
> >>
> >>  rdmsr -p 0 -xc 0x1a0
> >0x1764952489
> >
> >>  rdmsr -p 1 -xc 0x1a0
> >0x1364952489
> >
> 
> That's MSR_IA32_MISC_ENABLE_XD_DISABLE.  Looks like the kernel never
> plays with it.

Hope someone can fix this. IMO we should not depends on bios setting

> 
> Suggest:
> - updating your BIOS
> - playing with the NX feature in your BIOS setup screens

Enable the XD in bios resolved the problem. Thanks you all for the help.

> 
> 
> -- 
> error compiling committee.c: too many arguments to function
> 

  reply	other threads:[~2010-10-19 11:51 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
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 [this message]
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=20101019115200.GA2524@darkstar \
    --to=hidave.darkstar@gmail.com \
    --cc=avi@redhat.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