From: Anthony Liguori <anthony@codemonkey.ws>
To: devzero@web.de
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
ecollins@vmware.com, Javier Guerra <javier@guerrag.com>,
Martin Michlmayr <tbm@cyrius.com>
Subject: Re: Linux with kvm-intel locks up VMplayer guest is started
Date: Wed, 18 Jun 2008 14:52:32 -0500 [thread overview]
Message-ID: <48596780.7080004@codemonkey.ws> (raw)
In-Reply-To: <322174127@web.de>
devzero@web.de wrote:
> i`d like to give a comment about those claims in this thread (see below), vmware kernel part would be closed source or binary module.
>
> i think, they arenŽt. they just are not available via public/opensource code repository.
>
> just go and download workstation 6.5 beta from:
>
> http://download3.vmware.com/software/wkst/VMware-workstation-e.x.p-91182.i386.tar.gz
> (you may need register for that)
>
> unpack and take a look at vmware-distrib/lib/modules/source - there is source for 6 independent kernel
> modules in those .tar files:
>
> vmblock, vmci, vmmon, vmnet, vmppuser and vsock. (~3MB alltogether)
>
vmmon is sort of a stub that loads the actual monitor which is a binary
blob.
Regards,
Anthony Liguori
> 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
>
>
next prev parent reply other threads:[~2008-06-18 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 19:05 Linux with kvm-intel locks up VMplayer guest is started devzero
2008-06-18 19:52 ` Anthony Liguori [this message]
2008-06-19 1:08 ` Eli Collins
-- strict thread matches above, loose matches on Subject: below --
2008-06-16 15:05 Martin Michlmayr
2008-06-16 15:21 ` Anthony Liguori
2008-06-17 12:39 ` Martin Michlmayr
2008-06-17 13:16 ` Anthony Liguori
2008-06-17 13:32 ` Martin Michlmayr
2008-06-17 13:44 ` Martin Michlmayr
2008-06-17 14:02 ` Javier Guerra
2008-06-17 15:29 ` Alan Cox
2008-06-17 18:09 ` Anthony Liguori
2008-06-18 13:56 ` Avi Kivity
2008-06-18 20:59 ` 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=48596780.7080004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=devzero@web.de \
--cc=ecollins@vmware.com \
--cc=javier@guerrag.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tbm@cyrius.com \
/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