Anonymous_User Absent Member.
Absent Member.
2464 views

VMware CPU id mask

Anyone ever set up masks to hide/enable cpu capabilities within vmware?

We have 4 hosts for our VDI setup, I'd like to get VMotion working
between all 4. Currently if you're trying to VMotion between the two
older ones to the two newer ones, it cannot be done w/o powering the VM
down due to CPU 'incompatibilities'. Certain portions of the cpu id
mask can be 'hidden' from the VM to allow for easier VMotion.

Any help on this would be greatly appreciated.

--
Stevo
Labels (1)
0 Likes
4 Replies
bpenris1 Absent Member.
Absent Member.

Re: VMware CPU id mask

Stevo;2178343 wrote:
Anyone ever set up masks to hide/enable cpu capabilities within vmware?

We have 4 hosts for our VDI setup, I'd like to get VMotion working
between all 4. Currently if you're trying to VMotion between the two
older ones to the two newer ones, it cannot be done w/o powering the VM
down due to CPU 'incompatibilities'. Certain portions of the cpu id
mask can be 'hidden' from the VM to allow for easier VMotion.

Any help on this would be greatly appreciated.

--
Stevo

http://www.vmware.com/files/pdf/vmotion_info_guide.pdf

Wouldn't it be easier just enabling EVC in your cluster?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: VMware CPU id mask

bpenris sounds like they 'said':

> Wouldn't it be easier just enabling EVC in your cluster?


So my response to bpenris's comment is...

Yeah, we figured out what we needed to do for that. We didn't realize
we needed to have *all* VM's shut down on these hosts to do that.

--
Stevo
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: VMware CPU id mask

Stevo wrote:

> bpenris sounds like they 'said':
>
>> Wouldn't it be easier just enabling EVC in your cluster?

>
> So my response to bpenris's comment is...
>
> Yeah, we figured out what we needed to do for that. We didn't realize
> we needed to have *all* VM's shut down on these hosts to do that.
>


I take it you have an Essentials License so you have vCenter?
for vMotion to work when VMs are up, its a requirement

Also consider the following:

network setup, all separate subnets

vmk0 Management Network -- on vSwitch0 (standard switch) -- on uplink vmnic0

vMotion network -- on vSwitch1 (standard switch) -- on uplink vmnic1

storage if iSCSI -- on vSwitch2 (standard switch) -- on uplink vmnic2

VM network -- on vSwitch3 (standard switch or dvSwitch/Cisco Nexus 1000v) --
on uplink vmnic3 through how ever many you can aggrigate together


0 Likes
Highlighted
bpenris1 Absent Member.
Absent Member.

Re: VMware CPU id mask

Harv, TSE, GSS, VMware;2187989 wrote:
Stevo wrote:

I take it you have an Essentials License so you have vCenter?
for vMotion to work when VMs are up, its a requirement

Also consider the following:

network setup, all separate subnets

vmk0 Management Network -- on vSwitch0 (standard switch) -- on uplink vmnic0

vMotion network -- on vSwitch1 (standard switch) -- on uplink vmnic1

storage if iSCSI -- on vSwitch2 (standard switch) -- on uplink vmnic2

VM network -- on vSwitch3 (standard switch or dvSwitch/Cisco Nexus 1000v) --
on uplink vmnic3 through how ever many you can aggrigate together

I disagree with that. Just throw all the NIC's on one vSwitch and use VLAN's. I know it's against design regulations but the often heard 'security considerations' are bullocks imho. If you can't trust VLAN's anymore you can't trust anything. Don't use distributed switches for anything more than machines that can afford to lose the network connection. If your vCenter server needs maintenance your distributed switch goes down.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.