From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Brady Subject: RE: Red Hat dropped XEN Date: Tue, 10 Mar 2009 05:41:06 +1300 Message-ID: <1236616866.3566.7.camel@mosquito.devnull.net.nz> References: <7kfxhrfcmv.fsf@pingu.sky.yk.fujitsu.co.jp> <20090306163623.6E2E.27C06F64@necst.nec.co.jp> <7kljrfmsxn.fsf@pingu.sky.yk.fujitsu.co.jp> <0cdb01c9a050$7a7e86b0$6f7b9410$@com> <20090309101309.GG4578@redhat.com> <0d6401c9a0a1$062cade0$128609a0$@com> Reply-To: mike.brady@devnull.net.nz Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0d6401c9a0a1$062cade0$128609a0$@com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Venefax Cc: xen-devel@lists.xensource.com, "'Daniel P. Berrange'" List-Id: xen-devel@lists.xenproject.org You could try upgrading to 3.3.1 from http://www.gitco.de/repo/ On Mon, 2009-03-09 at 06:22 -0400, Venefax wrote: > I was trying to use some of the command set, like "xm new -F" etc., and it > did not work, so I did checked and the xm options are limited, compared to > SLES 10 SP2 or the Beta SLES 11. It is an inferior product. For example, > what I typically do is this: > Create a paravirtualized domU > Xm list --long domname > domname.sxp > Edit domname.sxp and add (cpus 2-15) > Xm new -F domname.sxp > > The question is: how do you achieve that with RHEL 5.3? I don't want my > Dumu's to use all the CPU's, since I restrict Dom0 to CPU's 0-1. Is there a > way, at all? > Federico > > > -----Original Message----- > From: Daniel P. Berrange [mailto:berrange@redhat.com] > Sent: Monday, March 09, 2009 6:13 AM > To: Venefax > Cc: xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] Red Hat dropped XEN > > On Sun, Mar 08, 2009 at 08:46:22PM -0400, Venefax wrote: > > I was really dismayed today when I installed the latest Red Hat 5.3 and > the > > version of Xen included is 3.1. Apparently, the only distribution with Xen > > 3.3 is Suse. Am I reading here that Red Hat will never upgrade Xen to > newer > > versions? I installed the released version, and it still uses Xen 3.1. > > Things are not quite that simple. The RHEL-5 userspace tools are mostly on > a 3.0.3 base, while the hypervisor and kernel are on a 3.1.0 base. The base > versions are typically not upgraded during the lifetime of a major RHEL > release series. That said, we do have a large number of carefully backported > > features & patches from newer versions, eg to add support for NPT/EPT, > improved HVM support, hugepage support, and much more besides. So just > comparing version numbers won't give you a true picture of Xen features > available in RHEL-5. > > Regards, > Daniel