Vmware-Tools and time synchronization - Revision history

Wolfm at 09:23, 3 March 2006

2006-03-03T09:23:49Z

← Older revision		Revision as of 09:23, 3 March 2006
Line 56:		Line 56:
	_nm_name='bus-pci-0000:00:11.0'		_nm_name='bus-pci-0000:00:11.0'
	</nowiki></pre>		</nowiki></pre>
			# Shut down the machine, power off the VM from the GSX-Console and start the VM new.

	Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!		Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!

Wolfm at 14:47, 2 March 2006

2006-03-02T14:47:18Z

← Older revision		Revision as of 14:47, 2 March 2006
Line 9:		Line 9:
	# Reboot.		# Reboot.
	# Install the Vmware-Tools. We use the <pre>dc:/pub/software/RPM/VMwareTools-5.5.1-19175.i386.rpm</pre> which compiles better with 2.6 kernals then the variant distributed with vmware-gsx-server.<pre>rpm -i VMwareTools-5.5.1-19175.i386.rpm</pre>.		# Install the Vmware-Tools. We use the <pre>dc:/pub/software/RPM/VMwareTools-5.5.1-19175.i386.rpm</pre> which compiles better with 2.6 kernals then the variant distributed with vmware-gsx-server.<pre>rpm -i VMwareTools-5.5.1-19175.i386.rpm</pre>.
			# Now we have to configure the kernel sources: <pre><nowiki>
			cd /usr/src/linux
			make cloneconfig
			make prepare</nowiki></pre>
	# Now we can successfully run <pre>/usr/bin/vmware-config-tools.pl</pre> and follow the instructions.		# Now we can successfully run <pre>/usr/bin/vmware-config-tools.pl</pre> and follow the instructions.
	# Run <code> vmware-toolbox </code> and check button [[Image:screen1.gif\|Options->Time synchronization ...]].		# Run <code> vmware-toolbox </code> and check button [[Image:screen1.gif\|Options->Time synchronization ...]].
Line 55:		Line 59:
	Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!		Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!

	'''If a kernel-update is installed the steps 3 and 5 have to be repeated!'''		'''If a kernel-update is installed the steps 3, 5 and 6 have to be repeated!'''

Wolfm at 13:47, 2 March 2006

2006-03-02T13:47:18Z

← Older revision		Revision as of 13:47, 2 March 2006
Line 9:		Line 9:
	# Reboot.		# Reboot.
	# Install the Vmware-Tools. We use the <pre>dc:/pub/software/RPM/VMwareTools-5.5.1-19175.i386.rpm</pre> which compiles better with 2.6 kernals then the variant distributed with vmware-gsx-server.<pre>rpm -i VMwareTools-5.5.1-19175.i386.rpm</pre>.		# Install the Vmware-Tools. We use the <pre>dc:/pub/software/RPM/VMwareTools-5.5.1-19175.i386.rpm</pre> which compiles better with 2.6 kernals then the variant distributed with vmware-gsx-server.<pre>rpm -i VMwareTools-5.5.1-19175.i386.rpm</pre>.
	# Now we have to configure the kernel sources: <pre><nowiki>
	cd /usr/src/linux
	make cloneconfig
	make prepare</nowiki></pre>
	# Now we can successfully run <pre>/usr/bin/vmware-config-tools.pl</pre> and follow the instructions.		# Now we can successfully run <pre>/usr/bin/vmware-config-tools.pl</pre> and follow the instructions.
	# Run <code> vmware-toolbox </code> and check button [[Image:screen1.gif\|Options->Time synchronization ...]].		# Run <code> vmware-toolbox </code> and check button [[Image:screen1.gif\|Options->Time synchronization ...]].
Line 59:		Line 55:
	Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!		Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!

	'''If a kernel-update is installed the steps 3~~, 5~~ and 6 have to be repeated!'''		'''If a kernel-update is installed the steps 3 and 5 have to be repeated!'''

Jkm at 13:34, 2 March 2006

2006-03-02T13:34:38Z

