Lesson 3 Part 2 - Storage requirements for vMotion
Video Activity
Lesson 3 part 2. Storage requirements for vMotion This lesson discusses the following storage requirements for vMotion: VM must NOT be connected to an internal vSwitch Must NOT be connected to any external devices (CD ROMS, Floppys) Must NOT have CPU affinity configured VM swap files MUST be accessible or creatable from destination host RDM MUST be...
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Video Description
Lesson 3 part 2. Storage requirements for vMotion This lesson discusses the following storage requirements for vMotion:
-
VM must NOT be connected to an internal vSwitch
-
Must NOT be connected to any external devices (CD ROMS, Floppys)
-
Must NOT have CPU affinity configured
-
VM swap files MUST be accessible or creatable from destination host
-
RDM MUST be accessible from target host
The source and destination host MUST have the following: - Visibility to all the storage
-
Gigabyte (GB) network
-
Identically named port groups (remember they're case sensitive)
-
Compatible CPU
Video Transcription
00:04
welcome to part two of Lesson three. So we left off just about to talk about the requirements for the motion. Well, actually, look at the requirements for storage the motion in the next portion of this lesson. All right, so a lot of a long list of requirements here,
00:20
one of the big ones right off the top is the VM was not be connected to an internal switch,
00:27
and internal switch
00:29
is useful in a sexy environment.
00:33
But that means that I've got V EMS that are connected to a switch
00:36
and some other V ems that are connected to that switch. And they can communicate to each other
00:41
on that internal switch
00:43
that's called internal when there are no up links. Once you add an up link, which is a,
00:48
um,
00:49
physical adapter on the host now that becomes a external switch so it can communicate with the network outside of the host itself.
00:58
So in order for this to work, the VM must have a connection to a switch that has up links.
01:04
Otherwise, there's no way to communicate with the other host.
01:08
No external devices are possible for the emotion.
01:12
So
01:14
when you when you try the motion. You might get an error warning
01:18
because your seedy Ron Drive is connected to a nice old file, for instance,
01:22
or you've got a USB controller that's connected. So all those must be disconnected
01:26
so that you don't have any external devices to allow the VM to move freely to the other. Host would know nothing binding it or holding it back.
01:37
CPU affinity must not be configured.
01:41
This is something we haven't really talked about yet.
01:44
But the fact it's a way for
01:47
for a V M to be given a rule that says that it should run on a particular CPU within the host.
01:53
And you could do some load balancing that way to say that I want VM one to run on CPU core number one. I want VM two to run in Seaview Court number two,
02:02
and that way you manually divide. Those are split those apart.
02:07
That's not possible in the demotion context, so that must be disabled.
02:13
We also have to think about the swap file.
02:16
That's what files usually stored with the B M in the same folder.
02:21
That's typically the way you you would do that. However, you can make your swap file on SSD disc and have it on another data store if you wish.
02:30
In that case, then you have Thio undo that change so that the swap file is accessible to both hosts.
02:38
Source Host obviously can access access to swap fall, but the destination host must be able to see it as well.
02:46
If the destination host can't see that the swap pilot must have at least the ability to create a swap file on this storage that the VM is using.
02:55
So a couple of little Gotsch is there
02:58
also related to a source in destination hosts. We have to think about what raw device map ings
03:05
mean. Those must be accessible from both hosts as well in order for a demotion to work.
03:10
So as far as things that both hosts must have sources destination hosts
03:15
visibility to all the storage. Kind of talked about that here
03:20
and I could have 128 concurrent migrations per data store,
03:24
so the day of store doesn't necessarily care how many hosts are connected to it. This is the data store limitation, not a host limitation.
03:34
But in any case, you could do a 128 of these at the same time
03:38
between your various different hosts that are connected to a single data store. It's pretty amazing bit of capability there.
03:46
If you have a gigabit network,
03:49
that's the minimum requirement you can do. Four,
03:53
uh, the emotions that at one time, if you have a 10 kicking butt
03:55
network, you can do eight the emotions at the same time.
04:00
So keep that that that limitation in mind
04:03
support groups. This is another thing that can be a real problem when your first working with the motion
04:10
if I have a source host in the destination, host
04:13
the port groups that the VM czar resigning on must be identically named
04:18
cased. Sensitive names do matter here.
04:21
So if you're if you're using a naming convention
04:25
for your source house, make sure you follow that for the destination host. Otherwise, your emotional will not be possible. It will fail,
04:32
and then we have the CPU compatibility to consider
04:36
the E V C is enhanced the motion compatibility. Some
04:42
CPU architectures support this and you'll see that as an option when you're doing your demotion to either disable EVC or enable it for a M D systems or enable it for Intel systems. So you have some choice. Is there to think about
04:57
speaking about CP use? There are constraints with CP years themselves.
05:02
So if we think about the characteristics here, our clocks be the amount of cash, the number of processor cores.
05:11
We don't need an exact match
05:14
when doing the motion
05:15
that that's really important.
05:17
That means I can have to host that are fairly similar, but don't have to be exactly a perfect match.
05:23
And the reason why is because of Ian Colonel. The hyper visor virtual ises
05:29
these characteristics so that their exact match is not required.
05:33
However, the manufacturer, whether it's Andy or Intel and the family
05:39
Pentium four opt around. For instance,
05:42
this must be an exact match,
05:44
and the reason for that is because different manufacturers and different process her family's from the same manufacturer have different instruction sets,
05:51
and you need to have an exact match for the instruction set
05:56
between the source and destination host. If the machine is up and running.
06:00
If that if that's not there, that the or the compatibility is not there than the V motion won't be possible
06:06
We also have multimedia instructions. S S E three s s s C three s s e forgot one.
06:15
Just like the other instruction sets. We need to have an exact match
06:18
because your multimedia applications
06:23
are using those instructions sites and they need to have an exact match if they require those. Since the VM is up and running
06:30
going back to the previous part of the lecture If the VM was cold migrated
06:34
meaning it's powered off, then these requirements wouldn't wouldn't be here because you're you're booting up on the other host.
06:42
Since the PM's running, we have a lot more restrictions.
06:45
There's also a virtual ization hardware assist
06:48
characteristic for your CPU.
06:51
If you put your host and go into the BIOS mode,
06:56
usually it's under the advanced CPU settings. You'll see a virtualization hardware assist enable disabled.
07:03
If if that is a,
07:05
um
07:06
ah, 32 bit bm that you're trying to be motion, I don't need to worry about this matching. If it's a 64 bit
07:14
BM
07:15
and it's running on Intel processor, that match must be there. So keep that in mind.
07:20
So 32 bit one could be virtualized. But at 64 bit level
07:26
until uses the virtual ization technology. If it detects that that that's enabled, then you must have an exact match in order for the demotion toe work.
07:35
And the last item is the execution disable, otherwise known as the Annex X d bit.
07:43
This is something that must match, but you can customize it,
07:46
and we don't go into that level of detail for this course. But you can,
07:51
uh,
07:51
make some changes to the way that that *** gets expressed in the CPU.
07:57
Ah, configuration. That's more of an advanced setting to consider.
08:01
The reason why is because the guest, alas, might detect the fact that the extract Steven is exposed or hidden,
08:09
and therefore the requirement is for that to be matching.
08:13
So this bit
08:15
when we hide that bit,
08:16
which which might be done in in certain cases, this is done because it enhances the motion compatibility between the hosts.
08:26
If that bin is exposed,
08:28
then both hosts sourcing and destination must have it exposed. You can't hide it on one and then exposing on the other that would cause the motion compatibility issues.
08:39
And then our last
08:39
item is VM, where provides a CP identification utility that you can download from Vienna where dot com
08:48
and that will run on your host and display all of the relevant parameters that we've been talking about here.
08:54
And you come running on the other host and just play those parameters and compare the two and make sure that they match up.
09:03
Okay, so the last thing to talk about is
09:05
how do you verify
09:07
that your VM is compatible before you,
09:11
uh, try to do of emotion?
09:13
One thing you could do is go to your
09:16
your maps tab
09:20
and look at the V m, the networking and the hosts
09:24
to see how they're connected.
09:26
So in this example, I've got VM one here. It's connected to the production network.
09:33
I've got two hosts. They're also connected to the production network,
09:35
and I have to host that are also connected to the same shared storage.
09:39
So, based on the requirements of doing of emotion, this map is showing that VM one should be able to
09:48
to move between those hosts
09:50
and share that storage.
09:54
So this
09:54
this is sort of a validation Check
09:56
if you're getting errors when you're when you're looking at your when you're attempting to do with the motion
10:03
in the compatibility pain at the bottom of the interface, when you're doing the emotion, you'll see those airs pop up.
10:09
It might be something that says that
10:11
you don't have
10:13
access to the shared storage, for instance,
10:16
or maybe one of the hosts
10:18
is not connected to this network, so you'll see messages of that nature
10:24
If you get a warning,
10:26
which will be a ah, yellow triangle
10:30
versus a red
10:31
diamond.
10:33
A warning is something that you can actually safely ignore for purposes of the motion of the motion will still succeed,
10:41
although you should probably try to address the warning if you can, in order to improve the efficiency of doing of emotion.
10:50
All right, so we've talked about the demotion requirements,
10:52
some of the concurrency limitations here
10:56
and quite a few of the CPU constraints
11:00
for doing the motion,
11:01
then had a glance. How using your maps
11:05
function within your within. These fear gives you extra information about
11:09
what's what's possible to do with of emotion.
11:13
All right, so stay tuned for the third part of less than three. Thank you
Up Next
Similar Content
