linux-kernel - Re: [Xen-devel] [PATCH] let XEN depend on PAE

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]

Message-ID: <47BF3B10.7070402@goop.org>
Date:	Fri, 22 Feb 2008 13:13:52 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Arnd Hannemann <hannemann@...s.rwth-aachen.de>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	xen-devel@...ts.xensource.com, Chris Wright <chrisw@...s-sol.org>
Subject: Re: [Xen-devel] [PATCH] let XEN depend on PAE

Arnd Hannemann wrote:
> Jeremy Fitzhardinge wrote:
>   
>> Arnd Hannemann wrote:
>>     
>>> This is with 2.6.24.2, but latest-git looks the same:
>>> I also tried with 2.6.23 which crashes instantly, without any output
>>> of the guest.
>>>   
>>>       
>> I'm not too surprised.  Non-PAE Xen is a bit of a rarity, and it only
>> gets tested rarely.  Chris Wright did spend some time on it a while ago,
>> but I don't know that its had any real attention since.  I've been
>> making sure non-PAE compiles, but I've been lax about testing it.
>> This is the first usermode exec, I guess?  The backtrace is a bit odd;
>> I've never seen a problem in move_page_tables before.
>>     
>
> Yes its trying to execute the first script in initramfs, I also tried with initramdisk
> and got a similar error. (move_page_tables also involved)
>
>   
>> Does "xm dmesg" tell you what Xen is complaining about?  You may need to
>> compile with debug=y in Config.mk.
>>     
>
> (XEN) mm.c:645:d44 Non-privileged (44) attempt to map I/O space 00000000
>
> I will recompile with debug=y and post the output.
> If I reduce the dom0 memory with dom0_mem=200000 I see something like
> 00000080 with dom0_mem=800000 I always see 00000000.
>   

That's helpful.  Looks like the mfn is getting mushed to 0.

    J
--
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/