Software RAID is *not* supported by ESXi. To VMware ESXi 5 this issue may. SSH as well as the password for the VMware vSphere Client (requires Windows).

The un-official VMware Reddit. Everything virtual.

Have a technical question? Just make a self post! Current Links: General Links: Icons: The VMware logo icon following a username indicates that this user is a VMware employee. If you are an employee, please PM one of the moderators that has a VMware logo for verification instructions and we will add it to yours as well! Certification Flair: To get flair with your certification level send a picture of your certificate with your Reddit username in the picture to the moderators. Spam Filter: The spam filter can get a bit ahead of itself.

If you make a post and then can't find it, it might have been snatched away. Please and we'll pull it back in. I would recommend using a cheapo 16gb USB drive (set boot priority to prefer this over the hardware raid card so that esxi boots) to load ESXi onto, which will give you your option of going raid-10 (3 stripes) with all the SSD's for some performance testing if that's what you desire.

That way you are not wasting high cost storage for the ESXi functions, yet can still get some great performance out of those SSD's. Alien Skin Blow Up 2 Keygen Mac. Or if you can scrounge up another chassis, then you could expirament with a hybrid SSD and HDD array in both chassis, with the vmware VSAN (currently in free beta) product with data tiering between the SSD's and the HDD's. Good luck, sounds like a fun project! The Scratch and Logs are not written to USB/SD based boot media.

So if you want those to persist across reboots, you have to put them on to your VMFS. So you are right back where you started with Scratch and Logs going on your SSD array. So USB/SD Boot media in ESXi is worthless when you will be adding local disk as a DataStore. Just go with a single Volume, slap ESXi on there, it will create DataStore1 and you are off to the races.

The impact of Scratch and Logs on your SSD array will hardly even be noticeable. Grab a megaraid controller that can use SSD as hot-cache (or esxi 5.5) and make good use of the SSD. I've had to move a DL320s with 12 x2tb drives to a DL180G6 by simply moving the USB stick and drives.

Literally booted right up. Wasn't happy about the new home VCENTER but it worked perfectly. 10gbe nic's included. I've also ripped out a shitty LSI megaraid controller and stuffed an HP P420/1gb FBWC in without changing the USB boot media, leveling all the drive data. It takes time to setup the host perfectly, if you don't have host profiles.

Inhaltsverzeichnis • • • • • • • • • • • • • • • • • • • • • • • • • • • General information Hardware • VMware vSphere Hypervisor 5.x and 6.0 (ESXi) use a filesystem called vmfs5 (formerly vmfs3), which uses GPT and supports drive sizes of up to 64 TiB (formerly 2 TiB). • Software RAID is *not* supported by ESXi. • The free version of ESXi starting with 5.5 supports a maximum of 4 TB RAM (formerly 32 GB RAM). Network configuration • VMware vSphere Hypervisor is an 'operating system' designed for pure virtualization and supports neither NAT nor routing. Therefore, only a true bridged setup can be used.

• To use a subnet an additional single IP needs to be setup as a router VM. Installation • The installation and configuration of ESXi takes about 20-30 minutes, even without any prior knowledge. Please check out the for further information on installing ESXi. License • After installation the system has a test license, which expires after 60 days. For the long-term usage of the OS a separate (free) license is required.

This can be requested by registering on the VMware website: • License for • License for • The license can be entered via the vSphere Client, under the tab 'Configuration', the section 'Software' and then under the menu item 'Licensed functions'. After selecting this you can click on the 'Edit' button to the right and then enter the license key. Hetzner specific information Installed hardware The Dell PowerEdge models DX150, DX151, DX290, DX291 and DX141 are certified and compatible with all versions from 5.0 onwards.

All other models are not certified by VMware, yet in most cases they can be run with VMware vSphere/ESXi. Compatibility (All information is subject to change. Last update: 2 April 2016) Model vSphere/ESXi Version AX50-SSD/AX60-SSD from 6.5a additional Intel NIC required AX160 from 6.5a PX91/PX121 from 5.5 Update 1 PX90/PX120 from 5.1 PX61 from 5.5 Update 3 / 6.0 Update 2 PX61-NVMe from 6.0 Update 2 PX60/PX70 from 5.5 Update 1 EX41/EX41S/EX51 from 5.5 Update 3 / 6.0 Update 2 (potentially an additional NIC required) EX40/EX60 5.0 - 5.1 Update 2, since 5.5 additional NIC required EX6/EX6S/EX8/EX8S from 5.0 EX4/EX4S/EX10 from 5.0 (with additional NIC) EQ4/EQ6/EQ8/EQ9 from 5.0 NOTES: • The models mentioned above should work with the appropriate version. However, newer versions are not necessarily compatible. To make sure please gather your own information. • The Realtek driver present in ESXi 5.0 to 5.1 Update 2 was just a Tech Demo that has not been updated.