← Older revision		Revision as of 13:34, 2 March 2006
Line 10:		Line 10:
	# Install the Vmware-Tools. We use the <pre>dc:/pub/software/RPM/VMwareTools-5.5.1-19175.i386.rpm</pre> which compiles better with 2.6 kernals then the variant distributed with vmware-gsx-server.<pre>rpm -i VMwareTools-5.5.1-19175.i386.rpm</pre>.		# Install the Vmware-Tools. We use the <pre>dc:/pub/software/RPM/VMwareTools-5.5.1-19175.i386.rpm</pre> which compiles better with 2.6 kernals then the variant distributed with vmware-gsx-server.<pre>rpm -i VMwareTools-5.5.1-19175.i386.rpm</pre>.
	# Now we have to configure the kernel sources: <pre><nowiki>		# Now we have to configure the kernel sources: <pre><nowiki>
	cd /usr/~~srs~~/linux		cd /usr/src/linux
	make cloneconfig		make cloneconfig
	make prepare</nowiki></pre>		make prepare</nowiki></pre>

Wolfm at 10:47, 2 March 2006

2006-03-02T10:47:42Z

← Older revision		Revision as of 10:47, 2 March 2006
Line 58:		Line 58:

	Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!		Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!

			'''If a kernel-update is installed the steps 3, 5 and 6 have to be repeated!'''

Wolfm at 10:15, 2 March 2006

2006-03-02T10:15:57Z

← Older revision		Revision as of 10:15, 2 March 2006
Line 40:		Line 40:
	# Shutdown the VM and configure the network to use <code>vmxnet</code> module instead of <code>pcnet32</code> [[Image:screen2.png]].		# Shutdown the VM and configure the network to use <code>vmxnet</code> module instead of <code>pcnet32</code> [[Image:screen2.png]].
	# Check if in the Vmwares *.vmx file the entry <pre>tools.syncTime = "TRUE"</pre> is correctly set.		# Check if in the Vmwares *.vmx file the entry <pre>tools.syncTime = "TRUE"</pre> is correctly set.
	# ~~Poweron~~ the VM and choose the right driver for eth0 using yast (it should be named eth? because even <code>/etc/init.d/vmware-tools</code> has to find it) Example:<pre><nowiki>		# Power on the VM and choose the right driver for eth0 using yast (it should be named eth? because even <code>/etc/init.d/vmware-tools</code> has to find it) Example:<pre><nowiki>
	brn-suse093-1:~ # cat /etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:11.0		brn-suse093-1:~ # cat /etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:11.0
	MODULE='vmxnet'		MODULE='vmxnet'

Wolfm at 10:15, 2 March 2006

2006-03-02T10:15:03Z

← Older revision		Revision as of 10:15, 2 March 2006
Line 39:		Line 39:
	</nowiki></pre>		</nowiki></pre>
	# Shutdown the VM and configure the network to use <code>vmxnet</code> module instead of <code>pcnet32</code> [[Image:screen2.png]].		# Shutdown the VM and configure the network to use <code>vmxnet</code> module instead of <code>pcnet32</code> [[Image:screen2.png]].
			# Check if in the Vmwares *.vmx file the entry <pre>tools.syncTime = "TRUE"</pre> is correctly set.
	# Poweron the VM and choose the right driver for eth0 using yast (it should be named eth? because even <code>/etc/init.d/vmware-tools</code> has to find it) Example:<pre><nowiki>		# Poweron the VM and choose the right driver for eth0 using yast (it should be named eth? because even <code>/etc/init.d/vmware-tools</code> has to find it) Example:<pre><nowiki>
	brn-suse093-1:~ # cat /etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:11.0		brn-suse093-1:~ # cat /etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:11.0

Wolfm at 09:38, 2 March 2006

2006-03-02T09:38:16Z

