Skip to main content

CPU compatibility override for VMotion

To do a fast POC, we did :

  • Pick all test boxes and VM'ed them one by one: time taken 3 days!
  • Take a cat 5e cross cable and setup your VMkernel port traffic
  • Do trunking, or as your Net admin to do so; we had DMZ and Secure VLANs
  • Setup a seperate DL 320 box for Virtual Center 2.0.1 and VMware Converter
  • CPU problems for VMotion we fixed as below

This applies specifically for HP G4 (regular dual socket xeon boxes) machines and G5 (typical multicore boxes)! so please don't just do it and DO NOT EVER DO THIS IN PRODUCTION! Your production machines must comply with the compatibility since this you need to do for every VM and that is not the right way to go ab out it, we did this just for a fast POC:




and voila, you can do and demo VMotion to your management!

Also check this important KB articles which John Troyer points to.
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more