VMware 2.2 RC and VMware Tools - can only ping

hblandford

Have a new 2.2 RC machine. Using the native vmx driver and vmxnet3 under ESXi5.5.

Everything works fine. Install VMware Tools according to the docs https://doc.pfsense.org/index.php/VMware_Tools

Reboot, redo the interfaces and IP addresses as before. All I can do is ping. In or out. Nothing else seems to work. Can't SSH or connect to web interface. Cannot telnet from pfSense to anything else on the network. Disabled firewall etc, no difference.

Only thing different is I am now using vmx3f0 etc instead of vmx0 etc.

Thoughts/suggestions?

johnpoz

So ran into this as well.. I had them working on the 32 bit version a few back.. Will have to try and see if can duplicate with 32bit.

izzarazzu

Hi, I've the same problem :'(

VMware ESXi 5.5 Update 2
With the last patch ESXi550-201412001 | Build 2302651 | Release Date 12/02/2014

On FreeBSD 10.1 the aren't problem with vmxnet3 and VMware Tools.

On this pfSense version, when I install VMware Tools (and vmxnet3 vmware drivers) the only thing that works is ping.

I think it's a big problem :-X

johnpoz

I think my problem was something else.. But have not bothered installing the native tools since open is working and the vmxnet3 are supported out of the box now. If I get a chance will play tmrw with native drivers.

marcelloc

Try open-vm-tools-nox11 from freebsd ports.

Jamerson

before the update i had vmware running fine,
after the update can't get network card up,
logged in and had to reconfigure the NICS,
names are changed from em0 to VMX1–-
managed the have the pfsense up and running.
vmware tools can't run with the next steps "
mkdir -p /mnt/cdrom
mount_cd9660 /dev/acd0 /mnt/cdrom
cd /tmp
tar xvzf /mnt/cdrom/vmware-freebsd-tools.tar.gz
cd vmware-tools-distrib
./vmware-install.pl -d --clobber-kernel-modules=vmxnet3,pvscsi,vmmemctl

johnpoz

I didn't have any problems getting the native tools running, other than having to use pkg install to get compat and perl5.20 installed. The instructions on pfsense doc work after that, and I also created ln for perl.. Tools come up fine.. now see nics vmx3f0 and vmx3f1 etc..

But can not get web gui up, can not ssh to pfsense.. I can ping pfsense is about it..

Something is off – but again there is really no reason for the vmtools - there is driver for vmx3 in freebsd out of the box now. And the openvm tools install to give you the ability to shutdown the vm gracefully, etc..

As to your mount -- you sure your cdrom is acd0, maybe its just cd0?

example

[2.2-RELEASE][root@pfSense.localdomain]/root: mount -t cd9660 /dev/cd0 /mnt/
[2.2-RELEASE][root@pfSense.localdomain]/root: cd /mnt
[2.2-RELEASE][root@pfSense.localdomain]/mnt: ls
manifest.txt vmware-freebsd-tools.tar.gz
[2.2-RELEASE][root@pfSense.localdomain]/mnt: cd /tmp
[2.2-RELEASE][root@pfSense.localdomain]/tmp: tar xvzf /mnt/vmware-freebsd-tools.tar.gz
x vmware-tools-distrib/
x vmware-tools-distrib/doc/
x vmware-tools-distrib/doc/open_source_licenses.txt
x vmware-tools-distrib/doc/INSTALL
x vmware-tools-distrib/doc/README

Jamerson

@johnpoz:

I didn't have any problems getting the native tools running, other than having to use pkg install to get compat and perl5.20 installed. The instructions on pfsense doc work after that, and I also created ln for perl.. Tools come up fine.. now see nics vmx3f0 and vmx3f1 etc..

But can not get web gui up, can not ssh to pfsense.. I can ping pfsense is about it..

Something is off – but again there is really no reason for the vmtools - there is driver for vmx3 in freebsd out of the box now. And the openvm tools install to give you the ability to shutdown the vm gracefully, etc..

As to your mount -- you sure your cdrom is acd0, maybe its just cd0?

example

[2.2-RELEASE][root@pfSense.localdomain]/root: mount -t cd9660 /dev/cd0 /mnt/
[2.2-RELEASE][root@pfSense.localdomain]/root: cd /mnt
[2.2-RELEASE][root@pfSense.localdomain]/mnt: ls
manifest.txt vmware-freebsd-tools.tar.gz
[2.2-RELEASE][root@pfSense.localdomain]/mnt: cd /tmp
[2.2-RELEASE][root@pfSense.localdomain]/tmp: tar xvzf /mnt/vmware-freebsd-tools.tar.gz
x vmware-tools-distrib/
x vmware-tools-distrib/doc/
x vmware-tools-distrib/doc/open_source_licenses.txt
x vmware-tools-distrib/doc/INSTALL
x vmware-tools-distrib/doc/README

can you share how did you install PEARL,
can't get it installed
the below steps arent working for me !

Shared object "libutil.so.8" not found, required by "perl"

setenv \
PACKAGESITE \

http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.3-release/Latest/

pkg_add -rv wget

pkg_add -r compat6x-amd64 perl

keep getting the below :

[2.2-RELEASE][root@firewall.root.nl]/: pkg
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.3-release/Latest/, please wait...
pkg: Error fetching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.3-release/Latest//Latest/pkg.txz: File unavailable (e.g., file not found, no access)
A pre-built version of pkg could not be found for your system.
Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'.

marcelloc

Pfsense 2.2 uses freebsd 10.1

You are trying to install 8.3 links and packages

Also, use pkg install instead of old pkg_add

Jamerson

@marcelloc:

Pfsense 2.2 uses freebsd 10.1

You are trying to install 8.3 lins and packages

Also, use pkg install instead of old pkg_add

thanks
i beleive this the link of the 10.1 ?
ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.1/

johnpoz

Guess I should edit that doc..

Clearly those are for the old pfsense.. I already went over how to install ;) pkg install

