From mboxrd@z Thu Jan 1 00:00:00 1970 From: devzero@web.de Subject: Re: Linux with kvm-intel locks up VMplayer guest is started Date: Wed, 18 Jun 2008 21:05:44 +0200 Message-ID: <322174127@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Anthony Liguori , ecollins@vmware.com, Javier Guerra , Martin Michlmayr To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from fmmailgate04.web.de ([217.72.192.242]:56302 "EHLO fmmailgate04.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752421AbYFRTFp convert rfc822-to-8bit (ORCPT ); Wed, 18 Jun 2008 15:05:45 -0400 Sender: kvm-owner@vger.kernel.org List-ID: 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=B4t. they just are not available via public/opensour= ce code repository. just go and download workstation 6.5 beta from: http://download3.vmware.com/software/wkst/VMware-workstation-e.x.p-9118= 2.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) 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= =20 >software arbitration mechanism. It's not, and worse yet, it's closed=20 >source so there's no chance it will be. Even if someone wrote an=20 >arbitration mechanism and got VMware to use it, it still shouldn't be=20 >merged because KVM would be the only thing using that mechanism=20 >upstream. I'm not interested in adding kernel infrastructure to suppo= rt=20 >external binary kernel modules. -----------------------------------------------------------------------= ------------- >VMware is a binary kernel module that's out of kernel. KVM is not=20 >misbehaving and the fact that VMware breaks when the KVM module is=20 >loaded isn't our problem. If they submitted their code for inclusion = in=20 >mainline, we could possibly come up with solution for arbitrating who = is=20 >using VT. -----------------------------------------------------------------------= ------------- _______________________________________________________________________ Jetzt neu! Sch=FCtzen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=3D0222= 20