Okay, so I've got my virtual machine hardware chosen for my guest operating system. I have choices here. Got a lot of options
from Microsoft Windows. Everything from server 2012
anti three, that one.
And Windows 95. So you can support some legacy
operating systems if you need to.
Underneath the lyrics choices
we have quite a bit to choose from. Here is well, we have red hat, Soucy Center, west Debian,
even Oracle Boom two and some generic colonels
We have Mac os, FreeBSD,
Anyways, we're gonna go back to Windows. We're gonna build a window 7 p.m.
We'll take the default for the number of virtual sockets and course per socket.
We don't have a lot of processing requirements for this P M. So we'll leave these
And that is a point worth bringing up
the big difference between physical building physical hosts and building a virtual host.
When we build a virtual host, we can start off with much lower,
uh, hardware provisions.
And as you use the virtual machine, you may decide to ADM or processor
or more memory at a later date,
so you have a lot of a lot more flexibility. We don't have to,
you know, power something down. Open up the rack,
get out the screwdrivers and mess with cables and such.
We could do all of this directly from
the Edit Settings page of the virtual machine itself.
Okay, we'll go ahead and click. Next
memory size will bump that up a little bit, too. Three gigabytes to gig is his bare minimum for Windows seven. Symbol will give it three
notice. You can enter this in megabytes or gigabytes. You can use the arrows or type the value in directly to the window.
We can also designate Hominy
virtual network cards we'd like
we're only going to use one, but we could support up to four,
and then we have the virtual Machine
network that gets built by default. Of'em Network. We'll talk about that a little bit more later,
and we'll also pick the default setting for the adapter.
We've got V mxnet three as as another option,
with higher performance in a lot of cases, but we'll just stick with the defaults for now.
We want to make sure this is connected power on, so the network hard
gets connected to the virtual network.
We'll pick the default for the scuzzy controller.
We'll create a brand new virtual disc notice. We can use an existing disc
or even create Ah, VM without a disc,
we'll take the defaults here.
We don't need to just to be very large will say 10 gigabytes.
You could specify megabytes or terabyte Stephen,
And then we have our provisioning choice.
the default of thick, provisional lazy zeroed
this is one of two options. Where VM where
pre allocate all the storage? So if I pick a 10 gigabyte disk,
take up 10 gigabytes on my data store.
Whether or not it's lazy, zeroed or eager zeroed
uh, some of the performance characteristics wants. The disk is built.
gives you takes the longest to build the disc,
but it does give you better performance once the disk is actually available.
Ah, ladies, your boat is slightly less performance, and the changes the way that the disk space is allocated
the quickest option, the one that's used
pretty frequently is thin provisioning.
In this case, we just build the basic structure for the virtual hard disk.
It just takes a few kilobytes. Actually, it's just a
a day of structure on on the
within. Today a store.
In this case, the disc actually grows as data is written to it.
So that's why we get a quick provisioning. It just builds a container for the data, and then we fill it as we go, so we'll pick thin provisioning.
We'll pick the default
device node. This this is something we'll talk maybe about a little bit later in the class.
that we have some different modes for the desk
if we go into independent mode.
What this means now is that the disk
just like a traditional hard disk, where, if I make changes to the operating system
than the changes are written to the disc permanently,
we have a note here that independent discs are not affected by snapshots, so that is one thing to keep in mind.
You could also use non persistent mode.
This is very useful when you want to
make a machine that you want to use for testing or some other special purpose
for perhaps very virtual lab. If you were practicing some security techniques and so on
and non persistent mode, the data has not saved to the desk.
So that way, if if you make changes or you do something with that virtual machine
the next time you boot it up, it's just the same way it was when you built it originally.
So we're not gonna check either of those options. We'll go with the default settings here
when we get our summary, or we can review all of the settings.
We can see what the V M will be called. Win seven.
Uh, I know which host it's coming going to be hosted on
I know which data store it's going to use. I've designated what the guest Os will be.
My CPU is in memory network hard and so on.
Go ahead and finish. You'll notice if you if you caught that only took about two seconds to create this Viet, it's very quick
because all we're doing is creating the data structure
that we that we will then install the guest operating system into