<?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 host &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<atom:link href="https://magander.se/tag/esxi-host/feed/" rel="self" type="application/rss+xml" />
	<link>https://magander.se</link>
	<description></description>
	<lastBuildDate>Thu, 25 Jan 2018 20:00:31 +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 host &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<link>https://magander.se</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>vSphere VM vCPU to ESXi host pCPU core allocation</title>
		<link>https://magander.se/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/</link>
					<comments>https://magander.se/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Sun, 01 Jun 2014 15:51:13 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[CPU core]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[ESXi host CPU]]></category>
		<category><![CDATA[ESXi host CPU core]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VM vCPU]]></category>
		<category><![CDATA[vSphere VM vCPU to ESXi host CPU subscription]]></category>
		<guid isPermaLink="false">http://magander.se/?p=3538</guid>

					<description><![CDATA[There has been quite a lot of discussion regarding resource utilization and resource allocation in vSphere environments lately. There are a lot of tools around doing analysis (some better than others) of your environment and gives suggestions if you need to e.g.: Add more resources (CPU, RAM, Disk, Network) to your vSphere cluster. Down size &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vsphere-vm-vcpu-to-esxi-host-cpu-core-allocation/feed/</wfw:commentRss>
			<slash:comments>14</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>ESXi host HBA priority</title>
		<link>https://magander.se/esxi-host-hba-priority/</link>
					<comments>https://magander.se/esxi-host-hba-priority/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Wed, 09 Oct 2013 20:31:04 +0000</pubDate>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[ESXi host HBA priority]]></category>
		<category><![CDATA[HBA]]></category>
		<category><![CDATA[host bus adapter]]></category>
		<category><![CDATA[priority]]></category>
		<guid isPermaLink="false">http://magander.se/?p=2125</guid>

					<description><![CDATA[A few days back i had an interesting chat with one of my customers. I’ll provide some background information before going in to the actual problem statement. Background information. The vSphere setup includes: Rack servers 2 x 8 core CPUs per ESXi host. 192 GB RAM per ESXi host. 2 x 1 port Fibre Channel &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-host-hba-priority/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-host-hba-priority/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>Configure and report the ESXi host TSM-SSH service using PowerCLI</title>
		<link>https://magander.se/configure-and-report-the-esxi-host-tsm-ssh-service-using-powercli/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 13 Jun 2013 14:49:38 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[TSM-SSH]]></category>
		<guid isPermaLink="false">http://magander.se/?p=1247</guid>

					<description><![CDATA[A customer contacted me the other day asking for a way to verify if the ESXi host TSM-SSH (SSH) service is running, and if so: Turn off the TSM-SSH service. Send an e-mail report including all ESXi hosts where the TSM-SSH service was stopped. The customer’s vSphere administrators sometimes enable the ESXi host TSM-SSH service &#8230; </p><p><a class="more-link block-button" href="https://magander.se/configure-and-report-the-esxi-host-tsm-ssh-service-using-powercli/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>ESXi host advanced configuration using PowerCLI &#8211; parameter Net.BlockGuestBPDU</title>
		<link>https://magander.se/esxi-host-advanced-configuration-using-powercli/</link>
					<comments>https://magander.se/esxi-host-advanced-configuration-using-powercli/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Mon, 06 May 2013 13:45:37 +0000</pubDate>
				<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[advanced configuration]]></category>
		<category><![CDATA[Advanced setting]]></category>
		<category><![CDATA[BPDU]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[ESXi host]]></category>
		<category><![CDATA[Get-VMHostAdvancedConfiguration]]></category>
		<category><![CDATA[Net.BlockGuestBPDU]]></category>
		<category><![CDATA[set-VMHostAdvancedConfiguration]]></category>
		<guid isPermaLink="false">http://magander.se/?p=1051</guid>

					<description><![CDATA[I was recently asked by one customer to verify the existing Bridge Protocol Data Unit (BPDU) Filter configuration for their 75+ ESXi hosts and if needed (not activated) change the default configuration from the value “0” to the value “1” to activate the feature. This blog post will focus on the PowerCLI configuration and not explaining &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-host-advanced-configuration-using-powercli/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-host-advanced-configuration-using-powercli/feed/</wfw:commentRss>
			<slash:comments>3</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 25/118 objects using Disk
Page Caching using Disk: Enhanced 

Served from: magander.se @ 2026-06-28 23:31:41 by W3 Total Cache
-->