From owner-freebsd-current@FreeBSD.ORG Wed Jul 31 19:10:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 31B0EFA0; Wed, 31 Jul 2013 19:10:35 +0000 (UTC) (envelope-from bryanv@daemoninthecloset.org) Received: from torment.daemoninthecloset.org (torment.daemoninthecloset.org [94.242.209.234]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E3DC4233A; Wed, 31 Jul 2013 19:10:34 +0000 (UTC) Received: from sage.daemoninthecloset.org (unknown [70.114.209.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "sage.daemoninthecloset.org", Issuer "daemoninthecloset.org" (verified OK)) by torment.localdomain (Postfix) with ESMTPS id DF81F42C082F; Wed, 31 Jul 2013 07:37:55 +0200 (CEST) X-Virus-Scanned: amavisd-new at daemoninthecloset.org X-Virus-Scanned: amavisd-new at daemoninthecloset.org Date: Wed, 31 Jul 2013 00:33:51 -0500 (CDT) From: Bryan Venteicher To: John Baldwin Message-ID: <1611226768.89.1375248831421.JavaMail.root@daemoninthecloset.org> In-Reply-To: <201307301155.51473.jhb@freebsd.org> References: <201307301155.51473.jhb@freebsd.org> Subject: Re: Problem with curret in vmware MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.10.20] X-Mailer: Zimbra 8.0.2_GA_5569 (ZimbraWebClient - GC20 ([unknown])/8.0.2_GA_5569) Thread-Topic: Problem with curret in vmware Thread-Index: oYBt6Wpsre1d6aQfKt1uub6a96iikA== Cc: Attilio Rao , freebsd-current@freebsd.org, Alexander Yerenkow X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 19:10:35 -0000 > On Tuesday, July 30, 2013 5:25:06 am Alexander Yerenkow wrote: > > Hello all. > > I have panics in vmware with installed vmwaretools (they are guessed > > culprit). > > Seems that memory balooning (or using more memory in all vms than there is > > in host) > > produces some kind of weird behavior in FreeBSD. > > This vm aren't shutted down now, is there somethin I can do to help > > investigate this? > > > > Panic screens: > > http://gits.kiev.ua/FreeBSD/panic1.png > > http://gits.kiev.ua/FreeBSD/panic2.png > > Looks like their code needs to be updated to work with locking changes in > HEAD. Attilio is probably the best person to ask. > This highlights why we should move away from the poorly supported, out of tree, unfriendly licensed VMware tools. I have a port of the vmxnet3 from OpenBSD [1] that I intend to commit in time for 10. Next, I hope to look at the OpenBSD vmt [2] VMware tools driver. The balloon is a bit trickier. AFAIK, OpenBSD doesn't have a driver for easy porting. The VMware tools driver for FreeBSD is GPL licensed, and VMware has shown no interest/ability to relicense their tools. Likely, the best way forward is to port their CDDL licensed Solaris driver. [1] - http://svnweb.freebsd.org/base/projects/vmxnet/sys/dev/vmware/vmxnet3/ [2] - http://www.openbsd.org/cgi-bin/man.cgi?query=vmt&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html > -- > John Baldwin > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >