<?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>Virtualization - Servers - OS - virtuBLOG.com &#187; esx</title>
	<atom:link href="http://virtublog.com/tag/esx/feed/" rel="self" type="application/rss+xml" />
	<link>http://virtublog.com</link>
	<description></description>
	<lastBuildDate>Wed, 22 Feb 2012 15:18:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>ESX 4.0u1 Intel Quad NIC issue</title>
		<link>http://virtublog.com/2010/01/24/esx-4-0u1-intel-quad-nic-issue/</link>
		<comments>http://virtublog.com/2010/01/24/esx-4-0u1-intel-quad-nic-issue/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 01:54:41 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere/ESX]]></category>
		<category><![CDATA[ddk]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[issue]]></category>
		<category><![CDATA[maintenance mode]]></category>
		<category><![CDATA[NIC]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[quad port]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[server adapters]]></category>
		<category><![CDATA[Service Console]]></category>
		<category><![CDATA[U PowerEdge]]></category>
		<category><![CDATA[undisker]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=199</guid>
		<description><![CDATA[My server of choice for running ESX 4.0 is currently Dell&#8217;s 2U PowerEdge R710. Recently I received 2 of these and began the build out process, only to find that the ESX 4.0u1 installer (and ultimately the entire OS) did [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2010/01/24/esx-4-0u1-intel-quad-nic-issue/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>SRM &#8211; Trusted Certificates</title>
		<link>http://virtublog.com/2009/09/23/srm-trusted-certificates/</link>
		<comments>http://virtublog.com/2009/09/23/srm-trusted-certificates/#comments</comments>
		<pubDate>Wed, 23 Sep 2009 00:46:45 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[SRM]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[certificate request]]></category>
		<category><![CDATA[command]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[issue certificates]]></category>
		<category><![CDATA[move]]></category>
		<category><![CDATA[move project]]></category>
		<category><![CDATA[SAN]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[site]]></category>
		<category><![CDATA[ssl certs]]></category>
		<category><![CDATA[virtual machines]]></category>
		<category><![CDATA[vSphere/ESX]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=167</guid>
		<description><![CDATA[Today I began my work with VMware&#8217;s DR product, SRM. I&#8217;ll be using this tool to migrate a few hundred virtual machines from one datacenter to another, not for DR purposes. The first issue I ran into took me quite [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/09/23/srm-trusted-certificates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Changing the Service Console VLAN ID via Command Line</title>
		<link>http://virtublog.com/2009/07/07/changing-the-service-console-vlan-id-via-command-line/</link>
		<comments>http://virtublog.com/2009/07/07/changing-the-service-console-vlan-id-via-command-line/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 22:35:27 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere/ESX]]></category>
		<category><![CDATA[Console]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[p service]]></category>
		<category><![CDATA[service]]></category>
		<category><![CDATA[Service Console]]></category>
		<category><![CDATA[Use]]></category>
		<category><![CDATA[VLAN]]></category>
		<category><![CDATA[vlan id]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSwitch]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=164</guid>
		<description><![CDATA[To set the VLAN ID of your service console (if you entered the wrong ID, forgot to enter an ID, etc.), you can use the esxcfg-vswitch command! esxcfg-vswitch vSwitch0 -v XX -p &#8220;Service Console&#8221; (where XX is your VLAN ID [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/07/07/changing-the-service-console-vlan-id-via-command-line/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Extending Windows Server Volumes</title>
		<link>http://virtublog.com/2009/06/18/extending-servervolumes/</link>
		<comments>http://virtublog.com/2009/06/18/extending-servervolumes/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 01:37:32 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere/ESX]]></category>
		<category><![CDATA[Windows Server]]></category>
		<category><![CDATA[available disk space]]></category>
		<category><![CDATA[dell computer corporation]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[extpart]]></category>
		<category><![CDATA[os boot]]></category>
		<category><![CDATA[script mode]]></category>
		<category><![CDATA[size]]></category>
		<category><![CDATA[VI]]></category>
		<category><![CDATA[volume]]></category>
		<category><![CDATA[volume expansion]]></category>
		<category><![CDATA[volume size]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=134</guid>
		<description><![CDATA[As ESX has matured, extending the size of .vmdk disks has become easier and easier.  In ESX 3.5, using the VI client, you can simply edit your VM settings and increase the size of the disk. (or you can use [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/06/18/extending-servervolumes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ESX &#8211; Enabling Hardware Virtualization</title>
		<link>http://virtublog.com/2009/06/15/hardware-virtualizatio/</link>
		<comments>http://virtublog.com/2009/06/15/hardware-virtualizatio/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 23:46:10 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere/ESX]]></category>
		<category><![CDATA[AMD-V]]></category>
		<category><![CDATA[BIOS]]></category>
		<category><![CDATA[compatible processors]]></category>
		<category><![CDATA[drs]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[fault tolerance]]></category>
		<category><![CDATA[grep]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[hardware 1]]></category>
		<category><![CDATA[hardware virtualization]]></category>
		<category><![CDATA[harpertown]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[Intel-VT]]></category>
		<category><![CDATA[Service Console]]></category>
		<category><![CDATA[system bios]]></category>
		<category><![CDATA[Tolerance]]></category>
		<category><![CDATA[vMotion]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=125</guid>
		<description><![CDATA[There are several advantages to enabling hardware virtualization technology in the BIOS of your servers when using vSphere or ESX. These include the ability to use EVC (Enhanced vMotion Compatibility) on your DRS clusters, the use of 64bit OS guests, [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/06/15/hardware-virtualizatio/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware &#8211; Security Bulletins</title>
		<link>http://virtublog.com/2009/06/15/vmware-security-bulletins/</link>
		<comments>http://virtublog.com/2009/06/15/vmware-security-bulletins/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 22:59:41 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere/ESX]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[security advisories]]></category>
		<category><![CDATA[security bulletins]]></category>
		<category><![CDATA[security center]]></category>
		<category><![CDATA[system]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=119</guid>
		<description><![CDATA[As with any good system, patching is extremely important to keeping your system in safe, running condition. The same holds true for ESX. I&#8217;d recommend that anyone who administers an ESX environment sign up to receive critical security bulletins from [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/06/15/vmware-security-bulletins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ESX &#8211; 64GB Memory Limitation</title>
		<link>http://virtublog.com/2009/06/10/esx-64gb-memory-limitation/</link>
		<comments>http://virtublog.com/2009/06/10/esx-64gb-memory-limitation/#comments</comments>
		<pubDate>Wed, 10 Jun 2009 16:27:50 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere/ESX]]></category>
		<category><![CDATA[Dell]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[host summary]]></category>
		<category><![CDATA[issue]]></category>
		<category><![CDATA[memory type range]]></category>
		<category><![CDATA[memory type range registers]]></category>
		<category><![CDATA[mttr]]></category>
		<category><![CDATA[RAM]]></category>
		<category><![CDATA[ram usage]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[single user mode]]></category>
		<category><![CDATA[Tab]]></category>
		<category><![CDATA[VMkernel]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=108</guid>
		<description><![CDATA[Trying to install ESX  3.X on a new server with greater than 64GB of RAM? Then you&#8217;ve probably run into a problem. When looking at the host summary in VC, a host with no VMs on it will appear to be utilizing [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/06/10/esx-64gb-memory-limitation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ESX &#8211; Options for setting a static MAC in a VM</title>
		<link>http://virtublog.com/2009/06/09/esx-options-for-setting-a-static-mac-in-a-vm/</link>
		<comments>http://virtublog.com/2009/06/09/esx-options-for-setting-a-static-mac-in-a-vm/#comments</comments>
		<pubDate>Tue, 09 Jun 2009 23:24:07 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere/ESX]]></category>
		<category><![CDATA[address]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[ethernet]]></category>
		<category><![CDATA[EthernetX]]></category>
		<category><![CDATA[ff ff]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[mac address]]></category>
		<category><![CDATA[NIC]]></category>
		<category><![CDATA[p2v]]></category>
		<category><![CDATA[range]]></category>
		<category><![CDATA[ssh session]]></category>
		<category><![CDATA[static addresses]]></category>
		<category><![CDATA[Virtual]]></category>
		<category><![CDATA[virtual center]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=97</guid>
		<description><![CDATA[Along the way you might run into a P2V (or need to build a new VM) that will host an application which has a license attached to it&#8217;s NIC. In order to do this, you generally need to provide the [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/06/09/esx-options-for-setting-a-static-mac-in-a-vm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware SRM &#8211; Datastore Naming</title>
		<link>http://virtublog.com/2009/06/08/vmware-srm-datastore-naming/</link>
		<comments>http://virtublog.com/2009/06/08/vmware-srm-datastore-naming/#comments</comments>
		<pubDate>Mon, 08 Jun 2009 23:15:32 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[SRM]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[c program]]></category>
		<category><![CDATA[convention]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[hosts]]></category>
		<category><![CDATA[lt]]></category>
		<category><![CDATA[NAME]]></category>
		<category><![CDATA[naming convention]]></category>
		<category><![CDATA[Per]]></category>
		<category><![CDATA[production]]></category>
		<category><![CDATA[site]]></category>
		<category><![CDATA[snapshots]]></category>

		<guid isPermaLink="false">http://virtublog.com/?p=84</guid>
		<description><![CDATA[When failing over from a production site to a DR site, the datastores that are mounted on the ESX hosts at your DR site are named using the &#8220;snap-xxxxxxx-NAME&#8221; naming convention by default. Per this thread, this was not this [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/06/08/vmware-srm-datastore-naming/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ESX Best Practice &#8211; Service Console memory</title>
		<link>http://virtublog.com/2009/06/07/esx-best-practive-service-console-memory/</link>
		<comments>http://virtublog.com/2009/06/07/esx-best-practive-service-console-memory/#comments</comments>
		<pubDate>Sun, 07 Jun 2009 06:00:14 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[vSphere/ESX]]></category>
		<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[Service Console]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://virtublog.com/2009/06/07/esx-best-practive-service-console-memory/</guid>
		<description><![CDATA[Something I&#8217;ve known the benefits of for a while, but didn&#8217;t actually make part of my standard ESX build until fairly recently, is increasing the service console memory during install to 800MB. Out of the box, VMware has given  (in [...]]]></description>
		<wfw:commentRss>http://virtublog.com/2009/06/07/esx-best-practive-service-console-memory/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

