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

Re: [Xen-devel] Via Cyrix 3 II / CentaurHauls Nehemiah support

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Via Cyrix 3 II / CentaurHauls Nehemiah support
From: Sean Atkinson <sean@xxxxxxxxxxxxxx>
Date: Fri, 12 Mar 2004 09:22:43 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 12 Mar 2004 08:34:07 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1B1RKw-0006vB-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: Netproject
References: <E1B1RKw-0006vB-00@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Hi,

> > > What happens if you try to boot an unmodified standard Xenolinux
> > > image? I would expect that you would see output from DOM0 but it will
> > > then panic about an unrecognised CPU type. If you see no output from
> > > DOM0 at all then that is weird.

Reading other posts on the list I just realised this was never going to
work anyway, since Xen 1.3 silently fails with a 1.2 DOM0 as used on the
demo CD.  However I got similar results using the correct version as
well.

> Make a debug build of Xen (edit arch/i386/Rules.mk and get rid of
> -DNDEBUG). You will then get some output when DOM0 crashes (you may
> want to specify 'noreboot' on Xen's command line).

Only get a couple more lines now:

DOM0: Guest OS virtual load adderss is c0000000
*** Serial input -> DOM0 (type 'CTRL-a' to switch input to Xen).
(file=schedule.c, line=264) DOM0 killed itself!
(file=schedule.c, line=265)  EIP = c0008b69
Domain 0 killed: rebooting machine!
Reboot disabled on cmdline: require manual reset

Perhaps I need to add some debugging to xenolinux too, or is that not
even getting started?

Cheers,

Sean.

-- 
Sean Atkinson <sean@xxxxxxxxxxxxxx>
Netproject



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel