While running VMs, they would be in locked states, when we are converting a VM server image to Esxi image, we would have difficulties (suspended mode, etc2).

For example, I want to convert a VM server image, using VMware Converter standalone, and i’ve got error. What i did to resolve this is to remove two lines from the virtual machine config file (.vmx):

checkpoint.vmState = “dgrand-vm.vmss”
extendedConfigFile = “dgrand-vm.vmxf”

and try to convert again, now this should settled the problems.

P/s:

To download VMware Converter, simply go to the download link . if already have vmware account, download it and install.

Loading and converting :

Convert to target destination:

Warning, you may have seen this in other websites. This is for my personal notes.

Usually, when we are in a server, we don’t really know if we are in physical or virtualized environment (except we already know).

This is to detect whether we’re in virtualized environment or not :

salawank@ubuntu:~$ ( dmesg; lsmod; prtdiag; modinfo -0; sysdef; ) | grep -i vmware
[ 0.000000] ACPI: SRAT 0000000041ef07f6 00080 (v02 VMWARE MEMPLUG 06040000 VMW 00000001)
[ 1.470135] ata1.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33
[ 1.510687] scsi 0:0:0:0: CD-ROM NECVMWar VMware IDE CDR00 1.00 PQ: 0 ANSI: 5
[ 3.420736] scsi 2:0:0:0: Direct-Access VMware Virtual disk 1.0 PQ: 0 ANSI: 2
[ 3.421765] scsi 2:0:1:0: Direct-Access VMware Virtual disk 1.0 PQ: 0 ANSI: 2

or just simply :

$dmesg | grep -i vmware
$dmesg | grep -i virtual

or :

salawank@ubuntu:~# dmidecode | egrep -i ‘manufacturer|product’
Manufacturer: VMware, Inc.
Product Name: VMware Virtual Platform
Manufacturer: Intel Corporation
Product Name: 440BX Desktop Reference Platform
Manufacturer: No Enclosure
Manufacturer: GenuineIntel
Manufacturer: GenuineIntel

or :

salawank@ubuntu:~# dmidecode | egrep -i ‘vmware|virtual’
Manufacturer: VMware, Inc.
Product Name: VMware Virtual Platform
Serial Number: VMware-56 4d a7 a1 10 59 2a e7-76 16 97 8a 38 5d 6e 1c
VME (Virtual mode extension)
VME (Virtual mode extension)
Description: VMware SVGA II
String 2: Welcome to the Virtual Machine

or;

salawank@ubuntu:~# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02

there are many other ways, this is some of it.

vSwitch within two different network dilemma :

Let say we have 2 different network,

network A = 192.x.x.x network

network B = 10.x.x.x network

vSwitch can be considered as physical layer 2 switch. Hence, how you isolate those two network, depends on your vSwitch.

However, since vSwitch is layer 2 switch, it’s clearly only can do network isolate via ip address instead software layer like vlan & etc which require layer 3 switch.

So, do u need another vSwitch for 10.x.x.x network?

First, no need if 10.x.x.x is only for virtual machine network and 192.x.x.x network sharing same physical layer 2 switch

Second, yes u need, if you need to manage your ESXi from both network (192.x.x.x and 10.x.x.x)

Not only vSwitch, but also secondary service console for management purposes via vi-client

greetz athlon_crazy

Hi, today i’ve learned new thing regarding vmware esxi 4.

If we open the Vmware vSphere client, go to Home -> Inventory -> HOST (Vmware esxi 4 host) -> Configuration -> Networking, by default the network is set up in Virtual Switch : vSwitch0. There we can see our network adapter card (e.g vmnic1) attached with the network.

So here’s my problem statement,
I have one network using ip 192.x.x.x and another network using 10.x.x.x .. My esxi 4 machine is configured with IP 192.x.x.x. IP 192.x.x.x is segregate with IP 10.x.x.x. Which means both IP can’t “see” each other.

In the esxi, there are bundles of virtual machine running, and I want to set 1 virtual machine (ubuntu) that host a web server to be accessed via both network (192.x.x.x and 10.x.x.x).

Method,
To do this, I set up additional LAN cable to be attached with another physical adapters/network card (e.g vmnic2).

Then, in vSphere client, go to Add networking -> Virtual Machine -> Create a virtual switch and choose your second network interface. The output is as follow..

Then next step is add another virtual network interface to the virtual machine. go to Edit settings and add another network adapter and choose Network connection -> network label.

Finally, fire up the virtual machine, you will see new network card added (eth0, eth1). eth0 is for 192.x.x.x, eth1 for 10.x.x.x. Issue ifconfig -a | more

Make sure to check the mac address of eth1 with vmimage in the vSphere client. If it is match, we are good to go..

greetz yomuds, hafiz, athlon crazy

Hi and salam,

Recently, I’ve posted my starting project / work on configuring / installing / managing VMWare ESXi 4 . Prior to my knowledge, I don’t know / maybe not enough search / any client based such as vSphere Client that is used on Windows platform, that can be used on gnu/linux base. What I know is using the vSphere Remote Command Line (RCLI) on gnu/linux, and that is quite tedious compare to the GUI – application vSphere Client. This post is about VMware Remote console plug-in, that is quite cool for me

While finding the way to install Vmware Server 2.0.2 x86_64 on Ubuntu 9.10 64bit, I’ve stumbled upon a bash script vmware-client-start.sh that is used to login into vmware server.. Maybe this is something that Vmware expert already knows, for a newb like me, I just know that script can also be used to login into an ESXi 4 server. It stated in the login popup that this can also be used to login into Vmware ESX 3.0, Vmware VirtualCenter 2.0, Vmware Server 2.0 or any later version of this products.

