Showing posts with label vmware. Show all posts
Showing posts with label vmware. Show all posts

Thursday, August 16, 2012

VMware Player Virtual Network Editor

Step 1: Extract all the contents in the installer package.
C:\Downloads>VMware-player-4.0.4-744019.exe /e C:.\extract

C:\Downloads>cd extract

C:\Downloads\extract>dir
 Volume in drive C is OS Drive
 Volume Serial Number is 28EB-171D

 Directory of C:\Downloads\extract

15/08/2012  01:40 PM    <dir>          .
15/08/2012  01:40 PM    <dir>          ..
15/08/2012  01:40 PM            24,440 bootstrap.lua
15/08/2012  01:40 PM             2,411 common.lua
15/08/2012  01:40 PM            30,511 keyboard.cab
15/08/2012  01:40 PM         2,855,112 network.cab
15/08/2012  01:40 PM        19,262,287 ovftoo~1.cab
15/08/2012  01:40 PM        15,132,466 ovftoo~2.cab
15/08/2012  01:40 PM           392,794 perfmon.cab
15/08/2012  01:40 PM         4,286,867 upgrad~1.cab
15/08/2012  01:40 PM         5,225,304 vcredist_x64.exe
15/08/2012  01:40 PM         4,485,976 vcredist_x86.exe
15/08/2012  01:40 PM         5,091,328 vmware player.msi
15/08/2012  01:40 PM       121,302,678 VMware-player-4.0.4-744019.exe
15/08/2012  01:40 PM           784,024 vnetlib.dll
15/08/2012  01:40 PM           761,496 vnetlib.exe
15/08/2012  01:40 PM                 0 windowsinstaller20.exe
              15 File(s)    179,637,694 bytes
               2 Dir(s)  40,682,328,064 bytes free

C:\Downloads\extract>

Step 2: Extract and copy the vmnetcfg.exe from the network.cab file to the VMware Player installed directory (eg: C:\Program Files\VMware\VMware Player).

Step 3: Launch vmnetcfg.exe and have fun! :-)



UPDATE:
VMware Player v5 installer does not include the vmnetcfg.exe anymore.
Get it from the core.cab in the VMware Workstation v9 installer.

VMware Fusion 4 NAT Networking

MacBookPro:/ yapchinhoong$ cat /Library/Preferences/VMware\ Fusion/networking
VERSION=1,0
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 192.168.11.0
answer VNET_1_VIRTUAL_ADAPTER yes
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 192.168.18.0
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes
MacBookPro:/ yapchinhoong$ 
MacBookPro:/ yapchinhoong$ cat /Library/Preferences/VMware\ Fusion/vmnet8/nat.conf
# VMware NAT configuration file

[host]

# NAT gateway address
ip = 192.168.18.2
netmask = 255.255.255.0

# VMnet device if not specified on command line
device = vmnet8

# Allow PORT/EPRT FTP commands (they need incoming TCP stream ...)
activeFTP = 1

# Allows the source to have any OUI.  Turn this on if you change the OUI
# in the MAC address of your virtual machines.
allowAnyOUI = 1

# Controls if (TCP) connections should be reset when the adapter they are
# bound to goes down
resetConnectionOnLinkDown = 1

[tcp]

# Value of timeout in TCP TIME_WAIT state, in seconds
timeWaitTimeout = 30

[udp]

# Timeout in seconds. Dynamically-created UDP mappings will purged if
# idle for this duration of time 0 = no timeout, default = 60; real
# value might be up to 100% longer
timeout = 60

[netbios]
# Timeout for NBNS queries.
nbnsTimeout = 2

# Number of retries for each NBNS query.
nbnsRetries = 3

# Timeout for NBDS queries.
nbdsTimeout = 3

[incomingtcp]

# Use these with care - anyone can enter into your VM through these...
# The format and example are as follows:
# = :
#8080 = 172.16.3.128:80

[incomingudp]

# UDP port forwarding example
#6000 = 172.16.3.0:6001

MacBookPro:/ yapchinhoong$ 
MacBookPro:/ yapchinhoong$ cat /Library/Preferences/VMware\ Fusion/vmnet8/nat.mac
00:50:56:FC:1B:04
MacBookPro:/ yapchinhoong$ 
MacBookPro:/ yapchinhoong$ ifconfig vmnet8
vmnet8: flags=8863 mtu 1500
 ether 00:50:56:c0:00:08 
 inet 192.168.18.1 nroetmask 0xffffff00 broadcast 192.168.18.255
