Usr lib vmware isoimages windows iso

I have some guest vms with a yellow exclamation point on the vmware tools icon indicating they can be updated. When I try and update vmware tools manually, I get the error: «The required VMware Tools ISO image does not exist or is inaccessible. See the error stack for details on the cause of this problem.» Below in the Error Stack window, I see the messages, «Call «VirtualMachine.MountToolsInstaller» or object <servername> on ESXi «192.168.3.39» failed. Unable to install VMware Tools. An error occurred while trying to access image file «/usr/lib/vmware/isoimages/windows.iso» needed to install VMware Tools: 0 (Input/output error). If your product shipped with the VMware Tools package, reinstall VMware ESX, then try again to install the VMware Tools package in the virtual machine.»

I found posts that indicated I should check symlinks to the vmtools directory and I think those are present. I also tried to manually browse to the image folder but it appears there is a problem of some sort with the file system. See images below:

ESXi is installed on a USB stick. Is the iso images directory corrupted? Can anyone help me on how I can fix this? Should I just replace the USB stick or is there another way?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I got this error when trying to install vmware tools ona 2008r2 vm.

Unable to install VMware Tools. An error occurred while trying to access image file «/usr/lib/vmware/isoimages/windows.iso» needed to install VMware Tools: 0 (No such file or directory). If your product shipped with the VMware Tools package, reinstall VMware ESX, then try again to install the VMware Tools package in the virtual machine.

The required VMware Tools ISO image does not exist or is inaccessible.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I renamed the folder from 5.0.0.old to 5.0.0 and it works now. I dont know why it was renamed to 5.0.0.old

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Did you already check whether you can access this directory from the command line? Does it contain all the .iso images for the different guest operating systems?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

yea the directory does not exist. any idea?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I found the isos here

/vmfs/volumes/250ba8ca-b5400aa2-6bf3-e851c7368c00/packages/5.0.0.old/vmtools # ls -l

-rwx—— 1 root root 12576768 May 11 14:40 darwin.iso

-rwx—— 1 root root 256 May 11 14:42 darwin.iso.sig

-rwx—— 1 root root 16044032 May 11 14:38 freebsd.iso

-rwx—— 1 root root 256 May 11 14:38 freebsd.iso.sig

-rwx—— 1 root root 66992128 May 11 14:38 linux.iso

-rwx—— 1 root root 256 May 11 14:38 linux.iso.sig

-rwx—— 1 root root 1738 May 11 14:38 linux_avr_manifest.txt

-rwx—— 1 root root 540672 May 11 14:42 netware.iso

-rwx—— 1 root root 256 May 11 14:42 netware.iso.sig

-rwx—— 1 root root 13017088 May 11 14:38 solaris.iso

-rwx—— 1 root root 256 May 11 14:38 solaris.iso.sig

-rwx—— 1 root root 451 May 11 14:38 tools-key.pub

-rwx—— 1 root root 13664256 May 11 14:42 winPre2k.iso

-rwx—— 1 root root 256 May 11 14:38 winPre2k.iso.sig

-rwx—— 1 root root 49 May 11 14:40 winPre2k_avr_manifest.txt

-rwx—— 1 root root 74252288 May 11 14:40 windows.iso

-rwx—— 1 root root 256 May 11 14:42 windows.iso.sig

-rwx—— 1 root root 1069 May 11 14:38 windows_avr_manifest.txt

why are they under /locker/packages/5.0.0.old/vmtools?

Источник

You know those issues that just sit in the background for a while until you can’t take it anymore and have to work them out. You have to fix them. You just have to make them stop. (Maybe not, heh). This problem was one of those ones.

For a number of our VMware guests, when being a good guy and installing VMware Tools, this error would come up.

Seems like a bit of an overreaction to try to get you to reinstall ESXi.

