<?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.5 &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<atom:link href="https://magander.se/tag/esxi-5-5/feed/" rel="self" type="application/rss+xml" />
	<link>https://magander.se</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2017 19:23:43 +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.5 &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<link>https://magander.se</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Heads Up! &#8211; ESXi 5.5 Update 3 can crash VMs after snapshot delete</title>
		<link>https://magander.se/heads-up-esxi-5-5-update-3-can-crash-vms-after-snapshot-delete/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Wed, 30 Sep 2015 18:24:51 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[[YYYY-MM-DD] Z| vcpu-0| I120: SNAPSHOT: SnapshotDiskTreeFind: Detected node change from 'scsiX:X' to '']]></category>
		<category><![CDATA[Caught signal 11]]></category>
		<category><![CDATA[Detected node change from]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi 5.5 U3]]></category>
		<category><![CDATA[ESXi 5.5 Update 3]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[scsiX:X]]></category>
		<category><![CDATA[SNAPSHOT: SnapshotDiskTreeFind]]></category>
		<category><![CDATA[SnapshotDiskTreeFind]]></category>
		<category><![CDATA[unexpected signal]]></category>
		<category><![CDATA[Unexpected signal: 11. And [msg.panic.haveLog]]]></category>
		<category><![CDATA[VCDX56]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6162</guid>

					<description><![CDATA[Updated 2015-10-06 VMware released a patch today that will fix this problem, KB available here ————————— Updated 2015-10-01 Today VMware leased a KB 2133118  for the below described issue. No resolution included but a workaround. ———————— Original post ———————– Today i came across this VMware Communities thread that explains different scenarios where vSphere ESXi 5.5 Update 3 &#8230; </p><p><a class="more-link block-button" href="https://magander.se/heads-up-esxi-5-5-update-3-can-crash-vms-after-snapshot-delete/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>vSphere 5.5 Update 3 released</title>
		<link>https://magander.se/vsphere-5-5-update-3-released/</link>
					<comments>https://magander.se/vsphere-5-5-update-3-released/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 17 Sep 2015 06:53:24 +0000</pubDate>
				<category><![CDATA[vSphere]]></category>
		<category><![CDATA[5.5 U3]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi 5.5 U3]]></category>
		<category><![CDATA[ESXi 5.5 Update 3]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[U3]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenter Orchestrator]]></category>
		<category><![CDATA[vCenter Orchestrator 5]]></category>
		<category><![CDATA[vCenter Orchestrator 5.5]]></category>
		<category><![CDATA[vCenter Orchestrator 5.5.3]]></category>
		<category><![CDATA[vCO]]></category>
		<category><![CDATA[vCO 5]]></category>
		<category><![CDATA[vCO 5.5]]></category>
		<category><![CDATA[vCO 5.5.3]]></category>
		<category><![CDATA[vSphere 5.5 U3]]></category>
		<category><![CDATA[vSphere 5.5 Update 3]]></category>
		<category><![CDATA[vSphere Replication]]></category>
		<category><![CDATA[vSphere Replication 5]]></category>
		<category><![CDATA[vSphere Replication 5.8]]></category>
		<category><![CDATA[vSphere Replication 5.8.1]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6101</guid>

					<description><![CDATA[Yesterday, 2015-09-16, VMware released vSphere 5.5. Update 3 which includes new versions for: vCenter Server ESXi I have identified at least two problems i have seen that are now resolved in vCenter Server Defined permissions behave differently in vSphere Client and Web Client Moving VMs between the folders is disabled in the Web Client when permission &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vsphere-5-5-update-3-released/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vsphere-5-5-update-3-released/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>ESXi mgmt network lost when adding ESXi to VDS</title>
		<link>https://magander.se/esxi-mgmt-network-lost-when-adding-esxi-to-vds/</link>
					<comments>https://magander.se/esxi-mgmt-network-lost-when-adding-esxi-to-vds/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 01 Sep 2015 19:16:56 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[esxcli]]></category>
		<category><![CDATA[esxcli network ip interface ipv4 get]]></category>
		<category><![CDATA[esxcli network ip interface set -i vmk0 -e true]]></category>
		<category><![CDATA[esxcli network ip route ipv4 list]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi 5.5 U2]]></category>
		<category><![CDATA[kill -9]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[PID]]></category>
		<category><![CDATA[ps -j]]></category>
		<category><![CDATA[ps -j |grep -i dcui]]></category>
		<category><![CDATA[Unable to kill DCUI]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenter Server 5.5 U2e]]></category>
		<category><![CDATA[vSphere vCenter Server]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6052</guid>

					<description><![CDATA[So the other day a had a very unpleasant experience when adding a few new ESXi hosts, version 5.5 U2 including the latest patch, to an existing vCenter Server (5.5 U2e) vNetwork Distributed switch (VDS). I used the wizard in the vSphere web client and followed the recommendation but i guess i could have made &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-mgmt-network-lost-when-adding-esxi-to-vds/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-mgmt-network-lost-when-adding-esxi-to-vds/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>vMotion &#8211; A general system error occurred</title>
		<link>https://magander.se/vmotion-a-general-system-error-occurred/</link>
					<comments>https://magander.se/vmotion-a-general-system-error-occurred/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 27 Aug 2015 12:57:30 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.5]]></category>
		<category><![CDATA[0xbad0004]]></category>
		<category><![CDATA[1031636]]></category>
		<category><![CDATA[195887108]]></category>
		<category><![CDATA[2143827]]></category>
		<category><![CDATA[2183111]]></category>
		<category><![CDATA[5]]></category>
		<category><![CDATA[6]]></category>
		<category><![CDATA[6.5]]></category>
		<category><![CDATA[A general system error occurred]]></category>
		<category><![CDATA[build 2143827]]></category>
		<category><![CDATA[build 2183111]]></category>
		<category><![CDATA[busy 195887108]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi 5.5.0 2143827]]></category>
		<category><![CDATA[failed]]></category>
		<category><![CDATA[failed with status busy]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vcenter Server 5.5]]></category>
		<category><![CDATA[vCenter Server 5.5.0 2183111]]></category>
		<category><![CDATA[vMotion fails with the error: remote host IP_Address failed with status Busy (1031636)]]></category>
		<category><![CDATA[vMotion migration]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6025</guid>

					<description><![CDATA[Updated 20170127 Apparently this applies to vSphere 6.5 as well according to a comment below. Thanks Joe for letting us know ———————————————————————– The other day i had an issue with vMotion migrations in my vSphere environment running the following versions: vCenter Server 5.5.0 build 2183111 ESXi 5.5.0 build 2143827 The error i was seeing happened at &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmotion-a-general-system-error-occurred/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vmotion-a-general-system-error-occurred/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>Storage vMotion fails with error Already disconnected</title>
		<link>https://magander.se/storage-vmotion-fails-with-error-already-disconnected/</link>
					<comments>https://magander.se/storage-vmotion-fails-with-error-already-disconnected/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 24 Mar 2015 19:54:57 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[(0xbad002e)]]></category>
		<category><![CDATA[A general system error occurred]]></category>
		<category><![CDATA[Already disconnected]]></category>
		<category><![CDATA[Already disconnected (0xbad002e)]]></category>
		<category><![CDATA[esxcli software vib list]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi 5.5 U2a]]></category>
		<category><![CDATA[ethtool -S]]></category>
		<category><![CDATA[ethtool -S vmnic0 | grep -i error]]></category>
		<category><![CDATA[ixgbe]]></category>
		<category><![CDATA[Migration to host]]></category>
		<category><![CDATA[MigrationResourceWarningEvent]]></category>
		<category><![CDATA[rx_missed_errors]]></category>
		<category><![CDATA[Storage vMotion]]></category>
		<category><![CDATA[Storage vMotion Fails]]></category>
		<category><![CDATA[TaskEvent]]></category>
		<category><![CDATA[vcenter Server 5.5]]></category>
		<category><![CDATA[vCenter Server 5.5 U2d]]></category>
		<category><![CDATA[VmBeginHotMigrateEvent]]></category>
		<category><![CDATA[VmEmigratingEvent]]></category>
		<category><![CDATA[VmFailedMigrateEvent]]></category>
		<category><![CDATA[vMotion]]></category>
		<guid isPermaLink="false">http://magander.se/?p=5337</guid>

					<description><![CDATA[This blog post applies to vCenter Server version 5.5. U2d and ESXi server version 5.5 U2a. A few days back i got involved in a virtual machine migration (VM) issue. The VMs were suppose to be migrated from one vSphere cluster to another without any chance of mounting one of the vSphere clusters datastore(s) to the other &#8230; </p><p><a class="more-link block-button" href="https://magander.se/storage-vmotion-fails-with-error-already-disconnected/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/storage-vmotion-fails-with-error-already-disconnected/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>HP HPSA driver 5.x.0.58-1 can cause ESXi 5.x PSOD</title>
		<link>https://magander.se/hp-hpsa-driver-5-x-0-58-1-can-cause-esxi-5-x-psod/</link>
					<comments>https://magander.se/hp-hpsa-driver-5-x-0-58-1-can-cause-esxi-5-x-psod/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 27 Jun 2014 08:25:13 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[5.5.0.60-1]]></category>
		<category><![CDATA[5.x.0.58-1]]></category>
		<category><![CDATA[cat /proc/driver/hpsa/hpsa0 | grep Driver]]></category>
		<category><![CDATA[DL 380]]></category>
		<category><![CDATA[DL380]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[G7]]></category>
		<category><![CDATA[HP Proliant DL380 G7]]></category>
		<category><![CDATA[HP ProLiant Smart Array Controller Driver for VMware vSphere 5.5]]></category>
		<category><![CDATA[hpsa]]></category>
		<category><![CDATA[hpsa 5.x.0.58-1]]></category>
		<category><![CDATA[hpsa0]]></category>
		<category><![CDATA[Proliant]]></category>
		<category><![CDATA[scsi]]></category>
		<category><![CDATA[scsi-hpsa]]></category>
		<category><![CDATA[scsi-hpsa-5.5.0.60-1OEM.550.0.0.1331820.x86_64.vib]]></category>
		<category><![CDATA[v 5.5.0.58-1OEM]]></category>
		<guid isPermaLink="false">http://magander.se/?p=3789</guid>

					<description><![CDATA[A few days ago i received a call from one of my old customers who asked for advice regarding a VMware ESXi 5.5 Purple Screen Of Death (PSOD) situation. He had already created a VMware service request but wanted a chat while waiting for a reply. I quickly searched the HP support center web site &#8230; </p><p><a class="more-link block-button" href="https://magander.se/hp-hpsa-driver-5-x-0-58-1-can-cause-esxi-5-x-psod/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/hp-hpsa-driver-5-x-0-58-1-can-cause-esxi-5-x-psod/feed/</wfw:commentRss>
			<slash:comments>23</slash:comments>
		
		
			</item>
		<item>
		<title>Nutanix Cluster, Storage Pool and Container setup</title>
		<link>https://magander.se/nutanix-cluster-storage-pool-and-container-setup/</link>
					<comments>https://magander.se/nutanix-cluster-storage-pool-and-container-setup/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 12 Jun 2014 17:18:36 +0000</pubDate>
				<category><![CDATA[Nutanix]]></category>
		<category><![CDATA[3.5.4]]></category>
		<category><![CDATA[cluster]]></category>
		<category><![CDATA[cluster setup]]></category>
		<category><![CDATA[Container]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[no video]]></category>
		<category><![CDATA[NOS 3.5.4]]></category>
		<category><![CDATA[novideo=true]]></category>
		<category><![CDATA[nutanix]]></category>
		<category><![CDATA[Nutanix cluster setup]]></category>
		<category><![CDATA[Nutanix Container]]></category>
		<category><![CDATA[Nutanix Operating System]]></category>
		<category><![CDATA[Nutanix Prism]]></category>
		<category><![CDATA[Nutanix Storage Pools]]></category>
		<category><![CDATA[Prism]]></category>
		<category><![CDATA[VCDX56]]></category>
		<guid isPermaLink="false">http://magander.se/?p=3689</guid>

					<description><![CDATA[During my first month at Nutanix I have been doing quite a few Nutanix presentations for potential customers and consultants. I have received a lot of questions during the presentations but also questions via email including, but not limited to, e.g. setup, management, snapshot, disaster recovery, availability, Controller Virtual Machine (CVM), performance. Even though there is a lot &#8230; </p><p><a class="more-link block-button" href="https://magander.se/nutanix-cluster-storage-pool-and-container-setup/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/nutanix-cluster-storage-pool-and-container-setup/feed/</wfw:commentRss>
			<slash:comments>13</slash:comments>
		
		
			</item>
		<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 VMkernel.Boot.terminateVMOnPDL configuration using PowerCLI</title>
		<link>https://magander.se/esxi-host-vmkernel-boot-terminatevmonpdl-configuration-using-powercli/</link>
					<comments>https://magander.se/esxi-host-vmkernel-boot-terminatevmonpdl-configuration-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 21 Jan 2014 16:51:58 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[5.1]]></category>
		<category><![CDATA[5.5]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[disk.terminateVMOnPDLDefault]]></category>
		<category><![CDATA[ESXi 5.1]]></category>
		<category><![CDATA[ESXi 5.1.x]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[user interaction]]></category>
		<category><![CDATA[VMkernel.Boot.terminateVMOnPDL]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere 5.5]]></category>
		<guid isPermaLink="false">http://magander.se/?p=2731</guid>

					<description><![CDATA[I have already written a blog post about how you can configure the ESXi host  setting disk.terminateVMOnPDLDefault in vSphere version 5.1. You can find that blog post here. I have received a couple of questions about how to configure the setting, called VMkernel.Boot.terminateVMOnPDL, in ESXi 5.5 so i decided to put together a blog post about it. &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-host-vmkernel-boot-terminatevmonpdl-configuration-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-host-vmkernel-boot-terminatevmonpdl-configuration-using-powercli/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Determine the VMFS disk space a thin provisioned virtual machine disk consumes</title>
		<link>https://magander.se/determine-the-vmfs-disk-space-a-thin-provisioned-virtual-machine-disk-consumes/</link>
					<comments>https://magander.se/determine-the-vmfs-disk-space-a-thin-provisioned-virtual-machine-disk-consumes/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 01 Nov 2013 09:03:39 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[determine thin provision disk consumption]]></category>
		<category><![CDATA[du]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[stat]]></category>
		<category><![CDATA[thin provision]]></category>
		<category><![CDATA[thin provision disk consumption]]></category>
		<category><![CDATA[vSphere 5.5]]></category>
		<guid isPermaLink="false">http://magander.se/?p=2271</guid>

					<description><![CDATA[I was asked by a customer the other day how to find out, using the ESXi command line, how much disk space a thin provisioned virtual machine disk consumes. Back in the ESX days you used the du command to query the virtual machine disk and in ESXi, version 5.5, you need to use the  stat command. Fot this &#8230; </p><p><a class="more-link block-button" href="https://magander.se/determine-the-vmfs-disk-space-a-thin-provisioned-virtual-machine-disk-consumes/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/determine-the-vmfs-disk-space-a-thin-provisioned-virtual-machine-disk-consumes/feed/</wfw:commentRss>
			<slash:comments>4</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>ESXi host disk.terminateVMOnPDLDefault configuration using PowerCLI</title>
		<link>https://magander.se/esxihost-disk-terminatevmonpdldefault-configuration-using-powercli/</link>
					<comments>https://magander.se/esxihost-disk-terminatevmonpdldefault-configuration-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 21 Mar 2013 21:06:33 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[5.1]]></category>
		<category><![CDATA[5.5]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[disk.terminateVMOnPDLDefault]]></category>
		<category><![CDATA[ESXi 5.1]]></category>
		<category><![CDATA[ESXi 5.1.x]]></category>
		<category><![CDATA[ESXi 5.5]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[user interaction]]></category>
		<category><![CDATA[VMkernel.Boot.terminateVMOnPDL]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere 5.5]]></category>
		<guid isPermaLink="false">http://magander.se/?p=195</guid>

					<description><![CDATA[This section is updated since vSphere 5.5 was GA during VMworld 2013. From now on the configuration option has changed regarding two things: Name – It is now called VMkernel.Boot.terminateVMOnPDL and not Disk.terminateVMOnPDLDefault Configuration – It is now an advanced ESXi configuration parameter and not a text string in the ESXi host file /etc/vmware/settings Continue reading if &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxihost-disk-terminatevmonpdldefault-configuration-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxihost-disk-terminatevmonpdldefault-configuration-using-powercli/feed/</wfw:commentRss>
			<slash:comments>6</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Object Caching 14/192 objects using Disk
Page Caching using Disk: Enhanced 

Served from: magander.se @ 2026-06-28 23:12:50 by W3 Total Cache
-->