MacBookPro:/ yapchinhoong$ 

Run the following commands in sequence to update the changes without restarting Fusion 4.x and later.
This can be useful if you do not want to relaunch Fusion (if you have other Virtual Machines running).
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --configure
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start

[root@localhost ~]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:0C:29:11:22:33  
          inet addr:192.168.18.123  Bcast:192.168.18.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe11:2233/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:400 (400.0 b)  TX bytes:6718 (6.5 KiB)

[root@localhost ~]# 
[root@localhost ~]# netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.18.0    *               255.255.255.0   U         0 0          0 eth0
169.254.0.0     *               255.255.0.0     U         0 0          0 eth0
default         192.168.18.2    0.0.0.0         UG        0 0          0 eth0
[root@localhost ~]# 
[root@localhost ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=128 time=32.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=128 time=33.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=128 time=30.3 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 30.372/32.180/33.998/1.487 ms
[root@localhost ~]# 
[root@localhost ~]# ping 192.168.18.1
PING 192.168.18.1 (192.168.18.1) 56(84) bytes of data.
64 bytes from 192.168.18.1: icmp_seq=1 ttl=64 time=0.259 ms
64 bytes from 192.168.18.1: icmp_seq=2 ttl=64 time=0.161 ms
64 bytes from 192.168.18.1: icmp_seq=3 ttl=64 time=0.141 ms

--- 192.168.18.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.141/0.187/0.259/0.051 ms
[root@localhost ~]# 
[root@localhost ~]# ping 192.168.18.2
PING 192.168.18.2 (192.168.18.2) 56(84) bytes of data.
64 bytes from 192.168.18.2: icmp_seq=1 ttl=128 time=0.168 ms
64 bytes from 192.168.18.2: icmp_seq=2 ttl=128 time=0.149 ms
64 bytes from 192.168.18.2: icmp_seq=3 ttl=128 time=0.143 ms

--- 192.168.18.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.143/0.153/0.168/0.014 ms
[root@localhost ~]# 
[root@localhost ~]# arp -a
? (192.168.18.2) at 00:50:56:FC:1B:04 [ether] on eth0
? (192.168.18.1) at 00:50:56:C0:00:08 [ether] on eth0
[root@localhost ~]# 

Friday, April 22, 2011

Installing VMware Tools on debian 6

- VM > Install VMware Tools...
- Accessories > Root Terminal

root@debian6:/# uname -a
Linux debian6 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
root@debian6:/# 
root@debian6:/# tar -xf /media/cdrom/VMwareTools-8.4.6-385536.tar.gz -C /tmp
root@debian6:/# 
root@debian6:/# /tmp/vmware-tools-distrib/vmware-install.pl 
Creating a new VMware Tools installer database using the tar4 format.

Installing VMware Tools.

In which directory do you want to install the binary files? 
[/usr/bin] 

What is the directory that contains the init directories (rc0.d/ to rc6.d/)? 
[/etc] 

What is the directory that contains the init scripts? 
[/etc/init.d] 

In which directory do you want to install the daemon files? 
[/usr/sbin] 

In which directory do you want to install the library files? 
[/usr/lib/vmware-tools] 

The path "/usr/lib/vmware-tools" does not exist currently. This program is 
going to create it, including needed parent directories. Is this what you want?
[yes] 

In which directory do you want to install the documentation files? 
[/usr/share/doc/vmware-tools] 

The path "/usr/share/doc/vmware-tools" does not exist currently. This program 
is going to create it, including needed parent directories. Is this what you 
want? [yes] 

The installation of VMware Tools 8.4.6 build-385536 for Linux completed 
successfully. You can decide to remove this software from your system at any 
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

Before running VMware Tools for the first time, you need to configure it by 
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want 
this program to invoke the command for you now? [yes] 

Initializing...


Making sure services for VMware Tools are stopped.

Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                                      done
   Virtual Printing daemon:                                            done
   Unmounting HGFS shares:                                             done
   Guest filesystem driver:                                            done



Before you can compile modules, you need to have the following installed... 

make
gcc
kernel headers of the running kernel


Searching for GCC...
The path "" is not valid path to the gcc binary.
Would you like to change it? [yes] no

Searching for a valid kernel header path...
The path "" is not valid.
Would you like to change it? [yes] no


WARNING: This program cannot compile any modules for the following reason(s)...

- This program could not find a valid path to make.  Please ensure that the 
make binary is installed in the system path.

- This program could not find a valid path to the gcc binary.  Please ensure 
that the gcc binary is installed on this sytem.

- This program could not find a valid path to the kernel headers of the running
kernel.  Please ensure that the header files for the running kernel are 
installed on this sytem.

[ Press Enter key to continue ] 


The memory manager driver (vmmemctl module) is used by VMware host software to 
efficiently reclaim memory from a virtual machine.
If the driver is not available, VMware host software may instead need to swap 
guest memory to disk, which may reduce performance.
The rest of the software provided by VMware Tools is designed to work 
independently of this feature.
If you want the memory management feature, you can install the driver by 
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine. 
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ] 


