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/
Home Products Support Community News


[Xen-devel] mini-os under xen 3.0.2

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] mini-os under xen 3.0.2
From: "Robert Kaiser (FH)" <kaiser@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 17 Jul 2006 21:10:51 +0200
Delivery-date: Mon, 17 Jul 2006 12:11:24 -0700
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>
Organization: FH Wiesbaden
Reply-to: kaiser@xxxxxxxxxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.6.2
Hello all,

[My apologies if this question is misplaced here, I initially posted it to 
xen-users but was told there that it might be better suited for xen-devel..]

I am just setting up Xen test/development environment and I have successfully 
installed xen 3.0.2 on a dual celeron system. Linux in  dom0 works fine. Now, 
I would like to play with the mini-os (my ultimate goal  is to implement a 
small RTOS as guest in Xen, so mini-os looks like a good starting point). 
However, I can't seem to get it to run as (I think) it  should: It boots up, 
but as far as I understand the source code and the  README, it should 
continue by printing  the current time in regular  intervals, which it does 
not. Here is the output I receive:

 Xen Minimal OS!
start_info:   c001d000
  nr_pages:   8192  shared_inf: 00be3000
  pt_base:    c0020000  mod_start:  0x0
  mod_len:    0
  flags:      0x0
MM: Init
  _text:        c0000000
  _etext:       c0009577
  _edata:       c000a604
  stack start:  c0011e40
  _end:         c00142a4
  start_pfn:    25
  max_pfn:      2000
Mapping memory range 0xc0400000 - 0xc2000000
MM: Initialise page allocator for c002c000(2c000)-c2000000(2000000)
MM: done
Initialising timer interface
Initialising console ... done.
Initialising scheduler, idle_thread 00000000
Thread "Idle": pointer: 0xc002d00c, stack: 0xc002e000
Thread "init_xs": pointer: 0xc002d034, stack: 0xc0030000
Thread "xenstore": pointer: 0xc002d05c, stack: 0xc0032000
Xenbus initialised.
Thread "init_xs" exited.

I have inserted some debug printk's into do_hypervisor_callback() to see 
whether any callbacks are made at all. According to this, a vtimer interrupt 
does happen, but only every 10 seconds, which -as I guess-  is far less 
frequent than it should be (the timer handler prints out the current time for 
every 1000th timer event, so it would take almost three hours before the 
first message is printed). Also interesting is that whenever I hit a key on 
the console, a timer event is almost always pending along along with the 
console event. It looks like the timer event bit is properly set by Xen, but 
the callback handler is not invoked.

Does anyone have an idea what is wrong?



P.S.: BTW, I have also tried to use the mini-os in from xen-untested. That one 
looks very different, but, alas, it does not even compile...

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] mini-os under xen 3.0.2, Robert Kaiser (FH) <=