VMware Notes - Revision history

PeterHarding at 03:08, 17 March 2008

2008-03-17T03:08:56Z

← Older revision		Revision as of 13:08, 17 March 2008
Line 21:		Line 21:

	To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).		To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).

			===Connect===

	<pre>		<pre>
Line 31:		Line 33:
	ssh -l root -X -c blowfish `ip`		ssh -l root -X -c blowfish `ip`
	</pre>		</pre>

			===Start X11 Session===

	<pre>		<pre>
Line 41:		Line 45:
	</pre>		</pre>

	===ip===		===Echo IP===

	<pre>		<pre>

PeterHarding at 03:08, 17 March 2008

2008-03-17T03:08:04Z

← Older revision		Revision as of 13:08, 17 March 2008
Line 38:		Line 38:
	# using a separate bash script for ip address (last parameter in tick marks)		# using a separate bash script for ip address (last parameter in tick marks)

	xwin -fullscreen -clipboard -query `ip`~~</pre>~~		xwin -fullscreen -clipboard -query `ip`
	</pre>		</pre>

PeterHarding: VMWare Notes moved to VMware Notes: More widely used naming convention.

2008-03-17T03:07:31Z

VMWare Notes moved to VMware Notes: More widely used naming convention.

← Older revision	Revision as of 13:07, 17 March 2008
(No difference)

PeterHarding at 03:04, 17 March 2008

2008-03-17T03:04:49Z

← Older revision		Revision as of 13:04, 17 March 2008
Line 53:		Line 53:


	[[Category:~~VMWare~~]]		[[Category:VMware]]

PeterHarding at 02:44, 17 March 2008

2008-03-17T02:44:35Z

← Older revision		Revision as of 12:44, 17 March 2008
Line 21:		Line 21:

	To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).		To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).

			<pre>
			#!/bin/sh
			#
			# Start an SSH session with fast encryption to remote host, with pass-through X support.
			# Uses separate bash script for ip address (last parameter in tick marks)
			# Note: login id is hardcoded, parameterise if you wish

			ssh -l root -X -c blowfish `ip`
			</pre>

			<pre>
			#!/bin/sh
			#
			# Start a fullscreen X11 session with desktop and login from remote host
			# using a separate bash script for ip address (last parameter in tick marks)

			xwin -fullscreen -clipboard -query `ip`</pre>
			</pre>

			===ip===

			<pre>
			#!/bin/sh
			#
			# A simple way to reuse IP address in other scripts.
			# Easier than updatingWindows hosts file all the time?

			echo 10.1.1.2
			</pre>


	[[Category:VMWare]]		[[Category:VMWare]]

PeterHarding at 02:32, 17 March 2008

2008-03-17T02:32:20Z

← Older revision		Revision as of 12:32, 17 March 2008
Line 21:		Line 21:

	To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).		To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).


			[[Category:VMWare]]

PeterHarding at 02:32, 17 March 2008

2008-03-17T02:32:06Z

← Older revision		Revision as of 12:32, 17 March 2008
Line 9:		Line 9:
	If you want to start/stop the VMs, you have two options:		If you want to start/stop the VMs, you have two options:

	#. Install the VMWare Server software on your own workstation, then use it to connect remotely to the VM Server software running on the relevant host system		# Install the VMWare Server software on your own workstation, then use it to connect remotely to the VM Server software running on the relevant host system
	#. Use Windows remote desktop to login directly to the remote system and run the VMWare Server Console there.		# Use Windows remote desktop to login directly to the remote system and run the VMWare Server Console there.

	The second option also lets you copy/backup the VM files on the host system.		The second option also lets you copy/backup the VM files on the host system.
