On Fri, Mar 05, 2010 at 12:51:02PM +0200, Pasi Kärkkäinen wrote:
> On Fri, Mar 05, 2010 at 09:13:59AM +0200, Pasi Kärkkäinen wrote:
> > On Thu, Mar 04, 2010 at 01:33:39PM -0800, Jeremy Fitzhardinge wrote:
> > > On 03/04/2010 12:28 PM, Pasi Kärkkäinen wrote:
> > >> It was 18.104.22.168-174.2.22.fc12.i686.PAE saying the above..
> > >> 22.214.171.124 xen/stable booted on baremetal doesn't say anything about NX.
> > >>
> > >
> > > What happens if you boot with noexec=no on the kernel command line?
> > >
> > noexec=no didn't change anything.. still crashes. console output is the
> > same as earlier.
> > I also checked the BIOS, it didn't seem to have any NX settings.
> latest xen/master 126.96.36.199 seems to boot OK on this box, with the same Xen
> 4.0.0-rc5 hypervisor.
> successful bootlog of xen/master 188.8.131.52 here:
xen/stable 184.108.40.206 boots OK on baremetal (without Xen).
Does it help to have a log of the boot on baremetal?
Here are a couple of xen/stable 220.127.116.11 crashing boots as Xen dom0,
with various debugging options, and also with "acpi=off":
two logs in the same file:
Xen-devel mailing list