public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Emmanuel Nicolas Millan
	<emmanueln-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kvm: disabled by bios
Date: Thu, 18 Oct 2007 12:39:57 +0200	[thread overview]
Message-ID: <20071018103956.GA29700@8bytes.org> (raw)
In-Reply-To: <89b20fb50710131730h6fd3791dv2c19081cf0ecf6f9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Sat, Oct 13, 2007 at 09:30:54PM -0300, Emmanuel Nicolas Millan wrote:
> >Hi,
> >
> >is there any option to reenable virtualisation support (AMD-CPU) if it
> >is disabled by bios (and Bios does not show an option to enable
> >virtualisation support)?
> 
> >Elmar
> 
> Hi, i'm having the same problem, my bios doesn't have an option to
> enable virtualization support, and I already upgrade the bios to the
> last version available.
> 
> I saw the patch "[patches] [PATCH] [19/50] Experimental: detect if SVM
> is disabled by BIOS" could this patch resolve the problem? is there
> any way to enable SVM support with KVM?

If SVM is disabled by BIOS there is nothing you can do with current
hardware to reenable it. If the BIOS does not provide an option to
reenable it please contact your BIOS vendor for a newer BIOS which
support reenablement of SVM.

Joerg

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-18 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14  0:30 kvm: disabled by bios Emmanuel Nicolas Millan
     [not found] ` <89b20fb50710131730h6fd3791dv2c19081cf0ecf6f9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-14  7:44   ` Avi Kivity
2007-10-18 10:39   ` Joerg Roedel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-10 10:25 Elmar Haneke
     [not found] ` <470CA897.70106-i3glvDR67ZKzQB+pC5nmwQ@public.gmane.org>
2007-10-10 10:27   ` Avi Kivity

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=20071018103956.GA29700@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=emmanueln-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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