ESX 3.5 - Can't add ISO from ISO_Library share on Windows server

[davismisbehavis]

I've recently upgraded 3 of our ESX hosts to 3.5 U4 using a scripted install. As part of that install I added an entry to the FSTAB file which maps to a share on a windows server, this is our ISO_Library. This is a method we have used for years on our ESX 3.0.x hosts without issue.

Now on the ESX 3.5 hosts the ISO_LIbrary windows share is mounted successfully and I can browse to it through the VI Client when looking to add an ISO to a virtual machine. I can add the ISO tick the connected boxes and then Ok the settings. The task completes 100% without error, however when I go looking for the ISO it's not attached. When you go back into the settings of the VM it's set back to client device and the settings that I had amended appear to have been discarded.

If I copy the ISO to a VMFS partition I can mount it without issue, just not from a windows share. If I go back to some of our existing ESX 3.0.x hosts I can still mount to ISO's on the windows share without issue.

Very strange and very frustrating, anyone got any ideas what could be causing this or logs I could reference on the host that might give me a clue.

Thanks

[davismisbehavis]

Right, I've done a bit of digging about and found a number of other posts that shed a little more light on this issue. We have a windows mount to /iso_library in the root partition, we then have created a symbolic link within the vmimages folder so that it pulls through to the VI Client.

As far as I can see it could be one of two things.

1) I believe VMImages is no longer supported in ESX 3.5, however because I have created the link I can actually see it in the VI Client. The issue is to do with support for VMimages

2) the image paths appear to be fixed with the following characters /vmimages/iso_library/Windows Server 2003.ISO and the characters are causing

I know I could put it on a VMFS LUN but we have different groups of hosts attached to different storage devices so a central ISO_Library store would be more beneficial. I could go down the NFS route but the server we have the ISO_Library on is not Windows 2003 R2

Can anyone tell me how I would add a symbolic link into the datastore browser window that does not utilise VMimages?

[AndreTheGiant]

Can anyone tell me how I would add a symbolic link into the datastore browser window that does not utilise VMimages?

Use this command (in COS):

ln -s /iso_library /vmimages/iso

Andre

[Texiwill]

Hello,

Alternatively you need to modify /etc/vmware/configrules to allow /iso_library to be accessible to the VIC, etc.

Best regards,

Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst[/url]
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]

[davismisbehavis]

Hi Andre

the symbolic link has already been created mapping the /iso_library CIFS share to /vmimages and it does show up. My problem is that I believe this is no longer supported in ESX 3.5

Edward, I had a look at the /etc/vmware/configrules file and am wondering what I need to amend and what I would need to restart to get the new config to pull through

I'm presuming the following section is the one I would need to add accept prefix_case "/iso_library/" to? I did that and have restarted the management services but nothing came through when trying to add a CD in the VI Client connected to Virtual Center

1. Only allow paths under /vmfs/, /vmimages, some media and relative paths

accept prefix_case "/vmfs/"

accept prefix_case "/vmimages/"

accept prefix_case "/usr/lib/vmware/isoimages/"

accept prefix_case "/var/lib/labmanager/isoimages/"

accept prefix_case "/var/lib/labmanager/mnt/"

accept prefix_case "/var/lib/labmanager/mnt_device/"

accept !prefix "/"

As always gents, I apprecaite your time and assistance in helping me with this issue