From owner-freebsd-current@FreeBSD.ORG  Tue Jul 30 09:25:07 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 D91EC74A
 for <freebsd-current@freebsd.org>; Tue, 30 Jul 2013 09:25:07 +0000 (UTC)
 (envelope-from yerenkow@gmail.com)
Received: from mail-vb0-x22d.google.com (mail-vb0-x22d.google.com
 [IPv6:2607:f8b0:400c:c02::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9A036204F
 for <freebsd-current@freebsd.org>; Tue, 30 Jul 2013 09:25:07 +0000 (UTC)
Received: by mail-vb0-f45.google.com with SMTP id p14so3577403vbm.18
 for <freebsd-current@freebsd.org>; Tue, 30 Jul 2013 02:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=KyYHcST7aXOXlJT1xw1HbywUXTr8TzDF3dkOnFR9TqU=;
 b=EFgMD8ET2gQUD3DRK4B9IDLO4qMY+/JNQUlEuW8vbbD80Sqtn+N8L4b976LbMvnC7f
 0GSQUMl+1zEYEYHuVnXf6vnwnLHuhXE2PgDXiZRTce2jtgZCo2MljJbtxWJ86e6D1NRl
 sWcurdQ9Kn/UukUvoyvqAWwKuHzrFiCdLR7XXF5CzvcqEU1SXvp69PQUuWhHtDFbOomC
 MVqZoqpMx9NWqSL8HgDcGwA0psLSMyuEkW0V04xMlzNnzGfpP2wm4miSRs2msMEjGPTY
 iWd4LpbZXfBgXcOYyDy7Jv276s1KQcRknjYDJmAz58BStGsOsL6g+drJRSj0n3qgAjzu
 MFtw==
MIME-Version: 1.0
X-Received: by 10.52.248.134 with SMTP id ym6mr15302336vdc.78.1375176306834;
 Tue, 30 Jul 2013 02:25:06 -0700 (PDT)
Received: by 10.52.23.7 with HTTP; Tue, 30 Jul 2013 02:25:06 -0700 (PDT)
In-Reply-To: <CAPJF9wkLe+R2tJ6ej1guzCARQ1OF0RWFzX_qUQam6+XOZjyF9A@mail.gmail.com>
References: <CAPJF9wkLe+R2tJ6ej1guzCARQ1OF0RWFzX_qUQam6+XOZjyF9A@mail.gmail.com>
Date: Tue, 30 Jul 2013 12:25:06 +0300
Message-ID: <CAPJF9wkVjA4McyFhm7Ys-Kd9kYxOREbkYGnDDgMiR0ASCVJeQA@mail.gmail.com>
Subject: Fwd: Problem with curret in vmware
From: Alexander Yerenkow <yerenkow@gmail.com>
To: freebsd-current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 09:25:07 -0000

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

-- 
Regards,
Alexander Yerenkow