← Older revision		Revision as of 09:38, 2 March 2006
Line 39:		Line 39:
	</nowiki></pre>		</nowiki></pre>
	# Shutdown the VM and configure the network to use <code>vmxnet</code> module instead of <code>pcnet32</code> [[Image:screen2.png]].		# Shutdown the VM and configure the network to use <code>vmxnet</code> module instead of <code>pcnet32</code> [[Image:screen2.png]].
	# Poweron the VM and ~~couse~~ the right driver for eth0 (it should be named eth? because even <code>/etc/init.d/vmware-tools</code> has to find it) Example:<pre><nowiki>		# Poweron the VM and choose the right driver for eth0 using yast (it should be named eth? because even <code>/etc/init.d/vmware-tools</code> has to find it) Example:<pre><nowiki>
	brn-suse093-1:~ # cat /etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:11.0		brn-suse093-1:~ # cat /etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:11.0
	MODULE='vmxnet'		MODULE='vmxnet'
Line 55:		Line 55:
	_nm_name='bus-pci-0000:00:11.0'		_nm_name='bus-pci-0000:00:11.0'
	</nowiki></pre>		</nowiki></pre>

			Hopefully after a reboot all services start correctly and the time is more accurate. If not please add details to this description!

Wolfm at 09:34, 2 March 2006

2006-03-02T09:34:16Z

@@ Line 38: / Line 38: @@
     initrd (hd0,0)/boot/initrd
 </nowiki></pre>
-# Shutdown the VM and [[Image:screen2.png|configure the network]] to use <code>vmxnet</code> module instead of <code>pcnet32</code>
+# Shutdown the VM and configure the network to use <code>vmxnet</code> module instead of <code>pcnet32</code> [[Image:screen2.png]].

Wolfm at 09:08, 2 March 2006

2006-03-02T09:08:51Z

← Older revision		Revision as of 09:08, 2 March 2006
Line 15:		Line 15:
	# Now we can successfully run <pre>/usr/bin/vmware-config-tools.pl</pre> and follow the instructions.		# Now we can successfully run <pre>/usr/bin/vmware-config-tools.pl</pre> and follow the instructions.
	# Run <code> vmware-toolbox </code> and check button [[Image:screen1.gif\|Options->Time synchronization ...]].		# Run <code> vmware-toolbox </code> and check button [[Image:screen1.gif\|Options->Time synchronization ...]].
	# Unfortunatly the guest OS gives timerevents with maximum 1000Hz, what is to slow fror the Linux-SMP-2.6 default kernel. [http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1420 See] Therfore we have to add the kernel boot options: <code>clock=pit noapic nolapic nosmp</code><pre><nowiki>		# Unfortunatly the guest OS gives timerevents with maximum 1000Hz, what is to slow fror the Linux-SMP-2.6 default kernel. [http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1420 See] Therfore we have to add the kernel boot options: '''<code>clock=pit noapic nolapic nosmp</code>'''<pre><nowiki>
	vi /boot/grub/menu.lst		vi /boot/grub/menu.lst
	# Modified by YaST2. Last modification on Tue Feb 21 12:52:40 UTC 2006		# Modified by YaST2. Last modification on Tue Feb 21 12:52:40 UTC 2006
Line 26:		Line 26:
	###Don't change this comment - YaST2 identifier: Original name: linux###		###Don't change this comment - YaST2 identifier: Original name: linux###
	title SUSE LINUX 9.3		title SUSE LINUX 9.3
	kernel (hd0,0)/boot/vmlinuz ...showopts ~~</nowiki>'''~~clock=pit noapic nolapic nosmp~~'''<nowiki>~~		kernel (hd0,0)/boot/vmlinuz ...showopts clock=pit noapic nolapic nosmp
	initrd (hd0,0)/boot/initrd		initrd (hd0,0)/boot/initrd
	###Don't change this comment - YaST2 identifier: Original name: floppy###		###Don't change this comment - YaST2 identifier: Original name: floppy###
Line 38:		Line 38:
	initrd (hd0,0)/boot/initrd		initrd (hd0,0)/boot/initrd
	</nowiki></pre>		</nowiki></pre>
			# Shutdown the VM and [[Image:screen2.png\|configure the network]] to use <code>vmxnet</code> module instead of <code>pcnet32</code>