From: Sander van Leeuwen <sandervl-2taLTamkYL2ELgA04lAiVw@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM & VMX root mode
Date: Sat, 01 Sep 2007 17:09:54 +0200 [thread overview]
Message-ID: <46D980C2.3040501@innotek.de> (raw)
In-Reply-To: <46D97669.7050609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Hi Avi,
Our non-vmx mode fails, because the cpu is in vmx root mode.
Two products that use vt-x for virtualization could perfectly co-exist
if both comply with the way Intel recommends people to use vt-x.
See figure 19.1 in chapter 19.4 of the 'Intel 64 and IA-32 Architectures
Software Developer's Manual'. VirtualBox is programmed to
follow these rules and therefor allows any other virtualizer to run
side-by-side.
Currently KVM prevents us from using our generic virtualization engine
and does not allow anybody else to use the vt-x extensions (without
explicitely leaving vmx root mode).
As your product is included in the mainline Linux kernel and enabled by
default, it would be nice if you could follow Intel's recommendations.
Thank you.
Avi Kivity wrote:
> Sander van Leeuwen wrote:
>> Hi,
>>
>> We have had several reports of users saying our product VirtualBox
>> crashes their (Linux) host. It turned out that KVM is responsible,
>> because
>> it leaves the CPU in VMX root mode.
>>
>> Doing this changes the way the cpu operates: updates to reserved bits
>> in control registers cause general protection faults.
>> We hit such cases on two occasions; clearing the X86_CR4_VMXE bit in
>> CR4 and turning off paging.
>>
>> I have added a workaround to detect VMX root mode, simply refuse to
>> run and recommend that the user disables KVM.
>> I would however appreciate if you could fix KVM instead.
>>
>>
>
> Simply '/sbin/rmmod kvm-intel' and kvm will exit vmx root mode.
>
> If VirtualBox uses vmx, then it can't be run side-by-side with kvm.
--
Kind regards / mit freundlichen Gruessen / Met vriendelijke groet
Sander van Leeuwen
innoTek GmbH
sandervl-2taLTamkYL2ELgA04lAiVw@public.gmane.org
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/
next prev parent reply other threads:[~2007-09-01 15:09 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 [this message]
[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
[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=46D980C2.3040501@innotek.de \
--to=sandervl-2taltamkyl2elga04laivw@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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