Therefore, for smooth operation a server with an Intel NIC (PX60, PX91, DX151 etc.) is recommended. • The installation of vSphere 5.5 or newer on the EX40, EX60 and some EX41/EX51 models requires a custom installation ISO that includes drivers for the Realtek NIC (). Alternatively, an additional compatible NIC can be installed. Please find the cost of an additional compatible NIC here: • Installing ESXi on the older DS or X servers is not possible. • When installing on a server with multiple identical drives, ESXi can potentially show the drives in a different order than the BIOS does.

Should the screen be blank with only a blinking cursor after the installation is done and you restart, try booting from the other drive. Network Configuration • For connectivity between multiple ESXi servers within the same subnet, host routes via gateway are necessary due to network security restrictions.

Host A esxcfg-route -a 255.255.255.255 host B esxcfg-route -a 255.255.255.255 Single IP addresses • IP addresses are, by default, statically mapped to the MAC address of the host. It is possible however to get separate MAC addresses for the additional single IPs via Robot. These can then be configured for the virtual machines. To get these MAC addresses assigned, log in to Robot, choose 'Server' from the menu on the left, select the desired server, and then click on the 'IPs' tab.

Here you can click on the icon next to the single IP address to get a MAC address. Subnets • To use a subnet (IPv4 as well as IPv6) in ESXi, at least one additional single IP is required as a router VM, since ESXi itself cannot route. When ordering a subnet, please make sure to note that it is required for ESXi and should be routed on the additional single IP. IMPORTANT Since IPv6 subnets are routed to link-local addresses (MAC-based), it is only possible to use IPv6 in a limited way (ie. In a single VM). IPv4 The confirmation email of the subnet contains (for example) the following information: Below you will find the IP subnet added to your server 192.168.13.156. Subnet: 192.168.182.16 /28 Mask: 255.255.255.240 Broadcast: 192.168.182.31 Usable IP addresses: 192.168.182.17 to 192.168.182.30 You do NOT get a separate MAC for each IP from a subnet.

IPv6 All servers come with a /64 IPv6 subnet. To see which IPv6 subnet your server has please check the 'IPs' tab of the server in. If you ordered your server before February 2013 this subnet can be ordered (freely) via and will be automatically activated. The IPv6 subnet is routed to the default link-local address (which is derived from the MAC address) of the main IP. Via the routing of the IPv6 subnet can be switched to the link-local address of the virtual MAC (in other words, the additional single IP).

This can be done in, using the same symbol which is found next to additional single IPs to request virtual MAC addresses. The host system, so the ESXi itself, receives no IPv6 address. This is neither necessary nor possible because ESXi can not work with a fe80::1 gateway. In order to use these IP addresses in virtual machines, a 'router VM' supplemented by an additional virtual NIC from the new subnet is necessary. The subnet itself requires a new vSwitch in ESXi to which all VMs in the subnet will be connected. Notes The network card type for the router VM should not be VMXNET2 or VMXNET3, as otherwise the TCP performance can be very bad. As a workaround LRO in the VM can be disabled via 'disable_lro=1'.

More information on this bug can be found here: After an upgrade to VMware ESXi 5 this issue may appear again. You can address this issue by disabling Large Receive Offload (LRO) on the ESXi host: • Log into the ESXi host with the vSphere Client.

• Select the host ->Configuration ->Software:Advanced Settings. • Select Net and scroll down slightly more than half way. • Set the following parameters from 1 to 0: Net.VmxnetSwLROSL Net.Vmxnet3SwLRO Net.Vmxnet3HwLRO Net.Vmxnet2SwLRO Net.Vmxnet2HwLRO Reboot the ESXi host to activate these changes. If you experience connection problems in systems with Realtek network cards then under certain circumstances deactivating offloading and activating polling can solve this. However, this also reduces the performance. • checksum offload: deactivated • segmentation offload: deactivated • large receive offload: deactivated • device polling: enabled Preparations in the vSphere client 1.

Create a vSwitch (in the example the name 'subnetz' is used) 2. Add a second NIC to the router VM.

Connected network: subnetz (the previously created vSwitch) 3. The NIC of the virtual machine in the subnet.