WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Mini-OS in dom0 - virtual memory problems

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Mini-OS in dom0 - virtual memory problems
From: Julian Stecklina <der_julian@xxxxxx>
Date: Thu, 25 Jan 2007 14:49:54 +0100
Delivery-date: Thu, 25 Jan 2007 05:50:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20061206)
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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>