<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Cannot start virtual machines with server 1.0.4</title>
    <link>http://communities.vmware.com/community/vmtn/server/server1?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Sun, 27 Jan 2008 02:39:55 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-01-27T02:39:55Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Cannot start virtual machines with server 1.0.4</title>
      <link>http://communities.vmware.com/message/849251?tstart=0#849251</link>
      <description>&lt;br /&gt;
Okay, I was able to fix the problem.  The short version is I had to run vmware-config.pl twice to get it to build the correct version of the vmmon kernel module.&lt;br /&gt;
&lt;p /&gt;
 Long explanation:&lt;br /&gt;
&lt;p /&gt;
The vmware-any-any-update115 uses  a script getversion.pl to determine for what version of VMware the vmmon module should be built.  It calls:&lt;br /&gt;
&lt;p /&gt;
vmware -v &amp;lt; /dev/null 2&amp;gt;&amp;#38;1&lt;br /&gt;
&lt;p /&gt;
to determine the version.  Unfortunately, if you have not run vmware-config.pl before (which is impossible since the vmmon won't compile...), the command errors out saying that vmware-config.pl has not been run.  In the process, it does not actually give the version.&lt;br /&gt;
&lt;p /&gt;
So, the first time vmware-config.pl is run, it builds the module for the wrong version.  The second time, the above command works, since everything is configured now, and builds the module with the correct version.&lt;br /&gt;
&lt;br /&gt;</description>
      <pubDate>Sun, 27 Jan 2008 02:39:55 GMT</pubDate>
      <author>plasmoidia</author>
      <guid>http://communities.vmware.com/message/849251?tstart=0#849251</guid>
      <dc:date>2008-01-27T02:39:55Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Cannot start virtual machines with server 1.0.4</title>
      <link>http://communities.vmware.com/message/849196?tstart=0#849196</link>
      <description>&lt;br /&gt;
Aha, I just found the "Run with debugging information" under Options, Advanced.  Now I get an error out of it:&lt;br /&gt;
&lt;p /&gt;
Unable to change virtual machine power state: The process exited with an error:&lt;br /&gt;
&lt;p /&gt;
vmxvmdb: Index name being generated from config file&lt;br /&gt;
POST(no connection): Version mismatch with vmmon module: expecting 138.0, got 137.0.&lt;br /&gt;
You have an incorrect version of the `vmmon' kernel module.&lt;br /&gt;
Try reinstalling VMware Server.&lt;br /&gt;
&lt;br /&gt;
POST(no connection): Failed to initialize monitor device.&lt;br /&gt;
&lt;br /&gt;
Failed to initialize VM.&lt;br /&gt;
End of error message.&lt;br /&gt;
&lt;p /&gt;
 The vmmon kernel module shows up in lsmod.  I had to install the vmware-any-any-update115 to get it to compile.  Any ideas on how to fix this? &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sat, 26 Jan 2008 20:49:39 GMT</pubDate>
      <author>plasmoidia</author>
      <guid>http://communities.vmware.com/message/849196?tstart=0#849196</guid>
      <dc:date>2008-01-26T20:49:39Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Cannot start virtual machines with server 1.0.4</title>
      <link>http://communities.vmware.com/message/849195?tstart=0#849195</link>
      <description>&lt;br /&gt;
I just installed Server 1.0.4 on Fedora 8 x86_64.  I am running on a box with an Athlon 64 x2, socket 939 processor (so, sadly, no virtualization instructions).  I have the latest Fedora 8 updates, running kernel 2.6.23.14-107.fc8.  Install and setup went smoothly and the Server Console connects just fine.  However, when I go to start a virtual machine, I immediately get an error:&lt;br /&gt;
&lt;p /&gt;
Unable to change virtual machine power state: The process exited with an error:&lt;br /&gt;
End of error message.&lt;br /&gt;
&lt;p /&gt;
And nothing else happens.  I have tried server different VMs (64-bit and 32-bit), including an appliance I have run on other machines, but no change.&lt;br /&gt;
&lt;p /&gt;
Does anyone have any idea what might be going on?  Is there anything I can do to get some useful output to debug the problem?&lt;br /&gt;
&lt;p /&gt;
Thanks.</description>
      <pubDate>Sat, 26 Jan 2008 20:41:50 GMT</pubDate>
      <author>plasmoidia</author>
      <guid>http://communities.vmware.com/message/849195?tstart=0#849195</guid>
      <dc:date>2008-01-26T20:41:50Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
  </channel>
</rss>