pkg install perl5.20

if you running 64 bit then compat would be

pkg install compat6x-amd64

And AGAIN - there really is no reason to install them, vmx3 is support out of the box on freebsd 10 that pfsense is using. When you setup the vm you can set interfaces to vmx3 and out of the box working.. If you want to be able to send a guest shutdown then install the openvm package..

Jamerson

@johnpoz:

Guess I should edit that doc..

Clearly those are for the old pfsense.. I already went over how to install ;) pkg install

pkg install perl5.20

if you running 64 bit then compat would be

pkg install compat6x-amd64

And AGAIN - there really is no reason to install them, vmx3 is support out of the box on freebsd 10 that pfsense is using. When you setup the vm you can set interfaces to vmx3 and out of the box working.. If you want to be able to send a guest shutdown then install the openvm package..

True vmx3 are working out of the speed,
the speed of the NIC is autoset, can't set it on 10Gbps,

is it possible to change this somehow for 10Gbps on the NICS?

marcelloc

@johnpoz:

And AGAIN - there really is no reason to install them, vmx3 is support out of the box on freebsd 10 that pfsense is using

Nic ok but what about memory and process management improvements with vmtools ???

Jamerson

@marcelloc:

@johnpoz:

And AGAIN - there really is no reason to install them, vmx3 is support out of the box on freebsd 10 that pfsense is using

Nic ok but what about memory and process management improvements with vmtools ???

I've read somewhere Johnpoz is going to update the RC2.2 Doc for vmware tools

KOM

Nic ok but what about memory and process management improvements with vmtools

And heartbeat. Don't forget about the heartbeat.

johnpoz

Memory and process.. Isn't what this does

[2.2-RELEASE][root@pfSense.local.lan]/root:dmesg
<snipped>VMware memory control driver initialized
[2.2-RELEASE][root@pfSense.local.lan]/root:

That is loaded from open tools.. What else are you looking for - heartbeat?

[2.2-RELEASE][root@pfSense.local.lan]/root: kldstat
Id Refs Address Size Name
1 10 0xffffffff80200000 22c57e8 kernel
2 1 0xffffffff82611000 22f7 vmmemctl.ko
3 1 0xffffffff82614000 237b vmxnet.ko
4 1 0xffffffff82617000 2d72 vmblock.ko
5 1 0xffffffff8261a000 890f vmhgfs.ko</snipped>

Jamerson

i've got this error at the last step :


[2.2-RELEASE][root@pfSense.localdomain]/tmp/vmware-tools-distrib: ./vmware-install.pl -d --clobber-kernel-modules=vmxnet3,pvscsi,vmmemctl
ELF binary type "0" not known.
ELF binary type "0" not known.
ELF binary type "0" not known.
VMware Tools 9.4.11 build-2400950 for Linux will not install on the operating
system you are running. Please be sure you install the version of VMware Tools
that is appropriate for your operating system.

Execution aborted.

johnpoz

"VMware Tools 9.4.11 build-2400950 for Linux will not install on the operating"

Why would you try and install linux tools on freebsd (pfsense)?

Jamerson

@johnpoz:

"VMware Tools 9.4.11 build-2400950 for Linux will not install on the operating"

Why would you try and install linux tools on freebsd (pfsense)?

i have followed this tutorial

http://www.v-front.de/2015/01/pfsense-22-was-released-how-to-install.html

i am on ESXI 5.5 Build 2403361
the Vmware tools i am trying to install is the one mounted

