From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julian Stecklina Subject: Mini-OS in dom0 - virtual memory problems Date: Thu, 25 Jan 2007 14:49:54 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hello, I am trying to port Mini-OS (from xen-3.0.4-testing) to the domain 0 environment. Setting the right flags in x86_32.S and changing the start of the text section to 0xC0100000 enabled it to boot. I expected that most of the Mini-OS's functionality to be working except everything that relied on the Xenbus. To my surprise there was an error setting up the virtual memory. Here is the console log: Bootstrapping... Xen Minimal OS! start_info: c0135000 nr_pages: 26700 shared_inf: 00bed000 pt_base: c0136000 mod_start: 0x0 mod_len: 0 flags: 0x3 cmd_line: stack: c0117040-c0119040 MM: Init _text: c0100000 _etext: c010a3b4 _edata: c010b760 stack start: c0117040 _end: c0119494 start_pfn: 3b max_pfn: 684c Mapping memory range 0xc0500000 - 0xc694c000 (XEN) mm.c:1664:d0 Bad type (saw e8000001 != exp 20000000) for mfn 1c3b (pfn 3b) (XEN) mm.c:1960:d0 Error while pinning mfn 1c3b ERROR: pinning failed Do_exit called! The first message from the hypervisor seems very strange. I would be very thankful, if anyone can point to the source of the problem. Regards, Julian