kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: jmahoney@waav.com (John Mahoney)
To: kernelnewbies@lists.kernelnewbies.org
Subject: KVM - virtualization support
Date: Tue, 21 Dec 2010 13:02:15 -0500	[thread overview]
Message-ID: <AANLkTinVy+gMJRZ7LELiNznTCqpnRcoFu4izQV8z626p@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimz0aiHUBMNdjEAG7AiQ-LWfgXJP0MMcmq_ZqW0@mail.gmail.com>

On Tue, Dec 21, 2010 at 1:49 AM, Sengottuvelan S
<sengottuvelan.s@gmail.com> wrote:
> Hi All,
>
> I am trying to see whether my kernel has KVM support or not. When i execute
> #egrep -c '(vmx|svm)' /proc/cpuinfo? , output shows '0'' which means my
> custom kernel does not have capability of KVM.
>

I think you are misunderstanding the flags in /proc/cpuinfo.  I
believe they represent which features the processor supports, not what
features the kernel supports.  Like Rajat said you may need to enable
the feature in your BIOS, but otherwise you may want to check the
datasheet for the processor.

feel free to paste the output of:

cat /proc/cpuinfo

If you do not have this feature you will have to use something such as
VirtualBox, of course there will be a performance penalty.

--
John

      parent reply	other threads:[~2010-12-21 18:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21  6:49 KVM - virtualization support Sengottuvelan S
2010-12-21  9:22 ` Rajat Sharma
2010-12-21 14:46   ` Mohammed Gamal
2010-12-21  9:56 ` Mohammed Gamal
2010-12-21  9:59 ` hiren panchasara
2010-12-21 10:38 ` Prasad Joshi
2010-12-21 16:57   ` Rajat Sharma
2010-12-21 13:57 ` matthias
2010-12-22  1:43   ` Sengottuvelan S
2010-12-22  4:09     ` Ponmuthu Subramaniam Nandan
2010-12-22  7:47     ` Robert P. J. Day
2010-12-24  5:19       ` Tapas Mishra
2010-12-24 23:15         ` Sengottuvelan S
2010-12-21 18:02 ` John Mahoney [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=AANLkTinVy+gMJRZ7LELiNznTCqpnRcoFu4izQV8z626p@mail.gmail.com \
    --to=jmahoney@waav.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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;
as well as URLs for NNTP newsgroup(s).