Testing with VMWare - Revision history

Ray N at 11:03, 11 August 2009

2009-08-11T11:03:21Z

←Older revision		Revision as of 11:03, 11 August 2009
Line 1:		Line 1:
	[[Category: Tutorials]]		[[Category: Tutorials]]
	[[Category: Testing]]		[[Category: Testing\| ]]
	~~[[Category: Hardware~~\| ]]

	If you have VMWare Workstation installed on your machine you can try LinuxMCE without the need for any additional hardware.		If you have VMWare Workstation installed on your machine you can try LinuxMCE without the need for any additional hardware.

Gundar: /* DHCP */

2008-07-06T08:28:15Z

DHCP

←Older revision		Revision as of 08:28, 6 July 2008
Line 32:		Line 32:

	=== DHCP ===		=== DHCP ===
	To avoid conflict with vmware's internal DHCP server ~~I just looked up it's Process Id and killed it~~, ~~I'm looking for a nicer and more permanent way to do~~ this~~, maybe reconfigure the network with~~ vmware~~-config~~.~~pl or cripple the internal dhcpd in it's config file~~. ~~It's~~ the ~~one running~~ on ~~vmnet1 usually.~~		To avoid conflict with vmware's internal DHCP server disable the service as per your running version of the VMware product as described here, in this KnowledgeBase article at www.vmware.com:

			[http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2012&sliceId=1&docTypeID=DT_KB_1_1&dialogID=13434918&stateId=1%200%2013436412 Disabling the VMware DHCP Service on the Host Computer]

	== Kubuntu-7.04 i386 ==		== Kubuntu-7.04 i386 ==

Alaric: Disk size for MCE 0710

2008-05-05T00:55:39Z

Disk size for MCE 0710

←Older revision		Revision as of 00:55, 5 May 2008
Line 20:		Line 20:
	# <location> (a directroy on a drive with enough room)		# <location> (a directroy on a drive with enough room)
	# Use NAT (eth0 for outside line)		# Use NAT (eth0 for outside line)
	# Disk size: plenty (AKA. I don't know what you'll need, default should be good to get you started)		# Disk size: plenty (AKA. I don't know what you'll need, default should be good to get you started). The LinxMCE 0710 install DVD created a 9.4GiB root filesystem, and use the remainder of my 20GB disk for an 2 extended partitions: 2GiB swap, and 9.9GiB recovery. (The default 8GB root disk for Server 2.0 did not work, so I bumped it to 20GB and this was the result.)

	=== Configure the new Virtual Machine ===		=== Configure the new Virtual Machine ===

Jeffr76: /* Kubuntu-7.10 */

2007-12-07T19:47:29Z

Kubuntu-7.10

←Older revision		Revision as of 19:47, 7 December 2007
Line 52:		Line 52:
	== Kubuntu-7.10 ==		== Kubuntu-7.10 ==
	The base for the upcoming next version of linuxMCE.		The base for the upcoming next version of linuxMCE.
			Update
			tested with VMware Server 1.x worked good was able to get the Core/hybrid working (no video capture card)

	== LinuxMCE 0710 ==		== LinuxMCE 0710 ==

Zaerc: small update

2007-11-06T17:31:35Z

small update

←Older revision		Revision as of 17:31, 6 November 2007
Line 11:		Line 11:

	== Getting started ==		== Getting started ==

	First we need to set up a Virtual Machine for our core (or hybrid).		First we need to set up a Virtual Machine for our core (or hybrid).

Line 44:		Line 43:

	== LinuxMCE-1.1 RC1 ==		== LinuxMCE-1.1 RC1 ==
			'''''This version is currently outdated and obsolete, try the latest one below instead'''''

	Change the ISO used for the CDROM drive to the LMCE packages ISO. And follow the usual instructions. You'll probably have to switch once or twice again for the LMCE cache ISO and Kubuntu desktop ISO. Set up eth0 with dhcp, and eth1 for the 192.168.80.1 internal network. As an alternative you can copy the 3 ISOs over (to the guest) and use them directly from the installer.		Change the ISO used for the CDROM drive to the LMCE packages ISO. And follow the usual instructions. You'll probably have to switch once or twice again for the LMCE cache ISO and Kubuntu desktop ISO. Set up eth0 with dhcp, and eth1 for the 192.168.80.1 internal network. As an alternative you can copy the 3 ISOs over (to the guest) and use them directly from the installer.

			== LinuxMCE 0704 ==
			Untested by me, feel free to add aditional notes, see the instructions for RC1 until then. --[[User:Zaerc\|Zaerc]] 10:31, 6 November 2007 (MST)

			== Kubuntu-7.10 ==
			The base for the upcoming next version of linuxMCE.

			== LinuxMCE 0710 ==
			The upcoming next version, which hasn't been released yet.

	== What's next? ==		== What's next? ==

