<?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; Service Console</title>
	<atom:link href="http://virtublog.com/tag/service-console/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>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>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>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>

