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] New OpenSolaris release for Xen..

To: Nate Carlson <natecars@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] New OpenSolaris release for Xen..
From: Joe Bonasera <joe.bonasera@xxxxxxx>
Date: Sun, 23 Jul 2006 08:30:27 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 23 Jul 2006 08:32:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.63.0607182350390.14099@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44BBE4F6.8010907@xxxxxxx> <Pine.LNX.4.63.0607182350390.14099@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.4 (X11/20060602)


Nate Carlson wrote:
On Mon, 17 Jul 2006, Joe Bonasera wrote:
On Friday we published an updated release of OpenSolaris for Xen. It is still pre-alpha quality but we wanted to get it out in the community as soon as it was relatively working.

This update adds OpenSolaris-based dom0 capabilities, as well as 32-bit and 64-bit MP guests. We're currently synced up with OpenSolaris build 41, and Xen 3.0.2-2.

Is there documentation anywhere on how to bootstrap a Solaris domU to run on a Linux dom0? Now that it looks like it's getting somewhat stable (at least supports block devices and such!), that would make it much easier for those of us with existing Linux dom0's to try it out.

This is actually how we did our initial development, but it's rather complicated
to set up as Linux and Solaris don't understand each other's file systems.
We wound up with multiple systems talking over NFS as their common language.

The problem is creating the Solaris domU image. For now you need our tools
and a base Solaris on h/w or dom0 to do that. Our plan is to continue to
extend existing Solaris tools for installation, so you'll always need a Solaris 
installation
to start from, unless someone wants to build some sort of 3rd party Solaris
repackager. That is just not anywhere near the top on our list of To Do things.

We are looking into the possiblity of making a pre-canned domU root file
system based image available for download. For example for a Xen demo-CD.
That has drawbacks as you'll be stuck with a fixed size initial root file
system and other installation choices, but we realize it makes life much
easier for other Xen developers to do some quick testing. It's not hard for
us to do technically, but we have to get some legal stuff cleared with the
lawyers around licensing issues for distribution, redistribution.


Also note to run interesting Solaris domains (MP or 64 bit) you need to use our 
patched version
of Xen. Note that a Linux dom0 should run just fine on that Xen. We'll be 
working
on getting the required changes pushed back into mainline Xen in the near 
future.
Given 3.0.3 is pretty close to done, I expect we'll target 3.0.4.




Joe

Thanks much for all the hard work!

------------------------------------------------------------------------
| nate carlson | natecars@xxxxxxxxxxxxxxx | http://www.natecarlson.com |
|       depriving some poor village of its idiot since 1981            |
------------------------------------------------------------------------


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

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