<?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 Update 3 &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<atom:link href="https://magander.se/tag/esxi-5-5-update-3/feed/" rel="self" type="application/rss+xml" />
	<link>https://magander.se</link>
	<description></description>
	<lastBuildDate>Thu, 18 Aug 2016 05:38:30 +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 Update 3 &#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>
	</channel>
</rss>

<!--
Object Caching 25/67 objects using Disk
Page Caching using Disk: Enhanced 

Served from: magander.se @ 2026-06-28 21:22:38 by W3 Total Cache
-->