<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vmware on Michele Bologna</title>
    <link>https://www.michelebologna.net/categories/vmware/</link>
    <description>Recent content in Vmware on Michele Bologna</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 20 Sep 2015 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.michelebologna.net/categories/vmware/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting started with cloud-init and CoreOS</title>
      <link>https://www.michelebologna.net/2015/getting-started-with-cloud-init-and-coreos/</link>
      <pubDate>Sun, 20 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://www.michelebologna.net/2015/getting-started-with-cloud-init-and-coreos/</guid>
      <description>&lt;p&gt;Lately I&amp;rsquo;ve been experimenting with &lt;a href=&#34;https://web.archive.org/web/20210209124335/https://coreos.com/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&lt;strong&gt;CoreOS&lt;/strong&gt;&lt;/a&gt;, a Linux distribution that enforces containerization (I made some experiments with Docker and I&amp;rsquo;d say that this area is fun!). CoreOS layer of containerization &lt;strong&gt;was&lt;/strong&gt; based Docker, but now that they moved to &lt;a href=&#34;https://github.com/coreos/rkt&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Rocket&lt;/a&gt;. Not only Rocket, though: CoreOS brings some curious innovations to lightweight Linux distributions like &lt;em&gt;clusterization&lt;/em&gt; with &lt;a href=&#34;https://github.com/coreos/fleet&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&lt;strong&gt;fleet&lt;/strong&gt;&lt;/a&gt; and &lt;em&gt;service discovery&lt;/em&gt; with &lt;a href=&#34;https://web.archive.org/web/20190531021446/https://coreos.com/etcd/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&lt;strong&gt;etcd&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Convertire una macchina fisica in una virtuale: VMware vCenter Converter</title>
      <link>https://www.michelebologna.net/2013/convertire-una-macchina-fisica-in-una-virtuale-vmware-vcenter-converter/</link>
      <pubDate>Sat, 19 Jan 2013 00:00:00 +0000</pubDate>
      <guid>https://www.michelebologna.net/2013/convertire-una-macchina-fisica-in-una-virtuale-vmware-vcenter-converter/</guid>
      <description>&lt;p&gt;Ho recentemente convertito due macchine fisiche Windows in macchine virtuali (per questioni di manutenibilità) con un tool gratuito messo a disposizione da VMware: &lt;strong&gt;VMware vCenter Converter.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Una volta installato si occupa di fare un&amp;rsquo;immagine virtuale di tutto il contenuto dell&amp;rsquo;hard disk (comprese eventuali partizioni), creando una macchina virtuale (compatibile con VMware e con Oracle VirtualBox).&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware Fusion 4: aggiornate la compatibilità delle virtual machines</title>
      <link>https://www.michelebologna.net/2011/vmware-fusion-4-aggiornate-la-compatibilita-delle-virtual-machines/</link>
      <pubDate>Fri, 25 Nov 2011 00:00:00 +0000</pubDate>
      <guid>https://www.michelebologna.net/2011/vmware-fusion-4-aggiornate-la-compatibilita-delle-virtual-machines/</guid>
      <description>&lt;p&gt;Dopo aver aggiornato VMware Fusion alla versione 4, ricordatevi di aggiornare la compatibilità di tutte le vostre virtual machines alla versione 4 (Settings -&amp;gt; Compatibility -&amp;gt; 4). Dovrete reinstallare i VMware tools, ma vista la notevole velocità d&amp;rsquo;esecuzione che si guadagna, è caldamente consigliato l&amp;rsquo;aggiornamento.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMWare Fusion e Ubuntu: risoluzione dello schermo fissa a 1280x720. Ecco come risolvere la situazione</title>
      <link>https://www.michelebologna.net/2011/vmware-fusion-e-ubuntu-risoluzione-dello-schermo-fissa-a-1280x720-ecco-come-risolvere-la-situazione/</link>
      <pubDate>Tue, 22 Mar 2011 00:00:00 +0000</pubDate>
      <guid>https://www.michelebologna.net/2011/vmware-fusion-e-ubuntu-risoluzione-dello-schermo-fissa-a-1280x720-ecco-come-risolvere-la-situazione/</guid>
      <description>&lt;p&gt;Dopo aver aggiornato la macchina virtuale con Ubuntu 10.10 in VMWare Fusion, mi sono trovato impossibilitato a selezionare una risoluzione superiore a 1280x720.&lt;/p&gt;&#xA;&lt;p&gt;Anche dopo aver reinstallato i VMWare Tools, la risoluzione disponibile era sempre bloccata a 1280x720. Dopo aver fatto qualche ricerca nei log, ho trovato alcuni messaggi che evidenziavano il problema: &lt;code&gt;could not apply the stored configuration for monitors Xserver does not support size requested VESA(0): Unable to estimate virtual size VESA(0): Not using built-in mode &amp;quot;2048x1536&amp;quot; (no mode of this name) VESA(0): Not using built-in mode &amp;quot;1920x1440&amp;quot; (no mode of this name) VESA(0): No valid modes left. Trying less strict filter... VESA(0): : Using hsync range of 31.50-37.90 kHz VESA(0): : Using vrefresh range of 50.00-70.00 Hz VESA(0): Unable to estimate virtual size VESA(0): Not using built-in mode &amp;quot;2048x1536&amp;quot; (hsync out of range) VESA(0): Not using built-in mode &amp;quot;1920x1440&amp;quot; (hsync out of range) VESA(0): Virtual size is 1280x720 (pitch 1280)&lt;/code&gt; Il problema risiede nella configurazione e nel rilevamento della risoluzione dello schermo; il pacchetto incriminato è quindi &lt;strong&gt;xserver-xorg-video-vmware&lt;/strong&gt;. Per risolvere è sufficiente aprire un terminale e digitare:&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware: come risolvere il problema &amp;ldquo;this machine appears to be in use&amp;rdquo;</title>
      <link>https://www.michelebologna.net/2009/vmware-come-risolvere-il-problema-this-machine-appears-to-be-in-use/</link>
      <pubDate>Fri, 25 Sep 2009 00:00:00 +0000</pubDate>
      <guid>https://www.michelebologna.net/2009/vmware-come-risolvere-il-problema-this-machine-appears-to-be-in-use/</guid>
      <description>&lt;p&gt;Se VMware non vi permette di avviare una macchina virtuale che è stata spenta &lt;em&gt;brutalmente&lt;/em&gt; (= senza un opportuno shutdown o suspend)  lamentandosi che “this machine appears to be in use” procedete in questo modo:&lt;a href=&#34;https://www.michelebologna.net/images/2009/09/image.png&#34; &gt;&lt;img src=&#34;https://www.michelebologna.net/images/2009/09/image_thumb.png&#34; alt=&#34;image&#34; title=&#34;image&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
