public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sander van Leeuwen <sandervl-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
To: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: KVM & VMX root mode
Date: Mon, 03 Sep 2007 09:29:05 +0200	[thread overview]
Message-ID: <46DBB7C1.60708@innotek.de> (raw)
In-Reply-To: <20070903031403.GA16190-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Daniel P. Berrange wrote:
> While one could in theory change KVM to only activate VMX when a guest is
> started this wouldn't give a significant improvement to the user experiance.
> Instead of being able to rely on KVM working, it now may or may not work 
> depending on whether you happen to have a VirtualBox guest running or not &
> vica-verca. You still would not be able to run guests from both concurrently
> which should surely be the real goal. The only way I see the latter being
> achieved is if VirtualBox were to leverage the existing KVM kernel APIs to
> access the underlying hardware virt capabilities.
>   
You are mistaken. VT-x allows multiple clients to work concurrently. 
There's only one catch: all those
clients should follow certain guidelines.


-- 
Kind regards / mit freundlichen Gruessen / Met vriendelijke groet
  Sander van Leeuwen

innoTek GmbH
http://www.innotek.de
Germany 



-------------------------------------------------------------------------
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-09-03  7:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 13:02 KVM & VMX root mode Sander van Leeuwen
     [not found] ` <46D81156.8050100-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
2007-09-01 14:25   ` Avi Kivity
     [not found]     ` <46D97669.7050609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-01 14:33       ` Alexey Eremenko
     [not found]         ` <7fac565a0709010733j2c3f58aav743949a3021a5c30-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-01 14:35           ` Avi Kivity
     [not found]             ` <46D9789B.9040001-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-01 14:44               ` Alexey Eremenko
2007-09-01 15:09       ` Sander van Leeuwen
     [not found]         ` <46D980C2.3040501-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
2007-09-01 15:59           ` Avi Kivity
     [not found]             ` <46D98C53.4070604-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-01 17:24               ` Sander van Leeuwen
     [not found]                 ` <46D9A030.1020904-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
2007-09-01 17:46                   ` Alexey Eremenko
2007-09-01 18:42                   ` Avi Kivity
     [not found]                     ` <46D9B297.5070502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-03  3:14                       ` Daniel P. Berrange
     [not found]                         ` <20070903031403.GA16190-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-09-03  7:29                           ` Sander van Leeuwen [this message]
     [not found]                             ` <46DBB7C1.60708-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
2007-09-03  7:44                               ` Avi Kivity
     [not found]                                 ` <46DBBB65.3020406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-03  8:09                                   ` Sander van Leeuwen
     [not found]                                     ` <46DBC120.3050301-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
2007-09-03 11:34                                       ` Avi Kivity
     [not found]                                         ` <46DBF13B.9080005-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-04  9:51                                           ` Sander van Leeuwen
     [not found]                                             ` <46DD2AA2.8010109-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
2007-09-04 13:55                                               ` Avi Kivity
     [not found]                                                 ` <46DD63B6.6050406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-04 14:16                                                   ` Sander van Leeuwen
     [not found]                                                     ` <46DD68A3.1060403-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
2007-09-04 14:29                                                       ` Avi Kivity
2007-09-04 14:02                                               ` Anthony Liguori
2007-09-04 14:23                                                 ` Sander van Leeuwen
     [not found]                                                   ` <46DD6A59.9000104-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
2007-09-04 14:51                                                     ` Anthony Liguori

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=46DBB7C1.60708@innotek.de \
    --to=sandervl-2taltamkyl2elga04laivw@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=berrange-H+wXaHxf7aLQT0dZR+AlfA@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