lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 18 Oct 2010 16:19:50 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Dave Young <hidave.darkstar@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Jan Kiszka <jan.kiszka@....de>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG] kvm: guest can not startup due to triple fault

  On 10/18/2010 04:15 PM, Dave Young wrote:
> On Mon, Oct 18, 2010 at 10:13 PM, Avi Kivity<avi@...hat.com>  wrote:
> >    On 10/18/2010 04:11 PM, Dave Young wrote:
> >>
> >>  On Mon, Oct 18, 2010 at 10:06 PM, Avi Kivity<avi@...hat.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