please go to the line the computer guy dot com in order to view schematics, code and Maur for the projects that you are learning about.
So today's video I'm going to give you a brief overview of virtual box in order to be able to do clinics.
Labs in a virtual environment.
The nice thing about virtual boxes This is a piece of a virtualization software that allows you to install a full operating system into an instance on your desktop or laptop computer.
So you have your desktop or laptop computer and has Windows or Mac or limits or whatever else you install Virtual box on onto that, as you're saying, normal piece of software and then within that you can create instances of other operating systems.
So these air full fledged installations of these operating systems, and you were able to interact with them as if they are normal computers so you can change network configurations.
You can change configuration files.
If you're dealing with Windows Server something like that, you've been set up full active directory infrastructure.
Basically these air, full fledged servers or computers.
They're simply a virtual instances sitting within a virtual box.
Now the reason that we're going to be using virtual boxes because it is open source and free for everything again, Whenever we talk about open source, when the big important things is, make sure you know what the hell you're talking about.
So the nice part with virtual box eyes, it is open source, and it is free for enterprise use education to use any kind of use out there.
The other thing that I like about it is that it runs basically all the operating systems that you folks will be using.
So it runs on Windows.
It runs on Mac is which was, But I'll be using it on it runs on Lennox.
And if anybody out there still using it and even runs on Solaris.
So, yeah, you couple of people out there that feel left out because you're running Solaris machines.
Hey, you can run or virtual box, too, so that's a nice part about it.
Anybody can go out there and use it.
You just download it in stolen and where you can go again, even in the enterprise environment.
So if you set something up and you really like it and you don't have to go over to a different product you could just continue to use for a jewel box.
So those were some of the things I don't like.
One of things that you have to be thinking about if you're going to be using virtual box is make sure you have a machine with decent resource.
Is so decent hardware, I would argue at least eight gigs of RAM out argue.
A solid state drive, I would argue relatively fast process or the reason being is, Remember, right, we're going to have operating systems on an operating system.
So now what's going to happen because you're gonna have your host operates is the Windows Lennox Mac.
Whatever else it's we're coming to require RAM, it's going to require hard drive.
It's gonna require CPU cycles.
Then we're going to spin up.
Basically, we're going to turn on instances of operating systems, and now those instances of operating systems will require RAM will require hard drive will require CPO, so just kind of keep this in mind again.
I would say you know that that eight gigs of RAM, a solid state drive that's a that's a good minimum.
Theoretically, you could do less.
I don't know.
Maybe you could do six gigs of Ram and 5400 rpm drive.
If you really wanted.
Just realize your performance.
Your performance is definitely going.
Be lacking the worst of the worst hardware you have.
So just kind of keep this in mind if you're going to be dealing with workable box or really any kind of virtualization software, remember, the hardware still matters.
And so if you do virtualization on crappy hardware, you're gonna get crappy kind of flaky results.
So anyways, let's go over the computer.
I'll show you where you can download of our toolbox from.
Then I'll take you through and show you some of their configuration panels and all that to give you an idea of how virtual box works and how you will be setting up a virtual bounce for your Lennox labs.
So here we are at virtual box dot or we're gonna go to virtual box dot or and if we want to be able to download and install a virtual box, we simply click on this big green button from there.
If they've been come here, we look for the platform packages and we can download for Windows hosts we can download for OS X host we can do for Lennox distributions.
And of course, we could do for Solaris if we're using Solaris for whatever reason.
Now again, I'm using a Mac book pro in order to do these demonstrations.
But more or less everything should be to say I really don't think there will be any differences once you've downloaded this you didn't install Virtual box is a very simple installation procedure.
I don't see any reason for me to show you how to do it.
So you then install it once it's installed.
Then you can open it up when you open up virtual box.
Basically, this is what you'll be looking at on Lee for you.
You won't initially see this u boat to service.
I've created a virtual machine for a bunch of server over here will be completely blank.
Now, when you first open up a virtual box for the first time, it may ask you to create a virtual machine s so we can just go through the creating a virtual machine process right now what you do, if you're going to create a virtual machine.
So if you're going to create a new bunch of server, whatever else you go over here to this weird blue starry type button, we click on that for a new, and we can start creating a virtual machine.
So test for class.
So basically the first thing you do is you name your virtual machine, whatever the hell your name or virtual machine.
This is basically for you to be clear, This is not the host name of the virtual machine.
This is what's gonna show up over here in the left hand side so you can name it whatever weird ass, name one.
You're not gonna have to plug that into, uh, into, you know, Network may mean or anything like that past that.
We're gonna go down here to the machine folder.
So where is the virtual machine?
Basically, the virtual hard drive going be stored.
All of this is going to be stored in a single file.
Eso Where's that file going to be stored?
And so it gives a default location.
The next thing is, then what kind of operating system do we have?
So the type of operating system is it Windows, Lennox, Solaris, BSD.
Whatever else we, of course, are using Lennox.
And then what kind of Lennox you have all these different.
Lennox is here, and so for us we will go down to about 2 64 now, Theoretically, you don't have to be specific on this, I suppose acquitted on Windows and then install Lennox.
But it's like all things, the more specific you could be, probably the better on.
Then, from there, all we're going to do is click on the continue.
The next thing that we're gonna be looking at is the memory.
This is the ram size.
You have to think about how much Ram your host computer has.
So my host has 16 gigs of Ram.
And then you have think about how much Ram you want to give to the virtual machine that you're gonna be creating now.
One of the funny things when the funny things in life is back when this virtual box is being created.
So one gig of Ram, That's what that's 1024 minutes is a gig.
One gig around was a hell of a lot of ran back in the day back 10 years ago, a gig of Ram was like, what?
How big around?
Um, here's here's one of the times, though.
You don't want to leave it a default like seriously, don't leave.
It is evil.
So if you're doing move on to server, if you're doing a Lennox distribution with no desktop environment so bummed to server, you know what, something like that sent OS, then 1000 24 might be okay for you.
But realize realize if you're using something with a modern desktop environment, 1024 is not gonna work literally.
Your virtual machine is gonna crash.
Bun to requires at least two gigs of RAM with the with the desktop environment.
So this is one of those times doing that.
Leave the default.
If you leave the default and you're installing a Lennox distribution with a desktop environment, you will run into problems.
So minimum is two gigs you can do to gigs.
I would say, if you if you have the extra, I would go up to three gigs that just gives you a little bit of what your wiggle will room do realize you can change this in the future.
So most these configurations that we're setting you can canvass in the future so you can start at three gigs.
If three gigs ends up being too much, you can set it down to two gigs.
But I would say Doom or first, because remember, you won't actually have to actually ingest only operate system into this instance.
So I would prefer to have Maur Ram to begin with and then realize I don't need as much versus not having enough ram and then having my installation process crash because there's not enough RAM.
So I put it to like, three gigs to begin with, and then later I'll show you how you can go back came to that they were going to go to continue from here.
It's asking about the virtual hard dressed in this.
The VD I do not add a virtual hard disk is an option.
Not really sure why you would do that?
I guess maybe if you're just setting up a placeholder, that's a possibility.
Use an existing virtual hardest.
So remember, with these virtual discs like this VD I this is a file.
The great thing about virtualization is that you can literally take the entire work school computer, copy it to a USB flash drive and just move it somewhere else.
So let's say I was doing that.
Let's say I created a virtual machine here.
I was doing all experimentation.
I was playing.
I set everything up.
I got I got exactly where I wanted.
Then I could copy it to a to a flash drive.
Take it to wherever I want to actually run it into a theoretical production environment on.
And then I could use that virtual hard drive, basically creating this process.
So that's one thing you could do.
What we're gonna do here is create a virtual hardness now, So this is a brand new instance.
This is a brand new operating system, so creative work your hardest on look like this, and then we'll create.
Then it says, What kind of a hard disk final type you want VD I V a.
T d or be in decay?
I would argue.
Just leave it at VD.
I this point, if you don't know the difference between these Leavitt of Edie, I will deal with the other ones later you go to continue then The next thing that's going to be asked is a storage on physical hard disk.
Do you want to be dynamically allocated or fixed size?
What this means is, if you say fixed size, if you say fixed size and you give the hard disk, let's say 20 gigs of storage, then it'll automatically allocate 20 gigs of the hard drive to this virtual machine.
So whether you have one file on it or you Philip, the 20 gigs all 20 gigs will be used.
If you don't do dynamically allocated, this is pretty cool.
What you could do is you can say what the max size you want it to be.
So what you can say is, I want this hard disk to be up to 30 gigs in size, and then it will grow to 30 gigs and socks on DSO.
That's a way that that you can set how big you wanted to grow, too, so it won't grow any bigger than that.
But until it gets to that point, it won't take up much space.
So if you give it dynamic, you said it to 30 then it takes five and then it grows and it goes a six and it goes a seven.
Then go 89 10 11 12.
So this is something I think about one of the reasons why you might want to go with fixed sizes.
Let's say you're running multiple virtual machines on this computer and you want to make sure that they don't all grow and then end up crashing the system, right?
So So let's say you had Let's say you had I don't know the hard drive with 100 gigs of storage space on it.
And so you you made them made dynamic hard drives.
And you said you let's say, Put three instances on your system and you put them all to a dynamic hard drive of up to 50 gigs and sighs.
Well, if you have three, theoretically, the max is 100 and 50 gigs, but you don't think you'll actually use 150 gigs, and so they're all slowly growing.
What happens of a log file gets turned on or something stupid happens, and all your different virtual machines keep growing, and then they grow outside the max amount of space that your host machine has available.
Then that could possibly crash the host machine and cause all kinds of problems.
So what you might do is you want to say, Hey, I don't wanna have any surprises in the future, so I will make sure it's all fixed.
I know I've got 100 gigs of storage space, so I'll make each one of these virtual machines.
I'll give them 33 gigs of fixed allocation, so I know exactly what I'm dealing with.
So this is kind of one of those things to be thinking about in general.
If you have a single machine again, you're doing basic lab tests with Lennox or anything else I would set it to dynamic, but something to be thinking about their.
Then we click on Continue, and then we say, What size do we walked?
The hard drive.
Now again, the important thing is to look at the requirements of the requirements so again, and they default to take gigs, cause back when they're creating these defaults, take gigs with huge galley 10 gigs.
I think the exact little big anymore, uh, move onto a bun to desktop.
Minimus asks for a minimum of 20 gigs at this point so again you can run into problems if you're trying to insult the operating system or do something else.
If they say the requirement is 20 gigs and you leave it at the default of 10 you can run into issues.
So you can simply just type in 30 gigs here, whatever else, you can change us in the future.
When I would argue, said it to a reasonable number 30 or 40 gigs, see how that goes, and then you can shrink it later.
Uh, then we're going to do create.
And okay, so now we have the virtual machine.
A test for class.
Now we're gonna go.
We can take a look at settings so we can change things.
Here s we look here, guy General, we have the name so theoretically can get here.
We have the type Lennox and move on to we can go to advanced.
We can see so some other things here, like shared a clipboard somebody think about, Especially if you're using a desktop operating system within the virtual machine.
What this means is, do you want to share between the host machine and the virtual machine description?
If you wantto disc encryption.
Theoretically, we could go, go over, take a look at the system.
So again, based memory.
So we can change that.
Here we have a boot.
Or so we have a floppy drive.
We have an optical drive.
We're gonna have a hard disk so we can add these or subtract thes if we want Chipset.
Doesn't really matter.
Pointing device doesn't really matter.
Some other information.
Here, go take a look at the processor.
So we can say how many cores do we want to give over to the virtual machine?
I would argue.
Just leave it at one.
And then execution cap.
Basically, how much of the CPU do you want the virtual machine to be able to use?
And it said all the way up the 100%.
I might be a little careful, but with this I may change this.
So if you're running into problems of your virtual machine is using a lot of CPU, I might come here and tweak that, uh, we could go over, take a look at display.
This is basic stuff.
How much been video memory do you want to use with the monitor account?
Is that kind of thing.
There's some remote displays and recording things here.
We won't go into that today, But you may want to again, depending on how you know you're running a desktop operating system within the virtual machine.
How you know how much graphics power you want to give that desktop the virtual machine.
You can change that here.
Then we can go to story store in here, then gives you your I.
D e controllers, your virtual i D e.
Controller, and then this is your controller for your safe.
So this is essentially your hard drive so that your test for class not beady eye.
This is your your virtual hard drive.
We go here, we can see the size.
So the virtual sizes.
Since I haven't set two dynamic allocation, it's only currently using to Meg's right.
Since I haven't insulted operating system, I haven't done anything yet.
It's only using to Meg's out of a theoretical 30 that 30 gigs.
It could use location, it says, where the location is attached to blah, blah, blah.
You can say whether it's a solid state drive or plug blow or other things.
I wanna worry about that.
The one thing that I would take a look at the Oh, this is what's gonna be important for when you install an operating system that will show you this what we actually do in a operating system installation.
But one of things you're going to do in order to install an operating system into the political machine is you're going to have to have an I S O phile.
So the I S O file is the disk image file that you use in order to install operating systems.
And so what you can do is you go here basically, So you goto I d controller.
You go to empty, and then what you can do, we go to choose virtual optical disk file, and what I've done is in downloads I've downloaded.
This is the desktop.
I s O for a bond to a 00.4 And this is the server.
I s O for a buck Thio, 18.4 So if I was going to be in Stone Lane, a operating system right now, I would select one of these.
I would do open.
And so now that I S O file is now connected to that control.
Or so when I boot wth E.
When I turn on this particular virtual machine, it will then boot into that installation routine so that this is where if you're sitting there, hell, I How did how do I How do I actually install the operating system?
You have to come here to storage.
You go to controller than you click that little circle thing there and then go from there.
We have audio is audio if you won't want to enable audio if you want to enable output for input.
You could do that here.
Uh, then we go to networking so you get a multiple adapter, especially since you're since you might be dealing with servers and they would do something fancy with network adapters.
We're not gonna do anything too fancy here.
Main thing we need to do is we need to enable the networking after it is is not enabled.
Then you don't gotta Nick.
If you don't got a Nick, you don't got the network.
So you have to enable at least one of these network adapters.
I would argue enable number one so it's easy to find, and then you have attached to this kind of interesting.
So you actually have multiple different options here for networking.
So what Nat does that does is basically that allows your virtual machine to simply go out to the Internet, go out to the network through your computer with the least amount of problems.
You have other options.
Here we may talk about a few.
Sure, that network of bricks did after internal Network host on Lee adapter.
And so these air some interesting things that you could do with a networking configuration based off of what kind of lab environment you're trying to create.
Basically, are you trying to create a server that can actually be access from the Internet from the outside world?
Are you trying to create some kind of internal network lets?
Let's say you're gonna create some kind of internal lab network where different machines were talking to other machines.
There's all kinds of things that you can d'oh basically right now, just leave it at that.
So if you leave it in that this will allow your virtual machine to go out to the Internet, will be able to download up light dates will be able to access the Internet through Web browsers, it will be able to do, like 99% of the things that you need to D'oh.
So at this point in time, I would highly suggest you leave it a nap.
If you if you go to anything else like these, these these are These are other valid options, but they get confused, they cause problems.
Then pass that when you go to ports, whether you want to enable serial ports if you have serial port.
So if you want to enable the USB controller, you can do that here.
Shared folders so you can actually share folders between the host operating system and the virtual machine that you're creating.
So you could do that there on.
And then you have this little inter user interface thing.
So you see these little these little button, the things here, uh, these will show up at the bottom of the screen when you turn on your virtual machine and so you can add those or subtract those if you want, so that will hit.
Okay, all of that gets saved.
And then let's say for the test for class, what we can do is we can simply double click that that will turn that on.
We see virtual box 6.0, and since since I connected that I s so you can see it's now trying to boot into the installation routine for for a bun, too.
You will see this stuff up here.
A mouse pointer integration.
So the virtual machine reports of the guest os support mouse point integration.
What mouse pointer integration means This is so nice is the fact that I can go from here out to the host operating system and back.
Look at that.
Isn't that cool?
You're probably thinking like What the hell?
Well, the thing is is back in the day.
See down here at the bottom, see how it says all the way at the bottom here, says left and has that little whatever clover thing it used to be.
Where if I if I moved my mouse into the virtual machine area, it would capture of the mouse and the only way to get my mouth back if I was going to try to interact with the host operating system was to oppress the left clover on DSO.
What's nice now is that the mouse pointer integration.
What this does is it means I can go from the host into into the the virtual machine and then back out again at will.
So that's one of things that's nice here.
I'll just close this.
You can see this when you close you and shaped save the machine state.
So if it's in a state that you like, you could save it.
You could send the power down signal if you want, or you just power off and you click okay on from that, that's really at the basics of virtual box.
You can check for updates and things you can go to preferences.
There's some preferences here.
Get a general so default machine folder.
So if you want to change the machine folder where things go, you can't get out here.
You input so different shortcuts.
Different hot keys.
You can do that here.
Update you want to check for updates?
Obviously, if you want to language, something about the displays allows you to deal with displays a little bit network.
This is for those network options that I was showing you.
One of things you can do is you can create internal networks, and this is than that network.
We won't deal with that.
They're extensions if you want to deal with those and proxies.
So if you want to send network traffic through proxies, you can set that up here.
Most of this here you probably won't mess with until you get more advanced.
The only thing that you genuinely may want to change is simply that default machine for her location.
It would just wantto basically put all the virtual machines somewhere else.
You could change that here, but that's basically what we'll be looking at when we're dealing with virtual box and when we're going to be creating instances of Lennox operating systems, and we're going to be dealing with them in the lab environment.
So that's a brief overview of or tool box.
We're going to be using this a lot in our Lennox Labs because again it's open source.
It's free and runs on Windows and Lennox and Mac and Solaris.
If you guys hilarious, it does run on that, um, and it works Well, this is this is one of those products has been out for a long time.
I've been using it for a decade.
I'm not sure when it came out before that, but it's been around for a long time.
It's good, easy.
Everybody knows how to use it s o.
We'll be using it for our projects.
Do realize again with virtualization software There is other virtualization software out there if you want to use it things like products from from VM where that type of thing we'll just be using this because again, it's kind of like one of standard deals when you're going to be using virtual box.
There's not too many Gosh is the only really stupid guys.
You really still we got Is that all how to connect in high us for O phile, you would think if you think you think they'll make that just a tiny bit easier.
But again, you got a storage and you go to the controller, then you go to that circular thing, then used to like the guy s O phile.
You want to be able to boot off in order to solve the operating system, and you go from there.
That's the only that's the only thing wrong with virtual box, he said.
They go, That was That's a piss Poor design.
That is like a shockingly horrible design.
Other than that, the important thing to remember is when you're gonna be creating your virtual machines is for the hardware resource is don't leave them at the default again.
A gig of RAM on any kind of Lennox operating system with a desktop environment is not gonna work.
It's just again, I say, If you're using gnome three or unity or anything else, you're gonna need at least two gigs of RAM.
So do make sure go take a look at the software requirements for whatever operates is and you're gonna be installing and then make sure you have that much ram.
The same is true it with the hard drive space again.
Take gigs of hard drive space.
10 years ago, that was a lot Aren't dry straits.
It's not a lot of hard drive space anymore, So go take a look and decide how much hard drive space you want to give it again.
Do you want to give it 30 gigs?
The other interesting thing that you may want to play with going into the future is the network configurations again that in that network, the hosted.
After all those things, those are very interesting to play with.
If you want to star again, messing around with networking, having multiple workable machines communicate with each other, having the virtual machines be able to communicate with the host machine on the outside world being to communicate with the internal virtual machines.
That is where you would go and you would change those network configurations again.
But if you don't know what the hell you're doing, you're gonna break everything and it's not gonna work.
So so to begin with, to begin with, just leave it with that.
Just leave it with that and go from there when you're comfortable.
When you're comfortable with Lennox and you're comfortable with that configuration, then you can go and try to futz around with the other things.
But it is important to understand, like if you're going to be creating multiple Lennox or other virtual machines within the host operating system, and then you want them to be able to communicate with each other, you will go to that network setting, and then you would change for what's appropriate.
There's a help thing that will tell you which what every single one does.
So you ago, you pick the right option and then go from there.
So did that.
That is also one of those places where you really do need to know what you're what you were trying to accomplish and then pick the right option and then also realize it could be a little bit quirky again.
Even if you look at the hell pages.
Even if you look at the the explanation, there's a whole bunch of asterisks.
This works on this but does not work on this and does not so just realized once you start messing with that, that might that might end up being a little bit more trouble shooting a bit more playing around than you may be expecting.
So anyways, that's really just an overview of vertical bucks.
I would say downloaded, install it, start playing around with it.