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] Deletion of 2.4 Linux sparse tree


On 6 Oct 2005, at 00:56, James Harper wrote:

This is a vague wishlist item for me, but what would it take to backport
the xen patches to the linux kernel to 2.0 or 2.2?

I ask because I have a client with an ancient SCO application that has
some historic data in it and it might just work under linux with iBCS,
which has long since disappeared.

Failing that, how will a kernel in a VMX domain see hardware? Would the
kernel need specific device drivers?

Would a Linux dom0 and a SCO domU cause a matter-antimatter-like
explosion? :)

Backporting to 2.0/2.2 would not be a simple task. You'd have to run them unmodified in a vmx domain, once that code has stabilised some more.

 -- Keir


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