Now I use the very cool repo/unmanaged solution for the majority of our guests, since they run RHEL 6. If you don’t know about this check it out here. If you use RHEL kickstart, it is trivial to make new guests come out with tools installed and the tools repo enabled. Anyway, enough gushing, just check it out if you use RHEL on VMware.

I should note before getting into this, that I am running ESXi from a USB key. This problem seems to be related to the backend media that ESXi is installed on, so if you’re on different media then your mileage may vary. I’d be interested to hear from anyone who sees this error on a non usb platform.

Following the path given in the error on a good system (/usr/lib/vmware/isoimages/) leads you to a symlink called /productLocker/vmtools/ , which in turn is a symlink to /locker/packages/4.1.0/ . No idea why this has to be so complicated, but there’s probably a reason.

After some more digging (tracking back through the innumerable symlinks), it seemed like the partition below was missing.

On a bad system

This is from a good system, notice the last partition

The mount point for this partition seems to be

Which was missing too. /vmfs/volumes/Hypervisor3 is a symlink back to the volume id of the partition. In the end, I just couldn’t figure out a pattern. Some hosts were fine and had the /productLocker symlink, and a bunch didn’t have it. Consequently, I have no idea how this happened to us, or how to prevent it, but let’s just get on and fix it. The solution seems clear, let’s just make a new partition, format it, and dump the files from a working system on there.

Partitioning the disk as FAT16 was easy (fdisk ftw), but formatting the disk was proving difficult. ESXi doesn’t seem to contain a working version of mkfs.vfat on it, and vmkfstools won’t do FAT16. (Also tried a mkfs.vfat binary from RHEL 5; didn’t work either). Of course, I could’ve pulled the usb key out, and fixed it up on a linux box, but I found an easier way.

To summarize, you create a scratch disk directory for the host inside some of your shared storage, and then point the host to it. After rebooting the host all the symlinks point to the new scratch location on your datastore. For complete steps on how to do it read this. VMware also recommends this as a best practice since your ESXi scratch disk area is now not on a limited ram disk.

Ok. Great. Now ESXi has a place to put VMware Tools. But how do you get the Tools files on there? I found the easiest way to do this was to apply a VMware Tools fix from VUM (VMware Update Manager). If you don’t use VUM I’m sure you could manually download the fix and apply it on your host using esxupdate. The latest VMware Tools fix is here. And that’s it – problem solved!

Источник

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I’m having a problem with installing CentOS 5 on ESXI 6.5 and I was hoping someone could point me in the right direction.

The CentOS 5 OS actually installed, however after installation the network card was not installed. During the installation it asks me to modify the Network Configuration. Then it asks me to add a device (Devernet Configuration) so I added an eth0 interface with a static IP. However, when i start the vm it has no network interfaces. When I try to bring the interface up I get a «Device eth0 does not exist» error message.

I looks like it’s missing the driver for the network card.

So I tried to install VMWare tools to see if I can get the network interface from it

ESXI > CentOS5 VM > Actions > Guest OS > Install VMWare tools

First I got the following error:

• Unable to install VMware Tools. An error occurred while trying to access image file «/usr/lib/vmware/isoimages/linuxPreGlibc25.iso» needed to install VMware Tools: 2 (No such file or directory). Please refer the product documentation or KB article 2129825 for details about how to get VMware Tools package for this guest operating system

The documentation basically said that this was an issue on VMware tools 10.1.0.

I tried making a copy of linux.iso and renamed it to /usr/lib/vmware/isoimages/linuxPreGlibc25.iso. This allowed me to install VMWare tools, however when I looked at the guest OS the drive was not mounted or even present under /dev/cdrom

I tried mounting the linux.iso file in ESXI straight to the VM under CentOS VM > Hardware Configuration > CD/DVD drive 1

However this did not show up in the guest VM

I read online about OSPs, however how can I get installed if I can’t get the package into the VM (mounting does not work and there is no network connectivity)

Any help or suggestions on this issue would be greatly appreciated

Источник

Задача:

Установка Open-vm-tools на виртуальную машину FreeBSD

Итак, немного теории. VMWare Tools — это набор утилит, повышающих производительность виртуальных гостевых машин и улучшающих управление виртуальными машинами. Без утилит операционная система виртуальной машины с меньшей производительность. Это из основного, почему стоит использовать VMWare Tools.

Существует два известных мне варианта установки:

• С диска
• Из портов
• при помощи утилиты pkg

Рассмотрим все варианты.

Установка с диска

Все попытки установки с диска, закончились ошибкой. Тем не менее покажу, что необходимо сделать и какой ошибкой всё закончилось. Монтируем ISO диск в виртуальную машину.

Failed&nbsp – The required VMware Tools ISO image does not exist or is inaccessible.
Unable to install VMware Tools. An error occurred while trying to access image file “/usr/lib/vmware/isoimages/freebsd.iso” needed to install VMware Tools: 2 (No such file or directory). Please refer the product documentation or KB article 2129825 for details about how to get VMware Tools package for this guest operating system.

Поиск ошибки привёл меня к отсутствующему freebsd.iso. Где его брать и почему его нет, не выяснял

В интернете много информации, что vmware tool работает с ошибками и многие используют

Open-vm-tools (OVT) — это реализация VMware Tools с открытым исходным кодом, первая версия которой была выпущена в 2007 году, состоит из набора утилит, которые улучшают функциональность, администрирование и управление. Обновления программы предоставляются вместе с обновлениями и исправлениями операционной системы.

Установка из портов

Установка из портов была также с ошибкой, поэтому переходим к третьему варианту и если и в третьем варианте будет ошибка, тогда будем по порядку разбираться со всеми ошибками

Установка при помощи утилиты pkg

На вопрос “Proceed with this action? [y/N]:”, отвечаем “Y” и наживаем Enter

перезагружаем виртуальную машину или запускаем двумя командами

Ну и на всякий случай, если вдруг у вас есть проблемы с VMware Tools и вы хотите перейти на Open-vm-tools (OVT). Вот вам команда для удаления

Источник

After upgrading my 2.5.3 to 3.0.2 via tarball and upgrading virtual hw from VM2 to VM3, I’m going to upgrade vmware tools in my VMs.

I started from a linux one and I got a general system error.

In VM logfile I have this:

Aug 30 11:00:35.199: vmx| TOOLS INSTALL entering BEGINNING state.

Aug 30 11:00:35.201: vmx| TOOLS INSTALL ‘/usr/lib/vmware/isoimages/linux.iso’ not present or

Aug 30 11:00:35.201: vmx| Msg_Post: Warning

Aug 30 11:00:35.201: vmx| [msg.tools.inaccessible] An error occurred while trying to access i

mage file «/usr/lib/vmware/isoimages/linux.iso» needed to install VMware Tools: No such file

Aug 30 11:00:35.201: vmx| Please reinstall VMware ESX Server, then try again to install the V

Mware Tools package in your virtual machine.

Aug 30 11:00:35.201: vmx| —-

Aug 30 11:00:35.231: vmx| TOOLS INSTALL Initialization failed.

Aug 30 11:00:35.231: vmx| TOOLS INSTALL entering IDLE state.

/usr/lib/vmware/isoimages/linux.iso should be part of the

package but I have not it on my disc.

rpm -qV VMware-esx-tools-3.0.2-52542

only the solaris.iso was copied.

In upgrade log I have nothing about it

and the rpm files of both tarball and cd are the same and correct.

Where can I found the reason why the iso files were not installed?

I have plenty of space in my /vmimages filesystem. and preinstall scriptlet gives me no information about isofiles not being copied.

The situation is the same on both the servers upgraded.

Can I safely do a

rpm -Uvh of the rpm?

Do I have to pass the —noscripts option?

Doing an rpm -qVa on the esx server gives also for package

a missing of many many files. what about this?

