Showing posts with label Vmware. Show all posts
Showing posts with label Vmware. Show all posts

Friday, May 10, 2019

Install ESXi 5.1/5.5/6.0 into Mac Mini 3.1 (Later 2009)

It is not new to install ESXi on Mac Mini for technical person . There are lots of benefits to do this. I have been used ESXi 5.5/6 on my Mac Mini 5.1 for many years now. Just recently I have got two Mac Mini 3.1  to play at my home and I was wondering if it is possible to get ESXi on them.

I have two types of Mac Mini 3.1, one is regular with one hard drive and one optical drive. Another Mac Mini 3.1 is server version. There is no optical drive but two hard drive installed.

The result is surprising and working very well although I had a small hiccup on storage adapter. First thing I did is to upgrade the RAM from 4G to 8G which is maximum you can have. You can not start installing process if you only have 4G RAM. I did not try 16G RAM since no one succeed that by googled online. It is enough to get me run 2-3 VMs anyway.

Saturday, February 2, 2019

Install ProxMox 5.3 into VMware Workstation 14

Proxmox VE is a complete open-source platform for all-inclusive enterprise virtualization that tightly integrates KVM hypervisor and LXC containers, software-defined storage and networking functionality on a single platform, and easily manages high availability clusters and disaster recovery tools with the built-in web management interface.

The enterprise-class features and the 100% software-based focus make Proxmox VE the perfect choice to virtualize your IT infrastructure, optimize existing resources, and increase efficiencies with minimal expense. You can easily virtualize even the most demanding Linux and Windows application workloads, and dynamically scale-out your computing and storage as your needs grow ensuring to stay adaptable for future growth of your data center. You can easily use Proxmox VE to control KVM and OpenVZ virtual machines and create a small computing cloud with it.

YouTube Video: Install ProxMox 5.3 into VMware Workstation

Wednesday, June 3, 2015

Cisco ASAv 9.4.1 and ASDM 7.4.1 in Workstation / ESXi (2)

In my previous post "Cisco ASAv 9.4.1 and ASDM 7.4.1 in Workstation / ESXi (1)", I tested the importing both OVA and VMDK file into Workstation and ESXi, but both ways failed. Those files are found and downloaded from Internet for only testing purpose. I believe those are good files and somebody has tested them. The only reason for my failure is because I am not using a right way to do it. In my old testing posts I have tested other versions such as 9.2.1, 8.42 and 8.02. All were successful loaded in either Vmware Workstation or ESXi.

Here are all related posts in this blog:

To find out the why this time failed I searched online again. My searching is based on error message I got from ESXi:
"The OVF package requires support for OVF PropertiesLine 264: Unsupported element 'Property'."

Monday, June 1, 2015

Install Vmware vCenter into ESXi 5.5 and Reset ESXi into Evaluation Mode

VMware vCenter Server provides centralized visibility, proactive management and extensibility for VMware vSphere from a single console.

The easiest way to deploy vCenter server is to use vCenter server appliance, which is a Linux-based virtual appliance used to manage vSphere. Following steps shows the procedures how this virtual appliacne deployed into ESXi environment.

1. Download Software

There are a couple of options you can download.
a. Download .iso file to install vCenter into windows / linux environment.
b. Download .ova virtual appliance to deploy it into virtual environment
c. Download ovf file, vmdk system disk and vmdk data disk to deploy template into virtual environment.

In my lab, I selected single 2g single ova file to download and deploy it into my ESXi 5.5 server.

Cisco ASAv 9.4.1 and ASDM 7.4.1 in Workstation / ESXi (1)

Cisco released ASA Software Version 9.4(x) on March 2015. Thre are some new features from release note in the Cisco website. I am going to give it a try to add it into my testing environment using Vmware workstation or ESXi. Some old ASA versions have been tested in my previous posts:
Here are all related posts in this blog:

Download ASA v 9.4.1

Here are some download links we could find from Internet.
1. Cisco Software Download Site

2. from (Link has been removed)

Problems when importing into Vmware Workstation / ESXi

1. Using OVA file

But When tried to open in the workstation, there is error which says "Line 264: Unsupported element 'Property'."

Tried again in ESXi 5.5, File -> Deploy OVF Template ...
But it seems same error message when tried to open downloaded asav941.ova file.
The OVF package requires support for OVF Properties
Line 264: Unsupported element 'Property'.

2. Using vmdk File

I thought I may use vmdk's file to add them into workstation or ESXi. I did find a vmware package from with following files:

Unfortunately, it does not boot properly into configuration mode. Eventually it will dip into a reboot loop. Captured screenshots with my testing in Vmware workstation and ESXi show all steps below:

2.1. Opened in the Vmware Workstation

 2.2. Since my Vmware Workstation host does not support VT-x, it will not be able to power on.

