Welcome to cyber ery. I'm Dean Camp you, Leo. And this is lesson one for module three
installation, configuration and management course.
All right, so we're talking about a lot of different concepts for virtual machines.
We'll be describing the different components that are available through virtual hardware
and looking at the different files and how the hardware actually works.
if you look at our virtual machine files, they have a lot of different things here.
Once you build a virtual machine, typically all the files are created in one folder. This makes managing virtual machines very easy. Actually,
you can just copy the folder as needed
to move it around. Or thio using a different system
much different than dealing with a physical machine, where you have to copy
hundreds, maybe even thousands of folders
and different foul systems to replicate that machines function somewhere else
but the virtual environment. We just have one folder
within that folder. We have several pieces. Your configuration file.
We'll have a dot BMX extension.
So whatever the name of your V m. Is,
you know, for instance, of'em one,
I am one of the M X would be your configuration file.
And just like a physical
server where you have swap files
to deal with memory problems, you have the same thing in the B M world,
so we would see the M one dot V S w p for virtual swap.
There's also a BIOS file,
and we know that bio settings let you control different aspects of other machine boots. It's some of its hardware capabilities and so on.
Then we have a log file.
So be aware. Got log
would be in the same folder as B. M one.
If the BM one was created from a template
or if you had a template to create this particular VM,
you might have a file vm one dot b m t X.
This would probably be in a different location than some of the other VM files that pertain to this particular VM.
in such a way so that your templates are kept separate so they don't become confused with the actual BM configuration files.
In an upcoming lab. We'll see how we can use a raw device mapping. That's what the R. D. M stands for here.
So if I had a raw device mapped
for VM one, I would see VM one are vehement. Dash RTM dot virtual machine disk file
Your disk descriptor is dot b m d k.
So the M one doubt the M v k.
The descriptor file contains sort of the metadata for the virtual desk.
How many cylinders? How many heads and some of the other characteristics. It doesn't contain the actual data.
This is a little bit of a point of confusion.
For instance, if you browse a data store
from within V center
and you see the doc BND k file,
it will actually appear to be the data file.
It'll, for instance, if you're just was three gigabytes
the dot b m one of the M d K would be three gigabytes,
but truly the actual data is in the VM one dash flat,
If you go into your host
or the day of store from the command line and look in the folder, all these files are you would see that this is the one that's actually three gigabytes, so it's a little bit confusing
if you're just browsing a day of store food from within the center. It will always be the dot PM decay that has the data.
It's just a pointer to it
s o. If you're comparing those two situations, that's that's what to be aware of their
for instance, by hitting the pause button,
we're effectively stopping it from processing.
You'll get a dot B m ss file created with, of course your name.
If I take a snapshot,
will be in dock B. M s de
allow. These are pretty self explanatory is far the name of the extension.
The state of the snapshot is a V m s n
Soviet snapshot state
is your bm name Dash Delta got the m d. K.
You might be wondering what snapshots are will cover that
So I mentioned browsing a data store. You'll see this,
and you will be something that you'll be doing regularly. When you're managing virtual environments,
I can connect to a virtual machine
and see what data store it's. It's files are located on.
I can also connect to a host and see what data stores are attached to that host,
and then you simply right click on one of the data stores, and you can browse it.
And once you're browsing of data story could do things like uploading files, downloading files, creating folders. It works a lot like Windows Explorer.
There's also a tab, which you'll see once you get connected to be center. That lets you look at your storage views,
and this lets you see
your storage in a different context
on. We'll even see some other options later in the course where you can draw maps or the the the center will draw a map for you, showing what the host is connected to us. Faras networks storage other hosts on and so on.
as us also see in the next lab, when you right click out of'em in the inventory, you could open a console,
and that's sort of what I did in the in the little video you saw where I demonstrated the features of the D. C. Why
so being able to open a council directly from the virtual machine in the inventory is a nice future?
You can, of course, use something like remote desktop if you wish,
so you can connect to a virtual machine the same way you would connect any other Windows
system, whether it's a workstation or server.
But the council is nice because it's more portable, and you can have many of them open at the same time.
Okay, we onto our virtual machine hardware.
We have a lot of different things to consider here,
starting off with the basics keyboard and mouse.
So the virtual machine hardware or the virtual hardware, if you will,
allows you to interact with physical devices and then virtual eyes is the commands of the instructions you're giving so that the virtual machine itself can take action.
So I used my physical keyboard. The virtual harbor translates to keep presses so that the VM can get those commands.
I can have an I D controller hooked up to mine.
It could be on my physical host,
and then the virtual hardware will translate those instructions so the virtual machine can use an I D device.
I could also have up to 10 different
network interface cards,
and the different types of interface cards have some interesting characteristics. For instance, V. Lance
is one of your choices. This is has a lot of compatibility for 32 bit operating systems.
Quite often, you want to pick the mxnet
for performance reasons.
This is not compatible with every operating system, but should be compatible with most Windows and Linux flavors that you might come across.
Then there's also the 1000 or E 1000 e,
which gives high performance for network cards.
But again, there are some compatibility considerations to take to take into account.
And then, if you use ah, be mxnet to RV mxnet three as your interface your network interface cards, you must have the, um where tools installed.
And that's something that
we'll talk about a little bit later as well.
In a nutshell. Veum, where Tools is a collection of utilities that gives your virtual machine better performance, especially as it relates to moving the mouse
and, uh, and other graphics options.
It also supports things like snapshots, which will get into a little bit later.
All right, so 10 10 network cards pretty pretty generous there.
I could also utilize a three D graphics card. So, for instance, if your host has an NVIDIA
you can utilize some of the three D functions and the hardware, too.
Thio give you better performance for your three D applications within the BM,
so that means that if you're doing
three D graphics or other kinds of maybe video editing that kind of thing,
on your host can be utilized from the virtual machine to give you a boost in performance.
The current version of Virtual Harmer supports up to one terabyte of RAM.
That's a tremendous amount of memory for a
for virtual machine to have all to itself. But it is possible
we can also use up to 64 Virtual CP use on one virtual machine
so you can imagine the possibilities. If you had a very powerful server
and you wanted to build some clusters, you could mix and match some of these capabilities to give you the performance characteristics you're looking for.
We can have up to four schedule controllers attached
each scuzzy controller. Typically, king service up to 16 devices,
so that's a lot of disk that you can attach to.
You can also have a floppy controller with two devices,
so if you had a need to use floppies and you're
your host had a floppy drive attached to have up to two of those, you could put a floppy into the drive and have it
get virtually attached to the virtual machine.
Same thing with USB devices. Up to 20 of those are possible.
I could have four serial ports,
so if you have cereal devices attached to your host, your virtual machines can attach to them, using the virtual hardware again to give them access.
Up to three parallel ports are also possible.
So if you've got things like plotters and printers,
uh, in serial parallel configuration, you should be able to use them from a virtual machine by just setting the parameters correctly when you go to at your settings within that b. M.
So regarding the storage, I mentioned being able to browse the data store.
These are some of the parameters that you would see in a typical data store,
if you would. If you look at it, we know that it's got a certain size in this case, four gigabytes.
Give it a unique name
such as my V M. F s.
And it's very trivial to rename a day the story. You just right click it and select rename from the drop down menu.
We can also pick the storage adapter.
There are several different choices here
para virtual one L s. I logic sass is another. We don't go into too much detail in this class about the different choices.
But much like the network cards, we can pick the adapter That gives us the best performance for the operating system that's running on that virtual machine.
We know that we have a disk file
of the VM named Avi Mdk. Remember, this is just the descriptor. This file,
the actual data is in the host one dash flat, not be MDK.
We know that the disk mode
will tell us, for instance, if snapshots are allowed,
if the disk is an independent mode or in persistent mode, that changes whether or not snapshots are possible.
If if you want to use your disk and non persistent mode, for instance,
you might have a V M that you want to do some testing with
and you might want to make changes.
And every time you use that B m, you want to be able to go back to the original configuration it had when you boot it up.
In that case, you use non persistent disc
that we know the changes are written to the desk.
If you's a persistent disk now, the changes are written directly
to the to the disk storage media the same way that would be for a typical physical server,
Onley allowed in the case of Of, uh, using the persistent mode.
And then we have this provisioning, which will cover in a later section.
the provisioning mode was thin
and thin. Provisioning means that
if I've got a four gigabyte disk,
if I deploy it and thin provisioning mode it creates a distance
descriptor file. It creates a little bit of data in the file.
But if I were to go to browse the data store, I would see that that the provision size of before gigabytes but the actual size on the disk would be very small. It might just be a couple 100 kilobytes.
Thin provisioning is very quick.
That means that if I develop or if I deploy a V m the storage
virtual diskettes created,
but it only grows as needed and we'll cover some of the other options, like thick provisioning lazy zero Think provisioning, eager zeroed.
So at this point, you should be able to describe the files that comprise your BM.
We have, ah, look at the different types of hardware
that are available to A B M through the virtual hardware
And then we explored some of the more detailed parameters forgiven Data store.
So that is the end of
Lesson one for Module three.