Is it correct to use these RH tools to do these kind of checks against virtual console OS?

Thanks in advance

Message was edited by:

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I had the same issue with a machine with a bad CDROM drive. I did a tarball upgrade and the .iso files were missing. I just did an scp from a good ESX server to the one that failed. EVerything is fine now.

RPM is ok, you may need to get them from the CD or extract them yourself from the tarball.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

This is one of those reasons I always recommend reinstallations over upgrades. Consider this. When you move from RedHat 2.1 to RHEL3, RedHat even recommends a reinstall however the upgrade path does work as well. If you upgrade there is a chance that the filesystems are not big enough to hold things, that there are left over configuration files, etc. Granted this ends up being a religious debate. But it boils down to. If you are not comfortable with the upgrade mechanism you performed, then I would reinstall ESX overwriting everything but the VMFS filesystems.

You can also just reinstall the Pegasus and VMware-esx-tools RPMs as well to solve this problem.

To improve your comfort levels you can also run ‘rpm -V’ on every installed RPM to verify that things are installed properly. But please note that this depends on properly built RPMs and most RPMs ignore the verification tags.

Message was edited by:

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

As far as VMware provides and supports upgrade, I would like it to beahave as expected.

I’m almost sure I had about 5Gb free in /vmimages, so in my case it should not be a problem of disk space.

I noticed that the upgrade routine passes «-U —ignorearch —nodeps —force» options to the «rpm» command, not the best ones I think for an rpm based system, in particular if it is a correctly mantained 2.5.3 one.

Also, vmwaretools installation for linux systems seems poorly documented at pages 133-137.. especially if you have a console based linux os.

step 4 mentions «on screen instructions» clearly meaning windows based VMs.

you only find a tar.gz file and an rpm one . without any readme

Is it needed a reboot or only a service restart or what when you install in a new VM? And in a VM where you are upgrading from vmwaretools 2 to 3?

If you do an rpm -Uvh you receive no messages and the guestd process is not running.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

vmware-tools for Linux is either .tgz or .rpm based on your distribution. The standard installation method is chosen based on the Linux of the VM. For example, for RPM based distributions, you would use the .rpm. For debian and its ilk, you would use the .tgz.

Once the .rpm or .tgz is installed then you run vmware-config-tools.pl and that will take care of uninstalling older vmware-tools and installing new ones or recompiling if necessary. There is no reason to reboot a Linux machine if installing/upgrading vmware-tools. If you are using a 2.6.19 or greater kernel please refer to the Linux vmware-tools patches at http://www.astroarch.com/virtual/patches.html.

As for is upgrade supported? Of course. Is it recommended? That is a different story and I think a reinstall of VI3 is a better way to go as it gives me a chance to correct disk layout issues I have with V2. Remember V2 used a LARGE local VMFS for a swap partition. That is no longer needed so that could just be so much wasted space that may be better attached to /vmimages or reduced to support MSCS or even increased to support MSCS. Or a largish /home for configuration files, which is also not needed. Yet, I may need to increase the size of /var, /tmp, /var/log to support the new update mechanism, corefile locations, and increased logging.

Источник

IBM HS22 Blade with IBM ESXi 4.1update2  USB Key
VMware tools installation fails with the error below…

Unable to install VMware Tools. An error occurred while trying to access image file «/usr/lib/vmware/isoimages/windows.iso» needed to install VMware Tools: 2 (No such file or directory). If your product shipped with the VMware Tools package, reinstall VMware ESX, then try again to install the VMware Tools package in the virtual machine.
 The required VMware Tools ISO image does not exist or is inaccessible.

Troubleshooting
SSH to the Vmware host reveals that the /usr/lib/vmware is not accessible

ls -l reveals that the isoimages folder is a symbolic link to /productLocker/vmtools/

cd /productLocker is inaccessible

/vmfs/volumes is missing Hypervisor3

