<?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>Natalino Picone &#187; vmware</title>
	<atom:link href="http://www.picone.it/tag/vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.picone.it</link>
	<description>Il mio blog su una vita tecnologica</description>
	<lastBuildDate>Sat, 11 Jun 2011 12:24:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Scripted Removal Of Non-present Hardware After A P2V</title>
		<link>http://www.picone.it/2011/06/11/scripted-removal-of-non-present-hardware-after-a-p2v/</link>
		<comments>http://www.picone.it/2011/06/11/scripted-removal-of-non-present-hardware-after-a-p2v/#comments</comments>
		<pubDate>Sat, 11 Jun 2011 12:24:19 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://www.picone.it/?guid=375a3a2d4e38692a81b9e8354a540413</guid>
		<description><![CDATA[After converting a physical machine to a virtual machine, it is considered a best practice to remove unneeded applications, software, services, and device drivers which were tied to the physical machine but no longer applicable to the present day virtu...]]></description>
			<content:encoded><![CDATA[<p>After converting a physical machine to a virtual machine, it is considered a best practice to remove unneeded applications, software, services, and device drivers which were tied to the physical machine but no longer applicable to the present day virtual machine.  Performing this task from time to time manually isn’t too bad but at large scale, a manual process becomes inefficient.  There are tools available which will automate the process of removing unneeded device drivers (sometimes referred to as ghost hardware).  A former colleage put together a scripted solution for Windows VMs which I’m sharing here. </p>
<p>Copy the .zip file to the virtual machine local hard drive, extract it, and follow the instructions in the readme.txt file.  I have not thoroughly tested the tool.  No warranties – use at your own risk.  I would suggest using it on a test machine first to become comfortable with the process before using it on production machines or using on a large scale basis.</p>
<p>Download: <a href="http://www.boche.net/blog/wp-content/uploads/2011/remnonpresent.zip">remnonpresent.zip</a> (719KB)</p>
<p>Post from: <a href="http://www.boche.net/blog">boche.net - VMware Virtualization Evangelist</a>
</p><p>
Copyright (c) 2010 Jason Boche.  The contents of this post may not be reproduced or republished on another web page or web site without prior written permission.<br /><br /><a href="http://www.boche.net/blog/index.php/2011/06/11/scripted-removal-of-non-present-hardware-after-a-p2v/">Scripted Removal Of Non-present Hardware After A P2V</a></p>
<h3>Related Posts</h3><ul><li>May 7, 2011 -- <a href="http://www.boche.net/blog/index.php/2011/05/07/starwindmellanox-add-datacenter-storage-efficiency/" title="StarWind/Mellanox Add Datacenter Storage Efficiency">StarWind/Mellanox Add Datacenter Storage Efficiency</a></li><li>May 4, 2011 -- <a href="http://www.boche.net/blog/index.php/2011/05/04/vmturbo-free-performance-and-efficiency-reporter/" title="VMTurbo Free Performance and Efficiency Reporter">VMTurbo Free Performance and Efficiency Reporter</a></li><li>April 21, 2011 -- <a href="http://www.boche.net/blog/index.php/2011/04/21/product-review-veeam-backup-replication-v5/" title="Product Review: Veeam Backup &amp; Replication v5">Product Review: Veeam Backup &amp; Replication v5</a></li><li>April 3, 2011 -- <a href="http://www.boche.net/blog/index.php/2011/04/03/hds-and-vaai-integration/" title="HDS and VAAI Integration">HDS and VAAI Integration</a></li><li>February 28, 2011 -- <a href="http://www.boche.net/blog/index.php/2011/02/28/tiny-core-linux-and-operational-readiness/" title="Tiny Core Linux and Operational Readiness">Tiny Core Linux and Operational Readiness</a></li><li>February 18, 2011 -- <a href="http://www.boche.net/blog/index.php/2011/02/18/vmturbo-introduces-real-time-management-suite-for-virtualized-data-centers/" title="VMTurbo Introduces Real-time Management Suite for Virtualized Data Centers">VMTurbo Introduces Real-time Management Suite for Virtualized Data Centers</a></li><li>February 14, 2011 -- <a href="http://www.boche.net/blog/index.php/2011/02/14/vsphere-integration-with-emc-unisphere/" title="vSphere Integration With EMC Unisphere">vSphere Integration With EMC Unisphere</a></li><li>November 29, 2010 -- <a href="http://www.boche.net/blog/index.php/2010/11/29/flow-control/" title="Flow Control">Flow Control</a></li><li>August 16, 2010 -- <a href="http://www.boche.net/blog/index.php/2010/08/16/veeam-reporter-4-0-free-edition/" title="Veeam Reporter 4.0 Free Edition">Veeam Reporter 4.0 Free Edition</a></li><li>May 19, 2010 -- <a href="http://www.boche.net/blog/index.php/2010/05/19/top-10-free-vsphere-esx-tools-and-utilities-by-kendrickcoleman-com/" title="Top 10 Free vSphere ESX Tools and Utilities by KendrickColeman.com">Top 10 Free vSphere ESX Tools and Utilities by KendrickColeman.com</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.picone.it/2011/06/11/scripted-removal-of-non-present-hardware-after-a-p2v/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bug di VmWare blocca le macchine virtuali</title>
		<link>http://www.picone.it/2008/08/12/bug-di-vmware-blocca-le-macchine-virtuali/</link>
		<comments>http://www.picone.it/2008/08/12/bug-di-vmware-blocca-le-macchine-virtuali/#comments</comments>
		<pubDate>Tue, 12 Aug 2008 16:20:37 +0000</pubDate>
		<dc:creator>Nat</dc:creator>
				<category><![CDATA[Generale]]></category>
		<category><![CDATA[Tecnologia]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://www.picone.it/?p=400</guid>
		<description><![CDATA[Un bug appena scoperto in Vmware non permette ai server virtuali di accendersi dopo il 12/Agosto. Maggiori info sulla pagina di supporto di Vmware http://kb.vmware.com/kb/1006716. Il problema affligge i Vmware ESX 3.5 con update 2 (e quindi anche l&#8217;ESX3i free rilasciato a fine mese scorso). E&#8217; ovviamente incredibile che un bug di questa entità possa [...]]]></description>
			<content:encoded><![CDATA[<p>Un bug appena scoperto in Vmware non permette ai server virtuali di accendersi dopo il 12/Agosto. Maggiori info sulla pagina di supporto di Vmware <a href="http://kb.vmware.com/kb/1006716">http://kb.vmware.com/kb/1006716</a>. Il problema affligge i Vmware ESX 3.5 con update 2 (e quindi anche l&#8217;ESX3i free rilasciato a fine mese scorso).<br />
E&#8217; ovviamente incredibile che un bug di questa entità possa essere presente in un software di questo tipo. Inoltre Vmware ha dichiarato che un fix sarà disponibile in 36 ore (1 giorno e mezzo!).<br />
A causa della presunzione che hanno dimostrato negli ultimi anni non credo che questo problema passerà inosservato&#8230;</p>
<p><strong>UPDATE:</strong>Nel dettaglio il bug non permette di avviare le macchine virtuali dopo il 12 Agosto. Per avvio non si intende un riavvio dal sistema operativo della virtuale ma un avvio della VM dal VI. L&#8217;errore è generico ma nei log se ne trovano i dettagli. Il problema affligge quindi anche il VMotion tra un esx ed un altro (il pratica lanciando il VMotion da un server verso un altro questo fallirà).</p>
<p><strong>UPDATE2</strong>: Vmware ha rilasciato dei patch per fixare il problema:</p>
<ul>
<li>ESX 3.5 Update 2 <a href="http://download3.vmware.com/software/esx/ESX350-200806812-BG.zip">ESX350-200806812-BG.zip</a></li>
<li>ESXi 3.5 Update 2 <a href="http://download3.vmware.com/software/esx/ESXe350-200807812-O-BG.zip">ESXe350-200807812-O-BG.zip</a></li>
</ul>
<p>L&#8217;aggiornamento comporta lo spegnimento delle VM sull&#8217;ESX ed il riavvio dello stesso (oppure un VMotion delle VM verso un host non affetto)&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.picone.it/2008/08/12/bug-di-vmware-blocca-le-macchine-virtuali/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

