<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: My Midsummer Night&#8217;s Dream of A Virtual Lab</title>
	<atom:link href="http://www.linux-mag.com/id/7397/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linux-mag.com/id/7397/</link>
	<description>Open Source, Open Standards</description>
	<lastBuildDate>Sat, 05 Oct 2013 13:48:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: nrarnot</title>
		<link>http://www.linux-mag.com/id/7397/#comment-6609</link>
		<dc:creator>nrarnot</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7397/#comment-6609</guid>
		<description>&lt;p&gt;\&quot;This is where confusion sets in for unsuspecting, starry-eyed customers—they aren’t able to install the software on their existing hardware—even for testing. A virtual lab would solve this dilemma.\&quot;&lt;/p&gt;
&lt;p&gt;For real-time testing the high-end stuff like VMotion, load-balancing, etc, that\&#039;s true. For leaning about VMware or for developing things to run in the datacentre, it certainly isn\&#039;t. I\&#039;m accomplishing many useful things with VMware server (free) on a desktop system with Intel DQ35JO MoBo, E8400 CPU (2 real cores, 4 Hyperthread cores - a quad Q9xxx CPU would be better), 4Gb RAM (8GB upgrade is possible), CentOS 5.3 i86-64 host, Intel VT turned on in the BIOS (not essential), and an old PCI Ethernet card to give me an eth1 to play with. &lt;/p&gt;
&lt;p&gt;This isn\&#039;t even top-end desktop hardware. That would be Core i7, 12Gb RAM (24Gb possible). &lt;/p&gt;
&lt;p&gt;The VMWare training course I went on was using real VMWare ESX but the datastore was just a bog-standard Linux server exporting via NFS. Too slow for production(?) but VMotion &amp; load-balancing demo worked fine.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>\&#8221;This is where confusion sets in for unsuspecting, starry-eyed customers—they aren’t able to install the software on their existing hardware—even for testing. A virtual lab would solve this dilemma.\&#8221;</p>
<p>For real-time testing the high-end stuff like VMotion, load-balancing, etc, that\&#8217;s true. For leaning about VMware or for developing things to run in the datacentre, it certainly isn\&#8217;t. I\&#8217;m accomplishing many useful things with VMware server (free) on a desktop system with Intel DQ35JO MoBo, E8400 CPU (2 real cores, 4 Hyperthread cores &#8211; a quad Q9xxx CPU would be better), 4Gb RAM (8GB upgrade is possible), CentOS 5.3 i86-64 host, Intel VT turned on in the BIOS (not essential), and an old PCI Ethernet card to give me an eth1 to play with. </p>
<p>This isn\&#8217;t even top-end desktop hardware. That would be Core i7, 12Gb RAM (24Gb possible). </p>
<p>The VMWare training course I went on was using real VMWare ESX but the datastore was just a bog-standard Linux server exporting via NFS. Too slow for production(?) but VMotion &#38; load-balancing demo worked fine.</p>
]]></content:encoded>
	</item>
</channel>
</rss>