Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How To Install VMware Tools On Mac OS X EL Capitan On VMware
62 views
Skip to first unread message
Amal Shelenberger
Dec 27, 2023, 8:08:03 PM12/27/23
to
I installed El Capitan on VMware Pro 12.0 running on x64 Ubuntu GNOME 15.10 using this torrented image. While trying to install VMware tools, I get an error saying Could not find component on update server.
As the error message says, you should have contacted VMWare Support, who would have likely pointed you at this knowledge base article, which details how to install the tools in a MacOS guest, and which also states that MacOS guests are only supported on VMware Fusion.
How to install VMware Tools on Mac OS X EL Capitan on VMware
DOWNLOAD https://7velde0guga.blogspot.com/?yq=2wXsSP
What i did (successfully) was:1. Make sure that you can see your Mac HD as a shared folder in Windows2. Under the FINDER, mount the windows.iso disk image from the Library>Apps Support>VMware>Disk images folder3. It will appear on the Mac desktop as a disk called 'VMWare Tools': don't try to use it yet.4. Then go in to Windows under VMWF, and navigate to the MAc HD in windows Explorer, and you will find a 'Volumes' folder.5. Click the triangle and you'll see the VM Ware Tools 'volume'6. Open that and double click the setup.exe7. For me that then run the VMWare Tools installer, and hey presto, all installed and no more cross on the VMWare tools symbol.The 'update tools' button is now greyed out and i'm running 8.2.3 build 204229Note that the VMWare menu itself still shows a 'Install VMWare Tools' option. No idea why...
Right click SnowLeopard in list of virtual machines > Show in Finder > right click SnowLeopard.vmwarevm > Show Package Contents > add the following line to SnowLeopard.vmx (to mask the CPU since new CPUs are not supported by versions prior to 10.6.7): cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101"
Not sure if this will be helpful or not, but I have been able to change the resolution of my Mac OS X vm's by using the esxi command line 'vim-cmd vmsvc/setsreenres' command. This appears to work for any vm that has vmware-tools installed. I use this command since I often connect to vm's running on esxi via my 11" macbook air and it has a screen resolution of 1366x768. By issuing this command I am able to change the VM's screen resolution. To use the command, log into the host esxi that the vm is running on and issue this command:
If your asking if it will work while running OS X under VMWare Workstation on a Windows 7 Machine? Not using this command, the command is specific to the host running ESXi and I have only run it under ESXi 6. However if you are asking if you can change the screen resolution of a Windows 7 Virtual Machine running under ESXi, then yes as long as VMWare tools are installed and the client has enough memory allocated to it's Video card.
according to my vmware rep, this was included in the fusion 8.1 update . . . .but I don't see the tool in the application bundle anywhere, and the GUI doesn't show any different behavior. HAs anyone figured out how to fix this using only Fusion 8.1?
I actually upgraded to Fusion 8.1 and just doubled check and the utility is indeed part of the latest VMware Tools (10.0.5) and the vmware-resolutionSet utility is located under '/Library/Application Support/VMware Tools'
Mark, I was just hunting for the same solution. Just yesterday, I copied the script from my Fusion 8.1 vmware tools folder to one of my ESXi 6 OSX guests. Running that command every time you reboot is obviously not optimal, although... it might have a performance consequence, I don't know. In my particular application, if there is a slight performance hit, it won't matter.
I tried the 10.0.5 vmware tools on OSX 10.11.3 running under ESXi 5.5 and the keyboard stops working using both vmrc and thick-client console, so that's a no-go for me. The earlier tools (9.9.2) do not have this issue.
Hi William,
First, many thanks for your posts.
Then, it worked simply for me (mac mini esxi server with updated vmware tools and a 10.11 WM) by simply adding more total video memory to 128Mo and setting max resolution to 1920 to 1080. No need to modify the vmx file in this case. Using sudo makes the change persistent.
I wonder if there's a way to disable vmware display completely? I'm passing through videocard in mac os x VM, and don't need internal display at all. With Windows I can disable it in settings, is there a way to do so in Mac os X on VmWare?
I had the problem, that your solution doesnt work on workstation 12.5.5 and windows 10. I've recreated the vmx file as hw gen 10 version. after that everything works as expected with latest vmware tools. hope this helps.
I recalled that reinstalling vmware-tools and rebooting could fix the kernel extension not starting. Doing so not only allwed vmware-resoluton to running properly but also the corner dragging started working (was not working because vmware-tools was not running).
I tried all of these tips plus a few found elsewhere and no luck. I'm running Mac OS X Mojave 10.14.2 inside of ESXI 6.5. In order to get that to work, I had to use -unlocker/releases, which works beautifully for running OS X inside ESXI. However, when I run "sudo ./vmware-resolutionSet 1920 1080", I get the following response:
Requested Resolution: 1920x1080
Effective Resolution: 1176x885
So I went to packages.vmware.com/tools and downloaded the ISO for Windows, thinking that the ISO type was supposed to be for the hosting computer OS, and not for the Virtual Machine. What I got, did not run on Ubuntu and I was told that it was supposed to be run only if the Virtual Machine was Windows.
I have been trying to find the ISO image specifically for Ubunto or Linux. and, so far, I have not found it. Maybe there is a special method to installing the VMware tools for Ubuntu that does not require an ISO image.
Here is what I have done. I went to packages.vmware.com/tools and, without describing the tree structures of all the folders and subfolders, I will sum up. Looking under the latest releases we see one folder for windows and another folder for ubuntu. This lead me to believe I was on the right path. From this point, drilling down the subfolders to find the ISO disk image for a windows virtual machine was easy. For Ubuntu, the experience was different.
The vApps in the HOL-DEV environment are behind a firewall, so in order to directly access the Main Console VM of a vApp in HOL-DEV via RDP, you will need to be on a system that is behind the firewall. The HOL-DEV RDP JumpServer ( hol-dev-jump.hol.vmware.com ) can be used as a jump box to get you behind the firewall and provide you direct access to the HOL-DEV vApp network.
The micro Linux VM is a simple appliance based on MicroCore Linux. It is mostly non-persistent and does not support guest customization, updating the VMware Tools or installing software via the common mechanisms such as YUM, YaST, or APT. Any customization to this appliance, beyond the changes outlined here, should be carefully considered. It will likely be much simpler to use one of the the linux-base templates, which are based on CentOS and use common Linux tools and processes.
The base package consists of 3 base CentOS 6.6, 64-bit machines with SELinux disabled and VMware tools installed. The initial IP addresses are indicated here, and the application will function right out of the box. The IPs may be changed as long as the appropriate files are updated on each machine to reflect the new addresses of the components. To demonstrate load sharing, the "web tier" may be scaled out and placed behind a load balancer, and a simple alteration to the script will display which node in the pool has serviced the request.
Most of our new appliances run the lighttpd (pronounced "lighty") web server for the VAMI and store its SSL certificate and private key in the file: /opt/vmware/etc/lighttpd/server.pem
The solution to the first problem is to add a temporary drive, unpack the installer to that space, and perform the installation, replacing the currently installed tools. Following a successful install, the temporary drive is removed and deleted. You want to use this option if you can.
Begin the process of installing tools by selecting the appropriate option from vCenter or vCD. If prompted, use the "Interactive" installation method. If you don't have space, the automatic option will fail anyway.
About VMware
VMware is a global leader in cloud infrastructure and business mobility. Built on VMware's industry-leading virtualization technology, our solutions deliver a brave new model of IT that is fluid, instant and more secure. Customers can innovate faster by rapidly developing, automatically delivering and more safely consuming any application. With 2014 revenues of $6 billion, VMware has more than 500,000 customers and 75,000 partners. The company is headquartered in Silicon Valley with offices throughout the world and can be found online at www.vmware.com.
0aad45d008
As the error message says, you should have contacted VMWare Support, who would have likely pointed you at this knowledge base article, which details how to install the tools in a MacOS guest, and which also states that MacOS guests are only supported on VMware Fusion.
How to install VMware Tools on Mac OS X EL Capitan on VMware
DOWNLOAD https://7velde0guga.blogspot.com/?yq=2wXsSP
What i did (successfully) was:1. Make sure that you can see your Mac HD as a shared folder in Windows2. Under the FINDER, mount the windows.iso disk image from the Library>Apps Support>VMware>Disk images folder3. It will appear on the Mac desktop as a disk called 'VMWare Tools': don't try to use it yet.4. Then go in to Windows under VMWF, and navigate to the MAc HD in windows Explorer, and you will find a 'Volumes' folder.5. Click the triangle and you'll see the VM Ware Tools 'volume'6. Open that and double click the setup.exe7. For me that then run the VMWare Tools installer, and hey presto, all installed and no more cross on the VMWare tools symbol.The 'update tools' button is now greyed out and i'm running 8.2.3 build 204229Note that the VMWare menu itself still shows a 'Install VMWare Tools' option. No idea why...
Right click SnowLeopard in list of virtual machines > Show in Finder > right click SnowLeopard.vmwarevm > Show Package Contents > add the following line to SnowLeopard.vmx (to mask the CPU since new CPUs are not supported by versions prior to 10.6.7): cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101"
Not sure if this will be helpful or not, but I have been able to change the resolution of my Mac OS X vm's by using the esxi command line 'vim-cmd vmsvc/setsreenres' command. This appears to work for any vm that has vmware-tools installed. I use this command since I often connect to vm's running on esxi via my 11" macbook air and it has a screen resolution of 1366x768. By issuing this command I am able to change the VM's screen resolution. To use the command, log into the host esxi that the vm is running on and issue this command:
If your asking if it will work while running OS X under VMWare Workstation on a Windows 7 Machine? Not using this command, the command is specific to the host running ESXi and I have only run it under ESXi 6. However if you are asking if you can change the screen resolution of a Windows 7 Virtual Machine running under ESXi, then yes as long as VMWare tools are installed and the client has enough memory allocated to it's Video card.
according to my vmware rep, this was included in the fusion 8.1 update . . . .but I don't see the tool in the application bundle anywhere, and the GUI doesn't show any different behavior. HAs anyone figured out how to fix this using only Fusion 8.1?
I actually upgraded to Fusion 8.1 and just doubled check and the utility is indeed part of the latest VMware Tools (10.0.5) and the vmware-resolutionSet utility is located under '/Library/Application Support/VMware Tools'
Mark, I was just hunting for the same solution. Just yesterday, I copied the script from my Fusion 8.1 vmware tools folder to one of my ESXi 6 OSX guests. Running that command every time you reboot is obviously not optimal, although... it might have a performance consequence, I don't know. In my particular application, if there is a slight performance hit, it won't matter.
I tried the 10.0.5 vmware tools on OSX 10.11.3 running under ESXi 5.5 and the keyboard stops working using both vmrc and thick-client console, so that's a no-go for me. The earlier tools (9.9.2) do not have this issue.
Hi William,
First, many thanks for your posts.
Then, it worked simply for me (mac mini esxi server with updated vmware tools and a 10.11 WM) by simply adding more total video memory to 128Mo and setting max resolution to 1920 to 1080. No need to modify the vmx file in this case. Using sudo makes the change persistent.
I wonder if there's a way to disable vmware display completely? I'm passing through videocard in mac os x VM, and don't need internal display at all. With Windows I can disable it in settings, is there a way to do so in Mac os X on VmWare?
I had the problem, that your solution doesnt work on workstation 12.5.5 and windows 10. I've recreated the vmx file as hw gen 10 version. after that everything works as expected with latest vmware tools. hope this helps.
I recalled that reinstalling vmware-tools and rebooting could fix the kernel extension not starting. Doing so not only allwed vmware-resoluton to running properly but also the corner dragging started working (was not working because vmware-tools was not running).
I tried all of these tips plus a few found elsewhere and no luck. I'm running Mac OS X Mojave 10.14.2 inside of ESXI 6.5. In order to get that to work, I had to use -unlocker/releases, which works beautifully for running OS X inside ESXI. However, when I run "sudo ./vmware-resolutionSet 1920 1080", I get the following response:
Requested Resolution: 1920x1080
Effective Resolution: 1176x885
So I went to packages.vmware.com/tools and downloaded the ISO for Windows, thinking that the ISO type was supposed to be for the hosting computer OS, and not for the Virtual Machine. What I got, did not run on Ubuntu and I was told that it was supposed to be run only if the Virtual Machine was Windows.
I have been trying to find the ISO image specifically for Ubunto or Linux. and, so far, I have not found it. Maybe there is a special method to installing the VMware tools for Ubuntu that does not require an ISO image.
Here is what I have done. I went to packages.vmware.com/tools and, without describing the tree structures of all the folders and subfolders, I will sum up. Looking under the latest releases we see one folder for windows and another folder for ubuntu. This lead me to believe I was on the right path. From this point, drilling down the subfolders to find the ISO disk image for a windows virtual machine was easy. For Ubuntu, the experience was different.
The vApps in the HOL-DEV environment are behind a firewall, so in order to directly access the Main Console VM of a vApp in HOL-DEV via RDP, you will need to be on a system that is behind the firewall. The HOL-DEV RDP JumpServer ( hol-dev-jump.hol.vmware.com ) can be used as a jump box to get you behind the firewall and provide you direct access to the HOL-DEV vApp network.
The micro Linux VM is a simple appliance based on MicroCore Linux. It is mostly non-persistent and does not support guest customization, updating the VMware Tools or installing software via the common mechanisms such as YUM, YaST, or APT. Any customization to this appliance, beyond the changes outlined here, should be carefully considered. It will likely be much simpler to use one of the the linux-base templates, which are based on CentOS and use common Linux tools and processes.
The base package consists of 3 base CentOS 6.6, 64-bit machines with SELinux disabled and VMware tools installed. The initial IP addresses are indicated here, and the application will function right out of the box. The IPs may be changed as long as the appropriate files are updated on each machine to reflect the new addresses of the components. To demonstrate load sharing, the "web tier" may be scaled out and placed behind a load balancer, and a simple alteration to the script will display which node in the pool has serviced the request.
Most of our new appliances run the lighttpd (pronounced "lighty") web server for the VAMI and store its SSL certificate and private key in the file: /opt/vmware/etc/lighttpd/server.pem
The solution to the first problem is to add a temporary drive, unpack the installer to that space, and perform the installation, replacing the currently installed tools. Following a successful install, the temporary drive is removed and deleted. You want to use this option if you can.
Begin the process of installing tools by selecting the appropriate option from vCenter or vCD. If prompted, use the "Interactive" installation method. If you don't have space, the automatic option will fail anyway.
About VMware
VMware is a global leader in cloud infrastructure and business mobility. Built on VMware's industry-leading virtualization technology, our solutions deliver a brave new model of IT that is fluid, instant and more secure. Customers can innovate faster by rapidly developing, automatically delivering and more safely consuming any application. With 2014 revenues of $6 billion, VMware has more than 500,000 customers and 75,000 partners. The company is headquartered in Silicon Valley with offices throughout the world and can be found online at www.vmware.com.
0aad45d008
0 new messages