when i am on the cd/mnt i see only

VMwareTools-9.4.11-2400950.tar.gz
vmware-tools-upgrader-32*
vmware-tools-upgrader-64*
run_upgrader.sh*
manifest.txt*

the only file i can extract is VMwareTools-9.4.11-2400950

thank you

KOM

When I mount the VMWare Tools CD under pfSense 2.2, I see

manifest.txt
vmware-freebsd-tools.tar.gz

If you're seeing VMWare Tools for Linux then I'm guessing you picked the wrong OS type when you created the virtual machine. Did you select a Linux flavour or Other (FreeBSD 64-bit)?

Jamerson

@KOM:

When I mount the VMWare Tools CD under pfSense 2.2, I see

manifest.txt
vmware-freebsd-tools.tar.gz

If you're seeing VMWare Tools for Linux then I'm guessing you picked the wrong OS type when you created the virtual machine. Did you select a Linux flavour or Other (FreeBSD 64-bit)?

yes i chosed Other 2.6.0(64-Bit)
when i chose Other Linux 64 bit, it support just E1000 adapter

KOM

Well, you picked the wrong selection and I wouldn't be surprised if other funny behaviours started happening too. Recreate your VM with the correct OS template (Other: FreeBSD 64-bit) and start again.

Jamerson

@KOM:

Well, you picked the wrong selection and I wouldn't be surprised if other funny behaviours started happening too. Recreate your VM with the correct OS template (Other: FreeBSD 64-bit) and start again.

My ESXI doesn't says Other : FreeBSD but it said Others : Linux

KOM

Time to upgrade to something a little more current then. What are you using, ESXi 3.x or 4.x? ESXI is free, so there is little excuse to not upgrade.

Jamerson

@KOM:

Time to upgrade to something a little more current then. What are you using, ESXi 3.x or 4.x? ESXI is free, so there is little excuse to not upgrade.

its not the Free version
i am on the latest one i am on ESXI 5.5 Build 2403361
i see the version of the FreeBSD thanks
i understand its used repro 10.1
which link can i use to tell Pfsense to look at to install pkg ?

KOM

which link can i use to tell Pfsense to look at to install pkg ?

I'm sorry, I don't know what you mean here. Are you asking how to install VMware Tools for FreeBSD?

Jamerson

@KOM:

which link can i use to tell Pfsense to look at to install pkg ?

I'm sorry, I don't know what you mean here. Are you asking how to install VMware Tools for FreeBSD?

i am sorry i mean
Pfsense 2.1 uses
PACKAGESITE \ http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.1-release/Latest/
Pfsense 2.2 users Packagesite 10.1 which i dont have the link

never mind the pfsense 2.2 looks directly to the Packagesite 10.1

going to try it again and get back to you
if it does work i may create a tutorial for this and share with you guys

thank you

johnpoz

tutorial for what? Install a vm?? Who would it be geared too.. Its fairly obvious that pfsense is based upon freebsd, why would you not pick freebsd as the OS type when creating a vm? If someone needs a guide for that - they really shouldn't be even attempting to run anything in VM.

Jamerson

@johnpoz:

tutorial for what? Install a vm?? Who would it be geared too.. Its fairly obvious that pfsense is based upon freebsd, why would you not pick freebsd as the OS type when creating a vm? If someone needs a guide for that - they really shouldn't be even attempting to run anything in VM.

i meant for VMware tools :)
i managed to install them but can't access the pfsense using the webgui or ssh
i can ping the pfsense

the error i see on the console of the pfsense is
vmx3f0: capabilities : sg jf vlan csum

i've disabled the firewall rules from the console but still no luck !
pfctl -d

tried a fresh install, come across the same !

what i am doing wrong !

johnpoz

There have been loads of threads about vmtools on 2.2.. Just use the open tools - the native tools seem broken and only allow ping.

Jamerson

@johnpoz:

There have been loads of threads about vmtools on 2.2.. Just use the open tools - the native tools seem broken and only allow ping.

oh ok thank you sir !
if i have pfsense on a hardware , the update will works just fine ?
no issues with the NICS ?

johnpoz

What?? Why would you install vmtools if your running pfsense on hardware??

Jamerson

@johnpoz:

What?? Why would you install vmtools if your running pfsense on hardware??

i didnt say install vmtools on hardware,
i asked if the NICS on the hardware need to be reconfigured , or something like this.

johnpoz

Are you in the wrong thread then???

This thread is about vmware tools
"VMware 2.2 RC and VMware Tools - can only ping (Read 877 times) "

VMware 2.2 RC and VMware Tools - can only ping

Products

Services

Support

News

Resources

Company

Our Mission

Subscribe to our Newsletter