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] Xen/XenoLinux interface versions

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen/XenoLinux interface versions
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 12 Mar 2004 07:27:48 +0000
Cc: "Barry Silverman" <barry@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 12 Mar 2004 07:32:21 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 11 Mar 2004 23:40:24 GMT." <E1B1Zmr-0005xr-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>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > I just tried to run Xen (updated daily from unstable) with an incompatible
> > version of XenoLinux (I forgot to rebuild the XenoLinux tree). Dom0 just
> > died with no messages (non-debug build). It worked fine once I realized that
> > the interface version had changed, and had to rebuild xenolinux?
> > 
> > I know it is sort of chicken, and egg thing, but could you somehow print an
> > error message that says that there is a hypervisor interface version
> > mismatch?
> 
> Absolutely. 
> 
> Christian made the very sensible suggestion that we should pass
> the interface version number in to the domain in one of the
> registers. It could then refuse to run or use a compatibility
> mode. (hopefully the interface version would be sufficiently
> close for it to be able to use HYPERVISOR_console_write to tell
> someone!)
> 
> One for the todo list...

Yes. It would be good to get error information from a domain when it
dies. At some point we should probably freeze such domains and notify
DOM0 so that error info (and other useful stuff such as a traceback)
can be picked up. In the nearer term, writing error information to the
'emergency console' would be better than nothing.

 -- Keir


-------------------------------------------------------
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

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