The ESXi partition table can be checked using the command fdisk -l

There is a Warning for partition table 8
Warning: ignoring extra data in partition table 8

And the file system for mpx.vmhba32:C0:T0:L0p8 is Unknowm
/dev/disks/mpx.vmhba32:C0:T0:L0p8   ?    740786   1480957 757935405   5a  Unknown

mpx.vmhba32:C0:T0:L0p8 should be the scratch disk location.

The fix

It is recommended that the persistent scratch location be set for ESXi

Configuring persistent scratch location using the vSphere Client

You can configure persistent scratch space for ESXi using the vSphere Client:

1. Connect to vCenter Server or the ESXi host using the vSphere Client.
2. Select the ESXi host in the inventory.
3. Click the Configuration tab.
4. Click Storage.
5. Right-click a datastore and select Browse.
6. Create a uniquely-named directory for this ESX host (eg, .locker-ESXHostname)
7. Close the Datastore Browser.
8. Click Advanced Settings under Software. 
9. Select the ScratchConfig section.
10. Change the ScratchConfig.ConfiguredScratchLocation configuration option, specifying the full path to the directory. For example:

    /vmfs/volumes/DatastoreName/.locker-ESXHostname

11. Click OK.
12. Put the ESXi host in maintenance mode and reboot for the configuration change to take effect.

Recreating scratch files including Vmware tools iso’s.

Once the scratch  location has been set you can run the current ESXi 4.1 update 2 patch this will recreate the Vmware tools installation iso in the scratch file location.

Once the patch has applied reboot the host.

You can check that the vmtools iso’s have been created by browsing the persistent scratch datastore.

You will then be able to deploy Vmware tools

Recently I was trying to upgrade vmware tools on a windows 2008 guest and I got an error

«Unable to install VMware Tools. An error occurred while trying to access image file «/usr/lib/vmware/isoimages/windows.iso» needed to install VMware Tools: 2 (No such file or directory). If your product shipped with the VMware Tools package, reinstall VMware ESX, then try again to install the VMware Tools package in the virtual machine.   The required VMware Tools ISO image does not exist or is inaccessible.»

Further investigation through remote tech support into the ESXi host I found that the iso image is missing from the directory and the directory is 100% full, which must be the reason for not installing the tool images. I found that old tool images are not removed from the system and as a result while upgrading , its not able to copy the new images due to file system full.

I guess this issue is due to a upgrade from esxi4 u1 to esxi4.1. Somehow the upgrade didnt went well or some other issue. But the ESXi server is up and running and hosting more than 100 vms. I dont want to reinstall the ESXi on the host. ESXi 4.1 comes with resmote tech support , no need to go through unsupported way anymore

I fix the issue by copying the image file from a working ESXi4.1 server.

1) Start the remote tech support (SSH), Click on the ESXi host on the left panel, go to configuration ,
on the software section click on Security profile, Click properties on the right top corner, click remote
tech support and click option and start the ssh.

2) Use putty to ssh into the ESXi host and delete the old images files from the below location

/vmfs/volumes/e00f98e1-2bcc0c91-e7a2-3487611c1557/packages/4.0.0/vmtools

3) Using winscp to copy files to the ESXi host location, provided you already copy the image files from a working ESXi 4.1 server to the laptop/desktop. Copy to below location:

/vmfs/volumes/e00f98e1-2bcc0c91-e7a2-3487611c1557/packages/4.1.0/vmtools.

4) Copy the  .iso, .sig and tools-key.pub. files, because all these files required if you want to upgrade the vmware tools.

Thats its close the winscp, putty and Dont forget to stop the remore tech support(SSH). Now right click on the VM ->guest -> Install/upgrade  vmware tools.

There is another way where you can copy the iso image (windows.iso) to the local datastore and mount the iso image and start the installation. This you have to mount and umount the iso image each time for every VMs. If you have only few VMs this will be easy way but tedious for 100 VMs.