<?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>ESXi 5.0 &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<atom:link href="https://magander.se/tag/esxi-5-0/feed/" rel="self" type="application/rss+xml" />
	<link>https://magander.se</link>
	<description></description>
	<lastBuildDate>Tue, 29 Apr 2014 20:34:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://magander.se/wp-content/uploads/2021/01/cropped-Screenshot-2021-01-19-at-22.37.56-32x32.png</url>
	<title>ESXi 5.0 &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<link>https://magander.se</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>ESXi 5.1 U1 Purple Screen of Death</title>
		<link>https://magander.se/esxi-5-1-u1-purple-screen-of-death/</link>
					<comments>https://magander.se/esxi-5-1-u1-purple-screen-of-death/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 29 Apr 2014 20:34:29 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[0x418044c00000]]></category>
		<category><![CDATA[1065491]]></category>
		<category><![CDATA[201401001]]></category>
		<category><![CDATA[5.1 U1]]></category>
		<category><![CDATA[5.1 U2]]></category>
		<category><![CDATA[crash]]></category>
		<category><![CDATA[e1000]]></category>
		<category><![CDATA[E1000DevRx]]></category>
		<category><![CDATA[e1000e]]></category>
		<category><![CDATA[E1000PollRxRing]]></category>
		<category><![CDATA[ESXi 5.0]]></category>
		<category><![CDATA[ESXi 5.1]]></category>
		<category><![CDATA[ESXi 5.1 U1]]></category>
		<category><![CDATA[ESXi 5.1 U2]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi crash]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[ESXi server]]></category>
		<category><![CDATA[ESXi500-201401001]]></category>
		<category><![CDATA[gs=0x418044c00000]]></category>
		<category><![CDATA[IOChain_Resume]]></category>
		<category><![CDATA[PortOutput]]></category>
		<category><![CDATA[PSOD]]></category>
		<category><![CDATA[Purple Screen of death]]></category>
		<category><![CDATA[VASpace]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vmxnet3]]></category>
		<guid isPermaLink="false">http://magander.se/?p=3475</guid>

					<description><![CDATA[A few days ago i was contacted by a customer who was running vSphere 5.1 U1 which is about one year old. For various reasons they have not yet upgraded to a later version of vSphere 5.1 or to vSphere 5.5. However, there has been quite some time since i a have seen a purple screen &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-5-1-u1-purple-screen-of-death/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-5-1-u1-purple-screen-of-death/feed/</wfw:commentRss>
			<slash:comments>9</slash:comments>
		
		
			</item>
		<item>
		<title>ESXi host advanced settings</title>
		<link>https://magander.se/esxi-host-advanced-settings/</link>
					<comments>https://magander.se/esxi-host-advanced-settings/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 16 Jul 2013 07:53:09 +0000</pubDate>
				<category><![CDATA[vSphere]]></category>
		<category><![CDATA[/etc/vmware/settings]]></category>
		<category><![CDATA[5.5]]></category>
		<category><![CDATA[BPDU]]></category>
		<category><![CDATA[disk.terminateVMOnPDLDefault]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[ESXi 5.0]]></category>
		<category><![CDATA[ESXi 5.1]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi advanced]]></category>
		<category><![CDATA[ESXi host advanced settings]]></category>
		<category><![CDATA[Net.BlockGuestBPDU]]></category>
		<category><![CDATA[ScratchConfig]]></category>
		<category><![CDATA[ScratchConfig.ConfiguredScratchLocation]]></category>
		<category><![CDATA[syslog]]></category>
		<category><![CDATA[VMkernel.Boot.terminateVMOnPDL]]></category>
		<category><![CDATA[vSphere 5.5]]></category>
		<guid isPermaLink="false">http://magander.se/?p=1455</guid>

					<description><![CDATA[During every vSphere design and Health Check the vSphere advanced settings are being discussed and every once in a while i receive an email asking me what vSphere advanced settings i normally use and recommends. I know Duncan Epping wrote a blog post about when to use the vSphere advanced settings a while ago. In general i agree &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-host-advanced-settings/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-host-advanced-settings/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>VMware Multiple NIC vMotion generates unicast flooding in the network</title>
		<link>https://magander.se/vmware-multiple-nic-vmotion-generates-unicast-flooding-in-the-network/</link>
					<comments>https://magander.se/vmware-multiple-nic-vmotion-generates-unicast-flooding-in-the-network/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 14 Mar 2013 19:02:03 +0000</pubDate>
				<category><![CDATA[vSphere]]></category>
		<category><![CDATA[ESXi 5.0]]></category>
		<category><![CDATA[ESXi 5.1]]></category>
		<category><![CDATA[vMotion multiple-NIC unicast flooding]]></category>
		<guid isPermaLink="false">http://magander.se/?p=31</guid>

					<description><![CDATA[————————————————————————————————- Blog post updated 2013-07-18 The problem described in this blog post has been fixed in the ESXi 5.0 U2 and in the 5.1 U1 releases but the original blog post is left unchanged. ————————————————————————————————- I have been using the VMware multiple NIC vMotion, VMware KB 2007467 , configuration where possible and needed, e.g. running high &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmware-multiple-nic-vmotion-generates-unicast-flooding-in-the-network/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vmware-multiple-nic-vmotion-generates-unicast-flooding-in-the-network/feed/</wfw:commentRss>
			<slash:comments>11</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Object Caching 25/86 objects using Disk
Page Caching using Disk: Enhanced 

Served from: magander.se @ 2026-06-29 00:17:05 by W3 Total Cache
-->