Date: Fri, 2 Aug 2013 20:04:17 +0200 From: Attilio Rao <attilio@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, Alexander Yerenkow <yerenkow@gmail.com> Subject: Re: Fwd: Problem with curret in vmware Message-ID: <CAJ-FndBNQDKMWn78Pn2GMOncM5WP1xEzH5HcijNUC2Ktjt-4AQ@mail.gmail.com> In-Reply-To: <201307301155.51473.jhb@freebsd.org> References: <CAPJF9wkLe%2BR2tJ6ej1guzCARQ1OF0RWFzX_qUQam6%2BXOZjyF9A@mail.gmail.com> <CAPJF9wkVjA4McyFhm7Ys-Kd9kYxOREbkYGnDDgMiR0ASCVJeQA@mail.gmail.com> <201307301155.51473.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 30, 2013 at 5:55 PM, John Baldwin <jhb@freebsd.org> wrote: > 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. Exactly which is the ports you installed? Attilio -- Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-FndBNQDKMWn78Pn2GMOncM5WP1xEzH5HcijNUC2Ktjt-4AQ>