Posts Tagged ‘vmware’

Using storcli to create RAID50 arrays

Wednesday, October 29th, 2014

The storcli command line can be installed on linux, vmware, windows and macos to provide management of raid devices on booted ibm 3650.  The MegaRaid GUI provides a guided wizard for RAID50 disk creation, but the storcli command line options aren’t as clear.  It turns out that you must provided an arrangement for the disks in order to create a raid 50 group.  For example:

./storcli /c0 add vd r50 name=446SSDRaid50 drives=9:3-8 strip=128
Controller = 0
Status = Failure
Description = operation not possible for current RAID level, Invalid RAID level

The above fails because it is missing the pdperarray options, which tells storcli how to arrange the disks:

/opt/StorCLI # ./storcli /c0 add vd type=raid50 name=446SSDRaid50 drives=9:6-11  \
pdperarray=3 strip=128
Controller = 0
Status = Success
Description = Add VD Succeeded

Click  here
for some further examples of the storcli command.

Windows 7 and Vmware Server 1.0.10

Friday, September 16th, 2011

I found a neat trick on-line to get windows 7 to recognize the virtual network card it doesn’t have a default driver for in vmware server 1.0.10.  You add the following line to the end of the .vmx config file, and it sees it as an intel e1000 card and installs the correct driver.

ethernet0.virtualDev = "e1000"

This is posted about in a few places, but here is a link to the one I found:

http://social.technet.microsoft.com/Forums/en-US/w7itprohardware/thread/5c74d385-98f9-47c8-962f-b0cfc47abadf

Moving VMware images – ethernet card problems

Wednesday, May 5th, 2010

I had originally seen this error when I copied a vm image to a larger drive – the ethernet interface had a static I.P. but stopped working.  When I created a new interface that worked fine.  This time, I look around on the web to figure out what was happening.  It turns out that the copied images would change the mac address.  Under debian, this would cause the udev system to create a new ethernet interface for the mac address, mapped to ethX (where X is 1 plus the last network adapter it created).  By the time I started it on my new vmware server, I had two ethernet addresses, so it created two new interfaces, eth3 and eth4.  I was using eth1 for networking so changing it to eth4 enabled internet access.

In /etc/udev/rules.d/70-persistent-net.rules is where the information about the ethernet cards and their mac addresses was stored.  I compared this to the information from the .vmx config file for the virtual machine to determine what network card was mapped to each ethX interface.

Vmware server on debian 5 lenny

Wednesday, May 5th, 2010

I’ve found some interesting things out about how vmware server works on debian 5.0 . Apparently there is problem with the vmmon module throwing an error when it is higher than version 138.  Here’s the error message:

[localized] Version mismatch with vmmon module: expecting 138.0, got 168.0

Several fixes on the internet are available, which patch the source for the vmmon module to allow it to compile.  I was successful when I applied the following patch from this link:

http://www.insecure.ws/2008/07/24/vmware-anspecific-specific-557-and-kernel-2626

I applied it after the vmware-any-any-update117d patch I found here:

NEW “How to install VMWare in 2.6.26 linux kernel”

I’m actually sure if the 117d patch was required or not.  Doing a diff on the vmmon source, it appears that thevmware-update-2.26-5.5.7.tgz file adds a little perl function that determines what the vmmon version should be, to deal with the issue above.

Install procedure on fresh debian 5 machine:

  • download VMware-server-1.0.10-203137.tar.gz from vmware
  • install vmware and try to compile (fails since debian is unsupported)
  • apply vmware-any-any-update117d patch
  • get vmmon error
  • apply vmware-update-2.26-5.5.7.tgz patch and it runs