2.3. Workstation Connect to ESXi

2.4. Upload workstation vm into ESXi. That was successful

2.5. ESXi vm's configuraiton

 2.6. It got into a rebooting loop.

Cause and Solutions:

Please check my next post - "Cisco ASAv 9.4.1 and ASDM 7.4.1 in Workstation / ESXi (2)".

Wednesday, September 24, 2014

Workaround for Windows XP VMware vSphere Client Connecting to ESXi 5.5

Just found the vSphere client is no longer compatible with Windows XP because it uses increased cypher strengths not available in Windows XP when connecting to ESXi 5.5. Later versions of windows will work, and there is a hotfix available for Windows 2003 server machines that fall foul of this change.

1. Symptoms

2. Solutions

Refer to Vmware Support KB:vSphere Client and vSphere PowerCLI may fail to connect to vCenter Server 5.1 and 5.5 due to a Handshake failure (2049143)

On the ESXi 5.1 and 5.5 host, modify the rhttpproxy service to reduce the implied security by allowing the host to communicate using weak cipher suites:

 For ESXi 5.1 and 5.5

  • Connect to the host via SSH. For more information, see Using ESXi Shell in ESXi 5.0 and 5.1 (2004746). For my case, my SecureCRT has to use Keyboard Interactive mode to do authentication to get log into Vmware ESXi 5.5. 
  • Navigate to the directory:


  • Backup the config.xml file. Do not skip this step.
cp config.xml config.xml.bak

  • Open config.xml file using vi editor. For more information, see Editing files on an ESX host using vi or nano (1020302).
  • Add the <cipherList>ALL</cipherList> parameter between the <ssl>...</ssl> section of the configuration file. Use the model below as an example: 

<doVersionCheck> false </doVersionCheck>

  • Save and close the config.xml file
  • Reset the rhttpproxy service for the change to take effect by running the command:

/etc/init.d/rhttpproxy restart

Sunday, August 24, 2014

Workaround for can not Edit Virtual Machine Settings in VMware vSphere ESXi 5.5

After upgraded ESXi to 5.5, some VMs got following screenshot error when tried to edit the configuration.

"You cannot use the vSphere Client to edit the settings of virtual machines of version 10 or higher.

Use the vSphere Web Client to edit the settings of this virtual machine


The solution is to use vSphere Web client. The workaround for me is in following two methos:

1. Change virtualHW.version to 9 or lower

  • In ESXi, Remote VM from Inventory
  • SSH into ESXi
  • cd /vmfs/volumes/datastore1/testvm
  • VI the VM's .VMX file
  • Find the line that says 'virtualHW.version'. Example : virtualHW.version = "10"
  • Change the value to 8. Example : virtualHW.version = "9"
  • Register this VM back into Inventory with command "vim-cmd solo/registervm /vmfs/volumes/datastore1/testvm/testvm.vmx"

2. Use VMware Workstation 

In Workstation, in there VM's manage menu, you can change VM's Hardware Compatbility to Workstation 9.0 or lower, then upload it to ESXi as shown in this post step 7.

OpenWRT in Vmware as a light weight router and virtual host

OpenWrt is a Linux distribution for embedded devices and provides a fully writable filesystem with package management.

Also for me, it is perfect for running OpenWRT as a small router or virtual host in my virtual rack. I was using BSD Router (BSDRP) for this purpose quite a while. Now it seems better one coming.

To make a mark on it, I list all steps regarding how to load it in the vmware workstation.

1. Download the package from
MD5Sums:  a258b7a5787f6bd8c8169391941813f4  

2. Create a vm with following configurations 

almost all are default settings except choosing Other Linux 2.6.x kernel as guest operating systemMemory = 32M
Hard Disk = 52M

Sunday, June 22, 2014

Cisco L2 L3 IOU Rack V5 (newer version from Cisco L2 L3 IOU Rack V3)

I was using Cisco L2 L3 IOU Rack V3 from flyxj for quite a while. Recently found Cisco L2 L3 IOU Rack V5. Not much difference except more devices in it for more complicated topology.

1. Vmware 10 workstation Configuration:

a. Create a custom linux vm with an existing virtual disk in your download file.
 b. Remove other unused hardware such as sounds, printer and usb. Add two more network cards.

2. After vm created, launch this vm. Here are some screenshots:

root /

/etc/issue and /etc/motd can be modified for the banner. 

Cisco L2/L3 I-O-U RackV5
Cisco L2/L3 I-O-U RackV5

3. Change eth0 IP address at /etc/network/interfaces

4. Change Login Banner at /etc/issue and /etc/motd

5. Change SSH Terminal to make it colorful

Wednesday, June 18, 2014

ASA 9.21 in Vmware Workstation 10

