1. Freebsd 9.1 Vmware Tools For Macos

Hi, so I've got a guest installed on my Vista machine (32bit) using Mac OS 10.4.8 as a FreeBSD environment. I've tried installing the VMware tools in the. Manually Installing VMware Tools on a FreeBSD Virtual Machine For FreeBSD virtual machines, you manually install or upgrade VMware Tools by using the command line. Power on the virtual machine. Verify that the guest operating system is running. Because the VMware Tools installer is written in Perl, verify that Perl is installed. This program, starts when the guest operating system boots and runs in the background, is called vmtoolsd.exe in Windows guest operating systems, vmware-tools-daemon in Mac OS X guest operating systems, and vmtoolsd in Linux, FreeBSD and Solaris.

I was just installing a FreeBSD 10 in VMware and found some patches that worked for my ESXI 5.1.0. I put together a simple BASH script that let's you choose between ESXi 5+ or 5.5 and then downloads patches and compiles as needed so you can run the normal install script afterwards. The script supports both old pkg tools and pkgng. Note: As always with VMware tools you need compat6x and perl installed before running the actual VMware installer (after my bash script). I'm installing Tools in a FreeBSD 9.1 x64 running on a vSphere 4.1 system, I've also tried this on a 5.0 with same result and it was the same in a 9.0 aswell. I have no problem to get it to work when I install in the same machine as I downloaded the SVN and source files on but if I move the tools package to a machine without it I get the usual errors for memory and vmblock.

What do I miss here? Am I not able to install in a machine without the source installed?

As a side note I might add that we who have huge active directory domains can't use vCenter 5.1 yet since SSO fails while enumerating accounts. For small ADs it's no problem though, keep at it.

Rhyous, excellent instructions. You saved me on my upgrade from 9.0 to 9.1-release. I figured everything would be fine since it was a minor version upgrade but after last run of freebsd-update install my pc got caught in a core dump reboot loop with a kernel trap 12 page fault pointing to the vm blocking file system.

Using you vmware recompile instructions from SUM fixed everything. One note though - make wouldn't run on 9.1 with MKCLANGISCC=no in make.conf so removed the line and all modules compiled without problem. Thanks again for your excellent instructions. Hello, Great instructions, as usual. Of all the instructions I have ever looked at, yours are the best - always detailed and accurate.

I'm trying to install VMware Tools on FreeBSD 9.1, but I always get a file not found/access denied message when I try to add the compat6x package remotely (pkgadd -r compat6x-amd64). I've looked in the FTP site, but can't find it.

My understanding of using the -r (remote) flag is that I shouldn't have to supply a version number, so I'm not sure what is happening or why. You also don't specify using the xf86-input-vmmouse VMware mouse driver in any of your posts. Don't you need it for things like drag and drop, and copy and paste? I've seen you mention that you have auto-sizing working, but I've never been able to make that work, even using the xf86-video-vmware driver. Do you have any clues?

Freebsd 9.1 Vmware Tools For Macos

And I've only been able to make drag and drop, and copy and paste work on the root account, not a regular user account. Is there any difference between installing as root instead of as 'su,' in terms of permissions propagating to user accounts? Is using 'su' instead of 'root' a possible reason why? Thanks in advance for any help you can offer.

I'm pretty new to FreeBSD, but I've learned a lot from reading your posts. Just letting you know - 9.1 and latest vSphere and Workstation has no issues - I didn't test without compat6x but just running the pl script works without any issues. root@toolbox /tmp/vmware-tools-distrib#./vmware-install.pl Creating a new VMware Tools installer database using the tar4 format. Installing VMware Tools. In which directory do you want to install the binary files? /usr/local/bin In which directory do you want to install the startup script?

/usr/local/etc/rc.d In which directory do you want to install the daemon files? /usr/local/sbin In which directory do you want to install the library files? /usr/local/lib/vmware-tools The path '/usr/local/lib/vmware-tools' does not exist currently. This program is going to create it, including needed parent directories. Is this what you want? yes In which directory do you want to install the documentation files? /usr/local/share/doc/vmware-tools The path '/usr/local/share/doc/vmware-tools' does not exist currently.

This program is going to create it, including needed parent directories. Is this what you want? yes The installation of VMware Tools 9.0.0 build-782409 for FreeBSD completed successfully. You can decide to remove this software from your system at any time by invoking the following command: '/usr/local/bin/vmware-uninstall-tools.pl'.