Bash script (Not by me) :

#!/bin/bash
################################################## ##############################
# Call VMWare Server’s Remote Console in a clean GTK setup.
################################################## ##############################

# Clean GTK setup for VMWare

export VMWARE_USE_SHIPPED_GTK=yes
export GDK_NATIVE_WINDOWS=true

# Find console executable in Firefox plugins.
vmrc=”$(find “$HOME/.mozilla/firefox” -name vmware-vmrc -type f -perm -111 | tail -1)”
[ -x "$vmrc" ] || exit 1

VMLIB=$(dirname “$vmrc”)
VMLIB=$(dirname “$VMLIB”)/lib

export LD_LIBRARY_PATH=$VMLIB/libexpat.so.0:$VMLIB/libsexymm.so.2:$VMLIB/libview.so.2:$VMLIB/libvmwarebase.so.0:$VMLIB/libvmwareui.so.0:$VMLIB/libgvmomi.so.0

set -x
cd “$(dirname “$vmrc”)” && “$vmrc” -h 192.168.1.2:8333

We can change the IP address for our own IP addresses / servers.

The script / plug in can also initiate multi login , to multi OSs and multi servers. Some of the screenshots:

Login page:

Snapshot below is for guest OS hosted in VMWare ESXi 4:

Multi login different server:

##P/S : VMware Remote console plug-in is not a VMWare vSphere Client.

##PP/S: This script does not support Vmware Server 1.xxx version

Hi there,

Recently, I wanna try to install the new release of Vmware Server on gnu/linux base which is Vmware Server 2.0.2 64bit on Ubuntu 9.10 x86_64
After download and extract it from the Vmware site , I’ve got several error
while issuing ./vmware-install.pl as below :

make[2]: *** [/tmp/vmware-config3/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config3/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic’
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config3/vmmon-only’
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please
visit our Web site at “http://www.vmware.com/go/unsup-linux-products” and
“http://www.vmware.com/go/unsup-linux-tools”.

Execution aborted.

This seems to happen for the 64bit version of Ubuntu 9.10 (or is it the vmware server itself?), I don’t know for other brand of gnu/linux out there whose based on 64bit arch.
After googling for a while, I’ve found solution on one of the blog here .
But the tuto or the solution is for Vmware server version 2.0.1 ,and I desperately in need of a VM server in my workplace for some testing, so I downloaded the Fix from the site here .

After download, extract and put it into vmware-server-distrib (the one we have extracted from Vmware-Server 2.0.2 version) directory.
Go into the directory “vmware-server.2.0.1_x64-modules-2.6.30.4-fix” and run the command:

sudo ./vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh

Just leave it run… until it finish.

Then as usual, open our browser, https://127.0.0.1:8333/

If you have any problem(s) with mouse / keyboard etc2.. just simply use this VMware Client. It’s easy, input the IP:Port (127.0.0.1:8333) and username / password.

In conclusion, this fix works also for the Vmware Server 2.0.2 x86_64.

In VmWare ESXi 4, VMWare Inc has apparently restricted Remote Command Line Interface (RCLI) administration of the free version of ESXi. The write permission are not possible since we need to upgrade it to full licensed one. This simple tuto is to enable the snmp via rcli

The VSphere Client 4.0 cannot enable/configure snmp on the VmWare ESXi 4. I’ve found that we can enable/configure snmp on Vmware ESXi 4 through the RCLI (remote command line) that are available on Windows and Linux.

Download the RCLI application from the vmware site and install it.

After that, open the Vmware Vsphere CLI.
To start configure, type in the console(in this example, my ESXi IP is 192.168.117.116, destination is 192.168.117.115:

vicfg-snmp.pl –server 192.168.117.116 -c public -t 192.168.117.115@162/public

insert the esxi username and password.

To enable it type:

vicfg-snmp.pl –server 192.168.117.116 -E

To show config:

vicfg-snmp.pl –server 192.168.117.116 -s

To test configuration:

vicfg-snmp –server 192.168.117.116 -T

I have encountered issue with free licensed esxi since it gaves me this error in the first attempt. This is because the write permission has been disabled on the free version:

“Failed : fault.RestrictedVersion.summary”

But, there is a trick where we can write the configuration file:

Go to VMWare Vsphere Client -> Configuration -> Licensed Features -> Edit-> Change to evaluation mode, No License key (if u have not registered/no license, this shouldnt be a problem).

When you have change it, go back to RCLI and try again the first command. This should settle the read/write permission and you can set/configure snmp on Vmware esxi4.

p/s: if error still occur, try rebooting the hosts.

Example below are the configuration:
C:\Program Files\VMware\VMware vSphere CLI\bin>vicfg-snmp.pl –server 192.168.117.116 -s
Enter username: root
Enter password:********
Current SNMP agent settings:
Enabled : 1
UDP port : 161

Communities :
public

Notification targets :
192.168.117.115@162/public
——————————————————————
then, try to snmpwalk from another host:

$snmpwalk -v1 -c public 192.168.117.116
SNMPv2-MIB::sysDescr.0 = STRING: VMware ESX 4.0.0 build-181792 VMware, Inc. x86_ 64
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.6876.4.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (15501613) 1 day, 19:03:36.13
SNMPv2-MIB::sysContact.0 = STRING: not set
SNMPv2-MIB::sysName.0 = STRING: VMserver.localdomain
SNMPv2-MIB::sysLocation.0 = STRING: not set
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
————-more————-

After we have finished setting up the snmp, we can insert back in the VMware VSphere Client our licensed that have been registered with the VMWare ESXi 4.

done.