Line 17:		Line 17:
	Follow these steps:		Follow these steps:

	#~~. install~~ cygwin, using the cached download at eaicc repository to avoid re-downlading the 200MB or so. Make sure the X11 component is selected for installation.		# Install cygwin, using the cached download at eaicc repository to avoid re-downlading the 200MB or so. Make sure the X11 component is selected for installation.
	# From inside a cygwin console window on your desktop, launch X11 and either ssh to the remote system and launch windows manually (remember to set the DISPLAY envirionment variable), or run a full remote desktop session using the xdm -query option.		# From inside a cygwin console window on your desktop, launch X11 and either ssh to the remote system and launch windows manually (remember to set the DISPLAY envirionment variable), or run a full remote desktop session using the xdm -query option.

	To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).		To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).

PeterHarding at 02:31, 17 March 2008

2008-03-17T02:31:37Z

← Older revision		Revision as of 12:31, 17 March 2008
Line 1:		Line 1:

	=Development Environment Virtual Machines=		=Development Environment Virtual Machines=

Line 10:		Line 9:
	If you want to start/stop the VMs, you have two options:		If you want to start/stop the VMs, you have two options:

	#. Install the VMWare Server software on your own workstation, then use it to connect remotely to the VM Server software running on the relevant host system		#. Install the VMWare Server software on your own workstation, then use it to connect remotely to the VM Server software running on the relevant host system
	#. Use Windows remote desktop to login directly to the remote system and run the VMWare Server Console there.		#. Use Windows remote desktop to login directly to the remote system and run the VMWare Server Console there.

	The second option also lets you copy/backup the VM files on the host system.		The second option also lets you copy/backup the VM files on the host system.
Line 18:		Line 17:
	Follow these steps:		Follow these steps:

	#. install cygwin, using the cached download at eaicc repository to avoid re-downlading the 200MB or so. Make sure the X11 component is selected for installation.		#. install cygwin, using the cached download at eaicc repository to avoid re-downlading the 200MB or so. Make sure the X11 component is selected for installation.
	# From inside a cygwin console window on your desktop, launch X11 and either ssh to the remote system and launch windows manually (remember to set the DISPLAY envirionment variable), or run a full remote desktop session using the xdm -query option.		# From inside a cygwin console window on your desktop, launch X11 and either ssh to the remote system and launch windows manually (remember to set the DISPLAY envirionment variable), or run a full remote desktop session using the xdm -query option.

	To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).		To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).

PeterHarding: New page: =Development Environment Virtual Machines= Note: if the VMs are run regularly the IP address assigned by DHCP remains fairly stable. If you start a VM after some days of not running, it ...

2008-03-17T02:31:16Z

New page: =Development Environment Virtual Machines= Note: if the VMs are run regularly the IP address assigned by DHCP remains fairly stable. If you start a VM after some days of not running, it ...

New page

=Development Environment Virtual Machines=

Note: if the VMs are run regularly the IP address assigned by DHCP remains fairly stable. If you start a VM after some days of not running, it may be assigned a new IP address by DHCP. If that occurs, please update the IP address on this page. If you can't readily determine the IP address, use VMWare Server Console to access the VM instance's console, login and use ifconfig to display the assigned address.

=How to access virtual machines=

If you just want to login and use the development environment you don't need to install the VMWare software. Instead, use a good X11 application (see details below).

If you want to start/stop the VMs, you have two options:

#. Install the VMWare Server software on your own workstation, then use it to connect remotely to the VM Server software running on the relevant host system
#. Use Windows remote desktop to login directly to the remote system and run the VMWare Server Console there.

The second option also lets you copy/backup the VM files on the host system.
Using Cygwin/X to access virtual machines

Follow these steps:

#. install cygwin, using the cached download at eaicc repository to avoid re-downlading the 200MB or so. Make sure the X11 component is selected for installation.
# From inside a cygwin console window on your desktop, launch X11 and either ssh to the remote system and launch windows manually (remember to set the DISPLAY envirionment variable), or run a full remote desktop session using the xdm -query option.

To make this easier, I use a few simple bash script files (see attached). Rather than modifying my Windows hosts file I just put the VM machine's IP address in a bash script and re-use it (again, see the attached files). Create a bin directory in your home directory in cygwin to hold these scripts, and they should then be found using the default command path (you may need to do chmod +x).