Before running VMware Tools for the first time, you need to configure it by invoking the following command: '/usr/local/bin/vmware-config-tools.pl'. Do you want this program to invoke the command for you now? yes Initializing. Making sure services for VMware Tools are stopped. Stopping VMware Tools services in the virtual machine: Guest operating system daemon: done The vmblock enables dragging or copying files between host and guest in a Fusion or Workstation virtual environment.

Do you wish to enable this feature? no No X install found. Starting VMware Tools services in the virtual machine: Switching to guest configuration: done Guest memory manager: done Guest operating system daemon: done For the VMware Tools for FreeBSD 9.1 it is recommended that you install the following packages: xf86-video-vmware xf86-input-vmmouse The easiest way to install these packages is by using pkgadd utility. Refer to the man pages on how to properly use this utility. The configuration of VMware Tools 9.0.0 build-782409 for FreeBSD for this running kernel completed successfully. You must restart your X session before any mouse or graphics changes take effect. You can now run VMware Tools by invoking '/usr/local/bin/vmware-toolbox-cmd' from the command line.

Please remember to configure your network by adding: ifconfigvxn0='dhcp' to the /etc/rc.conf file and start the network with: /etc/netstart to use the vmxnet interface using DHCP. Enjoy, -the VMware team. I'm pretty new to freeBSD however i did want to get familiar with the system and i did choose VMWare player since virtualBox has issues with NAT virtualization causing the system to fly during installation time with boot only disk. In any case i tried your tutorial, except for the source which i checked out using traditional CVSup, with the RELENG9 tag which i presume identical to ' /usr/src' path u were using, /and i mange to build everything. The issue is when VMWhere perl screens tries to start all it's services the exact two services ( Guest memory manager and Blocking File System) i built fail to start. I use 9.0 release of the free bsd (i used boot only method as i described so the system init was pretty much from scratch) so my first hunch might be source mismatch between kernel and modules? Or would that caused the build itself to fail?

If not does that mean i need to export my current generic kenrel defs and build a new one with the sources i have, or should i just get another source? Just for the record i tried building twice with make clean before that to be on the safe side running the vmware tools configure after that to no avail. (the Vmware is VMware Player 4.0.4 build-744019). Mikkel, It seems like a lot more work because it is a lot more work.

If you are fine with just removing a feature when it doesn't work, then Dan's guide is for you. However, that method is hiding the problems not solving them. That is a valid option and a quality guide for those who choose that option. I chose a different approach, to make the features work. There are still a few bugs with my way but once finished, I can provide the compiled files then the solution will be to simply copy and replace a few files. I guess I could provide the few buggy files, and the source of course, even though I changed nothing, because one of them is GPL after all and so providing the source is mandatory when providing a binary.

Thx for this great guide! I still have a problem though. I got it working on the 'messy' system. But now I copied the /vmware-tools-distrib/ folder and all it's contents to a usb thumbdrive, reverted back to the clean 'step 4' snapshot, copied the /vmware-tools-distrib/ folder back and ran the install script again. Once again the error: 'KLD vmmemctl.ko: depends on kernel - not available or version mismatch' and 'freebsd kernel: linkerloadfile: Unsupported file type' reappear. Anyone got an idea how to fix this? Finally had some time to spend on this little project again.

Started of from scratch more or less with a clean freebsd 9 release install (nothing fancy with custom kernels etc.) and went through the full guide. I made absolutely sure I downloaded the release source this time. Got it running on the 'dirty' system again and copied the whole vmware-tools-distrib directory to a usb flashdrive. Went back to the step 4 snapshot, copied the vmware-tools-distrib directory back and ran the install script. Same error once again. I really have no idea what I'm doing wrong here. This error is caused by the source being not perfectly aligned with the kernel.

I am pretty sure that I used the source on the CD and not from SVN the first time, and maybe that is why I didn't get this error. I haven't verified that.

But my build system is so far along, I didn't want to revert. I just built a new kernel on my build system, the same place I built the VMWare-tools, and I copied over the new kernel. On build system 1. Build kernel. Tar kernel: tar -czf /usr/kernel.tgz /boot/kernel On clean system 1. Copy kernel.tgz to system. Rename kernel folder: mv /boot/kernel /boot/kernel.old 3.

Extract new kernel: tar -xzf kernel.tgz 4. Copy the kernel into place: cp kernel /boot/kernel VMware-tools installs just fine once the new kernel is in place.