golddiggie's Accepted Solutions

Depending on how long it's going to take them to become compatible, go to 6.5u1 (not 6.5u2). That way you'll be able to go to 6.7 with an upgrade/update. Well, at least until 6.7u1 is released (could be during VMworld 2018 in August). Since this was a new install, your only course of action is to do a clean install. If you already setup vCenter (vCSA or Windows install) that can manage 6.5x hosts. But, if the software runs against vCenter/vCSA, then you have do a reinstall/rebuild of everything on the lower version. If you didn't know, you cannot administrate newer versions of hosts with an older version of vCenter.

Judging by the name of the file that is linked to in the HCL listing, they haven't actually updated the drivers since ESXi 5.5 came out. If you've not put any VMs on this host yet, I say pick either the version 19 or 20 and go for it. Personally, I tend to go for newer release dated drivers when I have a choice. But, that could be a bug fix update to an older driver. I tend to try to get as much hardware (as possible) that has drivers that are 'in box' with the ESXi GA releases. Or I grab the customized ISO versions that are made available (usually not long after the GA is released) such as for HP or Cisco (required if you value your sanity).

The way the hard drives are being displayed (assuming you set up the RAID correctly in bios) means that you have a software RAID controller. ESXi only supports HARDWARE RAID controllers. Any software RAID controller, that works with ESXi, will just show the individual drives within ESXi/vSphere. If you really need those drives inside the host server, you'll need to purchase a hardware RAID controller that's on the VMware HCL for ESXi 5.x... Otherwise, you're pretty much SOL here. When you look at the Network Adapters under the host's "Configuration" tab, does it only show a single vmnic for that adapter? If so, then I suspect you either need async drivers for the NIC, or it's defective/damaged. Although a quick check on the VMware HCL shows the NIC drivers as being 'inbox' under ESXi 5.x, so that's probably not the issue. See if there's an update for the NIC's themselves for the server. This would be separate from the motherboard's main bios updates...

I'm running ESXi 5 on a Dell Precision Workstation T7400 with dual e5405 Xeon's, 24GB RAM, Intel server class NIC's and booting it off of an 8GB USB flash drive. ALL my VM's live on my QNAP 5 drive NAS/SAN (with iSCSI LUNs for VM's). You can sometimes find this system in the Dell outlet site, or where they sell off lease hardware. It's been a solid performer since ESXi 3.5 for me. At one point I was using onboard storage via a PERC 6/i controller, but I've since removed that completely (along with those hard drives) and simply boot from the USB flash drive.

Is the bios at version 2.7.0? How about running a memtest burn-in on it (for 48-72 hours)? I've seen memory that wasn't quite 100% do all kinds of things to the stability of a host. It's good enough to pass the built-in tests, and boot, but if you put a load on it, it gaks. It also looks like you could have an issue with the actual CPU(s). How about testing with just one installed? You could have enough of a mismatch there to cause issues. Even though they could be the same model number, being from different lots/batches can make for a mismatch that's enough to cause issues.

Then install ESXi 5u1 onto the system and configure it up as a host server. Then use another computer (yes, you need to have another system to actually configure/use the host) to configure passthrough and such. I'm not sure if it's available in the free edition, so you'll have to try it out and see. Be aware that you'll only be able to use the video card on a single VM at one time. I did just enable DirectPath I/O on my own host's video card (an nVidia Quadro NVS 290). It requires a reboot before it's available though. So, if this works (for you too) you'll enable it, reboot the host, and then attach one of the VM's to the video card to use. You'll then be able to use your other system to open a console window to that VM (from the vSphere Client connecting directly to the host server) to do what you want/need.

You need to go to where the permission is defined in order to delete it. Look in the 'Defined in' column when you click on the permissions tab. Then go to that location's permissions tab in order to delete it. You'll know when you're in the correct spot since the 'Defined in' column for the item will say 'This object'.

Since you've not entered the key yet, since it's still listing "Evaluation Mode" that doesn't apply. Historically, evaluation mode has been Enterprise Plus license (everything available to you). Once you apply a license key, then you get those features. Do you have two physical CPUs installed in the server? I've not, yet, installed ESXi 5 on my host, since I need to test for iSCSI communication with my SAN/NAS before committing. I might do it via a nested VM, or with Workstation 8 on my main worker... You could have one slightly flaky CPU in the box, which ESXi simply doesn't like where the other operating systems are willing to deal with it. ESX/ESXi has been known to reject hardware that other operating systems accept/work with, even though it's compatible. Just for giggles, pull down the full diagnostics flash drive image, install to a new flash drive, boot the server from that and run it on a loop for a day or three. That should pick up any hardware issues. I would also run memtest on the host for at least 2-3 days. That will flush out any questionable memory sticks in the host. I've had that discover memory that was just bad enough to cause issues with ESX/ESXi, but not other operating systems. Replacing the memory before it's being actively used is usually the better choice. As such, a memtest 'burn-in' of at least 4-5 days is now SOP for me.

vSphere IS ESXi (or ESX) with the manangement add-ons... If you're talking about vCenter, then just make a VM on one of the hosts (on shared storage) and then start configuring it there. I've done this more than a few times with great success... Having the vCenter Server as a VM has several advantages, not the least of which is being able to vMotion if the host it's actually on goes dark. What kind of SAN are you using for the VM's?? What are you installing ESXi onto (on the physical hosts)?? Even though you can install ESXi to flash drives, I still prefer to install to a pair of SAS drives in a RAID 1 configuration. You don't need very large, or fast (anything over 10k rpm and you're golden) to do the job. You could do it with SATA drives, but you're better off with SAS (higher reliability numbers). I also like the RAID 1 configuration in case of drive failure. Just more resiliency to failure, or one less single point of failure... BTW, I would also use an actual SQL server for the database for vCenter and it's parts. IMO, far better than using SQL Express that's bundled with the installer. Sure, you CAN go with SQL Express, but you'll have more management options under full SQL... Make the SQL Server as either another VM (so you'll make two VM's to start with) or use an existing SQL server (for now)... If you use an existing SQL server, I would plan to migrate to a virtual one as soon as you can.

