Welcome back to vSphere 8 in the real world. Now we're going to discuss ESXi installation.
So ESXi is what's known as a Type 1 hypervisor or a bare-metal hypervisor. There's Type 1 and Type 2.
Whereas Type 2, we might have Windows or Linux installed already. We might install something
like VMware Workstation on top of the Windows operating system or the Linux operating system
with a Type 1 hypervisor or a bare-metal hypervisor like ESXi. There's nothing installed
on this hardware already. So we have a brand new server. It's just bare-metal and we install the
ESXi operating system onto that server. And that is why it's referred to as a bare-metal hypervisor
because there's nothing on there before we install ESXi. This becomes the platform on which we're
going to create virtual machines. So we're going to, within ESXi, we're going to configure virtual
networking. We're going to configure storage. We're going to, you know, all the different things that
we will need access to for our virtual machines. And then we're going to actually create the VM
itself, right? We'll assign it CPU. We'll assign it disk. We'll assign it networking. We'll assign
it memory. And the VM is going to use the resources from the ESXi host that the ESXi host has available
to that VM. The ESXi host is going to control that access to those resources. So we might
assign our VM 16 gigs of RAM and ESXi is going to control that access to that RAM. If the ESXi
needs to, it can take some of that physical memory away from the VM and use, you know, things like
swab or page files in order to control access and make sure all the VMs are running, you know,
as best as they can with the resources available on the host. The ESXi hypervisor is what's controlling
that access to those physical resources on that box. So requirements for installing ESXi 8.
So for CPUs, we want at least two cores on there. You want to have your nx.xd, you know,
hypervisor support enabled on your processors. At least 8 gigs of RAM. Virtual hardware will
be enabled. Your VP will be enabled. At least one gig network adapter. Really, that's the bare
minimum just to manage that host. Nowadays, it's very common to see hosts that might have
two or four or more 10-gig NICs, 25-gig NICs are very, very common nowadays. It might depend on
what kind of storage you're using. If you're using iSCSI storage, you might have a couple,
at least 25-gig NICs available for the iSCSI storage. And then your VMs might be running on,
you know, two or three or four 10- to 25-gig NICs for the VM access to the network. And then
if you have some one-gig interfaces on there also, you might manage the host through there,
but you'll probably use 10- or 25-gig NICs for things like vMotion and things like that as well.
All right. So at least one gig adapter just to manage the host. All right. You're going to need
at least 32 gigabytes of disk space, and that's minimum in order to install the operating system.
You probably want a little bit more than that, but you want to be able to have things like
login enabled. The more, you know, VMs that you're running, the more logging you might have,
so you might need more additional space for things like that. Now, that is only to install
the operating system. You're not going to want to create virtual machines on that same disk
that you've installed your OS on. You want a disk dedicated to the operating system or a disk if
you want them mirrored, dedicated to the operating system. And then you'll have other storage that
you'll use for the VMs. You might have local disks on that machine that you're using for something
like vSAN, or you might have some kind of shared storage of iSCSI or Fiber Channel, some kind of
SAN on the network. You could even use NFS. NFS has been supported for virtual machines for quite
a while, I think since around like version 6 or 6.5, it's been supported. All right. So you can
see some links here where you can go and see what processors are supported by, you know, EFXI,
other platforms, you know, resources that are available, like HBAs and things like that are
all available and supported. So it's very, very common now, you know, most servers will have some
kind of remote access cards that you can use to access those servers as if you're sitting in front
of them. So it's not as common anymore that you're going to want to have a crash cart and go around
and plug into servers in order to get to the console and, you know, type keyboard commands in
and things like that. Most likely you're going to use either a DRAC or an ILO. If you have DELs,
you have a DRAC, HPs, you have an ILO. If you have some other third-party server, they might have
their own management cards in there, but the most common two are DRACs with your DELs and ILOs with
your HPs. And this is just showing the different versions of firmware that are supported for those
kinds of cards. So some things to consider when you are installing ESXi without a local disk,
then you can deploy ESXi without local disk. You'll do what's called an auto-deploy,
or you can also install them on a remote disk, meaning if I have, for example, fiber channel,
I could use a LUN target on my SAN as the destination for I'm going to install my ESXi.
So that's just something to consider. It's very, very common now that people have a card in the
server they install the OS on. Booting from SAN is supported. You do see it sometimes.
The advantage of doing a boot from SAN is, like, for example, let's say you have a blade chassis
and you want to swap out a blade for one reason. Either the blade's gone bad or,
you know, you're upgrading or something like that. You can take a blade out. You can put a
new blade in. You can configure the HBA on that blade to boot from that LUN that the old blade
was booting from, and it comes up and it's the same host all over again. So there are advantages
to doing a boot from SAN. It's just not something you see a ton of. Cisco UCS, you see that kind of
quite a bit. Other vendors, you don't see it quite as often. So performance recommendations,
you know, let's say at least you want to have at least eight gigs of RAM. Again,
that's just kind of run the operating system. If you want to actually run VMs, you're going to have
to have a lot more RAM than that. So if your VMs, you know, are going to have 16 gigs of RAM each,
you're going to want to have 16 gigs of RAM available per VM plus some overhead for that,
right? And how much overhead will depend upon how many virtual CPUs you assign, how much RAM you
assign. Each VM will have, the bigger the VM, the more overhead that VM has. So a 16 gig and,
say, four virtual CPUs, you might need to have like 16 and a half gigs of RAM or something like
that per VM. Now, it's possible to do what's called oversubscription, where maybe all the
VMs running total on my host equals, you know, 64 gigs of RAM, but my host only has 56 gigs of RAM
or something like that in there. So I oversubscribe because I need RAM for the EFX host itself to run
then for the VMs on top of that. So that 56 gigs, I don't even have that much available because the
ESXi host needs resources. So I've oversubscribed that host. And what will happen is each VM will
get a certain amount of RAM, a percentage of what they are assigned, and then the rest will be
paged to a page file. And page files, obviously, are not going to be anywhere near as fast because
they're on a hard disk. So they won't be as quick as the actual RAM on the host. So you can do that.
It's a performance hit. I wouldn't recommend it. Most people don't recommend it. It's very,
very common to see hosts nowadays with 512 gigs of RAM in them. Some of these big, huge hosts,
you know, terabytes of RAM are not unheard of at all nowadays in ESXi hosts. Okay.
For your networking, you want multiple adapters on your host. You want adapters dedicated to things
like management. You want adapters dedicated to things like vMotion. If you're already fault
tolerant VMs, you want network adapters dedicated to your fault tolerant network.
And then you also want adapters dedicated to the VMs themselves. Now, I'm not saying to each VM,
but you might want a team of VMs. Maybe you have two or three or four adapters in your host that
are working as a team that all your VMs are running off of. So you need multiple adapters
on your host. Again, there's the management of the host. vMotion network would want a dedicated
NIC, at least fault tolerant network. You might want a dedicated NIC for that. And then the VMs
will also be dedicated NICs. So you want plenty of RAM. You want plenty of CPU. You want plenty
of network adapters. So some of the considerations, the disk, you don't want the VM stored
on the same disk as the operating system is installed on. You don't want to get some big,
huge 14-terabyte drive to install ESXi on and then put VMs on that same disk. You want
maybe like a small disk for the operating system itself. You see a lot of times you'll get
256-gig SSDs, and you'll install the operating system on that. And then you might have multiple
terabyte drives in some kind of array to array, some kind of storage configuration for vSAN or
something like that. If you're using vSAN, you're not using RAID. This depends on how you're using
your disks. And put the VMs on separate disks from your operating system. The aligning the sectors,
that used to be a big consideration when you were installing ESXi and configuring your VMFS
data stores and creating your virtual disks for your VMs is making sure that you had your sector
alignment configured correctly. ESXi does that for you now. It's something to maybe be aware of
that there is that sector alignment happening, but you don't have to worry about doing it. ESXi has
done that for you, again, I think since like version 6 or so. ESXi has taken care of aligning
the sectors on the virtual disk with the physical sectors on the physical disk. So it's not something
that you as an admin have to try and calculate and figure out anymore. All right. For your
processors, you know, what kind of processors do you want? For the most part, you want processors
with lots of cores, lots of cache. Of course, the faster the better. But if you're trying to trade
off what's better, faster or more cores, it depends on what you're running on that host. If you're
running a very small number of large VMs that need a lot of fast processors, then that's probably
what your host should have also. If you're running a large number of small VMs, then lots of cores
are sometimes going to be better for you or oftentimes will be better for you. So it's going
to depend on your workloads. But as a general rule, lots of cores, lots of cache, and then
as fast as you can afford to purchase for your host will be good.
So log files. The log files are going to be stored with the operating system.
If you have, you know, a very small disk you're installing, like you used to see people installing
on these 32-gig little SSD drives, you know, SSD cards that were on the motherboard of the servers,
and the SXI host would log to those, what would happen is they would fill up quick,
logs have to turn over quick, you wouldn't have the older log data you might be looking for.
And also VMware, the SXI, would log sometimes too much. And so disks were getting written to
very frequently, and those little SSD cards were getting worn out. VMware had some fixes for that
to make that not much of an issue, but SSD cards aren't even supported anymore. So now you're going
to be installing onto, not little SD cards, but like SSD drives, actual physical storage, not the
little cards that, you know, slip into a motherboard like you might have like in a digital camera or
something like that. But you want to make sure you do have plenty of space for your log files.
You don't want your log files filling up your disk. In reality, the log files on disk really
actually shouldn't be too much of a concern for you because you should be sending your
logs to a sys server. And if you have a sys log server, then all log files are going there,
and you're not going to worry about filling up your drives or them getting overwritten because
they're all being dumped off to another system. So ideally, sys log server, but if you're not
using a sys log server, make sure you have enough disk space for your log files to go to.
So if you're going to do an installation, one of the first things you need to do is you need
a MyVMware account. So you're going to go to myvmware.com, and you're going to make sure you
have your login credentials. You're going to log into MyVMware, and then you can go and you can
look at all the things that you have a subscription to. And you can see your license keys from here.
You can also, you know, find out what you would, based on your subscriptions, what do you want to
download. And you can download the ISOs for vCenter. You can download the ISOs for ESXi.
If you have a subscription to VMware Horizon, you can download the Horizon ISOs from there.
If you have NSX, then you can download licenses and things like that for NSX from here.
So myvmware.com is where you're going to go for your license keys, as well as downloading your
ISOs. Once you've downloaded your ISOs, you're going to want to run an MD5 check against that
ISO just to make sure that it's downloaded correctly. It's not any kind of corruption.
You're not going to get a bad installation of ESXi when you go to deploy it onto your physical host.
So there are three primary different ways you're going to do an installation of ESXi.
Either you can do an interactive installation, which means you're going to boot from, like,
the ISO on a thumb drive or something like that. Or if you have a DRAC or an iLO,
you can mount the ISO into that DRAC or to the iLO device and boot from that ISO.
If you have five or fewer hosts you're deploying, that might be the quickest,
easiest way of just getting that done. You can also create scripts. Now, if you're going to deploy
a large number of hosts, you might not want to sit and hit, you know, next, next, next,
and OK, and things like that. You might want to automate the deployment, and you might want to
automate the configuration of certain settings, you know, such as IP addresses and root passwords
and things like that, right? So you can do a scripted installation. And typically, if you're
doing over five hosts, that becomes an effective way of doing that. There's also auto-deploy.
Auto-deploy will allow you to basically boot up the host, do a PXE boot. It will get information
from, like, the network DHCP can tell it where is my PXE server at. It will go connect, get that
information, pull over the operating system. It will also, the PXE boot will tell it what vCenter
server is going to be using. And then the vCenter server can tell that system, here is the profile
we want you to use, meaning here's how we want to use your adapters, here's your IP addresses,
here's all this information that will be customizing that particular image. So you don't
have to go and click next, next, next, or anything like that. And if we do, again, swap out a blade,
for example, we can tell it to point to the auto-deploy image, pull it all over, boot up,
it has its name, it has IP addresses, passwords, all that kind of stuff, all configured to the
auto-deploy push. So interactive, again, booting to an ISO, whether it be on a USB drive or a
DRAC or an iLO, for a small number of hosts. A scripted installation is going to be, you could
boot to an image, and then you're going to interrupt the boot process, point it to a kickstart
file, which might be, like, on a FTP server or something, and it will get its answer file and
start the deployment. You can walk away. Auto-deploy is going to use DHCP, it's going to
use vCenter, and it's going to get the configuration for that host every time it boots, okay?
So, again, interactive, if you have five or fewer hosts you're booting, you could do a CD-DVD.
That's really going to be rare nowadays. Very few systems even have CD or DVD drives.
The ISO is probably going to be on a USB drive, all right? You could do a PXE boot over the
network and then install it, you know, get the image pushed to you that way also. That's not
auto-deploy, right? This particular PXE boot is going to PXE boot and then have a system basically
push the ISO files over that will go through an actual installation, and you're going to answer
the questions, you know, yes, I agree, and, you know, I don't have a keyboard and de-configure,
here's the disk I want to install to, some things like that, right, all pushed over the network.
So, once you start the installation, it's going to start a wizard. It goes through some basic
processes. It asks you, you know, what disk do you want to install to. If you have SSDs,
it'll show you the SSDs. If you have a fiber channel card, for example, an HBA, and it has
access to LUNs, you might see the LUNs on your SAM that the HBA is allowed to have to see,
that it's zoned for. The downside of that could be you might have VMs on there, and you might
pick the wrong one. So, make sure you're really careful when you're doing your installation
that you are not using drives on your HBA if you're not intending to do a boot from SAM.
If you're trying to install locally using, you know, an ISO file, make sure you're choosing a
local disk. You don't want to overwrite a VMFS data store, wipe it out,
lose all your virtual machines, okay? So, just be careful of that. Be aware of that.
So, the installation wizard is going to ask you to choose your keyboard type,
enter in your root password, start the installation, and it reboots. Really simple.
There's not a ton of steps, right? Keyboard, password, you know, what disk you want to
install to is going to ask you that, then it starts the installation, and then it reboots.
And then when it comes back up again, it will boot up. Hopefully, you have selected
the device that you've installed to as your boot device in your BIOS, and when it comes up,
you'll actually then be able to, from the console, log into the box and configure things like IP
addresses and stuff like that, okay? If you have a VMFS data store already on there,
you can tell it to leave the VMFS data store alone, not to do anything to it,
and, you know, to preserve the data, and just do an installation, or you can tell
it you want to wipe the VMFS data store and you want to start all over again, okay?
So, a scripted installation can be very similar to, you know, a traditional booting to ISO and
going through it manually, except as soon as you start the boot process, you're going to interrupt
it, and then you're going to give it a location for a kickstart file or for an answer file for
the installation. So, all the different things that you would configure, you know, by – through
the wizard by hand will be in that kickstart file. And you can even add some things in there like IP
addresses and, you know, additional information that you may not have done during the installation
can be done through the kickstart file, okay? So, here's kind of an example of a kickstart file.
So, it shows you – there is an example of where you can find a kickstart file on the host under
xe-vmware-weasel-ks.config, right, on the host. So, you can go in there and you can find it.
You can store this kickstart file on an FTP server, HTTP, HTTPS, NFS. I think FTP is one of
the more common ways that people store them, but it can be anywhere. You can also put it onto a USB
drive and plug it into the host. That means that you're kind of visiting boxes more. You're not
probably doing this as remotely like through a DRAC or something like that. So, that probably
is less common. More common would be remotely accessing the host through a DRAC, mounting the
ISO, and then pointing it to a kickstart file like on an FTP server or something like that, right?
So, in your kickstart file will be a bunch of different settings. For example, you have to
accept the end user license agreement. You're going to give it a root password. You can specify
there's additional drivers you need to pull over and install. For example, maybe for a
RAID controller or something like that. Or, you know, if you have a special keyboard,
that's not very common, but you might have special keyboards you need to configure or something like
that. This kind of shows you. So, when it boots up, when it first starts the installation,
you're going to quickly interrupt that process. You can hit shift O. Then you're going to give
it the location of your kickstart file. You can say kickstart is located on an NFS server.
Here is the IP address of that and the folder, the name of the file. And then you can probably
want to assign or going to need to assign that particular host a temporary IP address network
mask to get on the network with, right? So, this is where you can give it all that information.
Here's the kickstart file. Here's the IP I want you to use. Here's the mask you're going to use
and get it started. All right.
Auto deploy, as we've mentioned, auto deploy is a way of just quickly pushing out a config
or actually, you know, an operating system and a config. It's going to do a pixie boot and get,
you know, connect to a pixie server to get the operating system and vCenter,
your vSphere environment is going to give its configurations and give it its host name,
its IP address, its port groups for networking. You know, if there's multiple VM kernel ports,
all that kind of stuff can be pushed out through that profile for that host through the auto deploy.
So, here's just kind of showing, you know, some of the basic steps, right? So, you're going to
connect to the home screen in the vCenter, which is your web client, you know, GUI that you're
going to connect to. You're going to select auto deploy. It's been around since 6.5. So,
the vCenter is going to go in and load the ESXi images that it has for that machine. So, what you
might do is configure a machine first, like traditionally, use that to create that first
auto deploy image. Then you can go and you can customize the image for each host and assign it
to different hosts as they boot up, okay? So, basically, it's taking an image you created first
and just customizing that for each host that you want to connect to after that, right? And
that could be useful, very common, like I said, in an environment where you have blades.
It also works with regular rack mount servers. I'm not trying to say it's only for blades,
but I think in my experience, I've seen it a lot in blade environments where we know that all these
blades are exactly the same and I want to be able to swap out blades and upgrade blades easily.
With rack mount servers, it's more likely that you have internal storage you're going to use
and you're going to push out configs. You might script those installations, but you're going to,
you know, probably push them out to host and store them on local drives. Now that we have gone over
some different ways you can install or deploy ESXi, let's go ahead and go to our demo environment
and we'll go over how to install ESXi 8, all right? So, here's our demo environment. In this demo
environment, we have one physical host, which is a pretty large host, and on it we have created
three what we call nested ESXi 8 machines. We have a vCenter server and we have a
virtual science NAS device that we'll use for shared storage. What we're going to do now is just
create another virtual machine just for this demo. We're not going to keep it, so we can get rid of
it when we're done, that we're going to use to deploy ESXi 8 on. So, I'm going to create a new
VM, say create a new virtual machine. We're going to give it a name. I'm going to go ahead and call
this test deploy. We'll make it compatible with a guest OS. We're going to say other and for the
version we're going to say it is ESXi 8 or later, all right? And they're just saying here it's not
supported in production. This is a lab, a demo environment. So, for your lab, it's fine, but
obviously you're not going to do this in a production environment. All right, we're going to install it
onto this drive. Here's where we can customize our hardware for our CPU, right? So, we're fine with
having, you know, one core per socket. We've got two sockets. We don't have to enable hot add.
We're not going to be hot adding that kind of stuff like that. We're not going to set any
reservations or limits, but we do want to, because we are doing a nested ESXi environment, we want to
expose the hardware-assisted virtualization. This will be important in order to get this OS to
install successfully. Now, technically with this, because I'm checking this box, I can have my
physical ESXi host. I can create this virtual ESXi host and then create VMs inside of that, all right?
So, this box here is important to select when you're doing your lab environment,
recreating a demo or create a lab environment. For your RAM, we're going to do simple 8 gigs of RAM.
Hard disk drive, 40 gigs will be fine. We could, you know, set up to more if you wanted to have
additional space for logs and things like that. We're going to go ahead and accept all these
default settings. The only thing I need to do is connect to my ISO. So, I'm going to go to my data
store here and VMware images. And here is my VMware actual hypervisor. This is the vCenter,
if I wanted to create a vCenter server, this is to create my ESXi host. I'm going to select that.
Say next, I can review the options I've selected. And I'm going to say finish.
And it's going through creating my VM.
And it has successfully created my virtual machine. So, I'm going to go ahead and click
on my test deploy here because I want to start that up. And I want to go to console.
And here we go. Perfect.
So, here is what I've gone through. I hit enter to start the installation.
It's copying over files from the ISO. That's the need to load the installer.
This usually goes relatively quickly.
Now, it's actually, again, it's loading up the installer for ESXi.
In just a moment, it will come to the wizard. It will ask us a couple of questions about
installing, what options for installing ESXi. It will ask us to configure our root passwords
and things like that. You can see it's loading the VMware tools for this virtual machine here.
All right. So, now it's loaded the installation wizard. And basically, it's just showing us this
is the installation installer for version 8.0.2. And we just go ahead and hit enter if we want to
continue. So, I'll hit enter. Now, we need to accept the license agreement. And to accept the
license agreement, we're going to hit F11. If we don't want to accept it and not install ESXi,
we can hit escape and it will take us out of the installation wizard. I'll hit F11 to accept.
Now, it's going through looking for the devices that are on here. Basically, it wants to know
where can we install. It found that hard disk drive, that virtual disk we created that was
40 gigabytes when we created the VM. I'm going to go ahead and hit enter to choose that.
We'll go and accept the default US keyboard. Now, a root password. Let's go ahead and type
in my root password here. So, here it's just telling us that the CPUs on this host are not
technically supported by 8. All the features of 8 will be supported on the CPUs on this host.
But we can go ahead and continue anyway. So, I'm just going to hit enter to continue.
And are you sure you want to force installation? Yes, it's forced installation. Hit enter again.
And hit F11 to install.
Then go through the installation process. This will take a few minutes.
We went through the installation. The installation is completed. Now, it's going to ask you to
remove the media and we're going to go ahead and reboot the server. So, I'm just going to
go ahead and hit enter to reboot. And now we're loading ESXi.
I'm going to go ahead and change it open into a tab just because that way it can usually get
easier to see the whole screen. Now we see everything. We see the progress bar at the
bottom. All right. So, now here we can say we want to go in and customize the system,
look at the system logs, right, things like review logs, or we can do F12 to shut down.
I'm going to go ahead and say go to F2 so we can customize this installation. By customized,
what we're mainly talking about is going in and, you know, assigning the IP address and stuff.
Password.
So, here, if you wanted to go in there and change the password, we could go in here and say we want
to change that password. I'm not going to. I'm going to leave that alone. So, I hit escape.
I can go and configure the management network. So, if I had multiple adapters, I could go in
there and, you know, view the adapters I have on here and choose which one I wanted to be
the adapter for my first VM kernel port. But we have that already selected. We're good there.
So, I'll say okay. If we were using a VLAN for our management network, which in a production
environment, most of the time you will have a management network that you'll have your ESXi
host, you know, management VM kernel port on, and you'd want to go in here and set the VLAN ID for
that network. And we can set an IPv4 address. Now, here, you'll see I already have an address.
You'll see I already have an address on there because DHCP gave me an address. I could also
say I want to set that address statically and go in there and set all these options on there.
All right. So, for the sake of this right now, normally in production, I absolutely would go in
there and say set it static and statically assign an IP address. Just for this quick little demo,
I'm going to go ahead and leave it at that dynamic DHCP address. I'm just going to go
ahead and make a quick note of the IP we got so I don't forget it. It is 10.23.81.58. All right.
So, now I won't forget that. I have a note. I'm going to go ahead and I would go normally,
I would say set it statically. I would make those changes. I could enter for okay,
but I'm going to leave it at DHCP and say enter for okay there. I could go in there and set my DNS
servers. If I set my IPv4 address statically, I'd probably go in there and do my DNS settings
statically. Again, what's my primary DNS? What's my secondary DNS? Whatever name I want to assign to
it. And if I want to do a custom DNS suffix like, you know, company.com or something like that.
I'm going to hit escape here. Then once I've gone in and I have selected my adapter,
I configured the VLAN I want that adapter to be working, that VM kernel port to work on.
I set my IP address, my DNS, all that kind of stuff. I can go in there and say I want to test
my management network and just say, can we ping our gateway? Can we ping our DNS server? That
name resolution, that's going to fail. It's not going to be able to resolve.
Oh, it worked there. Must be registered somewhere already. I didn't realize that was.
If you completely jack up the configuration of your host, either here or through, you know,
the web interface or in vCenter, and this host becomes unreachable and you need to kind of start
all over again, you can go to network restore options and you can tell it just to restore it
back to the default, the way it was when you first installed it, and it'll go back to DHCP
and all that and you can start over again. You can also tell it to restart your management
network. If for some reason you think some settings aren't working properly or you just
need to restart without rebooting the whole entire host, just the management network,
you can have that option there. But basically, we've got that configured, so now we can see
if we can connect to the host and I have the connection here and I can log into it.
I'll log in as root and that password I configured.
All right. Here's my first time connecting to a ESXi host that I just installed fresh.
We can say if you want to join the customer experience to help, you know, improvement
program. I don't really have any storage configured other than my local disk that was on here,
right? So, I don't have any data stores, you know, from the, you know, storage array or something
like that. I don't have virtual machines. My networking is very basic. I have the default
VM network that I get my, you know, by installing the host. I have my management network just for
that first VM kernel port. But this is what a generic default installation looks like,
all right? Again, this is just for the demo for you to see what an installation looks like. We're
going to delete this. We have other hosts we'll be doing the rest of our demos with.
But now you know how to create a nested VM, how to install ESXi on it, how to configure
the network settings for ESXi, and then how to access it for management, for further management.