Technological Wanderings - vmware server http://www.technologicalwanderings.co.uk/taxonomy/term/37 en VMWare can't be run purely from the command line http://www.technologicalwanderings.co.uk/node/28 <div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Keywords:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/taxonomy/term/18">vmware</a></div><div class="field-item odd"><a href="/taxonomy/term/37">vmware server</a></div></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>VMControl error -16: Virtual machine requires user input to continue</p> <p>If you see that when manipulating a VMWare machine, you'll need to connect the management console and click on the window VMWare will show you.</p> <p>vmware-server-console or whatever you use.</p> <p>I can't see that even a hard reset can get rid of this without starting the graphical interface. If there is a way to get a machine back from the command line only, I'd be thankful to hear of it.</p> </div></div></div> Thu, 24 Apr 2008 20:17:20 +0000 techuser 28 at http://www.technologicalwanderings.co.uk http://www.technologicalwanderings.co.uk/node/28#comments vmware-cmd <machine> reset not working? http://www.technologicalwanderings.co.uk/node/21 <div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Keywords:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/taxonomy/term/18">vmware</a></div><div class="field-item odd"><a href="/taxonomy/term/37">vmware server</a></div></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>If your VMWare client crashes and becomes none responsive regularly (e.g. you're running a Windows client), it's a good idea to have a script monitoring it and calling reset when it dies.</p> <p>The first obstacle I encountered was when "vmware-cmd /mymachine.vmx reset" was run and I got the following:</p> <p><code>VMControl error -8: Invalid operation for virtual machine's current state: Make sure the VMware Server Tools are running</code></p> <p>This obscure error was because I didn't read the documentation. 'Reset' takes an argument, see [1]. By default, it will try to do a 'soft' reboot - i.e. it will only talk to vmware-tools inside the machine and try a clean reboot. If the machine is dead, that's not going to happen. The answer is to use 'hard' or 'trysoft'. I prefer trysoft. If a response is not found from vmware-tools, it tells VMWare to do a "hard" reset of the client.</p> <p>Here's the bit of perl I'm using to monitor my VMWare machine:<br /><code><br /> #!/usr/bin/perl -w</code></p> <p>use strict;<br /> use Net::Ping;</p> <p># This is the host we check is up.<br /> my $host = "192.168.16.54";</p> <p># Explict binding, not normally needed.<br /> #my $local_addr = "192.168.16.23";</p> <p>my $p = Net::Ping-&gt;new();<br /> #$p-&gt;bind($local_addr);<br /> if( !$p-&gt;ping($host) )<br /> {<br /> print "MachineX is down, forcing VMWare client reset...\n";<br /> `/opt/vmware/server/bin/vmware-cmd "/var/lib/vmware/Virtual Machines/client directory/client configuration.vmx" reset trysoft`<br /> }<br /></p> <p>[1] <a href="http://www.vmware.com/support/esx2/doc/vmware-cmd.html#1012418">http://www.vmware.com/support/esx2/doc/vmware-cmd.html#1012418</a></p> </div></div></div> Sun, 24 Feb 2008 10:40:26 +0000 techuser 21 at http://www.technologicalwanderings.co.uk http://www.technologicalwanderings.co.uk/node/21#comments