That we create a machine we need to give IT resources in order to run our Sebille memory story and all
other parts of our computer.
That an operating system relies on and to give the resources to our guest machine.
We need to bake or otherwise designate resources on the host your whole system has one or more Scipio's
on processors that take care of running software and doing the math that makes almost everything on
the system work.
But we create a virtual machine we need to tell what toolbox home and the processor the guest operating
system has to do.
This does not need to exactly match what the whole system has.
In fact it's usually a good idea to give the guest fewer places than the host has.
Telling a guest that it has set the number up to secert does roadblock or persists from the rest of
the system.
The virtual box that we're scared of sending commands from the guest to the processor as they need to
be executed on an older horse that don't support what Tula's Ishan box will Mullett possessor.
Instead it will appear to the first operating system that it has given amount of persisting resources.
Though that's not strictly strictly true.
It's really competing with the host and other guest for the time running instructions on the process.
Typically you can get by just fine with one processor but if you are a guest will be doing more combinational
interesting things you can add more processor.
If they are available
allocating memory to against them all the memory against CVS but the memory is not taken up all at once
on the host get started using them the host memory gets taken up.
And as things go out of memory on our guest the host of memory is released as well.
So the number that we set for the memory I guess to the present the large amount of memory that it can
take on the host most of the time guest needs storage in order to install them running the system or
work with data you really it will create a virtual hard drive.
As a file on the host and for that we have two options.
Two options.
We can create a dynamic image on a fixed image file both title file provides a hard disk Unforgiven
size to a great guest operating system.
And the difference lies in hold the file is managed on the host or that image only takes up space on
the host as data is added to it and a fixed image file takes all of the space for the guest hard drive
right from the beginning.
Reading and writing data from the fix we need is a little bit faster.
But to fix the image takes up a lot of space but it helps you to
conserve space on the host.
It does not take up tens or hundreds of gigabyte to store a mostly empty guest hard drive for networking.
Video Audio and chipset virtual boss creates a series of emulated devices devices which looks to the
guest as though they are real devices but which in reality are virtual.
What you want takes the information sent to these little devices and translates it to the host computer.
Real hard.
How did the devices are pretty generic and most of us just don't have built in support for them.
Usually we don't need special drivers or anything to get them working on a common labelling system.
As you will see later on.
A big exception here is the video device.
The vulnerable toolbar use a very generic device and many object system like a fallback or the lowest
common denominator.
So we need to install a driver with a guest and the Shanes in order to get a better experience.
More reservation's options and so on.
I look at the resources between the host and Gerster machine.
Is all these are Bello's you need to make sure you give your guests enough resources but not at the
expense of the host usability or stability.
Taking too much processor time are limited and can slow down the host to the point of load running very
well and piggin too much disk space can cause problem when the host needs to see files.
Two days.