Re: [Xen-devel] mini-os under xen 3.0.2
I've been away from the list for little to long I think. Still I hope
I can be of help.
The README file is a bit out of date. Mini-OS periodically writes the
current time, but the period is extremely long (as you correctly
calculated it's about 3 hours). Still the domain should be up and
If the domain is responding to the console events (it should print:
"No console input handler" every time you press Enter) everything is
The reason why the timer event happens every 10 second is that idle
Mini-OS domain is configured to block for periods of 10 seconds.
However, if the domain receives console events if will be woken up
more frequently (and thus the period between time printouts will be
The reason why you see pending timer events when using the console is
- Only running domains will respond to timer events. Since Mini-OS is
blocked most of the time you will not handle the usual 10ms frequency
- As soon as the domain wakes up the timer event is delivered.
- Domain wakes up every time you press a key on the console. If the
frequency of your key presses is less then 100 times a second you
should see a pending event each time.
If you remove "block_domain(10000);" call from sched.c, the domain
will never go to sleep. It will then handle all of the 10ms timer
events. You should then see the printouts of the current time roughly
every 10 seconds.
On 17 Jul 2006, at 20:10, Robert Kaiser (FH) wrote:
[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-
I am just setting up Xen test/development environment and I have
installed xen 3.0.2 on a dual celeron system. Linux in dom0 works
I would like to play with the mini-os (my ultimate goal is to
small RTOS as guest in Xen, so mini-os looks like a good starting
However, I can't seem to get it to run as (I think) it should: It
but as far as I understand the source code and the README, it should
continue by printing the current time in regular intervals, which
not. Here is the output I receive:
Xen Minimal OS!
nr_pages: 8192 shared_inf: 00be3000
pt_base: c0020000 mod_start: 0x0
stack start: c0011e40
Mapping memory range 0xc0400000 - 0xc2000000
MM: Initialise page allocator for c002c000(2c000)-c2000000(2000000)
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
Thread "init_xs" exited.
I have inserted some debug printk's into do_hypervisor_callback()
whether any callbacks are made at all. According to this, a vtimer
does happen, but only every 10 seconds, which -as I guess- is far
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
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
console event. It looks like the timer event bit is properly set by
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
Xen-devel mailing list
|<Prev in Thread]
||[Next in Thread>|
- Re: [Xen-devel] mini-os under xen 3.0.2,
Grzegorz Milos <=