Installing HMC in VirtualBox or VMWare - AIXWiki

Size: px

Start display at page:

Download "Installing HMC in VirtualBox or VMWare - AIXWiki"

Douglas Austin
6 years ago
Views:

1 1 z :42 Installing HMC in VirtualBox or VMWare From AIXWiki In the instructions below I will explain how to install the Hardware Management Console Software into a Virtual Machine. This should also work for VMWare but the instructions are based on VirtualBox. The instructions is based on the latest HMC version available at the time of writing, which is HMC v7.7 (with Service Pack 1). At the end of the page you will find the modified files for HMC v7.7 (SP1). 1. Download HMC recovery images from Fix Central: Product Group: System p Product: Firmware and HMC Processor type: POWER5 and POWER6 class Machine Type-Model: 9117-MMA (Power6-570, does not really matter.) Fix Type: HMC Firmware HMC firmware release levels: V7R7.1.0 Download: HMC V7R7.1.0M0 - MH01205 HMC V7R7.1.0M1 - MH01213 Do NOT download: Mandatory efix for HMCV7R710 - MH01214 (Service Pack 1 superceeds this efix) Download using DownloadDirector or FTP. You will get the following files: HMC_Recovery_V7R710_1.iso HMC_Recovery_V7R710_2.iso HMC_Update_V7R710_SP1.iso 2.Download latest Knoppix version (v6.2 at the time of writing)

2 2 z :42 KNOPPIX-ADRIANE_V6.2CD EN.iso ftp://ftp.knoppix.nl/pub/os/linux/distr/knoppix/ 3. Download & Install MagicISO and enter license code (v5.5 Build 0281 at the time of writing) Download and install latest VirtualBox (v3.1.6 at the time of writing) 5. Create a Linux Profile with at least 512M of memory wilmette kochman ( and IDE controller (1024 MB RAM recommended like original HMCs). Name: HMC Operating System: Linux Version: Linux 2.6 Memory: 1024 MB (Recommended, 512 MB minimum) Harddisk: Dynamic, 160 GB (Installed HMC size is 12-13GB (with SP1)) Controller: IDE (default in this profile) 6. Extract the file initrd.gz from first HMC install-dvd using MagicISO (or WinRAR, 7-Zip): CDROM:/isolinux/initrd.gz to a local directory. 7. Add Knoppix to VirtualBox and boot Linux 2.6 from this ISO. 8. Start sshd and transfer initrd.gz from the local computer to the virtual computer: Choose Option 10: Shell Run the following commands to start sshd: su - /etc/init.d/ssh start Check the IP-address of Knoppix: ifconfig -a

3 3 z :42 In our case: Set root password: passwd Enter 'abc123' twice. 9. Modify initrd using Knoppix. Copy the file initrd.gz using a SCP-client to the IP-address of virtual machine. Use account login: root with password 'abc123'. Be aware that you might not be able to connect when the network adapter of the virtualbox is not set to Bridged Adapter or Host-only Adapter. Bridge Adapter is the most useful especially if you want to be able to connect to real POWER-systems. If you did not specify the target directory then your file will be transferred your home-directory (in our case gunzip the file and mount it: gunzip /root/initrd.gz losetup /dev/loop0 /root/initrd mkdir /mnt/initrd mount /dev/loop0 /mnt/initrd Go to /opt/hmc/bin of initrd, which is in this case: /mnt/initrd/opt/hmc/bin Please edit the file 'Install' within this directory using vi or nano. Add the following line (line-number 22): VPDINFO="7042CR4" Between CMDLINE=`cat /proc/cmdline` And cd / It should look like this: FILES="bzImage initrd.gz disk1.img disk2.img disk3.img" CMDLINE=`cat /proc/cmdline`

4 4 z :42 VPDINFO="7042CR4" cd / case "$VPDINFO" in Save the file (:wq! in vi) and repack initrd (umount, gzip): cd umount /mnt/initrd losetup -d /dev/loop0 gzip /root/initrd Then, copy the file back to your workstation using scp/winscp. 9. Modify first HMC install-dvd using MagicISO: HMC_Recovery_V7R710_1.iso Remove the original initrd.gz: CDROM:/isolinux/initrd.gz And add the modified version you just copied over from the knoppix-virtualbox. Use 'Save As..' to save the modified iso (HMC_Recovery_V7R710_1_modified.iso for example) 10. Boot from the modified dvd and install HMC v7.7. After the installation you will be prompted for a login. Enter the default hmc username/password: hscroot/abc123 Now, you can get root access using 'su -'. The password is 'passw0rd'. 11. Change the start-up check file 'gethmcvpd' using nano or vi. vi /opt/hsc/bin/gethmcvpd Comment out line 5: # /usr/sbin/dmidecode --string bios-version sed -e 's/-\[//g' sed -e 's/\]-//g' And this add line under line 5: echo "2AKT51A" Comment out line 31: # echo "$cmodel$mtype*$sn" And add under this line:

5 5 z :42 echo "7042CR4* A" Comment out line 34: # echo "$cmodel$mtype" And add user this line: echo "7042CR4" Save the file and reboot using the command 'reboot'. 12. Once your HMC is started, configure it. Logon using hscroot/abc123. You can install the service pack (HMC_Update_V7R710_SP1.iso) without any checks. What about XF86Config? Well, it seems not to be needed for VirtualBox. It is possible that it is needed for VMWare but I did not test this. Download modified files HMC v7.7 For the people that were not able to modify the files using the instructions above or for the ones that are just to lazy, download here ( the modified files for HMC v7.7. Special thanks to the pseriestech.org forum and all contributors to thread: Running HMC in VMware ( Without them it would have been more difficult to get HMC v7.7 working in VirtualBox. For the people who get "A critical error has prevented normal HMC startup. Please reboot the HMC and try again. If the problem persists, contact your support personnel. 1901: HMC Startup aborted due to a malfunction of a required module."

6 6 z :42 As far as I understand in the last release (R7.1.0) or can be last build of this release, VPD check is not only using the script /opt/hsc/gethmcvpd, but also the class of ccfw.jar (/opt/ccfw/ccfw.jar). Which directly calls dmidecode from the java code. GetInfo (com/ibm/hwmca/fw/util/getinfo in ccfw.jar) class formed file /opt/ccfw/data/pciinfo /sys_info.out, which is used to validate the hardware. In the log file /opt/ccfw/ccfw.out we see an error "Java.lang.StringIndexOutOfBoundsException at java.lang.string.substring (String.java: 1092) at com.ibm.hwmca.fw.managed.hmc.getvpdinfo (HMC.java: 1358) at com.ibm.hwmca.fw.managed.hmc.getbiosmachinetype (HMC.java: 1088)... " indicating that improper handling of type String. This error arises from the fact that the "dmidecode - string system-product-name"/"dmidecode - string bios-version" returns are not what is expected. Accordingly, the need to give what is expected of us. For those with an error can help the following decision: 1) Move the original dmidecode cd /usr/sbin mv dmidecode dmidecode.orig 2) Create a script named /usr/sbin/dmidecode with this content: #!/bin/bash DMIDECODE=/usr/sbin/dmidecode.orig if [[ "$2" == "bios-version" ]] then echo " " elif [[ "$2" == "system-product-name" ]] then echo " " else $DMIDECODE "$@" fi 3) Make the script executable chmod +x dmidecode 4) Reboot the HMC. I've tested this solution on VMWare Server and old SuperMicro server. P.S. Please, someone correct my grammatical mistakes ) I think I found an easier way to install in Virtualbox, I used r64453 for

