 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Real (and Virtual) Adventures of Nathan the IT Guy &#187; e1000</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/information-technology/tag/e1000/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/information-technology</link>
	<description></description>
	<lastBuildDate>Fri, 17 May 2013 13:18:20 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>vSphere 4 Vmxnet3 Adapter</title>
		<link>http://itknowledgeexchange.techtarget.com/information-technology/vsphere-4-vmxnet3-adapter/</link>
		<comments>http://itknowledgeexchange.techtarget.com/information-technology/vsphere-4-vmxnet3-adapter/#comments</comments>
		<pubDate>Tue, 01 Dec 2009 00:25:47 +0000</pubDate>
		<dc:creator>Nathan Simon</dc:creator>
				<category><![CDATA[e1000]]></category>
		<category><![CDATA[Intel]]></category>
		<category><![CDATA[network infrastructure card]]></category>
		<category><![CDATA[NIC]]></category>
		<category><![CDATA[paravirtualization]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[vmxnet]]></category>
		<category><![CDATA[vmxnet3]]></category>
		<category><![CDATA[vSphere 4]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/information-technology/vsphere-4-vmxnet3-adapter/</guid>
		<description><![CDATA[So you think you know Vmware, you have recently upgraded to vSphere 4.0 and you provision a new virtual machine, using the standard E1000 Nick (basically an Intel Pro 1000 Network Interface Card), you have bound 4 1Gb Nics to the virtual switch that the VM is on, so basically, your OS will only get [...]]]></description>
				<content:encoded><![CDATA[<p>So you think you know Vmware, you have recently upgraded to vSphere 4.0 and you provision a new virtual machine, using the standard E1000 Nick (basically an Intel Pro 1000 Network Interface Card), you have bound 4 1Gb Nics to the virtual switch that the VM is on, so basically, your OS will only get 1Gb max through-put. Want more? That&#8217;s easy, bind a vmxnet3 adapter to the vm and you will now open up that pipe.</p>
<blockquote><p><strong>Question:</strong> What is VMXNET3?<br />
<strong>Answer:</strong> VMXNET3 builds upon VMXNET and Enhanced VMXNET as the third generation paravirtualized virtual networking NIC for guest operating systems.</p></blockquote>
<p>The VMXNET3 network adapter is a 10Gb virtual nic, with cards bound to it, you basically give that vm access to 4Gb of through-put, and if you attach more physical nics, you just keep increasing the through-put. With todays technology, server to workstation(1Gb Nic) file transfers are up to 60MB/sec!</p>
<p>Check out this <a href="http://communities.vmware.com/thread/208241" target="_blank">link</a>, to get the full scoop.</p>
<p>-NS</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/information-technology/vsphere-4-vmxnet3-adapter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
