> regards
> roland
>
>
> ------------------------------------------------------------------------------------
>
>
>> i think what he's saying is that VMWare is a closed binary blob
>> executing in the kernel; so there's no way to certify anything with
>> this.
>>
>
>
>> as soon as you put some unknown (and unknowable, unverifiable,
>> untrustable) code in the kernel, you can't know what will work and
>> what won't.
>>
>
> ------------------------------------------------------------------------------------
>
>
>> So ask vmware. They have source to both parts we don't."
>>
>
> ------------------------------------------------------------------------------------
>
>
>> If the VMware code was upstream, then we could work together to make a
>> software arbitration mechanism. It's not, and worse yet, it's closed
>> source so there's no chance it will be. Even if someone wrote an
>> arbitration mechanism and got VMware to use it, it still shouldn't be
>> merged because KVM would be the only thing using that mechanism
>> upstream. I'm not interested in adding kernel infrastructure to support
>> external binary kernel modules.
>>
>
> ------------------------------------------------------------------------------------
>
>
>> VMware is a binary kernel module that's out of kernel. KVM is not
>> misbehaving and the fact that VMware breaks when the KVM module is
>> loaded isn't our problem. If they submitted their code for inclusion in
>> mainline, we could possibly come up with solution for arbitrating who is
>> using VT.
>>
>
> ------------------------------------------------------------------------------------
>
>
> _______________________________________________________________________
> Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage
> kostenlos testen.
http://www.pc-sicherheit.web.de/startseite/?mc=022220
>
>