There is old post "ASA 8.02 in Vmware Workstation " in this blog posted on Dec 2011. Anothe post "How to Make your own ASA 8.42 in VMware".  Here are all related posts in this blog:

This time I got ASA 9.21 tested.

There are some ASA 9.21 vmware packages from Internet by google-ing:
Downloaded one and hooked it up in the Vmware. It uses 2G memory but little CPU power. Bridge to real network is working perfectly as well. CPU must be 64bit and supporting VT.

Sunday, June 1, 2014

Use Serial Port in Virtual Machines Running on Vmware Workstation and ESXi

1. Using Serial Port in the VMs running at Vmware Workstation

Named Pipe TCP Proxy is the one I am using on my laptop to connect to Named pipe on my Vmware Workstation VMs.  The Configuration looks like following:
  • Virtual Machine's Settings
  •  Named Pipe TCP Proxy's Settings
  •  SecureCRT's Settings

2. Using Serial Port in the VMs running on ESXi

In ESXi, it is already built-in feature for Vms.
  •  ESXi VM's Settings - Near End is set to Com1 and Server mode, waiting windows serial client to connect to it
  •  Windows 7 VM's Settings - There are four serial port added , and Serial port 1 has been set to Com1 as a client.
  •  SecureCRT's Serial Connection setting

Monday, March 10, 2014

My Cisco IOU Racks - from flyxj IOUv3

My Cisco IOU Racks:
- from flyxj

Vmware configuration:

I have modified Interface IP to match my local configuration:
Root password is
Change IOUv3 interface ip command:
[email protected]:~/LAB# ifconfig eth0

This is topology looks like. Totally there are six routers and four switches. Good enough to finish most routing / switching lab.

Enabled R1 and R2. Now it shows green in the topology.

[email protected]:~/LAB# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0c:29:df:93:07
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::20c:29ff:fedf:9307/64 Scope:Link
          RX packets:52 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5397 (5.2 KiB)  TX bytes:908 (908.0 B)
          Interrupt:19 Base address:0x2000

eth1      Link encap:Ethernet  HWaddr 00:0c:29:df:93:11
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::20c:29ff:fedf:9311/64 Scope:Link
          RX packets:141 errors:0 dropped:0 overruns:0 frame:0
          TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13924 (13.5 KiB)  TX bytes:12882 (12.5 KiB)
          Interrupt:16 Base address:0x2080

eth2      Link encap:Ethernet  HWaddr 00:0c:29:df:93:1b
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::20c:29ff:fedf:931b/64 Scope:Link
          RX packets:44 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4843 (4.7 KiB)  TX bytes:468 (468.0 B)
          Interrupt:17 Base address:0x2400

lo        Link encap:Local Loopback
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2014 (1.9 KiB)  TX bytes:2014 (1.9 KiB)

Using Telnet access 10 devices with port from 2001 to 2010. Also IOU3 itself support ssh access.


Thursday, March 14, 2013

How to upgrade Nexus 7K NX-OS Emulator Titanium VMware image to 6.1.1

1. Setup Network Environment for Upgrade

1.1 Configure Mgmt0 IP address under Management VRF

vrf context management
  ip route

interface mgmt0
  ip address

1.2 Setup FTP server on your vmware host which is using 

1.3 Copy files using ftp.

N7K-2(config)# copy ftp://[email protected]/titanium-d1.6.1.1.gbin bootflash: vrf management 

***** Transfer of file Completed Successfully *****    
N7K-2(config)# now saving to 
N7K-2(config)# copy ftp://[email protected]/titanium-d1-kickstart.6.1.1.gbin bootflash: vrf management 
***** Transfer of file Completed Successfully *****    
Copy complete, now saving to disk (please wait)...
N7K-2(config)# dir bootflash:
      16384    Jan 06 19:54:26 2011  lost+found/
      23203    Mar 19 09:35:19 2013  mts.log
   28511744    Dec 22 21:21:57 2010  titanium-d1-kickstart.5.1.2.gbin
   27604992    Mar 19 11:53:16 2013  titanium-d1-kickstart.6.1.1.gbin
   60024194    Dec 22 21:22:00 2010  titanium-d1.5.1.2.gbin
   63184888    Mar 19 11:52:22 2013  titanium-d1.6.1.1.gbin
       4096    Jan 06 19:55:10 2011  vdc_2/
       4096    Jan 06 19:55:10 2011  vdc_3/
       4096    Jan 06 19:55:10 2011  vdc_4/
        784    Mar 19 09:35:46 2013  vlan.dat

Usage for bootflash://sup-local
  294207488 bytes used
 1300668416 bytes free
 1594875904 bytes total

2. Boot with new binaries

