Anthony Liguori wrote:
On Tue, 2007-09-04 at 11:51 +0200, Sander van Leeuwen wrote:
Avi Kivity wrote:
I think it's a bit risky to use somebody else's vmxon pointer.
You have a point with the msr updates though.
I think the easiest way forward is for you to unload
Avi Kivity wrote:
> Sander van Leeuwen wrote:
>> You may want to reconsider as KVM breaks VMWare server 1.3 on 64 bits
>> linux hosts as well. In exactly the same way
>> as it breaks VirtualBox.
>>
>> We have tried this ourselves and others have reported the
edhat.com/archives/rhl-list/2007-June/msg02501.html
--
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: S
Avi Kivity wrote:
Sander van Leeuwen wrote:
You are mistaken. VT-x allows multiple clients to work concurrently.
There's only one catch: all those
clients should follow certain guidelines.
Currently, kvm assumes that it is the only user that issues vmptrld
instructions. There m
PIs 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 Le
tension.
Avi Kivity wrote:
> Sander van Leeuwen wrote:
>> 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
g 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
/ 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