All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Venefax" <venefax@gmail.com>
To: mike.brady@devnull.net.nz
Cc: xen-devel@lists.xensource.com,
	"'Daniel P. Berrange'" <berrange@redhat.com>
Subject: RE: Red Hat dropped XEN
Date: Mon, 9 Mar 2009 12:45:23 -0400	[thread overview]
Message-ID: <0dd601c9a0d6$74041580$5c0c4080$@com> (raw)
In-Reply-To: <1236616866.3566.7.camel@mosquito.devnull.net.nz>

Are there any instructions as how to do that? Or it is just a case of
downloading the RPM's and installing them?
Federico

-----Original Message-----
From: Mike Brady [mailto:mike.brady@devnull.net.nz] 
Sent: Monday, March 09, 2009 12:41 PM
To: Venefax
Cc: 'Daniel P. Berrange'; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] Red Hat dropped XEN

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

  reply	other threads:[~2009-03-09 16:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  5:23 [PATCH 0/2] passthrough: make management of PCI D-states by guest optional Kouya Shimura
2009-03-06  5:26 ` [PATCH 1/2] tool: " Kouya Shimura
2009-03-06  5:26 ` [PATCH 2/2] ioemu: " Kouya Shimura
2009-03-11  8:16   ` Yuji Shimada
2009-03-11  8:57     ` Kouya Shimura
2009-03-12  6:05     ` [PATCH v2 " Kouya Shimura
2009-03-06  7:40 ` [PATCH 0/2] passthrough: " Yuji Shimada
2009-03-06 13:41   ` Cui, Dexuan
2009-03-09  0:38     ` Kouya Shimura
2009-03-09  0:46       ` Red Hat dropped XEN Venefax
2009-03-09  7:41         ` Jayaraman, Bhaskar
2009-03-09  8:07           ` Keir Fraser
2009-03-09  8:06         ` Keir Fraser
2009-03-09 10:13         ` Daniel P. Berrange
2009-03-09 10:22           ` Venefax
2009-03-09 16:41             ` Mike Brady
2009-03-09 16:45               ` Venefax [this message]
2009-03-09  5:29       ` Re: [PATCH 0/2] passthrough: make management of PCI D-states by guest optional Cui, Dexuan
2009-04-23  5:48 ` Yuji Shimada
2009-04-23  7:08   ` Kouya Shimura

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='0dd601c9a0d6$74041580$5c0c4080$@com' \
    --to=venefax@gmail.com \
    --cc=berrange@redhat.com \
    --cc=mike.brady@devnull.net.nz \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.