WEBVTT 00:00:00.000 --> 00:00:04.400 Welcome back to VMware vSphere 8 in the real world. Now we're going to discuss some VM options. 00:00:07.280 --> 00:00:11.040 So in a previous lesson, we discussed how to create new virtual machines. So now we're going 00:00:11.040 --> 00:00:15.360 to dive a little deeper in some of the options that you have when you create a virtual machine. 00:00:15.360 --> 00:00:21.520 So you can change the VM options either when you're creating the VM or after the VM has already 00:00:21.520 --> 00:00:26.320 been deployed, you can go in and make changes. Some changes the VM would have to be powered off 00:00:26.320 --> 00:00:30.080 to make those changes. Other changes you can make while the VM is up and running. 00:00:30.719 --> 00:00:36.400 So for example, if you want to change the network, the port group that the virtual machine 00:00:36.400 --> 00:00:42.400 adapter is connected to, you can easily make that change while the VM is running. Other changes 00:00:42.400 --> 00:00:47.919 would depend upon the operating system. For example, are you able to hot add a CPU or hot 00:00:47.919 --> 00:00:52.480 add RAM while the virtual machine is running? That would be dependent upon the operating system 00:00:52.480 --> 00:00:55.840 that virtual machine is running. So you'd want to check with the vendor's documentation 00:00:55.840 --> 00:01:02.160 and see if that vendor supports adding CPU or adding RAM. Also, most of the time, if you choose 00:01:02.160 --> 00:01:07.680 correctly the operating system installed on the VM when you're creating that virtual machine, 00:01:07.680 --> 00:01:12.080 then those options are going to be already set. VMware is going to know, oh, this OS does support 00:01:12.080 --> 00:01:18.559 it, that one doesn't, and they won't let you try to add CPU to a VM that's running. If you're 00:01:18.559 --> 00:01:24.320 running, for example, Windows 2008 or something like that, some old version of Windows or some 00:01:24.320 --> 00:01:30.959 old version of Linux that doesn't support that feature, VMware won't let you choose that option. 00:01:30.959 --> 00:01:36.639 If you have upgraded the VM to a newer version of Windows that does support it and you didn't 00:01:36.639 --> 00:01:40.800 change the options of the VM, then VMware still won't let you because they don't realize you're 00:01:40.800 --> 00:01:45.440 adding or running the newer operating system. You can go in and make those changes, though, 00:01:45.440 --> 00:01:49.760 and change the OS options you've selected for the virtual machine. 00:01:50.400 --> 00:01:55.519 So this basically allows you to tune the VM based upon how you need it. You can add devices, 00:01:55.519 --> 00:02:00.400 you can remove devices. If you need another hard disk, you can go in and you can add a hard disk. 00:02:00.400 --> 00:02:06.400 You can increase the size of a VMDK, a hard disk file. You can add another network adapter 00:02:06.400 --> 00:02:12.320 to the machine if you need a second network adapter for some reason. So this basically 00:02:12.320 --> 00:02:15.919 affects how the VM is going to interact with the environment that it's in, right? How it's going to 00:02:15.919 --> 00:02:21.279 work with the host. Are you going to encrypt the VM or are you not encrypting the virtual machine? 00:02:21.279 --> 00:02:26.559 Do you want vMotion data to be encrypted? So basically, if you're trying to move the VM from 00:02:26.559 --> 00:02:31.839 one host to another host while the VM is running, one of the first things it does, it copies the RAM 00:02:31.839 --> 00:02:37.600 of that VM from the old host to the new host where it's going to land. And you want that copying of 00:02:37.600 --> 00:02:44.320 the memory to be encrypted. So you can have both the VM storage on the disk be encrypted as well as 00:02:44.320 --> 00:02:49.279 when you migrate the data over the network is encrypted or not. Power management, you know, 00:02:49.279 --> 00:02:54.240 how do you want the buttons when you go to, you know, put the VM to sleep or power it off, 00:02:54.240 --> 00:02:59.119 things like that. How do you want the buttons to respond? You have security options, boot options. 00:02:59.119 --> 00:03:03.919 You can specify when you power the VM, you want to go straight into the BIOS settings. 00:03:04.559 --> 00:03:09.119 If, you know, so you can go there, you can make changes to that. How long do you want it to wait 00:03:09.119 --> 00:03:13.679 to allow you to go into the BIOS before it goes in or do you want to go in straight right away? 00:03:13.679 --> 00:03:17.839 A lot of times on a VM, you don't want to wait like a number of seconds. You want just to go 00:03:17.839 --> 00:03:22.720 straight into the operating system. If you need to get into the BIOS for something, then you just 00:03:22.720 --> 00:03:26.880 check the box that says, when you boot it up, take me straight into the BIOS. And then you're there. 00:03:26.880 --> 00:03:31.520 You don't really need that pause, that delay over and over and over again, even, you know, when you're 00:03:31.520 --> 00:03:38.720 not trying to get in there. Paravirtual PID. So this will allow you basically to use a virtual 00:03:38.720 --> 00:03:45.279 adapter that is compatible with Fiber Channel. So you can connect to a Fiber Channel SAM from the 00:03:45.279 --> 00:03:50.960 VM natively, you know, vCenter settings, cluster settings, resource pools, etc. So there's a bunch 00:03:50.960 --> 00:03:57.119 of different options obviously available there. So some of the most important options that are 00:03:57.119 --> 00:04:02.320 going to be the things that you will set most often. First thing is obviously the name of the 00:04:02.320 --> 00:04:07.759 VM. When you're creating a new VM, location of the files, location of the VM. So you might say, 00:04:07.759 --> 00:04:13.919 well, what's that mean? So location of the files means what datastore do you want the VM to 00:04:13.919 --> 00:04:19.600 consider to be like, let's call it its home directory. What you can do is say, I want datastore 00:04:19.600 --> 00:04:26.160 one, which is my middle speed, middle tier datastore. I want that to be the VM's home 00:04:26.160 --> 00:04:31.679 directory. And by default, all the files go there. Your VMX file goes there. Your swap file goes there. 00:04:32.880 --> 00:04:40.959 The hard disk, the VMDK files, everything goes to that datastore. What you can do then is say, 00:04:40.959 --> 00:04:46.720 I actually want the VMDK files to go to another location. I can move the VMDK, the virtual 00:04:46.720 --> 00:04:53.119 machine's virtual disk, to another datastore. And maybe that other datastore is more expensive, 00:04:53.119 --> 00:04:58.160 much faster storage. So I want better performance for my VMDK files. I'm not really worried about 00:04:58.160 --> 00:05:03.679 how fast you can read that VMX file. It's a small, you know, couple of K file. But I do want 00:05:03.679 --> 00:05:08.079 my virtual machine's hard disk to run very quickly. And so I'm going to put those on very 00:05:08.079 --> 00:05:14.480 fast storage. Maybe I'll put my C drive on middle fast storage, not super fast. Maybe, you know, 00:05:14.480 --> 00:05:21.200 it's some flash storage, but the rate isn't all that high. And then I have another datastore, 00:05:21.200 --> 00:05:27.760 another set of storage, that has faster flash disk. The rate level's higher. I have much better 00:05:27.760 --> 00:05:34.079 performance out of this one. And that's where I'm going to put my B drive that has my SQL database 00:05:34.079 --> 00:05:37.600 files and things like that. And I want that to be super fast. My operating system, I want to be 00:05:37.600 --> 00:05:43.760 pretty fast. And the files that store my VMX and my swap and things, that can be just average speed, 00:05:43.760 --> 00:05:47.760 no big deal. I'm not worried about that. So you can choose a location for all those files. 00:05:48.720 --> 00:05:53.279 Now, the location of the VM, that would mean what clusters I want to put it in, 00:05:53.279 --> 00:05:58.640 what host do I want to put it on, where is the compute going to come from for this, 00:05:58.640 --> 00:06:03.839 right? I can choose, you know, things like data centers and clusters and then host individually. 00:06:03.839 --> 00:06:08.640 So those are some pretty important options that you will consider when you're deploying a new 00:06:08.640 --> 00:06:15.760 virtual machine. So notice here, for the guest OS family and guest OS version, those options are 00:06:15.760 --> 00:06:21.519 grayed out. Normally grayed out means you can't change them. But what grayed out here means is 00:06:21.519 --> 00:06:28.399 you actually can change them, but it's not exactly the same thing as if you would have chosen these 00:06:28.399 --> 00:06:34.239 options when you created the VM. Some of the options just don't matter anymore. For example, 00:06:34.239 --> 00:06:38.160 when you create a brand new VM, I would say, okay, my operating system's going to be Linux 00:06:38.160 --> 00:06:43.519 and it's going to be in boom two version whatever. When you do that, then you go to the next screen 00:06:43.519 --> 00:06:48.799 for the hardware. VMware and vCenter are going to say, okay, when you choose this operating system, 00:06:48.799 --> 00:06:54.720 we recommend normally you have two virtual CPUs. You have one gig of RAM. I'm not sure what the 00:06:54.720 --> 00:06:59.040 recommendations are. I'm making this up. And we think you need a hard disk size of at least 00:06:59.040 --> 00:07:04.880 X number of gigabytes for the hard disk. If I would have chosen Windows, a Windows Server 2022, 00:07:04.880 --> 00:07:08.799 it might have recommended more virtual CPU. It probably for sure would have recommended a lot 00:07:08.799 --> 00:07:15.200 more RAM. And it might have recommended a larger hard disk for my C drive. So now, obviously, now 00:07:15.200 --> 00:07:20.399 that I am changing the operating system later, I'm probably not going to go from Linux to Windows, 00:07:20.399 --> 00:07:26.320 but maybe I'm going from Linux RHEL version 5 to RHEL version 7 or something like that. 00:07:27.920 --> 00:07:34.880 I'm upgrading from 5 to 6 and 6 to 7 for RHEL. And so now, some of those options won't matter 00:07:34.880 --> 00:07:40.640 because the initial what I'm first suggesting isn't going to be relevant anymore because I've 00:07:40.640 --> 00:07:46.160 already created it and already gone past that stage. But when it says, but RHEL version 5 00:07:46.720 --> 00:07:51.600 only supported these types of things. And now that you're going to 7, there's more new features that 00:07:51.600 --> 00:07:55.920 are going to be available to you. So it's important to change this and make sure that VMware knows 00:07:55.920 --> 00:08:00.239 what operating system you're running because you can say, oh, well, with version 7, you can do this. 00:08:00.239 --> 00:08:04.640 And with version 7, you can do that. When version 5 couldn't do those things. So now with this VM, 00:08:04.640 --> 00:08:10.880 we'll make those options available to you. So it's grayed out because not all the same 00:08:10.880 --> 00:08:14.480 things are going to happen as if you would have chosen from the very beginning, but it's still 00:08:14.480 --> 00:08:19.359 very important to go in and select this and make these changes. Just remember, when you see it 00:08:19.359 --> 00:08:23.200 grayed out, you don't want to say, oh, it's grayed. I can't change it. Click on the dropdown menu. 00:08:23.200 --> 00:08:27.200 You can actually make the change. You can save the change and it will save it and it'll be applied. 00:08:27.200 --> 00:08:36.239 So encryption options. Do you want to encrypt this virtual machine? Do we want to encrypt 00:08:36.239 --> 00:08:40.880 the virtual machine on disk? And do we want to encrypt the virtual machine 00:08:41.599 --> 00:08:46.799 when it does a storage vMotion? So there are different requirements for both those things. 00:08:46.799 --> 00:08:55.039 If we wanted to encrypt it on disk, what happens is the system's going to go in and the host is 00:08:55.039 --> 00:08:59.039 going to say, okay, let me create a key. And with this key, I'm going to encrypt that disk. 00:08:59.840 --> 00:09:07.039 Then that key gets encrypted. But where does the key get encrypted from? Well, if I am in a cluster, 00:09:07.039 --> 00:09:14.880 let's say I have three or four ESXi hosts in my environment and the host goes in and it writes 00:09:14.880 --> 00:09:21.840 the VM to disk and it encrypts it and then it stores that key. Well, the other VMs in that 00:09:21.840 --> 00:09:27.359 cluster, they're going to need that key also. So if I have an HA event and so I need to be able to 00:09:27.359 --> 00:09:33.039 go in and read that file, so that is the VMDK and all the virtual machine files on another host, 00:09:33.039 --> 00:09:39.119 the other host needs to have the key to decrypt that key as well. And so what happens is it goes 00:09:39.119 --> 00:09:44.719 in a vCenter. It's going to copy that key for that VM to all the hosts. And then all the hosts are 00:09:44.719 --> 00:09:49.520 going to encrypt that key. But they encrypt this key, the key that is used to encrypt the disk, 00:09:49.520 --> 00:09:54.719 so the disk encryption key, they're going to encrypt it with a key from a KMS, a key management 00:09:54.719 --> 00:10:00.159 server. So they're going to get this key for the key management server from vCenter. So when it 00:10:00.159 --> 00:10:04.799 says that vCenter must be trusted, it must be trusted by the key management server. So the 00:10:04.799 --> 00:10:10.640 hosts are going to ask vCenter for this key to encrypt the key, the key encrypting key. And vCenter 00:10:10.640 --> 00:10:15.200 with the trust relationship it has with the key management server, it gets a key from the key 00:10:15.200 --> 00:10:19.520 management server, sends it to vCenter, vCenter can send it to the hosts, and then they can encrypt 00:10:19.520 --> 00:10:25.039 that key and they can decrypt that key. So the disks are encrypted with a key, that key gets 00:10:25.039 --> 00:10:32.080 encrypted with another key that is used to encrypt the virtual disk encrypting keys. And all the hosts 00:10:32.080 --> 00:10:38.799 in a cluster, in an HA cluster, this HA cluster is the security boundary that all the VMs in there, 00:10:38.799 --> 00:10:43.200 all the hosts in there need to be able to read all the VMs that are in there so that we can decrypt 00:10:43.200 --> 00:10:48.960 those files and all the hosts can run them. So we need a key management server, right, 00:10:48.960 --> 00:10:52.719 KMS server, key management server, and it needs to trust our vCenter server. 00:10:54.400 --> 00:11:01.440 Also, do we want to encrypt vMotion traffic? So when we, again, when we vMotion a VM from one 00:11:01.440 --> 00:11:06.479 host to another, its memory gets copied over. Once all the memory is copied over, then it copies over 00:11:06.479 --> 00:11:10.640 all the CPU registers. Once all the CPU registers are copied over, and that's a lot smaller so it 00:11:10.640 --> 00:11:15.840 happens really fast, then the new host can take over and start running that virtual machine. 00:11:16.640 --> 00:11:21.840 When we copy all this data over, do we want it sent over in clear text or do we want it encrypted? 00:11:21.840 --> 00:11:27.359 If you want it encrypted, then what happens is the two hosts that are doing this transfer, 00:11:27.919 --> 00:11:32.559 they create session keys for this encryption time. We don't need a key management server. We're not 00:11:32.559 --> 00:11:38.799 saving these keys. This key is only used for copying the VM from one host to the other. 00:11:38.799 --> 00:11:43.679 Once that copy is done, that key is thrown away and it's not used again. So we don't need to worry 00:11:43.679 --> 00:11:47.359 about going to a key management server and having it saved and all this stuff. It's just a real 00:11:47.359 --> 00:11:53.520 quick session key. It's a 256-bit key that the two hosts agree on that we then use to copy that 00:11:53.520 --> 00:12:00.239 machine over. vMotion encryption can be disabled. It can be opportunistic, and what opportunistic 00:12:00.239 --> 00:12:05.760 means is if both hosts support it and they can do it, then we'll encrypt it. If it doesn't support, 00:12:05.760 --> 00:12:10.400 if one doesn't support it, then we'll do it in clear text. So the options can be we don't need 00:12:10.400 --> 00:12:14.880 to waste overhead. We don't need to waste CPU trying to encrypt this VM. The data on it isn't 00:12:14.880 --> 00:12:20.479 that important. Hopefully that's not really ever an option. Opportunistic means if we can do it, 00:12:20.479 --> 00:12:25.440 we will. If we can't, we'll do the vMotion anyway. Also, hopefully that's not really an option. 00:12:26.239 --> 00:12:34.880 Required means if I can't do a secure encrypted transfer from the source host to the destination, 00:12:34.880 --> 00:12:39.039 vMotion is going to fail. It'll tell me that there's a compatibility issue and I can't 00:12:39.039 --> 00:12:43.039 move that host or the VM from this host to that host. I'd have to choose a different 00:12:43.039 --> 00:12:48.400 host where the vMotion traffic can be encrypted. So that's what the different options are for 00:12:48.400 --> 00:12:56.080 encrypted vMotion. So here we're just seeing vMotion enabled. Do we want to allow it, not 00:12:56.080 --> 00:13:01.919 allow it? Opportunistic. And then encrypt fault tolerant. So we also, do we want to have fault 00:13:01.919 --> 00:13:09.520 tolerant VMs? Again, fault tolerant VMs are where I have a VM running on one host and I have a copy 00:13:09.520 --> 00:13:14.640 of it running on another, but the other one's a slave. All the work, everything's happening, 00:13:14.640 --> 00:13:20.400 all the memory changes, all the CPU changes, everything's happening on a source host. And 00:13:20.400 --> 00:13:28.239 then all those changes get copied to that slave machine, that copy of it. So if the source one 00:13:28.239 --> 00:13:34.320 were to fail, then the one that's the copy, that's not doing any of the work, that one takes 00:13:34.320 --> 00:13:39.200 over and starts doing all the work. And this happens like in a second. It happens super fast. 00:13:39.200 --> 00:13:45.359 So if we have critical applications we can't have go down, we can create a fault tolerant VM, 00:13:45.359 --> 00:13:50.000 whereas HA would maybe take a few minutes to get up and going again by having to restart it 00:13:50.000 --> 00:13:55.760 someplace else. Fault tolerant takes over right away. The users won't even see a blip. All right. 00:13:56.320 --> 00:13:59.599 So we can also say, do you want that fault tolerant information that's being exchanged 00:13:59.599 --> 00:14:07.840 to be encrypted or not? So power management. So how does the guest OS respond to be put into 00:14:07.840 --> 00:14:12.239 standby? That's an option. How does it respond for suspend mode? Do we want to leave it on? 00:14:13.359 --> 00:14:18.960 How do we want to do suspension? So if we say we want to put the guest machine in 00:14:19.440 --> 00:14:26.400 standby mode, either the hypervisor can just pause the virtual machine's processing and the 00:14:26.400 --> 00:14:31.760 hypervisor can write the virtual machine's memory to a file that it controls. The virtual machine 00:14:31.760 --> 00:14:36.400 itself has no idea that what's happening to it. And when it wakes back up again, all that it will 00:14:36.400 --> 00:14:41.039 know is the clocks jump forward a bunch of times. But the virtual machine is completely out of the 00:14:41.039 --> 00:14:44.799 loop. So if you have a virtual machine that does not support suspend mode, or if you don't have 00:14:44.799 --> 00:14:49.359 VMware tools installed and you can't pass the suspend command to it, then the host can do it 00:14:49.359 --> 00:14:56.080 for you. But what can also happen is we can actually tell the guest OS, you go into standby 00:14:56.080 --> 00:15:00.479 mode. You go ahead and put yourself to sleep. So it will go in and it will write its memory 00:15:00.479 --> 00:15:06.479 within a file on the VMDK file and the guest OS quietly shuts itself down. And then when you go 00:15:06.479 --> 00:15:11.119 and you say the power back on again, it takes itself out of standby mode. So do you want the 00:15:11.119 --> 00:15:16.159 hypervisor to do it or do you want the guest OS to do it? Most of the time you'd rather let the 00:15:16.159 --> 00:15:22.320 guest OS know as much about what's going on as possible. We don't want to necessarily have the 00:15:22.320 --> 00:15:28.719 guest OS be oblivious to what's happening, if possible. All right. Wake on LAN, do we want to 00:15:28.719 --> 00:15:33.359 have wake on LAN enabled for a virtual machine? So we need to select the adapter, enable that or 00:15:33.359 --> 00:15:39.919 not enable that option. So here we can see our standby mode responses. Again, we can suspend 00:15:39.919 --> 00:15:45.200 the virtual machine or have the guest OS put it into suspend mode. Wake on LAN, we can check that 00:15:45.200 --> 00:15:50.400 box if we want to enable wake on LAN or not for a virtual adapter. All the showing here means 00:15:50.400 --> 00:15:54.640 basically you can see it's the exact same set of options and all that, just the layout's gotten a 00:15:54.640 --> 00:16:06.719 little different. So next four are some key options, VMware tool power controls. So shutdown 00:16:06.719 --> 00:16:12.159 versus the power off. So when we hit that red box, do we want to send that shutdown command 00:16:12.159 --> 00:16:18.159 to the guest OS or would you want it to just power off the VM? You probably want the guest OS to do a 00:16:18.159 --> 00:16:23.840 nice orderly shutdown versus just being powered off as if you pulled the power cord out of the 00:16:23.840 --> 00:16:29.119 wall. Suspend versus suspend guest, we kind of just discussed that option. So do you want the 00:16:29.119 --> 00:16:34.640 hypervisor to suspend the VM and it's unaware or do we want a suspend command sent to the virtual 00:16:34.640 --> 00:16:41.840 machine's operating system and it goes through and does a suspend for us, right? Guest OS restart 00:16:41.840 --> 00:16:46.799 versus a reset. So a reset would be kind of like you hit the power button on the front of your 00:16:46.799 --> 00:16:51.679 computer for a moment and it just power cycles that computer real quick versus shutting it down. 00:16:52.239 --> 00:16:58.080 Whereas the guest OS restart means it goes through and it actually does a reboot. Again, it's always 00:16:58.080 --> 00:17:03.280 better if you can get the guest OS to participate in whatever command you're trying to execute 00:17:03.359 --> 00:17:09.280 versus just brutally pulling power cords out of walls or hitting power buttons in front of 00:17:09.280 --> 00:17:14.319 computers. It's better if the guest OS can participate. Now if the machine's frozen and it 00:17:14.319 --> 00:17:18.880 can't, you've got to do what you got to do. But if you can get the guest OS to reboot or if you can 00:17:18.880 --> 00:17:24.880 get the guest OS to suspend or to power down, things like that, that's always an option 00:17:24.880 --> 00:17:29.040 preferred. You do need the VMware tool to be installed. You want the current version of VMware 00:17:29.040 --> 00:17:37.520 tools on the VM for things like this. Another option for our VM is when you go in, you want to 00:17:37.520 --> 00:17:41.119 have the current version of VMware tools. That's always super important. So you might go to a 00:17:41.119 --> 00:17:48.479 virtual machine and you might see it say in the banner in the vSphere web client that your virtual 00:17:48.479 --> 00:17:53.040 machine tools, VMware tools are out of date and you'll be tempted to right then, oh yes, update 00:17:53.040 --> 00:17:57.599 these really quick. Remember, upgrading VMware tools requires a restart. So you don't want the 00:17:57.599 --> 00:18:03.199 tools upgraded and the VM not able to restart. So now we're in this limbo mode of VMware tools. 00:18:03.199 --> 00:18:07.280 So you want to schedule that at a time when you know that you can have a maintenance window. 00:18:07.280 --> 00:18:11.599 So then we can upgrade the VMware tools, reboot the virtual machine, have it come back up again. 00:18:12.160 --> 00:18:17.040 Everything's good. Now when you install VMware tools, you're going to be installing new device 00:18:17.040 --> 00:18:22.880 drivers, right? New versions of device drivers on that virtual machine. And so you might also want 00:18:22.880 --> 00:18:30.160 to, before you install the VMware tools, the new version, snapshot the VM, then upgrade the VMware 00:18:30.160 --> 00:18:35.920 tools, reboot it, it comes back up, everything's good, I'm not getting any errors or anything, 00:18:35.920 --> 00:18:40.319 and then delete your snapshot. If something goes wrong and it doesn't want to reboot correctly, 00:18:40.319 --> 00:18:44.719 revert back your snapshot to the old version, bring it up, look and see what's going on. Okay, 00:18:44.719 --> 00:18:49.040 let's start troubleshooting that and see why that happened, okay? And then scripts. You want to run 00:18:49.040 --> 00:18:52.239 scripts. You want to run scripts when the machine powers on. You want to run scripts when the machine 00:18:52.239 --> 00:18:58.239 powers off. There's a bunch of options for that, right? So here we're seeing power options. What 00:18:58.239 --> 00:19:02.560 do you want to do when you hit the red box? Do you want to shut down or do you want to power it off, 00:19:02.560 --> 00:19:07.280 things like that? The big thing is the bottom there, running the scripts. So you want to do 00:19:07.280 --> 00:19:12.160 it at power on, you want to do it after resuming. So if you have suspended it and you resumed it, 00:19:12.160 --> 00:19:17.599 you want to run scripts at that time before suspend or before shutting down the guest OS. So 00:19:18.719 --> 00:19:21.839 you can choose all of them or you can choose any combination of those options there. 00:19:22.239 --> 00:19:31.520 So virtualization-based security. So additional security for the virtual machine, you need the 00:19:31.520 --> 00:19:36.560 latest versions of Windows to support this. And basically what this is going to do, you also need 00:19:36.560 --> 00:19:44.959 to have EFI enabled and basically it will allow for additional level security between the hypervisor 00:19:44.959 --> 00:19:51.760 and the operating system for things like a TPM and TPM2 and just basically overall security for 00:19:51.760 --> 00:19:55.599 the virtual machine to make it so executables aren't going to be ran, that shouldn't be around 00:19:55.599 --> 00:20:00.319 on the machine. It just makes it a much more secure environment. It does give you secure boot. 00:20:00.319 --> 00:20:06.880 With secure boot is basically the operating system itself is signed with a certificate 00:20:06.880 --> 00:20:11.280 and that certificate is on the motherboard. So it says, does this certificate on my motherboard 00:20:11.280 --> 00:20:16.640 match the certificate that's on the operating system? You know, the signing of it, this file 00:20:16.640 --> 00:20:20.640 is encrypted, I can decrypt it and read it. Yep, we've got a good operating system. We trust this 00:20:20.640 --> 00:20:26.319 OS to not have been compromised and we trust the vendor of it, things like that. So that's 00:20:26.319 --> 00:20:33.920 virtualization-based security. So some boot options, EFI. So if we want to use a virtualization-based 00:20:33.920 --> 00:20:39.439 security, we need to have EFI. We also have BIOS options available. So BIOS might be, you know, 00:20:39.439 --> 00:20:42.800 useful if we have some really old operating systems and we're trying to boot that doesn't 00:20:42.800 --> 00:20:48.560 support EFI. Boot delay, you can specify a boot delay when you power it on so you can hit, you 00:20:48.560 --> 00:20:53.040 know, Dell and get into the BIOS. There's also an option, you can just check a box that says, 00:20:53.040 --> 00:20:58.079 next time I reboot this machine, take me into the BIOS. You probably don't want to choose that 00:20:58.079 --> 00:21:03.040 boot delay option very often because you don't want the machine always delaying every time you 00:21:03.040 --> 00:21:08.640 do a reboot for a few seconds. You want it back up and going as fast as possible and you rarely go 00:21:08.640 --> 00:21:13.599 into the BIOS. So for those rare occasions you do, just choose the box that takes you into the BIOS. 00:21:14.239 --> 00:21:19.439 What happens if I fail to boot? Okay, that's another thing you want to consider. So if we 00:21:19.439 --> 00:21:24.560 look over here, we see we can choose what firmware. EFI, BIOS is also an option. Do we 00:21:24.560 --> 00:21:29.119 want to enable secure boot? If your OS does not support secure boot and you check this box, it 00:21:29.119 --> 00:21:33.760 won't boot. So make sure you have an OS that supports secure boot like all the current versions 00:21:33.760 --> 00:21:39.439 of Windows do. A boot delay option is there. You can specify that in, you know, a number of 00:21:39.439 --> 00:21:45.680 milliseconds. Forced EFI setup, so it's basically forced if you want to go into the EFI settings 00:21:46.959 --> 00:21:52.800 when it comes back up again. And if I fail to boot recovery, how long do I wait before I try again? 00:21:54.239 --> 00:21:59.199 You want to set this option to, you know, to be a reasonable number. You don't want to be hours. 00:21:59.199 --> 00:22:05.359 You don't want to be a single second. So, okay, failed to boot. Let's try this again. And honestly, 00:22:05.359 --> 00:22:08.479 usually, if it fails to boot the first time, it's going to fail to boot the second, third, 00:22:08.560 --> 00:22:13.760 and fourth, too. So you may not want it to try and reboot on a failure to boot. You might want 00:22:13.760 --> 00:22:16.239 just to wait so you can go in there and start troubleshooting and figure out why. 00:22:19.280 --> 00:22:24.400 So secure boot makes it the hardware-only boot using pre-approved software, meaning a 00:22:24.400 --> 00:22:30.319 pre-approved operating system. It's a certificate that's created by Microsoft, but if you are a 00:22:30.319 --> 00:22:34.400 Linux distributor, you can get that certificate. You know, different OSes can get that certificate. 00:22:34.400 --> 00:22:40.479 They can also do a secure boot. Trusted by the manufacturer, basically the hardware manufacturer 00:22:40.479 --> 00:22:45.520 of that motherboard. We can also say on a virtual environment, then, of course, 00:22:45.520 --> 00:22:48.800 it's going to be trusted by, you know, the certificate that's on the VMware system. 00:22:49.439 --> 00:22:58.479 VMs can be enabled or disabled using secure boot, right? So EFI is a firmware, right? So we used to 00:22:58.479 --> 00:23:02.800 be always with BIOS. Now we have EFI. Different vendors have different implementations of this 00:23:02.800 --> 00:23:07.599 EFI. You see different options in there. Some of the cool things about it, if you're used to the 00:23:07.599 --> 00:23:12.319 old BIOS, everything was done through tab and arrows and things like that. Now with EFI, you can 00:23:12.319 --> 00:23:16.719 use, you know, your mouse. You can point around in there and click on boxes and things like that. 00:23:16.719 --> 00:23:21.599 So from a use perspective, it's easier, but it gives you a lot more security features, too. 00:23:21.599 --> 00:23:25.439 Like, for example, secure boot is one of our options, right? You do need to have virtual 00:23:25.439 --> 00:23:29.920 hardware version 13 or later, right? So you're not going to, you know, do this with some older 00:23:29.920 --> 00:23:35.280 versions of ESX, like, you know, 5.5 or something like that. You need a current version of VMware 00:23:35.280 --> 00:23:42.160 support, at least version 13 of hardware. And the OS needs to have UEFI secure boot support, 00:23:42.160 --> 00:23:48.719 meaning it needs to basically have encryption, kind of a certificate that is by a trusted vendor, 00:23:48.719 --> 00:23:55.520 and that vendor happens to be Microsoft. So to enable or disable secure boot, you can see 00:23:55.520 --> 00:23:59.680 your options in here, right? You're going to navigate to the virtual machine, select it, 00:23:59.680 --> 00:24:05.119 you know, edit and go to settings. Then you're going to expand the secure boot options. 00:24:05.119 --> 00:24:11.040 You can say you want to verify the EFI options in there. You can check the box or uncheck the 00:24:11.040 --> 00:24:16.079 box to enable secure boot, if you want to enable secure boot or not. And then you can go in there 00:24:16.079 --> 00:24:20.400 and you can say, okay, and that basically enables the settings. So really, it's a matter of going 00:24:20.400 --> 00:24:26.079 in and choosing EFI for your BIOS and checking the box for secure boot, really is what all those 00:24:26.079 --> 00:24:34.880 steps are saying. Fiber channel MPIV. So what you can do with this is we can actually give a virtual 00:24:34.880 --> 00:24:44.160 machine an adapter that is going to be a fiber channel adapter. So what MPIV is, it allows a 00:24:44.160 --> 00:24:51.920 physical fiber channel HBA to have multiple worldwide names, so that I can then give a 00:24:51.920 --> 00:24:59.680 virtual machine fiber channel adapter with its own unique worldwide name, and that will go through 00:24:59.680 --> 00:25:06.400 my physical fiber channel adapter that has its own worldwide name that the ESXi host is using, 00:25:06.400 --> 00:25:11.040 but the virtual machine's traffic can just slip right through there and connect to the SAN, 00:25:11.040 --> 00:25:17.040 and the SAN isn't going to see the ESXi host, it's going to see the Windows VM or the Linux 00:25:17.040 --> 00:25:23.280 VM or whatever it is that's using this virtualized fiber channel adapter. So now my virtual machine 00:25:23.280 --> 00:25:29.599 can see my fiber channel storage. There aren't tons of scenarios where it's important that the 00:25:29.599 --> 00:25:37.439 VM can see my SAN storage natively, but if you have a scenario where you have an application 00:25:37.439 --> 00:25:42.400 or some kind of a use where you want the VM to see the fiber channel storage natively, 00:25:42.400 --> 00:25:49.199 you can do this with this fiber channel MPIV so that it will allow the physical, and of course, 00:25:49.199 --> 00:25:55.040 the adapter has to support it, the host, the ESXi host supports it. The adapter can actually have 00:25:55.040 --> 00:25:59.280 multiple virtual worldwide names, and the reason why it has multiple is because it has its own, 00:25:59.280 --> 00:26:04.640 and the VMs going through it also can have their unique own. That's not saying that every VM is 00:26:04.640 --> 00:26:10.800 going to. You'd have to configure it. Most of the time, the storage only sees the ESXi host talking 00:26:10.800 --> 00:26:14.800 to it, and the VMs are talking, you know, communicating through the virtualization 00:26:15.439 --> 00:26:20.640 that I need to write to a disk. The hypervisor translates that, sends it through the HBA, 00:26:20.640 --> 00:26:25.119 and again, the SAN just thinks it's talking to the ESXi host. This would be a unique situation 00:26:25.119 --> 00:26:31.439 where you've decided to configure a VM to also have a unique worldwide name and a fiber channel 00:26:31.439 --> 00:26:41.199 virtualized adapter. So, this is a screenshot of what the MPIV would look like, right? So, 00:26:41.199 --> 00:26:45.119 you just have some options here for configuring that. If you want to create a new worldwide name, 00:26:45.119 --> 00:26:48.479 are we going to remove the worldwide name assignment on there? Okay, what are we going 00:26:48.479 --> 00:26:52.959 to do with all those settings? So, basically, we're just going through and configuring a virtual 00:26:52.959 --> 00:26:59.839 fiber channel adapter on a virtual machine. So, here in this demo environment, this is 00:26:59.839 --> 00:27:06.000 VMware's hands-on lab environment. So, it's hol.vmware.com that we're working in, and we're 00:27:06.000 --> 00:27:11.280 just working on the virtualization 101 lab. So, in here, we can look at, like, I created this demo 00:27:11.280 --> 00:27:18.640 VM1 here. This is not part of the VMware's normal environment. So, let's go ahead and right-click 00:27:18.640 --> 00:27:26.640 on this guy, and let's go to edit settings. And from here, we can change the different settings 00:27:26.640 --> 00:27:32.560 in here. So, for example, this was the tiny Linux machine that I cloned. And so, it has one virtual 00:27:32.560 --> 00:27:40.000 CPU and 256 gigs of RAM. I can go in. I can change the number of virtual CPUs that are in here, 00:27:40.000 --> 00:27:43.439 right? We have some other options for, like, are we going to allow hot plug or not? Are we going 00:27:43.439 --> 00:27:49.119 to set reservations and limits, which we'll discuss all that later. Here, I can change the 00:27:49.119 --> 00:27:54.800 memory. Right now, I have 256 megabytes, which is basically a quarter of a gig. I could change 00:27:54.800 --> 00:28:02.959 this to one gigabyte from here. And, you know, we could start this up. We have our virtual hard 00:28:02.959 --> 00:28:09.040 disk. We can go in there and change the size. One thing we can do also is if we were, say, 00:28:09.040 --> 00:28:14.239 going to add a new virtual device, we can go in. So, we want to add a hard disk. 00:28:16.560 --> 00:28:21.280 And here's our new hard disk. And how big do we want to make that hard drive? And we can say, 00:28:21.280 --> 00:28:25.680 okay, we're going to make this hard drive one gig. Now, if I made it too big, let's say I wanted to 00:28:25.680 --> 00:28:32.319 go in there and make it 100 gigs, we'll see we don't have capacity for a 100-gig virtual disk. 00:28:32.880 --> 00:28:39.599 So, what I can do if I needed that is I can go in and instead of being thick provisioned, 00:28:39.599 --> 00:28:44.719 I can thin provision it. And that will allow me to create the virtual disk, start it up, 00:28:45.439 --> 00:28:49.199 thin provisioned. And then later, if I add more space to my storage, 00:28:49.760 --> 00:28:56.000 I can then let it grow to the entire 100 gigs. Right now, if we were trying to exceed the 64.29 00:28:56.000 --> 00:29:00.880 gigs, it would actually end up crashing the VM because we wouldn't have enough space to grow 00:29:00.880 --> 00:29:05.359 the virtual disk to that size. But one way we're going to round that limited space where it was 00:29:05.359 --> 00:29:09.119 a temporary situation where we just need to add more storage and maybe it's on order or something 00:29:09.119 --> 00:29:15.839 like that, we can just go there and we can thin provision that. We can also say, yeah, but I don't 00:29:15.839 --> 00:29:20.479 need all these different devices. Like, for example, maybe I don't need that CD-ROM drive 00:29:20.479 --> 00:29:27.280 on here or on a Windows system. A lot of times our Windows systems will have USB devices. So, 00:29:27.280 --> 00:29:35.599 we can say a host USB device. Oh, I haven't added. I don't want a host device. A host device means 00:29:35.599 --> 00:29:40.000 I'm actually borrowing one that's actually physically on the host, right? I don't want 00:29:40.000 --> 00:29:46.800 to do that. I just want to add a USB controller. So, if this was a new VM I was creating and like, 00:29:46.800 --> 00:29:52.000 oh, well, I don't need any USB devices on here. I don't need this or that. I can just go in and 00:29:52.000 --> 00:30:01.439 say I want to go and remove all the USB controllers because I'm not going to use any USB devices with 00:30:01.439 --> 00:30:05.680 this. No USB mice and keyboards and miles, that kind of stuff. Now, what will happen sometimes 00:30:05.680 --> 00:30:09.839 if you have to remove all the USB virtual controllers is sometimes the virtual mice 00:30:09.839 --> 00:30:14.400 don't work because there's, you know, virtualized USB mice instead of the old-fashioned PS2 or 00:30:14.400 --> 00:30:18.959 serial and things like that. So, you actually sometimes will want that. Another common thing 00:30:19.520 --> 00:30:25.040 that you will see, and not a lot, but sometimes we'll need more than one virtual network 00:30:25.680 --> 00:30:30.880 on a virtual machine. So, you'll say add a virtual device, add the adapter, 00:30:31.760 --> 00:30:38.239 and then I'll go in and say, okay, I want this guy to be my VMXNet3. I've installed VMware tools 00:30:38.239 --> 00:30:43.359 on this virtual machine, and because I've installed VMware tools, that VMXNet3 adapter 00:30:43.359 --> 00:30:49.199 is going to work just fine for me, but I want it connected to a different port group. And I can go 00:30:49.199 --> 00:30:53.439 through and say, okay, I want it connected to this port group, for example. So, now I have multiple 00:30:54.400 --> 00:31:02.479 virtual adapters. I have configured my hard disk. I have maybe customized the number of virtual 00:31:02.479 --> 00:31:09.680 CPUs, the amount of RAM that this system is going to run on, the CD-ROM drive. 00:31:12.000 --> 00:31:16.160 Am I going to go in and say I want this connected to the client device, meaning 00:31:16.160 --> 00:31:20.880 I want to connect it to the client that's connecting to manage this vCenter environment 00:31:20.880 --> 00:31:26.800 to its CD-ROM drive? The most common thing you'll do is either an ISO, sometimes host device, 00:31:26.800 --> 00:31:31.760 meaning the ESXi host CD-ROM drive, whatever ISO or whatever CD is in there, most common 00:31:31.760 --> 00:31:35.119 is going to be this guy here. You're going to connect to an ISO in a data store. 00:31:35.119 --> 00:31:38.560 In this HOL environment, the hands-on lab environment, we don't have any ISOs, 00:31:38.560 --> 00:31:42.880 but normally I would check on that, and then I would browse to whatever data store, 00:31:43.839 --> 00:31:49.920 add my ISOs, and select it, and then it shows connected there. And then the next thing is, 00:31:49.920 --> 00:31:55.359 do you want to do connect the power on? Oftentimes, if you're going to be installing 00:31:55.359 --> 00:31:59.359 an operating system, you want to check that box, and then after you're done installing, 00:31:59.359 --> 00:32:02.719 you're going to uncheck the connect the power on, and you're going to uncheck the connected. 00:32:02.719 --> 00:32:07.199 You don't want that on there after that. I'm going to go ahead and put it back at 00:32:07.199 --> 00:32:10.400 client device for right now because I don't have an ISO to map to it. 00:32:13.520 --> 00:32:16.719 Video card, you can specify some video card specifications. This used to be 00:32:17.280 --> 00:32:22.640 a pretty generic, simple thing, but now we can set a number of devices. I want one monitor or 00:32:22.640 --> 00:32:27.280 I want two monitors. How much video memory do you want to dedicate? The more monitors and more RAM 00:32:27.280 --> 00:32:31.359 than the higher resolutions and things like that, you can more easily support. All right. 00:32:31.359 --> 00:32:35.439 So, those are some of the generic settings you can go there and set on the virtual machine like that. 00:32:36.239 --> 00:32:42.239 When you're creating a new VM, one interesting thing, I can say I want to add a new virtual 00:32:42.239 --> 00:32:49.199 machine. I'm going to say create a virtual machine here. I'm going to go ahead and call this 00:32:55.119 --> 00:33:00.160 and I'll say next, and I'm going to choose my compute resource of this host. 00:33:01.359 --> 00:33:08.560 Next. I'll choose some storage. I'll say next. Now this, okay, the ESXi version I want to be 00:33:08.560 --> 00:33:13.599 compatible with, if all my hosts are eight or going to be newer, I can choose eight. If some 00:33:13.599 --> 00:33:19.599 of my hosts are going to be 7.0 update two or newer, then I would select that, but we'll just 00:33:19.599 --> 00:33:26.400 leave it at eight. Say next. Now the guest operating system, this is interesting because what you'll see 00:33:26.400 --> 00:33:34.239 is it's going to tell VMware, one, what features this VM can support because VMs that are running 00:33:34.319 --> 00:33:42.880 Windows, the version of Windows Server 2022 will have features that VMs running Windows Server 2012 00:33:42.880 --> 00:33:47.599 don't have, right? So, different versions of operating systems support things like hot add 00:33:47.599 --> 00:33:53.599 CPU or hot add memory where other older versions may not or certain versions of Linux may not. 00:33:54.239 --> 00:33:57.920 Another thing that this will do is let's go ahead and just say we're going to do Windows 00:33:57.920 --> 00:34:07.439 Server 2022 and say next. And notice that I have two virtual CPUs, four gigs of RAM, 00:34:07.439 --> 00:34:11.760 and it wants to give me a, you know, saying here a 90 gig hard drive, but it can't support that 00:34:11.760 --> 00:34:16.879 because there's not enough free space. So, I'd have to go in there and say, okay, do this, but 00:34:16.879 --> 00:34:23.120 we want a thin provisioner, right? What I can also do is let's say instead I'm going to install a 00:34:23.120 --> 00:34:28.800 version of Linux and the version of Linux I want to install, Alma Linux works just fine for this. 00:34:29.919 --> 00:34:40.719 I'll say next. This only needs one virtual CPU, two gigs of RAM, and 16 gigs of hard disk space. 00:34:41.760 --> 00:34:46.239 So, it knows based upon the operating system, here's kind of the minimum recommended 00:34:46.239 --> 00:34:52.879 requirements for this particular guest operating system. If I go back and instead of Alma, 00:34:52.879 --> 00:35:03.439 I choose Photon, Veeam or Photon OS, and say next. Now, I only need 16 gigs of hard drive, 00:35:03.439 --> 00:35:09.120 one virtual CPU, two gigs of RAM. So, depending upon what operating system you choose, 00:35:09.120 --> 00:35:14.239 there's different options or different default settings that it will select for you. 00:35:15.679 --> 00:35:19.919 So, it doesn't really matter for this right now. We're just going to say any. We've already been 00:35:19.919 --> 00:35:24.399 through this before in another demo where we went through and customized all the different things, 00:35:24.399 --> 00:35:28.159 and it's just similar to when we right-clicked on an existing computer and said edit. 00:35:28.159 --> 00:35:34.479 I wanted to show you that based upon this OS family and the version, you'll get different 00:35:34.479 --> 00:35:40.959 options and different default settings for your customization. Besides that, it also tells 00:35:40.959 --> 00:35:47.679 a hypervisor what features that this VM is going to support. Now, if we go to our demo 00:35:47.679 --> 00:35:55.439 virtual machine here, and we go back to edit settings, go to VM options. 00:35:58.959 --> 00:36:05.600 All right. So, under our general options here, right, we have the name. Notice the guest OS family 00:36:05.600 --> 00:36:09.840 and the guest OS version. These are grayed out. And generally, grayed out will tell us, 00:36:09.840 --> 00:36:15.120 oh, we can't change that. But actually, I can go in and change this and say, actually, 00:36:15.120 --> 00:36:21.919 I'm going to be running. Let's see here. Doesn't really matter too much. 00:36:23.919 --> 00:36:29.600 I'll just say a version of Ubuntu. I'm going to be running Ubuntu. All right. So, obviously, 00:36:29.600 --> 00:36:33.919 the default settings don't change because that's already said and done. We've already created a 00:36:33.919 --> 00:36:39.520 virtual machine. But it might say the version of Linux I had selected before I know only supports 00:36:39.520 --> 00:36:44.560 these features. And this new version I know supports additional features or fewer features. 00:36:44.560 --> 00:36:50.959 So, it's grayed out, which normally, like I said, means we can't change these. But we can. 00:36:50.959 --> 00:36:56.320 It's just grayed out to let you know that not everything that would normally be changed is 00:36:56.320 --> 00:37:01.840 going to be changed by selecting this. Okay. And here's where we can go in and do things 00:37:01.840 --> 00:37:07.840 like encryption. Do we want to enable encryption for vMotion, fault-tolerant VMs? Remember, 00:37:07.840 --> 00:37:13.600 opportunistic means if both hosts support it, I'll do it. But if one doesn't, one doesn't, 00:37:13.600 --> 00:37:17.520 I'll still do the vMotion anyway. I just won't do it encrypted. If both sides support the 00:37:17.520 --> 00:37:23.040 encryption, I'll do it encrypted. All right. And that's what the opportunistic means. I can disable 00:37:23.040 --> 00:37:27.520 it, which means I'll never use encryption. Or I can say it's required. Required would mean 00:37:27.520 --> 00:37:34.399 both sides have to support it or the vMotion is going to fail. All right. Some options there. 00:37:34.399 --> 00:37:41.600 VMware tools. What do you want to have happen? You know, for example, if I hit this little, 00:37:41.600 --> 00:37:45.600 you know, shutdown button, by default, it shuts down the guest OS. It sends a signal to the guest 00:37:45.600 --> 00:37:49.840 operating system to shut down. I can say if I hit that button, just power it off. I just basically 00:37:49.840 --> 00:37:55.439 yank the power cord out of the back of the system. What happens if I hit the little pause icon? 00:37:56.080 --> 00:38:01.600 It can suspend or it can suspend the guest, meaning it sends a suspend signal to the guest 00:38:01.600 --> 00:38:08.080 operating system. And what happens if we hit this little, you know, restart symbol? We can say 00:38:08.080 --> 00:38:13.679 restart or restart the guest, meaning it will send a signal to the operating system saying to 00:38:13.679 --> 00:38:19.600 reboot the operating system, whereas this other option, which doesn't say guest, that is going to 00:38:19.600 --> 00:38:27.760 be basically like resetting the hardware, the actual, you know, workstation or server itself, 00:38:27.760 --> 00:38:32.719 and power cycle it without letting the operating system know it's going to happen. So, you might 00:38:32.719 --> 00:38:36.959 end up getting some correction or something like that on there if you do that. All right. 00:38:36.959 --> 00:38:40.639 VMware tools, you want to check and upgrade VMware tools before each power on. 00:38:41.840 --> 00:38:44.719 Normally, you don't want to automatically upgrade to VMware tools. You want to schedule that. 00:38:45.840 --> 00:38:52.399 Time synchronization, you want to start a synchronized startup and every time you resume. 00:38:55.040 --> 00:39:00.719 Run VMware tool scripts, you want to run after a power on, when resuming, before suspending. We've 00:39:00.719 --> 00:39:04.320 been through all these options here. Your boot options, this is where you're going to go in, 00:39:04.320 --> 00:39:11.280 and we talked about, you want to force a BIOS setup. So, next time I turn this computer on, 00:39:11.280 --> 00:39:16.399 if I check this box, it'll go right into the BIOS, right? If it fails to boot, what do we 00:39:16.399 --> 00:39:21.120 want to do? We want to try Albergan automatically after so many seconds have passed, right? How 00:39:21.120 --> 00:39:27.439 many seconds we want that to be. You can set some of those options there. Power management. 00:39:28.320 --> 00:39:33.120 So, how should the virtual machine respond when the guest OS is placed in standby? Do you want to 00:39:33.120 --> 00:39:37.840 suspend the virtual machine or put the guest OS in standby, right, but leave the machine powered on? 00:39:39.040 --> 00:39:40.719 Some of our advanced options. 00:39:44.479 --> 00:39:49.600 This is disabled acceleration or enable logging, right? Enable logging means you'll get, 00:39:49.600 --> 00:39:53.520 obviously, some logs you have to set up the startup and running the VM. 00:39:57.439 --> 00:40:04.719 Debugging and statistics. You can say how much detail you want to get in there, right? 00:40:04.719 --> 00:40:09.439 Where do you want your swap file? The default location of the swap file means wherever the 00:40:09.439 --> 00:40:13.360 virtual machine is stored, that's where you're going to store the swap file as well, right? 00:40:15.199 --> 00:40:20.959 You can say you want the virtual machine directory or if a cluster has settings. So, 00:40:20.959 --> 00:40:25.760 I can go to the cluster and put a swap file location, and normally the cluster is set to 00:40:26.239 --> 00:40:30.239 with the virtual machine. So, the default cluster setting is with the virtual machine, 00:40:30.239 --> 00:40:35.280 but the VM setting says whatever the cluster says. The cluster could say one thing, though, 00:40:35.280 --> 00:40:39.600 you can go in and do something different. You could go in and say, I know the VM is stored 00:40:39.600 --> 00:40:45.199 on this certain data store, but I want to store a swap file onto a different data store, right? 00:40:45.199 --> 00:40:49.919 So, maybe it has this really cheap storage that I want the swap file location to be on because swap 00:40:49.919 --> 00:40:54.320 files can just get really big and kind of carried away. Your swap files can be equal to the amount 00:40:54.320 --> 00:40:59.199 of RAM in the virtual machine, unless you have a reservation, then it's set equal to the size 00:40:59.199 --> 00:41:07.919 of your reservation. All right. So, the Fiber Channel MPIV, if you're setting up MPIV for 00:41:07.919 --> 00:41:15.679 Fiber Channel for your VM, as we discussed, CPU topology, right? CPU topology available 00:41:15.679 --> 00:41:21.280 for virtual machines that are eight or later, which I believe we did choose that. Oh, actually, 00:41:21.280 --> 00:41:25.360 we cloned that machine over there. So, we created a new machine, we could set the CPU topology. 00:41:25.360 --> 00:41:31.199 This one here might be an older VM from an older version of VMware. All right. So, this is editing 00:41:32.479 --> 00:41:36.000 the settings on a virtual machine that already exists, and we walk through 00:41:36.560 --> 00:41:41.600 editing the settings of a VM that we are creating brand new from scratch. So, you can either edit 00:41:41.600 --> 00:41:46.959 the settings of a VM as you're creating it to be the non-standard default. You can also go in and 00:41:46.959 --> 00:41:52.719 edit the settings of a VM after it's been created. Now, when it's powered off, like this one, 00:41:52.719 --> 00:41:57.439 you can change pretty much everything. Once they are powered on, there will be certain things you 00:41:57.439 --> 00:42:04.080 can and cannot change. You're not going to be able to remove a disk controller and things like that, 00:42:04.080 --> 00:42:07.199 or certain items you're not going to be able to remove. Like most operating systems, I'm not 00:42:07.199 --> 00:42:12.000 going to let you remove CPUs when it's powered on, you have to shut it down to do that. So, 00:42:12.000 --> 00:42:15.520 that is virtual machine settings.