public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Cam Macdonell <cam@cs.ualberta.ca>
To: Majid Salame <msalame@nortel.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: Running KVM on rhel4
Date: Wed, 28 Jan 2009 09:49:31 -0700	[thread overview]
Message-ID: <49808C9B.90004@cs.ualberta.ca> (raw)
In-Reply-To: <29D15BBCA340DA4D8146D38B4924FC7A16A37855@zcarhxm0.corp.nortel.com>


The release notes for KVM-55 indicate that it can run on 2.6.9 (ver 56 
jumps to 2.6.17), so if I use KVM-55 modules and userspace it will run, 
correct?

Thanks,
Cam

Majid Salame wrote:
>  
> You need a more recent kernel then 2.6.9 in order to detect the VT
> feature on the processor which is needed by kvm.
> 
> MS
> 
> Cheers,
> Majid
> 
> -----Original Message-----
> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On
> Behalf Of Cam Macdonell
> Sent: Tuesday, January 27, 2009 1:14 PM
> To: kvm-devel
> Subject: Running KVM on rhel4
> 
> 
> Hi,
> 
> I've been asked to setup KVM on a rhel4 cluster.  Are there any issues
> as to which KVM versions are usable with rhel4 (kernel 2.6.9)?
> Obviously, in this case we would be compiling our own module and
> userspace.
> 
> Thanks,
> Cam
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in the
> body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-01-28 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 18:13 Running KVM on rhel4 Cam Macdonell
2009-01-27 18:52 ` Majid Salame
2009-01-28 16:49   ` Cam Macdonell [this message]

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=49808C9B.90004@cs.ualberta.ca \
    --to=cam@cs.ualberta.ca \
    --cc=kvm@vger.kernel.org \
    --cc=msalame@nortel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox