On Tue, Jul 30, 2013 at 5:55 PM, John Baldwin j...@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
That was their official tools, which are came from ISO which mounted with
command install/upgrade client tools.
2013/8/2 Attilio Rao atti...@freebsd.org
On Tue, Jul 30, 2013 at 5:55 PM, John Baldwin j...@freebsd.org wrote:
On Tuesday, July 30, 2013 5:25:06 am Alexander Yerenkow wrote:
On Fri, Aug 2, 2013 at 8:27 PM, Alexander Yerenkow yeren...@gmail.com wrote:
That was their official tools, which are came from ISO which mounted with
command install/upgrade client tools.
There is not much I can do then, unless they update their source-code.
Or do you have any pointer?
2013/8/2 Attilio Rao atti...@freebsd.org
On Fri, Aug 2, 2013 at 8:27 PM, Alexander Yerenkow yeren...@gmail.com
wrote:
That was their official tools, which are came from ISO which mounted with
command install/upgrade client tools.
There is not much I can do then, unless they update
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
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