The filesystem driver (vmhgfs module) is used only for the shared folder 
feature. The rest of the software provided by VMware Tools is designed to work 
independently of this feature.

If you wish to have the shared folders feature, you can install the driver by 
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine. 
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ] 


The fast network device driver (vmxnet module) is used only for our fast 
networking interface. The rest of the software provided by VMware Tools is 
designed to work independently of this feature.
If you wish to have the fast network driver enabled, you can install the driver
by running vmware-config-tools.pl again after making sure that gcc, binutils, 
make and the kernel sources for your running kernel are installed on your 
machine. These packages are available on your distribution's installation CD.
[ Press Enter key to continue ] 


The vmblock module enables dragging or copying files from within a host and 
dropping or pasting them onto your guest (host to guest drag and drop and file 
copy/paste).  The rest of the software provided by VMware Tools is designed to 
work independently of this feature (including guest to host drag and drop and 
file copy/paste).

If you would like the host to guest drag and drop and file copy/paste features,
you can install the driver by running vmware-config-tools.pl again after making
sure that gcc, binutils, make and the kernel sources for your running kernel 
are installed on your machine. These packages are available on your 
distribution's installation CD.
[ Press Enter key to continue ] 


The communication service is used in addition to the standard communication 
between the guest and the host.  The rest of the software provided by VMware 
Tools is designed to work independently of this feature.
If you wish to have the VMCI feature, you can install the driver by running 
vmware-config-tools.pl again after making sure that gcc, binutils, make and the
kernel sources for your running kernel are installed on your machine. These 
packages are available on your distribution's installation CD.
[ Press Enter key to continue ] 


The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and 
host.  The rest of this software provided by VMware Tools is designed to work 
independently of this feature.  If you wish to have the VSOCK feature  you can 
install the driver by running vmware-config-tools.pl again after making sure 
that gcc, binutils, make and the kernel sources for your running kernel are 
installed on your machine. These packages are available on your distribution's 
installation CD.
[ Press the Enter key to continue.] 

The module vmxnet3 has already been installed on this system by another 
installer or package and will not be modified by this installer.  Use the flag 
--clobber-kernel-modules=vmxnet3 to override.


Unable to compile the pvscsi module.  If you wish to have the pvscsi feature, 
you can install the driver by running vmware-config-tools.pl again after making
sure that gcc, binutils, make and the kernel sources for your running kernel 
are installed on your machine. These packages are available on your 
distribution's installation CD.
[ Press Enter key to continue ] 



Detected Xorg X server version 1.7.7.


X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32.29-dsa-ia32 i686 Debian
Current Operating System: Linux debian6 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=9236b7ad-efe8-4f77-8cec-0d6b4d92a668 ro quiet
Build Date: 19 February 2011  02:37:36PM
xorg-server 2:1.7.7-13 (Cyril Brulebois ) 
Current version of pixman: 0.16.4
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/vmware-config0/XF86ConfigLog.2111", Time: Fri Apr 22 16:22:19 2011
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) Failed to load module "vmwgfx" (module does not exist, 0)
(EE) vmware: Please ignore the above warnings about not being able to to load module/driver vmwgfx
(EE) open /dev/fb0: No such file or directory
SELinux: Disabled on system, not enabling in X server

X is running fine with the new config file.

Creating a new initrd boot image for the kernel.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-686
   Checking acpi hot plug                                              done
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                                   done
   Guest operating system daemon:                                      done
   Virtual Printing daemon:                                            done
The configuration of VMware Tools 8.4.6 build-385536 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take 
effect.

You can now run VMware Tools by invoking "/usr/bin/vmware-toolbox-cmd" from the
command line or by invoking "/usr/bin/vmware-toolbox" from the command line 
during an X server session.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and 
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.

Enjoy,

--the VMware team

Found VMware Tools CDROM mounted at /media/cdrom0. Ejecting device /dev/sr0 ...

root@debian6:/# 
root@debian6:/# shutdown -r now