On 26 Jun 2001, Johan Ihren wrote:

# But still no go. I get the first indication of problems on the console
# during boot:
# -----------
# ...
# /dev/vmnet1: Bad file descriptor
# -----------
# Ahem. No good. And this is definitely different from how it behaved
# previously. This is what modstat reports afterwards:

...do you have a .../dev/vmnet1?

# urple:patches/halflife>modstat 
# Type    Id  Off Loadaddr Size Info     Rev Module Name
# DEV       0  29 d4105000 0008 d4106a00   1 vmnet
# DEV       1  30 d410e000 0014 d41117a0   1 vmmon
# -----------
# If I try to power on the virtual machine anyhow I get this in the VMware log
# -----------
# ...
# Jun 26 19:09:47: DICT                 tag.tools = ToolsInstall.htm
# Jun 26 19:09:47: DICT --- GLOBAL SETTINGS
# Jun 26 19:09:47: GuestOSId = 0x5006 
# Jun 26 19:09:47: Msg_Post Error: msg.moduletable.powerOnFailed
# Could not open Please make sure that the kernel module `vmmon' is loaded.
#  (/dev/vmmon).
# Module 5 power on failed.

Do you have a .../dev/vmmon?

...
# Where should I start looking? It seems a bit strange that the message
# is "Could not open". Could not open what? And I cannot find that exact
# string in any of the supplied files, especially not in the vmware
# binary:

# snout:vmware>strings -a /usr/local/vol/vmware-2.0.3/bin/vmware | grep
# "Could not open"

# Could not open %s (%s). <<<
# Could not open /proc/cpuinfo.
# Could not open %s (%s). <<<
# Could not open %s: %s 

Either of the "<<<" marked strings would tend to match your query; it
almost appears as though something internal to VMwhore is not necessarily
broken as much as incorrectly written.

# Regards,

# Johan


				--*greywolf;
--
NetBSD: Feed The Computer.