Author Topic: VMware Server hostonly adapter does not start automatically  (Read 17640 times)

Offline admin

  • Administrator
  • Hero Member
  • *****
  • Posts: 250
  • Karma: 0
    • http://meineipadresse.de/
VMware Server hostonly adapter does not start automatically
« on: Wednesday, 14.02.2007 13:40 »
There seems to be an issue in VMware Server 1.0.1 with automatically started virtual machines, where the VM starts with vmnet1 network interface disconnected, even though it is set to start connected in VMware Console.

In the logfiles there is a message such as:

Could not get interface flags for vmnet1: No such device Virtual device Ethernet0 will start disconnected.

Problem is, the vmnet1 hostonly adapter needs several seconds to initialize. In order to speed up the booting process, VMware decided to not wait for this hostonly adapter to initialize, but to initialize it in the background while continuing the boot process. If a VMware virtual machine is set to start automatically and the server is fast (we discovered this on Suse 10 running on an AMD Opteron dual core server), the vmnet1 adapter may not finish initializing in time.

As a workaround, edit /usr/lib/vmware/net-services.sh and locate the lfollowing line:

vmware_bg_exec 'Host-only networking on /dev/vmnet'"$vHubNr" \

and substitute vmware_bg_exec by vmware_exec

(vmware_bg_exec means "Background"-Execution, while vmware_exec waits until completion)

Took me several hours to find this out...


« Last Edit: Wednesday, 14.02.2007 13:50 by admin »

Offline tankwart

  • Sr. Member
  • ****
  • Posts: 165
  • Karma: 0
Re: VMware Server hostonly adapter does not start automatically
« Reply #1 on: Saturday, 03.03.2007 10:04 »
This hostonly bug is still present in the new VMware Server 1.0.2 release....
« Last Edit: Saturday, 03.03.2007 10:08 by tankwart »

Offline tankwart

  • Sr. Member
  • ****
  • Posts: 165
  • Karma: 0
Re: VMware Server hostonly adapter does not start automatically
« Reply #2 on: Monday, 30.04.2007 22:07 »
Guess what? They still have not fixed this bug in VMware Server 1.0.3.

Aside of this omission, this is a great piece of software and rock stable.