7 7 z :42 windows. >Download the in code from fix central >Create a linux VM in virtualbox (I used generic linux 2.6) > 1gb memory, 64bg disk Edit the XML file located, in windows xp, at: C:\Documents and Settings\<your user>\.virtualbox\machines\<vm name> In the <ExtraData> section add the following to fake out the HMC code. It will think the VM is now a 7310-CR3 :-) <ExtraDataItem name="vboxinternal/devices/pcbios/0/config/dmisystemproduct" value="7310cr3"/> <ExtraDataItem name="vboxinternal/devices/pcbios/0/config/dmisystemvendor" value="ibm CORPORATION"/> "not sure the second line is needed" you could probalby add more "pcbios" options but less is always better. I added a second ethernet to the VM config after the initial install But the best thing is that I did not have to muck around inside of the.iso files. Bryan Thx Bryan, it is so easy, but... In the new version of VirtualBoxes the path is different: C:\Documents and Settings\<your user>\.virtualbox\virtualbox.xml Must be switched off all virtual machines - sleeping/standby is also not good. Exit from the software, save a copy from the xml file, modify the original, save and try. That is all, I hope it helps for someone. Laksi Bryan- This procedure is genius. Thank you. I would like contribute a little to this body of work: July 30, 2011: I successfully installed HMC into a 32-bit virtual machine on a VMware ESXi 3.5 build server. I used the following images from ibm.com: MH01255: HMC Recovery V7R730 MH01256: HMC Update V7R730 HM01257: HMC Mandatory efix V7R730 When initially creating the VM profile, I selected 'Other 32-bit linux' and among other

8 8 z :42 things, 'Flexible' ethernet adapter type. Unfortunately, the 'Flexible' adapter type doesn't work with this procedure and there are no other options available to you in the GUI. To get around this, I had to change the ethernet adapter type to 'e1000' by editing the.vmx file directly. 1. After creating the initial VM profile using the vsphere client, remove the VM from the inventory (don't delete from the disk). The reason for this step is you will want to force VMware to re-read the profile later after editing the profile manually. Right-click on the VM and select 'Remove from Inventory' 2. Log in as root to the local ESXi console or connect to it via ssh. 3. cd into the directory where the HMC VM's files are located and edit the.vmx file with vi. In my case, cd /vmfs/volumes/datastore1/hmc-vm vi hmc-vm.vmx 3. Add the following entry to the.vmx file and save it, adjusting for the actual ethernet# you have created. If you only have one ethernet, then ethernet0 is correct for you. ethernet0.virtualdev = "e1000" 4. Add the VM back to the inventory. Back on the vsphere GUI, click on the Vmware host name in the upper left of the GUI. Click the server's Configuration tab and then its Storage hardware item. In the Storage pane, right-click on the datastore where you have stored the VM profile and select 'Browse Datast In the datastore browser, navigate to the VM's profile directory and locate the.vmx file. Right-click the.vmx file and select 'Add to Inventory' 5. Done. Now proceed to Bryan's procedure. One last note, I got the error that Bryan mentions at the end of his procedure regarding dmidecode. Following Bryan's dmidecode bypass procedure cleared that up. -Henri I recently tested initrd procedure with and work ok. Also, after reboot you get only restriced shell So, comment the "set -r" command to get rid of restricted shell cd /opt/hsc/data/ssh/ chmod 755 hmcsshrc vi hmcsshrc

9 9 z :42 Add # before "set -r" -Mr.Toth Retrieved from " Category: Tutorials This page was last modified on 12 July 2012, at 16:05.

Reset the Admin Password with the ExtraHop Rescue CD

Reset the Admin Password with the ExtraHop Rescue CD Published: 2018-01-19 This guide explains how to reset the administration password on physical and virtual ExtraHop appliances with the ExtraHop Rescue