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
Stevo;2178343 Wrote:[color=blue]
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[/color]
http://www.vmware.com/files/pdf/vmotion_info_guide.pdf
Wouldn’t it be easier just enabling EVC in your cluster?
bpenris’s Profile: http://forums.novell.com/member.php?userid=7496
View this thread: http://forums.novell.com/showthread.php?t=452802
bpenris sounds like they ‘said’:
[color=blue]
Wouldn’t it be easier just enabling EVC in your cluster?[/color]
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
Stevo wrote:
[color=blue]
bpenris sounds like they ‘said’:
[color=green]Wouldn’t it be easier just enabling EVC in your cluster?[/color]
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.
[/color]
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
Harv, TSE, GSS, VMware;2187989 Wrote:[color=blue]
Stevo wrote:
[color=blue]
I take it you have an Essentials License so you have vCenter?
for vMotion to work when VMs are up, its a requirementAlso consider the following:
network setup, all separate subnets
vmk0 Management Network – on vSwitch0 (standard switch) – on uplink
vmnic0vMotion 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[/color]
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.
bpenris’s Profile: http://forums.novell.com/member.php?userid=7496
View this thread: http://forums.novell.com/showthread.php?t=452802