Which HCL's are you using? The one from VMware is my primary, but there's also the one from vm-help and ultimate whitebox... If the motherboard uses RealTek network hardware, get an Intel card before you even start (one from the HCL). Use the VMware HCL for that, since you'll need to have support for the NIC with the installer. For RAID level with four drives, I would do RAID 10. Install ESXi to a flash drive (2-8GB in size) and use the RAID array for VM's and such.

The LUN/Datastore would be limited to 2TB-512k in size (through ESX/ESXi 4.1 u1/VMFS 3.x). Depending on the block size you went with, VMDK files will be limited to a max size. Such as 256GB with a 1MB block size. If you need larger VMDK files, then you'll need to storage vMotion the VM's off of the LUN/Datastore, reformat/recreate the LUN/Datastore, then move them back onto it. This is part of proper planning of how you set up the LUNs... If you need to have 500GB VMDK files, then don't use the 1MB block size. By the same token, don't use 8MB block size if you're going to have <256GB VMDK files.

To vMotion a running VM between hosts, you need to have the VM on shared storage. You can vMotion a cold VM to any place the host can see/read. IMO, it's best to have VM's on shared storage especially once you have more than one host server. Hell, I even have my VM's, in my home lab, on a SAN. Basically, I'm prepared for using another system as a host server, even if it's only temporary (booting off of an USB flash drive) so that I can apply updates to my main host... 

Nested ESX/ESXi hosts can only run 32 bit VM's... It's one of the very well known limitations to running a nested host. Basically, the physical host is passing the full information to the virtual host, which cannot pass it along (again) to the VM's running inside the nested host. You can only pass the info in so far.

At this point, the difference between ESX 4.1 and ESXi 4.1 is shrinking, for what you can do via administration tasks. Get the vMA appliance, and you have more capabilities. With the new remote SSH capability on ESXi 4.1, you gain a lot of what ESX 4.x used to bring to the table (by itself without needing to modify an ESXi 4 confd file)... So unless you have tools/software that only works under ESX 4.1, I wouldn't wipe and install ESX 4.1... For one thing, you'll need to do the reverse when you want to go to the next release. For another, most of the third party tools either have been updated for ESXi 4.1, are in the process of being updated, or will be before too long. At least the ones that actually want to keep their customers that are running VMware's products. I've moved my VM's to a SAN/NAS in my home lab. It comes in handy when I want to update the host, since I can have them run on a temporary host (a good system, using ESXi 4.1 installed on a thumb drive). Eventually, I'll have at least two hosts in my lab running 24x7 so that I can more easily update things. Plus it will allow me to run more VM's at the same time.

Just get an Intel Pro/1000 NIC that's listed on the VMware HCL and you'll have no issue. You'll want more than a single network connection in the box anyway, so better to either get a pair of cards, or a dual port NIC (or quad port, or a combination of both)... Using a single NIC for everything is typically a very bad idea. VMware VCP4 Consider awarding points for "helpful" and/or "correct" answers.

You'll need to keep the old vCenter online to use it's license server while going through the upgrade process. The vCenter 4 Server will use that old vCenter license to allow you to administrate the ESX 3.5 hosts during the process. You should have a new vCenter, as well as vSphere/ESX/ESXi 4.x licneses available to you on your account page. Keeping the old while using the new should be fine (which edition of vCenter Server are you licensed for?)... I would pull all the 3.5 hosts into the vCenter 4 Server configuration at the start of the process, then migrate VM's from one host at a time as you upgrade the host (as you pretty much outlined)... I would balance the VM's across the two hosts not being upgraded at each step. That way, you 'spread the load' across them. Then repeat in the other environment... You can also opt to have the two vCenter Servers linked, allowing you to manage both from the same login... Provided you have the correct edition... VMware VCP4 Consider awarding points for "helpful" and/or "correct" answers.

You could set up a VM on the host, install the vSphere Client onto it, make sure you can manage the host with it, and then enable RDP on the VM. Enable port forwarding on your dlink(ie) router to the IP address of that VM and test... I would also suggest using a service such as dyndns.com's (free) offerings to use a regular url to connect to your home setup. Install their agent, or have your router keep their listing up to date, and you're good... I use the RDP method to a vCenter Server (on my ESXi host) in my home lab environment. I enable the port forwarding on my Linksys router (WRT610N) to the IP of the vCenter Server when I think I'll need to connect into the home setup... Otherwise, I leave the port forwarding off. I also use more of the services (now) from dnydns.com to make sure my web and ftp servers are available no matter what my public/home IP address changes to... I would advise setting up an AD DC to use for authentication... Also use at least a strong password (you can use something like passutils.exe to check the password strength) for that account and make sure your network is otherwise secure. I would NOT install anything onto the host directly (not that you could under ESXi)... VMware VCP4 Consider awarding points for "helpful" and/or "correct" answers.