Zaerc: moved categories

2007-10-05T15:11:14Z

moved categories

←Older revision		Revision as of 15:11, 5 October 2007
Line 1:		Line 1:
			[[Category: Tutorials]]
			[[Category: Testing]]
			[[Category: Hardware\| ]]

	If you have VMWare Workstation installed on your machine you can try LinuxMCE without the need for any additional hardware.		If you have VMWare Workstation installed on your machine you can try LinuxMCE without the need for any additional hardware.

Line 51:		Line 55:

	Another neat thing is that VMWare should be able to hook LMCE up directly with USB devices, but that has not been tested yet (at least not by me, [[User:Zaerc\|Zaerc]]).		Another neat thing is that VMWare should be able to hook LMCE up directly with USB devices, but that has not been tested yet (at least not by me, [[User:Zaerc\|Zaerc]]).

	~~[[Category: Tutorials]]~~
	~~[[Category: Testing]]~~
	~~[[Category: Hardware]]~~

Zaerc: updated

2007-08-02T15:18:01Z

updated

←Older revision		Revision as of 15:18, 2 August 2007
Line 27:		Line 27:
	# Use ISO Image		# Use ISO Image
	# The name and path of the Kubuntu installation CD image (*.iso) you downloaded earlier.		# The name and path of the Kubuntu installation CD image (*.iso) you downloaded earlier.

			=== DHCP ===
			To avoid conflict with vmware's internal DHCP server I just looked up it's Process Id and killed it, I'm looking for a nicer and more permanent way to do this, maybe reconfigure the network with vmware-config.pl or cripple the internal dhcpd in it's config file. It's the one running on vmnet1 usually.

	== Kubuntu-7.04 i386 ==		== Kubuntu-7.04 i386 ==
Line 32:		Line 35:

	== LinuxMCE-1.1 Beta2 ==		== LinuxMCE-1.1 Beta2 ==
	~~Change the ISO used for the CDROM drive to the LMCE packages ISO. And follow the usual instructions. You~~'~~ll probably have to switch once or twice again for the LMCE cache ISO. Set up eth0 with dhcp~~, ~~and eth1 for~~ the ~~192.168.80.1 internal network.~~		'''''This version is currently outdated and obsolete, try the latest one below instead'''''

	==~~= DHCP =~~==		Change the ISO used for the CDROM drive to the LMCE packages ISO. And follow the usual instructions. You'll probably have to switch once or twice again for the LMCE cache ISO. Set up eth0 with dhcp, and eth1 for the 192.168.80.1 internal network. As an alternative you can copy the 2 ISOs over (to the guest) and use them directly from the installer.
	~~To avoid conflict with vmware~~'~~s internal DHCP server I just looked~~ up ~~it's Process Id~~ and ~~killed it, I'm looking~~ for ~~a nicer and more permanent way to do this, maybe reconfigure~~ the ~~network with vmware-config~~.~~pl or cripple the~~ internal ~~dhcpd in it's config file~~. ~~It's~~ the ~~one running on vmnet1 usually~~.
			== LinuxMCE-1.1 RC1 ==
			Change the ISO used for the CDROM drive to the LMCE packages ISO. And follow the usual instructions. You'll probably have to switch once or twice again for the LMCE cache ISO and Kubuntu desktop ISO. Set up eth0 with dhcp, and eth1 for the 192.168.80.1 internal network. As an alternative you can copy the 3 ISOs over (to the guest) and use them directly from the installer.

	== What's next? ==		== What's next? ==
