Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-users

[Xen-users] guest kernel portability

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] guest kernel portability
From: Tim Freeman <tfreeman@xxxxxxxxxxx>
Date: Sun, 26 Feb 2006 12:19:49 -0600
Delivery-date: Sun, 26 Feb 2006 18:20:32 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
What guarantees are made about the interface between guest kernels and the
hypervisor/domain0 from Xen version to version?  (domain loading, hypercalls,
front/back device drivers, etc.)   

Does a certain minor/sub-version equality guarantee compatibility?  Are there
instead any known version compatibilities/incompatibilities?

Sorry if this has been addressed recently, and pointers would be much
appreciated.

For some background, we may want to allow authorized guests to bring their
specialized kernels with them and I'm trying to ascertain what kind of structure
we can put around the process (this is for the Globus Workspace Service, where
such a (signed) kernel image could be an authorized thing to bring with a guest
image).

Thanks,
Tim 



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

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