<?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 Archives - Igor Oseledko</title>
	<atom:link href="https://www.igoroseledko.com/category/sysadmin/applications/virtualization/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.igoroseledko.com/category/sysadmin/applications/virtualization/</link>
	<description>I know everything. Just not all at once...</description>
	<lastBuildDate>Mon, 20 May 2024 22:19:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>AWS CLI Cheat Sheet</title>
		<link>https://www.igoroseledko.com/aws-cli-cheat-sheet/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Mon, 20 May 2024 22:19:49 +0000</pubDate>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">https://www.igoroseledko.com/?p=132824</guid>

					<description><![CDATA[<p>Originally published May 21, 2018 @ 10:18 pmThe installation and configuration process for AWS CLI is fairly simple. The package itself is installed with pip (yum -y install python-pip): pip install awscli --upgrade --user Selecting what you need from the output can be accomplished via awscli filters and queries; using the excellent jq JSON processor; [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/aws-cli-cheat-sheet/">AWS CLI Cheat Sheet</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>The Mystery of a Hemisphere</title>
		<link>https://www.igoroseledko.com/the-mystery-of-a-hemisphere/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Fri, 09 Feb 2024 14:57:44 +0000</pubDate>
				<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">https://www.igoroseledko.com/?p=132561</guid>

					<description><![CDATA[<p>Originally published February 9, 2018 @ 10:32 pmTo make this long (and embarrassing) story short: a friend&#8217;s kid had a homework assignment in geometry to calculate the surface area of a conjoined cone, a cylinder, and a hemisphere. Geometry being the only subject in which I never had anything less than perfect marks, I decided [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/the-mystery-of-a-hemisphere/">The Mystery of a Hemisphere</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Use PowerCLI to Change NIC Type</title>
		<link>https://www.igoroseledko.com/use-powercli-to-change-nic-type/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Tue, 31 Oct 2023 03:07:59 +0000</pubDate>
				<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">http://www.igoroseledko.com/?p=131563</guid>

					<description><![CDATA[<p>Originally published April 17, 2017 @ 11:16 amThis is a quick PowerCLI script that reads from a list of VM names and for each VM with network adapter type &#8220;E1000&#8221; changes it to &#8220;Vmxnet3&#8221;. Nothing fancy, no reboot is needed. MAC should stay the same, but this depends on your cluster network configuration. Set-PowerCLIConfiguration -Scope [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/use-powercli-to-change-nic-type/">Use PowerCLI to Change NIC Type</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Get a List of all ESX Hosts in a Datacenter</title>
		<link>https://www.igoroseledko.com/get-a-list-of-all-esx-hosts-in-a-datacenter/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Sun, 29 Oct 2023 00:32:55 +0000</pubDate>
				<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">http://www.igoroseledko.com/?p=131560</guid>

					<description><![CDATA[<p>Originally published April 17, 2017 @ 11:14 amAnother simple one-liner to get a list of hostnames of all ESX servers in the vCenter. This can be useful for a number of things, specifically as input for other PowerCLI scripts. Set-PowerCLIConfiguration -Scope Session -WebOperationTimeoutSeconds -1 -Confirm:$false; Import-Module VMware.VimAutomation.Vds; $VMHost=&#34;vcenter01.domain.com&#34;; Connect-VIServer -Server $VMHost -User &#039;DOMAIN\User&#039; -Password &#039;Password1&#039;; [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/get-a-list-of-all-esx-hosts-in-a-datacenter/">Get a List of all ESX Hosts in a Datacenter</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Configure and Run esxcli on Red Hat</title>
		<link>https://www.igoroseledko.com/configure-and-run-esxcli-on-red-hat/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Fri, 27 Oct 2023 04:03:34 +0000</pubDate>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">http://www.igoroseledko.com/?p=131574</guid>

					<description><![CDATA[<p>Originally published March 20, 2017 @ 1:00 pmThe esxcli utility is used to interface with the vSphere and ESX hosts. It is a useful tool for getting to some basic VMWare functionality from the Unix shell. It is also a pre-requisite for some of the server deployment and configuration management tools, such as SaltStack. Download [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/configure-and-run-esxcli-on-red-hat/">Configure and Run esxcli on Red Hat</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Sample Salt Proxy Configuration for vCenter/ESX</title>
		<link>https://www.igoroseledko.com/sample-salt-proxy-configuration-for-vcenter-esx/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 26 Oct 2023 14:07:29 +0000</pubDate>
				<category><![CDATA[Commands & Shells]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">http://www.igoroseledko.com/?p=131569</guid>

					<description><![CDATA[<p>Originally published March 20, 2017 @ 11:20 amThe Salt proxy agent is a&#160;relatively new feature of Salt allowing to control networked devices&#160;where salt-minion cannot be installed directly.&#160;The official Salt documentation on the subject is outdated and full of syntax errors. It&#8217;s actually quite sad that some talented folks at SaltStack spend months developing new functionality [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/sample-salt-proxy-configuration-for-vcenter-esx/">Sample Salt Proxy Configuration for vCenter/ESX</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Managing VMs with PowerCLI</title>
		<link>https://www.igoroseledko.com/managing-vms-with-powercli/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Mon, 23 Oct 2023 15:05:59 +0000</pubDate>
				<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">http://www.igoroseledko.com/?p=131585</guid>

					<description><![CDATA[<p>Originally published February 20, 2017 @ 1:21 amBelow is a collection of useful Power-CLI one-liners (or thereabouts) that can speed up your script-writing efforts. As everything Windows, things change often and for no obvious reason, so expect to see type is deprecated&#160;and parameter is obsolete&#160;warnings now and then.More often than not, they&#8217;re harmless: they like [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/managing-vms-with-powercli/">Managing VMs with PowerCLI</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Copying a VM between VCenters</title>
		<link>https://www.igoroseledko.com/copying-a-vm-between-vcenters/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Sun, 15 Oct 2023 20:12:56 +0000</pubDate>
				<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">http://www.igoroseledko.com/?p=131683</guid>

					<description><![CDATA[<p>Originally published November 12, 2016 @ 11:14 pmI had a little task: clone an operational VM from one VCenter to another. Normally, for such a task I would use the Standalone Converter. Unfortunately, this time I ran into an annoying SSH key issue: the source VM was an old 32-bit RHEL using DSA and my [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/copying-a-vm-between-vcenters/">Copying a VM between VCenters</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Fixing NIC Name in Cloned VMWare Linux Machines</title>
		<link>https://www.igoroseledko.com/fixing-nic-name-in-cloned-vmware-linux-machines/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 28 Sep 2023 01:17:14 +0000</pubDate>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">http://www.igoroseledko.com/?p=131740</guid>

					<description><![CDATA[<p>Originally published June 28, 2016 @ 11:28 amA suspected bug with certain versions of VMware ESX causes cloned Linux VMs to obtain a sequentially-number NIC. For example, if the parent VM had eth0, the clone will have eth1, and the clone of that clone will have eth2, etc. This can cause issues with centralized configuration [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/fixing-nic-name-in-cloned-vmware-linux-machines/">Fixing NIC Name in Cloned VMWare Linux Machines</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>VMWare VMDK Locked Error</title>
		<link>https://www.igoroseledko.com/vmware-vmdk-locked-error/</link>
		
		<dc:creator><![CDATA[Igor]]></dc:creator>
		<pubDate>Thu, 28 Sep 2023 00:39:28 +0000</pubDate>
				<category><![CDATA[Virtualization]]></category>
		<guid isPermaLink="false">http://www.igoroseledko.com/?p=132159</guid>

					<description><![CDATA[<p>Originally published May 21, 2016 @ 11:13 pmSo, being a Unix admin on-call for the week, I just spent half of my Saturday fixing a dead Windows VM. Very annoying. The best I can tell, the issue occurred during the snapshot operation. Either the VM was powered down or powered back up by some genius [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.igoroseledko.com/vmware-vmdk-locked-error/">VMWare VMDK Locked Error</a> appeared first on <a rel="nofollow" href="https://www.igoroseledko.com">Igor Oseledko</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