Line 43:		Line 48:
	You can build up an entire network of virtual machines to test and experiment with LMCE and add virtual machines running other operating systems as well.		You can build up an entire network of virtual machines to test and experiment with LMCE and add virtual machines running other operating systems as well.

	Or you could even reconfigure the network so that the second virtual network card is connected to a physical adapter and hook up real devices. Another neat thing is that VMWare should be able to hook LMCE up directly with USB devices, but that has not been tested yet (at least not by me, [[User:Zaerc\|Zaerc]]).		Or you could even reconfigure the network so that the second virtual network card is connected to a physical adapter and hook up real devices.

			Another neat thing is that VMWare should be able to hook LMCE up directly with USB devices, but that has not been tested yet (at least not by me, [[User:Zaerc\|Zaerc]]).

	[[Category: Tutorials]]		[[Category: Tutorials]]
	[[Category: Testing]]		[[Category: Testing]]
	[[Category: Hardware]]		[[Category: Hardware]]

Zaerc: /* What's next? */

2007-08-02T15:01:39Z

What's next?

←Older revision		Revision as of 15:01, 2 August 2007
Line 38:		Line 38:

	== What's next? ==		== What's next? ==
	Now you can configure it with the web interface, even from the machine running the virtual machine. If you have done a core only install you'd want to enable the [[Web Orbiter]] first as well.		Now you can configure it with the web interface, even from the machine running the virtual machine (requires modification of LMCEs firewall rules first). If you have done a core only install you'd want to enable the [[Web Orbiter]] first as well.
	Then you can add extra virtual machines that can boot on the "Host-only" network, as [[Media ~~Director~~]]s, provided that you have dealt with VMWare's internal DHCP server.		Then you can add extra virtual machines that can boot on the "Host-only" network, as [[Media Directors]], provided that you have dealt with VMWare's internal DHCP server.

	You can build up an entire network of virtual machines to test and experiment with LMCE and add machines running other operating systems as well.		You can build up an entire network of virtual machines to test and experiment with LMCE and add virtual machines running other operating systems as well.

			Or you could even reconfigure the network so that the second virtual network card is connected to a physical adapter and hook up real devices. Another neat thing is that VMWare should be able to hook LMCE up directly with USB devices, but that has not been tested yet (at least not by me, [[User:Zaerc\|Zaerc]]).

	[[Category: Tutorials]]		[[Category: Tutorials]]
	[[Category: Testing]]		[[Category: Testing]]
	[[Category: Hardware]]		[[Category: Hardware]]

Zaerc: /* What's next? */ other OS-es should work too

2007-07-11T19:01:23Z

What's next?: other OS-es should work too

←Older revision		Revision as of 19:01, 11 July 2007
Line 41:		Line 41:
	Then you can add extra virtual machines that can boot on the "Host-only" network, as [[Media Director]]s, provided that you have dealt with VMWare's internal DHCP server.		Then you can add extra virtual machines that can boot on the "Host-only" network, as [[Media Director]]s, provided that you have dealt with VMWare's internal DHCP server.

	You can build up an entire network of virtual machines to test and experiment with LMCE.		You can build up an entire network of virtual machines to test and experiment with LMCE and add machines running other operating systems as well.

	[[Category: Tutorials]]		[[Category: Tutorials]]
	[[Category: Testing]]		[[Category: Testing]]
	[[Category: Hardware]]		[[Category: Hardware]]

Zaerc: /* LinuxMCE-1.1 Beta2 */ added header

2007-07-11T18:58:45Z

LinuxMCE-1.1 Beta2: added header

←Older revision		Revision as of 18:58, 11 July 2007
Line 34:		Line 34:
	Change the ISO used for the CDROM drive to the LMCE packages ISO. And follow the usual instructions. You'll probably have to switch once or twice again for the LMCE cache ISO. Set up eth0 with dhcp, and eth1 for the 192.168.80.1 internal network.		Change the ISO used for the CDROM drive to the LMCE packages ISO. And follow the usual instructions. You'll probably have to switch once or twice again for the LMCE cache ISO. Set up eth0 with dhcp, and eth1 for the 192.168.80.1 internal network.

			=== DHCP ===
	To avoid conflict with vmware's internal DHCP server I just looked up it's Process Id and killed it, I'm looking for a nicer and more permanent way to do this, maybe reconfigure the network with vmware-config.pl or cripple the internal dhcpd in it's config file. It's the one running on vmnet1 usually.		To avoid conflict with vmware's internal DHCP server I just looked up it's Process Id and killed it, I'm looking for a nicer and more permanent way to do this, maybe reconfigure the network with vmware-config.pl or cripple the internal dhcpd in it's config file. It's the one running on vmnet1 usually.