<?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: Cloning Or Converting Linux VM From VMWare Workstation To ESX Server: ETH0 Gone. ETH1 Available?</title>
	<atom:link href="http://lostechies.com/derickbailey/2009/06/20/cloning-or-converting-linux-vm-from-vmware-workstation-to-esx-server-eth0-gone-eth1-available/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/derickbailey/2009/06/20/cloning-or-converting-linux-vm-from-vmware-workstation-to-esx-server-eth0-gone-eth1-available/</link>
	<description>Better Than Yesterday</description>
	<lastBuildDate>Fri, 24 May 2013 06:39:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Ike</title>
		<link>http://lostechies.com/derickbailey/2009/06/20/cloning-or-converting-linux-vm-from-vmware-workstation-to-esx-server-eth0-gone-eth1-available/#comment-2593</link>
		<dc:creator>Ike</dc:creator>
		<pubDate>Wed, 04 Jul 2012 08:51:00 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derickbailey/archive/2009/06/20/cloning-or-converting-linux-vm-from-vmware-workstation-to-esx-server-eth0-gone-eth1-available.aspx#comment-2593</guid>
		<description>Thanks Derick, I had same error after restoring a vmware virtual vCenter appliance (vcsa) 5.0. VM powered up ok, but had no NIC. After much searching came across your article, I applied above, and voila! I have a working vm. 
Thanks</description>
		<content:encoded><![CDATA[<p>Thanks Derick, I had same error after restoring a vmware virtual vCenter appliance (vcsa) 5.0. VM powered up ok, but had no NIC. After much searching came across your article, I applied above, and voila! I have a working vm.<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Jensen</title>
		<link>http://lostechies.com/derickbailey/2009/06/20/cloning-or-converting-linux-vm-from-vmware-workstation-to-esx-server-eth0-gone-eth1-available/#comment-2096</link>
		<dc:creator>Christian Jensen</dc:creator>
		<pubDate>Mon, 09 Jan 2012 18:28:00 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derickbailey/archive/2009/06/20/cloning-or-converting-linux-vm-from-vmware-workstation-to-esx-server-eth0-gone-eth1-available.aspx#comment-2096</guid>
		<description>Thanks a ton - I had never found out this myself :-)

Uploaded from Workstation 8 directly to ESX 4 and had this problem.</description>
		<content:encoded><![CDATA[<p>Thanks a ton &#8211; I had never found out this myself :-)</p>
<p>Uploaded from Workstation 8 directly to ESX 4 and had this problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Leverton</title>
		<link>http://lostechies.com/derickbailey/2009/06/20/cloning-or-converting-linux-vm-from-vmware-workstation-to-esx-server-eth0-gone-eth1-available/#comment-309</link>
		<dc:creator>Nick Leverton</dc:creator>
		<pubDate>Sun, 21 Jun 2009 21:04:21 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derickbailey/archive/2009/06/20/cloning-or-converting-linux-vm-from-vmware-workstation-to-esx-server-eth0-gone-eth1-available.aspx#comment-309</guid>
		<description>This is a product of the last few versions of udev and has bitten me equally on both Debian and Fedora (Fedora perhaps even the more so cos it&#039;s hit more machines).   Both in the case where you change one interface card and in the case where you change the entire platform, I would think it more useful to enumerate new network cards into the places of those which are no longer present, rather than continuing from eth2, eth3 etc.</description>
		<content:encoded><![CDATA[<p>This is a product of the last few versions of udev and has bitten me equally on both Debian and Fedora (Fedora perhaps even the more so cos it&#8217;s hit more machines).   Both in the case where you change one interface card and in the case where you change the entire platform, I would think it more useful to enumerate new network cards into the places of those which are no longer present, rather than continuing from eth2, eth3 etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
