Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Feb 2014 15:47:55 -0500
From:      Charles Sprickman <spork@bway.net>
To:        Dennis Glatting <freebsd@pki2.com>
Cc:        owner-freebsd-stable@freebsd.org, Mark Saad <nonesuch@longcount.org>, freebsd-stable@freebsd.org
Subject:   Re: FreeBSD 10 on VMWare in a corporate network; How?
Message-ID:  <21D8F382-134A-4F9F-B5DC-4A4E7A0C7CC6@bway.net>
In-Reply-To: <1392405933.19170.1.camel@btw.pki2.com>
References:  <CAF-3MvPCUDjv4tGeFBf1DkRC6gr2QGsMUT_uH6Q0UU9mo9tv_g@mail.gmail.com> <0ac901cf2437$458837b0$d098a710$@FreeBSD.org> <773DBB2B-D421-44DB-848F-E4B7A9238085@gmail.com> <20140208203859.b6a9c4f555b7e8301541e676@mimar.rs> <1392385745.4914.83410473.135CDC76@webmail.messagingengine.com> <28B68434-113E-4ABA-931E-3DAB666A2BA5@longcount.org> <5dcefb214b0503028606f53da194f4c1@dweimer.net> <1392405933.19170.1.camel@btw.pki2.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 14, 2014, at 2:25 PM, Dennis Glatting wrote:

> On Fri, 2014-02-14 at 09:13 -0600, dweimer wrote:
>> On 02/14/2014 8:43 am, Mark Saad wrote:
>>>> On Feb 14, 2014, at 8:49 AM, Mark Felder <feld@FreeBSD.org> wrote:
>>>>=20
>>>>=20
>>>>=20
>>>>> On Sat, Feb 8, 2014, at 13:38, Marko Cupa=C4=87 wrote:
>>>>> First of all, I wouldn't go with 10-RELEASE, as it is not =
officially
>>>>> supported. Go for 9.2-RELEASE amd64 or expect all kinds of =
problems.
>>>>=20
>>>> "FreeBSD" is "not officially supported" by VMWare. Trust me. We =
threw
>>>> $60,000 at them and they still wouldn't acknowledge bugs. I =
couldn't
>>>> even find an engineer that knew what FreeBSD was!
>>>>=20
>>>=20
>>> So you need to remind the engineers at VMware their parent company =
EMC
>>> uses and sells things based on FreeBSD. Mainly Isilon and spectra
>>> logic as well as other things .
>>>=20
>>>=20
>>>> Plus you have to consider that we don't even know what version of =
ESXi
>>>> he's working with in the first place. According to their OS support
>>>> matrix, FreeBSD 9.2 is only "supported" on ESXi 5.5.
>>>>=20
>>>> =
http://www.vmware.com/resources/compatibility/search.php?deviceCategory=3D=
software&partner=3D109&testConfigurations=3D16&page=3D1&display_interval=3D=
10&sortColumn=3DPartner&sortOrder=3DAsc&testConfig=3D16
>>>> ______________________________________________
>>>=20
>>> If we , all of the VMware users who use FreeBSD on esxi , work out a
>>> good set I notes for using VMware esxi  + FreeBSD and work up a good
>>> page on wiki.freebsd.org; we can make some of the users have a =
better
>>> experience and we can help EMC / VMware with support as a Side =
effect
>>> .
>>>=20
>>> Anyone interested in helping ?
>>>=20
>>> --/
>>> Mark Saad
>>> _______________________________________________
>>> freebsd-stable@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to=20
>>> "freebsd-stable-unsubscribe@freebsd.org"
>>=20
>> I would be interested, I have been running various version of FreeBSD =
on=20
>> various ESX and VMWare for some time.  I have found few little =
gotchas,=20
>> but for the most part it has been running great.  Including FreeBSD =
10,=20
>> on the latest version of VMware Workstation, ESXi 5.5 and ESXi 5.1.  =
I=20
>> don't however use the VMware Tools install from within VMware, and=20
>> instead use the emulators/open-vm-tools port.
>>=20
>=20
> Sorry to jump in the middle of this thread but I too have been running
> FreeBSD 9.x and 10.0 under ESXi 5.1 for some time. It is NOT problem
> free, such as 'dump' can cause the system to lock, but it does work =
well
> enough.

We're running 8.4 under ESXi 5.0 and 5.1 with no huge issues.

I am still unclear on what the best choices are for vmware tools -
the open source tools or the vmware-supplied tools.  Ditto on which
NIC is most proper.  I've also seen conflicting notes on whether to
let the host sync time using vmware tools or ntp.  I'm currently
using ntp.

I can also share an ugly bug and workaround.  We had time stop on a
bunch of hosts.  It was not immediately apparent what was going on,
as the first symptom was the inability to create new inbound
connections.  This was pf not seeing time move forward, and
therefore not aging anything out of the state tables.  Oops.

My notes reference this KB article:

=
http://kb.vmware.com/selfservice/microsites/search.do?language=3Den_US&cmd=
=3DdisplayKC&externalId=3D2021185

Apparently it's fixed.  The workaround worked.  Upating vmware does
scare the crap out of me.  I'm seriously considering moving to Xen
or BHyve the next time an upgrade is necessary.

Charles

>=20
>=20
>=20
>=20
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to =
"freebsd-stable-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21D8F382-134A-4F9F-B5DC-4A4E7A0C7CC6>