N7K-2(config)# boot kickstart bootflash:/titanium-d1-kickstart.6.1.1.gbin
Note: system and kickstart bootvars are pointing to incompatible images
N7K-2(config)# boot system bootflash:/titanium-d1.6.1.1.gbin
N7K-2(config)# copy run start
[########################################] 100%
Copy complete, now saving to disk (please wait)...

3. Booting screen

N7K-2(config)# reload
This command will reboot the system. (y/n)?  [n] y
2013 Mar 19 12:04:36 N7K-2 %$ VDC-1 %$ %PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart from Command Line Interface
SysRq : Resetting

Auto booting bootflash:/titanium-d1-kickstart.6.1.1.gbin bootflash:/titanium-d1
Booting kickstart image: bootflash:/titanium-d1-kickstart.6.1.1.gbin....
.....Image verification OK

INIT: version 2.86 booting
SCSI disk detected.
Enter system maintenance mode? (y/n) [n]: 
Checking all filesystems....r.r done.
Trying to mount cdrom...
hostname: invalid option -- '-'
Try `hostname --help' for more information.
Renaming eth interfaces
  renaming interfaces: eth0 to eth7
Loading system software
Uncompressing system image: bootflash:/titanium-d1.6.1.1.gbin Tue Mar 19 12:05:11 EST 2013
blogger: nothing to do.

..done Tue Mar 19 12:05:14 EST 2013
Load plugins that defined in image conf: /isan/plugin_img/img.conf
Loading plugin 0: core_plugin...
num srgs 1
0: swid-core-titanium, swid-core-titanium
num srgs 1
0: swid-sup1e-ks, swid-sup1e-ks
INIT: Entering runlevel: 3
Mounting other filesystems:  [  OK  ]
Starting NFS statd: [  OK  ]

2013 Mar 19 12:05:53 N7K-2 %$ VDC-1 %$ %COPP-2-COPP_NO_POLICY: Control-plane is unprotected.
2013 Mar 19 12:05:54 N7K-2 %$ VDC-1 %$ %MODULE-2-MOD_UNKNOWN: Module type [0] in slot 1 is not supported

2013 Mar 19 12:05:55 N7K-2 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online 

 Username: admin
 Password: cisco
.N7K-2 login: 2013 Mar 19 12:05:56 N7K-2 %$ VDC-1 %$ %PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module A ok
2013 Mar 19 12:05:56 N7K-2 %$ VDC-1 %$ %PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is clock-A

 Username: admin
 Password: cisco
N7K-2 login: admin
Last login: Tue Mar 19 12:06:04 on ttyS0
Cisco NX-OS Software
Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.
NX-OS/Titanium software ("NX-OS/Titanium Software") and related
documentation, files or other reference materials ("Documentation")
are the proprietary property and confidential information of Cisco
Systems, Inc. ("Cisco") and are protected, without limitation,
pursuant to United States and International copyright and trademark
laws in the applicable jurisdiction which provide civil and criminal
penalties for copying or distribution without Cisco's authorization.
The use of NX-OS/Titanium Software and Documentation is strictly
limited to Cisco's internal use.

Any use or disclosure, in whole or in part, of the NX-OS/Titanium
Software or Documentation to any third party for any purposes is
expressly prohibited except as otherwise authorized by Cisco in writing.
The copyrights to certain works contained herein are owned by other
third parties and are used and distributed under license. Some parts
of this software may be covered under the GNU Public License or the
GNU Lesser General Public License. A copy of each such license is
available at and
N7K-2# sh ver
Cisco Nexus Operating System (NX-OS) Software
TAC support:
Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at

  loader:    version N/A
  kickstart: version 6.1(1) [gdb]
  system:    version 6.1(1) [gdb]
  kickstart image file is: bootflash:/titanium-d1-kickstart.6.1.1.gbin
  kickstart compile time:  12/25/2020 12:00:00 [06/24/2012 00:54:16]
  system image file is:    bootflash:/titanium-d1.6.1.1.gbin
  system compile time:     7/1/2012 0:00:00 [06/24/2012 01:26:13]

  cisco Nexus 7000 Unknown Chassis ("Unknown Module")
--More--2013 Mar 19 12:06:07 N7K-2 %$ VDC-1 %$ %PLATFORM-2-MOD_DETECT: Module 2 detected (Serial number ) Module-Type Titanium Ethernet Module Model 
2013 Mar 19 12:06:07 N7K-2 %$ VDC-1 %$ %PLATFORM-2-MOD_PWRUP: Module 2 powered up (Serial number )
  Intel(R) Xeon(R) CPU         with 2066240 kB of memory.
  Processor Board ID T50569F000C

  Device name: N7K-2
  bootflash:          0 kB
Kernel uptime is 0 day(s), 0 hour(s), 1 minute(s), 27 second(s)

  Core Plugin, Ethernet Plugin