<?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>Res Publica Non Dominetur - カルマン &#187; VMware</title>
	<atom:link href="http://karman.cc/blog/archives/category/vmware/feed" rel="self" type="application/rss+xml" />
	<link>http://karman.cc/blog</link>
	<description>Lo público no tiene dominio.</description>
	<lastBuildDate>Sun, 29 Jun 2025 11:22:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>VMware Fusion (OSX): Mooltipass in Virtual Machines</title>
		<link>http://karman.cc/blog/archives/898</link>
		<comments>http://karman.cc/blog/archives/898#comments</comments>
		<pubDate>Tue, 19 Aug 2014 21:26:36 +0000</pubDate>
		<dc:creator>KaRMaN</dc:creator>
				<category><![CDATA[Arduino]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://karman.cc/blog/?p=898</guid>
		<description><![CDATA[So, I wanted to test the Mooltipass in different platforms besides my main OS, Mac OS X. The better way is to use virtual machines I already have VMware Fusion. On first try I wasn&#8217;t able to associate the Mooltipass to any of my virtual machines because the MP is an HiD device and as [...]]]></description>
			<content:encoded><![CDATA[<p>So, I wanted to test the Mooltipass in different platforms besides my main OS, Mac OS X. The better way is to use virtual machines I already have VMware Fusion. On first try I wasn&#8217;t able to associate the Mooltipass to any of my virtual machines because the MP is an HiD device and as so, is always connected to the main OS and then emulated via VMware Fusion in the guest OS (in my case, Windows XP and Windows 8):</p>
<div id="attachment_899" class="wp-caption aligncenter" style="width: 310px"><a href="http://karman.cc/blog/descargas/Captura-de-pantalla-2014-08-19-a-las-23.06.31.png" rel="lightbox"><img class="size-medium wp-image-899" title="vmware_fusion_screenshot_without_usb_mooltipass" src="http://karman.cc/blog/descargas/Captura-de-pantalla-2014-08-19-a-las-23.06.31-300x107.png" alt="vmware_fusion_screenshot_without_usb_mooltipass" width="300" height="107" /></a><p class="wp-caption-text">Mooltipass is not eligible to be associated to the guest OS</p></div>
<p>After some googling I found a relevant KB (knowledge base) article about associating HiD devices entirely to a Virtual Machine and disassociating it from the host OS: <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1033435" target="_self">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1033435</a>.</p>
<p>The article says that the virtual machine hardware definition file (.vmx extension, usually located at /Users/$USER/Documents/Virtual Machines.localized) has to be manually edited after shutting down the virtual machine and the VMware Fusion to add the two following lines:</p>
<p><code>usb.generic.allowHID = "TRUE"</code><br />
<code>usb.generic.allowLastHID = "TRUE"</code></p>
<p>After adding both lines, you can safely search for the Mooltipass HiD devide to properly associate it to the guest OS:</p>
<div id="attachment_900" class="wp-caption aligncenter" style="width: 310px"><a href="http://karman.cc/blog/descargas/Captura-de-pantalla-2014-08-19-a-las-23.21.50.png" rel="lightbox"><img class="size-medium wp-image-900" title="vmware_fusion_screenshot_with_usb_mooltipass" src="http://karman.cc/blog/descargas/Captura-de-pantalla-2014-08-19-a-las-23.21.50-300x93.png" alt="vmware_fusion_screenshot_with_usb_mooltipass" width="300" height="93" /></a><p class="wp-caption-text">vmware_fusion_screenshot_with_usb_mooltipass</p></div>
<div id="update"><b>Update: </b>Since VMware Fusion 7.1.1 it&#8217;s necessary to also add <b>usb.generic.allowHID = &#8220;TRUE&#8221;</b> in the following file: /Users/$USER/Library/Preferences/VMware\ Fusion/preferences</div>
]]></content:encoded>
			<wfw:commentRss>http://karman.cc/blog/archives/898/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Crear PEN Bootable de ESXi 4.1 Update 1</title>
		<link>http://karman.cc/blog/archives/645</link>
		<comments>http://karman.cc/blog/archives/645#comments</comments>
		<pubDate>Wed, 09 Mar 2011 08:29:24 +0000</pubDate>
		<dc:creator>KaRMaN</dc:creator>
				<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://karman.cc/blog/?p=645</guid>
		<description><![CDATA[El procedimiento es similar al de imágenes ESXi anteriores pero con los nombres cambiados.
Una vez descargado la iso de ESXi 4.1 Update 1 (VMware-VMvisor-Installer-4.1.0.update1-348481.x86_64.iso) la abrimos con algún extractor de archivos que lea ISOs y de la raíz extraemos el archivo imagedd.bz2, que como bien indica su nombre se trata de una imagen del sistema [...]]]></description>
			<content:encoded><![CDATA[<p>El procedimiento es similar al de imágenes ESXi anteriores pero con los nombres cambiados.</p>
<p>Una vez descargado la iso de ESXi 4.1 Update 1 (<strong>VMware-VMvisor-Installer-4.1.0.update1-348481.x86_64.iso</strong>) la abrimos con algún extractor de archivos que lea ISOs y de la raíz extraemos el archivo <strong>imagedd.bz2</strong>, que como bien indica su nombre se trata de una imagen del sistema operativo ESXi para &#8216;quemar&#8217; con <a href="http://en.wikipedia.org/wiki/Dd_(Unix)" target="_blank">dd</a>. No olvidar extraer <strong>imagedd</strong> de <strong>imagedd.bz2</strong>.</p>
<p>En linux podemos quemar esta imagen sobre un pen con:</p>
<blockquote><p>user@host:~ # dd if=imagedd of=/dev/sdb</p></blockquote>
<p>Donde deberemos reemplazar <em>/dev/sdb</em> con la localización correcta de nuestro pen drive (ojo! muy importante, si nos equivocamos podríamos formatear el/los disco(s) duro(s) de nuestro ordenador!!). Se puede averiguar con <em>dmesg</em>.</p>
<p>En Windows podemos utilizar la opción &#8216;Restaurar imagen de disco en disco físico&#8217; del programa WinImage.</p>
]]></content:encoded>
			<wfw:commentRss>http://karman.cc/blog/archives/645/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
