<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Vmware on Wapnet Blog</title><link>https://blog.wapnet.nl/category/vmware/</link><description>Recent content in Vmware on Wapnet Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 08 Apr 2013 22:39:33 +0000</lastBuildDate><atom:link href="https://blog.wapnet.nl/category/vmware/feed.xml" rel="self" type="application/rss+xml"/><item><title>Force shutdown or kill a stuck VMWare virtual machine</title><link>https://blog.wapnet.nl/2013/04/force-shutdown-or-kill-a-stuck-vmware-virtual-machine/</link><pubDate>Mon, 08 Apr 2013 22:39:33 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=1024</guid><description>&lt;p&gt;Sometimes when a LUN is full a VM cannot shutdown properly&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Make a SSH connection to the host where the VM running at&lt;/li&gt;
&lt;li&gt;Login as root&lt;/li&gt;
&lt;li&gt;list all running VM&amp;rsquo;s&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;# vmware-cmd -l
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Get the current state&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;# vmware-cmd /vmfs/volumes/&amp;lt;UUID&amp;gt;/&amp;lt;VMDIR&amp;gt;/&amp;lt;VMNAME&amp;gt;.vmx getstate
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Output:&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;[root@esx ~]# vmware-cmd /vmfs/volumes/&amp;lt;UUID&amp;gt;/&amp;lt;VMDIR&amp;gt;/&amp;lt;VMNAME&amp;gt;.vmx getstate
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;getstate() = stuck
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Now you know for sure the status is stuck you can kill the VM&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ps auxwww |grep -i &amp;lt;VMNAME&amp;gt;.vmx&amp;lt;/span&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Output:&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-gdscript3" data-lang="gdscript3"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;root &lt;span style="color:#ae81ff"&gt;3093&lt;/span&gt; &lt;span style="color:#ae81ff"&gt;0.0&lt;/span&gt; &lt;span style="color:#ae81ff"&gt;0.3&lt;/span&gt; &lt;span style="color:#ae81ff"&gt;2016&lt;/span&gt; &lt;span style="color:#ae81ff"&gt;860&lt;/span&gt; &lt;span style="color:#960050;background-color:#1e0010"&gt;?&lt;/span&gt; S&lt;span style="color:#f92672"&gt;&amp;lt;&lt;/span&gt; Jul30 &lt;span style="color:#ae81ff"&gt;0&lt;/span&gt;:&lt;span style="color:#ae81ff"&gt;17&lt;/span&gt; &lt;span style="color:#f92672"&gt;/&lt;/span&gt;usr&lt;span style="color:#f92672"&gt;/&lt;/span&gt;lib&lt;span style="color:#f92672"&gt;/&lt;/span&gt;vmware&lt;span style="color:#f92672"&gt;/&lt;/span&gt;bin&lt;span style="color:#f92672"&gt;/&lt;/span&gt;vmkload_app &lt;span style="color:#f92672"&gt;/&lt;/span&gt;usr&lt;span style="color:#f92672"&gt;/&lt;/span&gt;lib&lt;span style="color:#f92672"&gt;/&lt;/span&gt;vmware&lt;span style="color:#f92672"&gt;/&lt;/span&gt;bin&lt;span style="color:#f92672"&gt;/&lt;/span&gt;vmware&lt;span style="color:#f92672"&gt;-&lt;/span&gt;vmx &lt;span style="color:#f92672"&gt;-&lt;/span&gt;ssched&lt;span style="color:#f92672"&gt;.&lt;/span&gt;group&lt;span style="color:#f92672"&gt;=&lt;/span&gt;host&lt;span style="color:#f92672"&gt;/&lt;/span&gt;user &lt;span style="color:#f92672"&gt;-&lt;/span&gt;&lt;span style="color:#75715e"&gt;# name=VMware ESX Server;version=3.5.0;licensename=VMware ESX Server;licenseversion=2.0 build-158874; -@ pipe=/tmp/vmhsdaemon-0/vmx569228e44baf49d1; /vmfs/volumes/49392e30-162037d0-17c6-001f29e9abec/&amp;lt;VMDIR&amp;gt;/&amp;lt;VMNAME&amp;gt;.vmx&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;The code right after root is the PID you must kill.&lt;/li&gt;
&lt;li&gt;First try only kill&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;#kill 3093
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Wait 30 seconds and try a getstate again:&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;# vmware-cmd /vmfs/volumes/&amp;lt;UUID&amp;gt;/&amp;lt;VMDIR&amp;gt;/&amp;lt;VMNAME&amp;gt;.vmx getstate
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;If the state is &amp;ldquo;off&amp;rdquo; your ready. If the state is still stuck try the following:&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;#kill -9 3093
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Wait 30 seconds and see the state is &amp;ldquo;off&amp;rdquo; now.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If the state is still &amp;ldquo;stuck&amp;rdquo; migrate all VM&amp;rsquo;s to another host en reboot the host.&lt;/p&gt;</description></item><item><title>virtual ethernet card network adapter 1 is not supported</title><link>https://blog.wapnet.nl/2012/04/virtual-ethernet-card-network-adapter-1-is-not-supported/</link><pubDate>Tue, 24 Apr 2012 15:49:23 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=859</guid><description>&lt;p&gt;I had the &amp;ldquo;error virtual ethernet card network adapter 1 is not supported&amp;rdquo; on a 64 bit Linux (ubuntu) virtual machine.&lt;/p&gt;
&lt;p&gt;To fix this problem I shutdown the virtual machine, removed the NIC and add a new E1000 network card. Then I boot the server even everything was fine :)&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.wapnet.nl/wp-content/uploads/2012/04/vmware.png"&gt;&lt;img loading="lazy" src="https://blog.wapnet.nl/wp-content/uploads/2012/04/vmware.png"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>VMware “Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on.”</title><link>https://blog.wapnet.nl/2010/09/vmware-cannot-open-the-disk-xxxxxx-vmdk-or-one-of-the-snapshot-disks-it-depends-on/</link><pubDate>Mon, 13 Sep 2010 09:12:33 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=408</guid><description>&lt;p&gt;Source: &lt;a href="http://www.ardamis.com/2009/11/20/vmware-cannot-open-the-disk-xxxxxx-vmdk-or-one-of-the-snapshot-disks-it-depends-on/"&gt;http://www.ardamis.com/2009/11/20/vmware-cannot-open-the-disk-xxxxxx-vmdk-or-one-of-the-snapshot-disks-it-depends-on/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;From time to time, I want to copy just the minimum files for a VMware virtual machine: the two .vmdk files and the .vmx file. After moving those files to a new location or deleting a snapshot file, attempting to boot the virtual machine returns the following error message:&lt;/p&gt;
&lt;p&gt;Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on.
Reason: The system cannot find the file specified.&lt;/p&gt;</description></item><item><title>Configure Jumbo Frames in esx 4 Vsphere</title><link>https://blog.wapnet.nl/2010/02/configure-jumbo-frames-in-esx-4-vsphere/</link><pubDate>Thu, 25 Feb 2010 08:49:34 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=349</guid><description>&lt;p&gt;&lt;strong&gt;Jumbo Frames !!!!!!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;-&amp;gt; Lets understand what’s Jumbo Frames first and how it benefits us &amp;hellip;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Jumbo frames&lt;/strong&gt; are Ethernet frames with more than 1,500 bytes of payload (MTU). Conventionally, jumbo frames can carry up to 9,000 bytes of payload.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Jumbo Frames allow ESX Server to send larger frames out onto the physical network. The network must support Jumbo Frames end‐to‐end for Jumbo Frames to be effective.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;iSCSI with jumbo frames gives better or rather much better performance .If you are getting sluggish performance then try enabling jumbo frames&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>VMWare URL's</title><link>https://blog.wapnet.nl/2008/03/vmware-urls/</link><pubDate>Fri, 14 Mar 2008 11:23:54 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=29</guid><description>&lt;p&gt;&lt;a href="http://www.ntpro.nl/blog/"&gt;http://www.ntpro.nl/blog/&lt;/a&gt;          (Website VMWare Teatcher)
&lt;a href="http://www.vizioncore.com/"&gt;http://www.vizioncore.com/&lt;/a&gt;       (ESX Server backup software )
&lt;a href="http://www.vmug.nl/"&gt;http://www.vmug.nl/&lt;/a&gt;                 (Dutch VMWare Users Group)&lt;/p&gt;</description></item></channel></rss>