After setting up the lab with two ESXi 4.1 hosts, I failed to vMotion VMs from one host (Dell PE2950 Xeon E5335 @2GHz) to the other (Dell PE2950 Xeon 3.20GHz). The first error I got is below on 'eax'.
Then I shut down the VM and went to change the eax value in Level1 to the exactly the same value in the image.
Tried to vMotion again and got the 2nd error on ecx. Then I repeated the process to change the value on ecx in level1.
Then vMotion worked!!!!
Subscribe to:
Post Comments (Atom)
Azure MFA NPS extension stopped working due to expired certification
Users complained they were unable to log in VMware Horizon Client portal and the logon stuck at "Authenticating...." screen. So I...
-
This has been a frequent seen issue in our environment. The common symptoms are: After a Word or Excel file open, or when trying to save...
-
Users complained they were unable to log in VMware Horizon Client portal and the logon stuck at "Authenticating...." screen. So I...
-
Recommended by a very knowledgeable Xerox technician - perform this procedure once a month Unplug both Ethernet and power cable for 5 fu...
No comments:
Post a Comment