<?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>Ali Aboosaidi &#187; VMware</title>
	<atom:link href="http://insanelabs.com/category/vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://insanelabs.com</link>
	<description>Umm... Unorthodox?</description>
	<lastBuildDate>Tue, 08 Nov 2011 21:04:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>VMware vSphere: Install ESX from bootable USB drive.</title>
		<link>http://insanelabs.com/vmware/vmware-vsphere-install-esx-from-bootable-usb-drive/</link>
		<comments>http://insanelabs.com/vmware/vmware-vsphere-install-esx-from-bootable-usb-drive/#comments</comments>
		<pubDate>Fri, 22 Apr 2011 18:49:16 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[usb install]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=985</guid>
		<description><![CDATA[Google and download UNetbooin. Run, select Diskimage, ISO and browse to installation DVD. Select your USB drive letter and click OK. Boot from the USB drive and you&#8217;re all set. Related posts: VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine [...]
Related posts:<ol>
<li><a href="http://insanelabs.com/vmware/vmware-install-intel-et-82575-and-82576-drivers-on-esx-4-vsphere/" rel='bookmark' title='VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere' class="liinternal">VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere</a></li>
<li><a href="http://insanelabs.com/linux/vmware-linux-os-cannot-mount-devsd-after-a-virtual-machine-is-converted-waiting-for-device-devsd-to-appear-not-found-fall-back/" rel='bookmark' title='VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back' class="liinternal">VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<ul>
<li>Google and download UNetbooin.</li>
<li>Run, select Diskimage, ISO and browse to installation DVD.</li>
<li>Select your USB drive letter and click OK.</li>
</ul>
<p>Boot from the USB drive and you&#8217;re all set.</p>
<p>Related posts:<ol>
<li><a href="http://insanelabs.com/vmware/vmware-install-intel-et-82575-and-82576-drivers-on-esx-4-vsphere/" rel='bookmark' title='VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere' class="liinternal">VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere</a></li>
<li><a href="http://insanelabs.com/linux/vmware-linux-os-cannot-mount-devsd-after-a-virtual-machine-is-converted-waiting-for-device-devsd-to-appear-not-found-fall-back/" rel='bookmark' title='VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back' class="liinternal">VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://insanelabs.com/vmware/vmware-vsphere-install-esx-from-bootable-usb-drive/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere</title>
		<link>http://insanelabs.com/vmware/vmware-install-intel-et-82575-and-82576-drivers-on-esx-4-vsphere/</link>
		<comments>http://insanelabs.com/vmware/vmware-install-intel-et-82575-and-82576-drivers-on-esx-4-vsphere/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 18:03:48 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[intel 82576]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=930</guid>
		<description><![CDATA[Update: Drivers are included in vSphere 4.1. Download the ISO with drivers from HERE. Burn to a CD and insert in the drive. Logon to the console as root and mount: mount /dev/cdrom /mnt Browse to /mnt and find the file &#8220;INT-intel-lad-ddk-igb-1.3.19.12.1-offline_bundle-185976.zip&#8221; Install the driver: esxupdate --bundle=INT-intel-lad-ddk-igb-1.3.19.12.1-offline_bundle-185976.zip update Reboot. Related posts: VMware vSphere: Install ESX [...]
Related posts:<ol>
<li><a href="http://insanelabs.com/vmware/vmware-vsphere-install-esx-from-bootable-usb-drive/" rel='bookmark' title='VMware vSphere: Install ESX from bootable USB drive.' class="liinternal">VMware vSphere: Install ESX from bootable USB drive.</a></li>
<li><a href="http://insanelabs.com/debian/debian-lenny-cannot-load-broadcom-nic-drivers-asking-for-firmware-bnx2-06-405fw-during-install/" rel='bookmark' title='Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install' class="liinternal">Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>Update: Drivers are included in vSphere 4.1.</p>
<p>Download the ISO with drivers from <a href="http://downloads.vmware.com/d/details/esx_esxi40_intel_82575_82576_dt/ZHcqYmR0QGpidGR3" target="_blank" class="liexternal">HERE</a>.</p>
<p>Burn to a CD and insert in the drive. Logon to the console as root and mount:</p>
<pre>mount /dev/cdrom /mnt</pre>
<p>Browse to /mnt and find the file &#8220;INT-intel-lad-ddk-igb-1.3.19.12.1-offline_bundle-185976.zip&#8221;</p>
<p>Install the driver:</p>
<pre>esxupdate --bundle=INT-intel-lad-ddk-igb-1.3.19.12.1-offline_bundle-185976.zip update</pre>
<p>Reboot.</p>
<p>Related posts:<ol>
<li><a href="http://insanelabs.com/vmware/vmware-vsphere-install-esx-from-bootable-usb-drive/" rel='bookmark' title='VMware vSphere: Install ESX from bootable USB drive.' class="liinternal">VMware vSphere: Install ESX from bootable USB drive.</a></li>
<li><a href="http://insanelabs.com/debian/debian-lenny-cannot-load-broadcom-nic-drivers-asking-for-firmware-bnx2-06-405fw-during-install/" rel='bookmark' title='Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install' class="liinternal">Debian: Lenny cannot load Broadcom NIC drivers, asking for firmware bnx2-06-4.0.5.fw or bnx2-09-4.0.5.fw during install</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://insanelabs.com/vmware/vmware-install-intel-et-82575-and-82576-drivers-on-esx-4-vsphere/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back</title>
		<link>http://insanelabs.com/linux/vmware-linux-os-cannot-mount-devsd-after-a-virtual-machine-is-converted-waiting-for-device-devsd-to-appear-not-found-fall-back/</link>
		<comments>http://insanelabs.com/linux/vmware-linux-os-cannot-mount-devsd-after-a-virtual-machine-is-converted-waiting-for-device-devsd-to-appear-not-found-fall-back/#comments</comments>
		<pubDate>Mon, 06 Apr 2009 16:19:26 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[SuSE]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=590</guid>
		<description><![CDATA[This happened when I created a SLES 11 VM with VMware Workstation and then moved to to ESX for production. Problem was that VMware Workstation used LSILogic SCSI drives to emulate my disks, but for some reason it wasn&#8217;t made clear to ESX by VMware Converter during conversion. To fix this browse to your datastore [...]
Related posts:<ol>
<li><a href="http://insanelabs.com/linux/linux-cannot-turn-on-a-virtual-machine-after-unclean-shutdown-failed-to-lock-the-file-error-vmware-server/" rel='bookmark' title='Linux: Cannot turn on a virtual machine after unclean shutdown &#8211; failed to lock the file error VMware Server' class="liinternal">Linux: Cannot turn on a virtual machine after unclean shutdown &#8211; failed to lock the file error VMware Server</a></li>
<li><a href="http://insanelabs.com/debian/linux-debian-etch-x64-and-vmware-server-cannot-connect-to-host-xxxx-no-connection-could-be-made-because-the-target-machine-actively-refused-it/" rel='bookmark' title='Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.' class="liinternal">Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.</a></li>
<li><a href="http://insanelabs.com/debian/debian-vmware-server-1x-and-debian-etch/" rel='bookmark' title='Debian: VMware Server 1.x and Debian Etch' class="liinternal">Debian: VMware Server 1.x and Debian Etch</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>This happened when I created a SLES 11 VM with VMware Workstation and then moved to to ESX for production. Problem was that VMware Workstation used LSILogic SCSI drives to emulate my disks, but for some reason it wasn&#8217;t made clear to ESX by VMware Converter during conversion.</p>
<p>To fix this browse to your datastore and download your guest&#8217;s configuration file &lt;vmname&gt;.vmx to your desktop (or use your root access and open it in vi through ssh). Open it with a text editor and add the following line above your SCSI devices:</p>
<pre>scsi0.virtualDev = "lsilogic"</pre>
<p>So the whole SCSI device section should look like this:</p>
<pre>scsi0.present = "true"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsilogic"
scsi0:0.present = "true"
scsi0:0.fileName = "disk1.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
scsi0:1.present = "true"
scsi0:1.fileName = "disk2.vmdk"
scsi0:1.deviceType = "scsi-hardDisk"</pre>
<p>Copy the config back to your datastore and start guest OS. You will be asked to confirm changes during post &#8211; answer yes to changes.</p>
<p>Disclaimer: Make sure you have a backup before making any change.</p>
<p>Related posts:<ol>
<li><a href="http://insanelabs.com/linux/linux-cannot-turn-on-a-virtual-machine-after-unclean-shutdown-failed-to-lock-the-file-error-vmware-server/" rel='bookmark' title='Linux: Cannot turn on a virtual machine after unclean shutdown &#8211; failed to lock the file error VMware Server' class="liinternal">Linux: Cannot turn on a virtual machine after unclean shutdown &#8211; failed to lock the file error VMware Server</a></li>
<li><a href="http://insanelabs.com/debian/linux-debian-etch-x64-and-vmware-server-cannot-connect-to-host-xxxx-no-connection-could-be-made-because-the-target-machine-actively-refused-it/" rel='bookmark' title='Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.' class="liinternal">Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.</a></li>
<li><a href="http://insanelabs.com/debian/debian-vmware-server-1x-and-debian-etch/" rel='bookmark' title='Debian: VMware Server 1.x and Debian Etch' class="liinternal">Debian: VMware Server 1.x and Debian Etch</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://insanelabs.com/linux/vmware-linux-os-cannot-mount-devsd-after-a-virtual-machine-is-converted-waiting-for-device-devsd-to-appear-not-found-fall-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linux: Cannot turn on a virtual machine after unclean shutdown &#8211; failed to lock the file error VMware Server</title>
		<link>http://insanelabs.com/linux/linux-cannot-turn-on-a-virtual-machine-after-unclean-shutdown-failed-to-lock-the-file-error-vmware-server/</link>
		<comments>http://insanelabs.com/linux/linux-cannot-turn-on-a-virtual-machine-after-unclean-shutdown-failed-to-lock-the-file-error-vmware-server/#comments</comments>
		<pubDate>Tue, 30 Dec 2008 21:41:33 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=300</guid>
		<description><![CDATA[I don&#8217;t recall the exact error message, but sometime after an unclean shutdown your virtual machines will not start with an error that contains &#8220;unable to unlock file&#8221;. To resolve the issue simply navigate to the directory where your virtual machine resides, and delete all files with .WRITELOCK and .lck extension.That should remove the lock [...]
Related posts:<ol>
<li><a href="http://insanelabs.com/linux/vmware-linux-os-cannot-mount-devsd-after-a-virtual-machine-is-converted-waiting-for-device-devsd-to-appear-not-found-fall-back/" rel='bookmark' title='VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back' class="liinternal">VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back</a></li>
<li><a href="http://insanelabs.com/debian/linux-debian-etch-x64-and-vmware-server-cannot-connect-to-host-xxxx-no-connection-could-be-made-because-the-target-machine-actively-refused-it/" rel='bookmark' title='Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.' class="liinternal">Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.</a></li>
<li><a href="http://insanelabs.com/debian/debian-setup-is-unable-to-find-the-killall-program-error-when-installing-vmware-tools/" rel='bookmark' title='Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools' class="liinternal">Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>I don&#8217;t recall the exact error message, but sometime after an unclean shutdown your virtual machines will not start with an error that contains &#8220;unable to unlock file&#8221;. To resolve the issue simply navigate to the directory where your virtual machine resides, and delete all files with .WRITELOCK and .lck extension.That should remove the lock and make your VM&#8217;s accessible. If that didn&#8217;t help, go ahead and delete all files <span style="color: #ff6600;">EXCEPT .vmdk AND .vmx EXTENSIONS</span>. That should definitely do the trick.</p>
<p>You can actually delete the .vmx files as well but in order to have VMware recreate them you will have to start the &#8220;new virtual machine wizard&#8221; and use the .vmdk as your disk file. Instead of creating a disk you use an existing.</p>
<p>Related posts:<ol>
<li><a href="http://insanelabs.com/linux/vmware-linux-os-cannot-mount-devsd-after-a-virtual-machine-is-converted-waiting-for-device-devsd-to-appear-not-found-fall-back/" rel='bookmark' title='VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back' class="liinternal">VMware &#8211; Linux: OS cannot mount /dev/sd* after a virtual machine is converted &#8211; Waiting for device /dev/sd* to appear&#8230; not found &#8211; fall back</a></li>
<li><a href="http://insanelabs.com/debian/linux-debian-etch-x64-and-vmware-server-cannot-connect-to-host-xxxx-no-connection-could-be-made-because-the-target-machine-actively-refused-it/" rel='bookmark' title='Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.' class="liinternal">Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.</a></li>
<li><a href="http://insanelabs.com/debian/debian-setup-is-unable-to-find-the-killall-program-error-when-installing-vmware-tools/" rel='bookmark' title='Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools' class="liinternal">Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://insanelabs.com/linux/linux-cannot-turn-on-a-virtual-machine-after-unclean-shutdown-failed-to-lock-the-file-error-vmware-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debian: VMware Server 1.x and Debian Etch</title>
		<link>http://insanelabs.com/debian/debian-vmware-server-1x-and-debian-etch/</link>
		<comments>http://insanelabs.com/debian/debian-vmware-server-1x-and-debian-etch/#comments</comments>
		<pubDate>Sun, 14 Dec 2008 08:55:42 +0000</pubDate>
		<dc:creator>Ali</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://insanelabs.com/?p=252</guid>
		<description><![CDATA[To install VMware Server 1.x: Install the following packages if you don&#8217;t already have them: aptitude install build-essential linux-headers-$(uname -r) openssl libssl-dev psmisc Untar the package, navigate to vmware-server-distrib directory and type ./vmware-install.pl To install VMware Tools: The following packages are needed in order to install VMware Tools: aptitude install build-essential linux-headers-$(uname -r) Open VMware [...]
Related posts:<ol>
<li><a href="http://insanelabs.com/debian/linux-debian-etch-x64-and-vmware-server-cannot-connect-to-host-xxxx-no-connection-could-be-made-because-the-target-machine-actively-refused-it/" rel='bookmark' title='Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.' class="liinternal">Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.</a></li>
<li><a href="http://insanelabs.com/debian/linux-symantec-backup-exec-12-and-debian-etch-3264/" rel='bookmark' title='Debian: Symantec Backup Exec 12 and Debian Etch 32/64' class="liinternal">Debian: Symantec Backup Exec 12 and Debian Etch 32/64</a></li>
<li><a href="http://insanelabs.com/debian/debian-setup-is-unable-to-find-the-killall-program-error-when-installing-vmware-tools/" rel='bookmark' title='Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools' class="liinternal">Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>To install VMware Server 1.x:</p>
<p>Install the following packages if you don&#8217;t already have them:</p>
<pre>aptitude install build-essential linux-headers-$(uname -r) openssl libssl-dev psmisc</pre>
<p>Untar the package, navigate to vmware-server-distrib directory and type</p>
<pre>./vmware-install.pl</pre>
<p>To install VMware Tools:</p>
<p>The following packages are needed in order to install VMware Tools:</p>
<pre>aptitude install build-essential linux-headers-$(uname -r)</pre>
<p>Open VMware Server Console and Click VM &#8211; Install VMware Tools. Then go to your guest Debain VM and mount the CD:</p>
<pre>mount /dev/cdrom</pre>
<p>I usually copy tar files to the hard drive and extract:</p>
<pre>cp /media/cdrom0/VMwareTools-1.0.8-126538.tar.gz /root

cd /root/</pre>
<pre>tar -zxf VMwareTools-1.0.8-126538.tar.gz</pre>
<p>If you want to directly untar it to another directory:</p>
<pre>tar -zxf /media/cdrom0/VMwareTools-1.0.8-126538.tar.gz -C &lt;directory&gt;</pre>
<p>Navigate to vmware-tools-distrib and execute the install command:</p>
<pre>./vmware-install.pl</pre>
<p>Follow directions and you should be able to install VMware Tools without incident.</p>
<p>Note: If you are running an early release of Debian Etch you may be asked to provide path to C compiler directory. That means you do not have a compiler installed and will have to install the following two packages:</p>
<pre>aptitude install gcc-3.4 g++-3.4</pre>
<p>Related posts:<ol>
<li><a href="http://insanelabs.com/debian/linux-debian-etch-x64-and-vmware-server-cannot-connect-to-host-xxxx-no-connection-could-be-made-because-the-target-machine-actively-refused-it/" rel='bookmark' title='Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.' class="liinternal">Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.</a></li>
<li><a href="http://insanelabs.com/debian/linux-symantec-backup-exec-12-and-debian-etch-3264/" rel='bookmark' title='Debian: Symantec Backup Exec 12 and Debian Etch 32/64' class="liinternal">Debian: Symantec Backup Exec 12 and Debian Etch 32/64</a></li>
<li><a href="http://insanelabs.com/debian/debian-setup-is-unable-to-find-the-killall-program-error-when-installing-vmware-tools/" rel='bookmark' title='Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools' class="liinternal">Debian: Setup is unable to find the &#8220;killall&#8221; program error when installing VMware tools</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://insanelabs.com/debian/debian-vmware-server-1x-and-debian-etch/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

