Link to home
Start Free TrialLog in
Avatar of esxijock
esxijock

asked on

How do I install ESXi installable with SAN safety?

I've seen a similar question asked for ESX and the solution - I'd like to do something equivalent for ESXi 4.1.0 installable, but the media seems to be very different.  The QLogic HBA drviers seem to be located within a .vgz file but how to remove these modules?
Avatar of bgoering
bgoering
Flag of United States of America image

A number of ways come to mind.

Disable HBA in BIOS until install has completed
Unplug fiber during install
Disable port on fiber channel switch
Have storage admin un-present the storage durin install

Personally I haven't had any problems... Just don't pick a SAN volume to install on. In fact all of my ESXi installs are on USB stick these days.

Good Luck
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
   * An internal database error has occured
whoops, sorry, having problems posting to EE!
We cannot discuss the modification of VMware software on EE.

I would recommend following @bgoering: suggestions.

If you want to continue modifying VMware source software, all I can suggest is you have a look at the following resources

VMware Community forums.

http://www.vm-help.com/esx/esx3i/customize_oem_tgz.php

However, EE cannot help you any further with the discussion on how to complete the operation of modifying VMware software, as it's against the rules. I've checked with the Moderations if this can be discussed, and the answer was no, as it's in breach of the VMware EULA.
Avatar of c0s
c0s

When you install vmware during the installation there is a question asking you if you want to add third party drivers or if you want to load the default drivers, just chose no
If you are using kickstart to automate your installs you can bind the installation to a specific driver or to "local" storage (FC is seen as remote storage).

In my current installation of ESXi 4.1 Update 1 installable I use this kickstart file option:
autopart --firstdisk=megaraid_sas,local --overwritevmfs

This seems to work for me, I used to remove the drivers too from the installer when I was back at ESX 3.5
Btw, the installer will halt if it cannot find a drive utilizing the specified driver or another local drive.
Avatar of esxijock

ASKER

Thanks for all comments - am testing the use of --firstpart=mptsas,local  ... as a first line of defence!

Also wondered if I could use a modified oem.tgz with a pci.ids file which excludes all PCI HBA devices. would this override any default version of the same file within the ESXi installable media?

I've not yet tried using an oem.tgz file with ESXi installable media - is this do-able / problematic?

N.B. I only want to disable HBA cards within the ESXi installer, not in the final installed ESXi
We cannot discuss the modification of VMware software on EE.

If you want to continue modifying VMware source software, all I can suggest is you have a look at the following resources

VMware Community forums.

http://www.vm-help.com/esx/esx3i/customize_oem_tgz.php

However, EE cannot help you any further with the discussion on how to complete the operation of modifying VMware software, as it's against the rules. I've checked with the Moderations if this can be discussed, and the answer was no, as it's in breach of the VMware EULA.
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok Thanks

I think that adding a modified oem.tgz doesnt necessarily strike me as modifying (base) VMware software, but configuring/extending it ... moot point I guess!?
This questions comes up many times, with users that want to modify VMware ESXi to run on unsupported hardware (not on HCL) by incorporating drivers into ESXi that are not included.

After so many questions, I've had long discussions with the moderators on EE about this. It's clear, it's in breach of the EULA. If it's not included in the original distributed software as supplied by VMware, it's could be referred to "hacking" the source. EE does not support "hacking software", or breaching the manufacturers EULA in any shape or form. We are also not allowed to discuss the running of Apple software on non-Apple Mac products, again it's in breach of the manufacturers EULA. These are not my rules, they are EEs, if we discuss it openly here, we could both end up with suspensions, if we continue. Hence my warning!

If you search using Google you'll find what you are looking for, we've shown you the way. I'm sorry, but I cannot discuss it further here on EE, otherwise I could be suspended.
On a side note -  I have heard a rumor that Mac OS-X will be supported on vSphere 5
@bgoering: our current nda prohibts us by saying anything - so I'll respond with is that true?