vmware server not start when start computer

[janpihlgren]

Two times I discover that vmware server doesn't start when I start my computer.
I have to manually start the server (MCC- System)
This is my configuration:

Code: Select all

[root@Humlan grub]# more menu.lst
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=4a60ad22-fc85-418c-9bb1-559f16d53f35 splash quiet r
esume=UUID=56bb3f65-3e42-4177-83f7-42d06e37b4f4 vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=4a60ad22-fc85-418c-9bb1-559f16d53f35 resume=U
UID=56bb3f65-3e42-4177-83f7-42d06e37b4f4
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=4a60ad22-fc85-418c-9bb1-559f16d53f35 failsafe
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title desktop 3.3.6-2.mga2
kernel (hd0,4)/boot/vmlinuz-3.3.6-desktop-2.mga2 BOOT_IMAGE=desktop_3.3.6-2.mga2 root=UUID=4a60ad22-fc85-4
18c-9bb1-559f16d53f35 splash quiet resume=UUID=56bb3f65-3e42-4177-83f7-42d06e37b4f4 vga=788
initrd (hd0,4)/boot/initrd-3.3.6-desktop-2.mga2.img

title desktop 3.3.8-2.mga2
kernel (hd0,4)/boot/vmlinuz-3.3.8-desktop-2.mga2 BOOT_IMAGE=desktop_3.3.8-2.mga2 root=UUID=4a60ad22-fc85-4
18c-9bb1-559f16d53f35 splash quiet resume=UUID=56bb3f65-3e42-4177-83f7-42d06e37b4f4 vga=788
initrd (hd0,4)/boot/initrd-3.3.8-desktop-2.mga2.img

[root@Humlan grub]# uname -a
Linux Humlan.localdomain 3.3.8-desktop-2.mga2 #1 SMP Mon Jul 30 21:35:06 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[root@Humlan grub]#


I have set the server to start att startup.
I have done every updates that are advertised.
The first time this happends I thought it was an accident but when it happend again this morning I think there might be something with the kernel or ----?

[wintpe]

vmware server product is usualy started (from memory quite old info here)
from init.d

so chkconfig --list|grep -i vmware.

if it does not have on set on one of the run levels then try

chkconfig vmwarexxxxxx on

then reboot and see if it starts automaticly.

regards peter

[janpihlgren]

This is the result:

Code: Select all

[root@Humlan jan]# chkconfig --list|grep -i vmware

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overriden by native
      systemd configuration.

vmware                     0:off    1:off    2:on    3:on    4:off    5:on    6:off    7:of
vmware-USBArbitrator       0:off    1:off    2:on    3:on    4:off    5:on    6:off    7:off
vmware-workstation-server  0:off    1:off    2:on    3:on    4:off    5:on    6:off    7:off
vmware-wsx-server          0:off    1:off    2:on    3:on    4:off    5:on    6:off    7:off
[root@Humlan jan]#


I supuse that when vmware (and every other vmwerefunction) is on in runlevel 5 the it mean that the server have to start when starting the computer.

[wrw105]

My experience with vmware player is that the services are started at program startup. If you want to keep the services running all the time, go to MCC-->System-->services and check "At boot" for the vmware service.

[wintpe]

yes, well your clearly not a command line user.

chkconfig --list and chkconfig service on/off is the same as MCC services.

you can also run chkconfig service status (where service is the vmware service)
this will tell you if the service started or is running.

looks to me as if all nessasary services for vmware are set to start.

thats does not mean they successfully started, hence status.

alternativly ps -ef|grep -i vmware.

and lsmod |grep -i vmware

then if its anything like vmware esxi you will need to specifiy what guests are started at boot.

you use vmware console to do this in esxi, i would think its the same in server.

this runs under windows only unfortunatly (or at least as far as im currently aware)

as far as i can remember the only diff between server and esxi is that server runs as a service under a forien linux or windows OS and esxi provides the parent OS (based on linux) with all the services built in as a kind of blackbox OS.

ps your guests will need vmwaretools.

if you dont add vmwaretools to your guests then a shutdown of your host os will be like a poweroff of your guests.

vmwaretools implements (well one of its functions) the link that sends an acpi soft power shutdown.

it could be you are shuting off your guests in a abrupt manor.

regards peter

[janpihlgren]

I stops all guests before I shutdown the computer.
I never have a guest to start at start th computer.
I use the guest just to test severel different OS.
I have installed vmwaretools at every guest exept Mageia 3 Alfa3 which not mount vmwaretools. (bug 7917 reported)

by wintpe » Dec 19th, '12, 17:15
it could be you are shuting off your guests in a abrupt manor.

That's possible for guest Mageia 3 Alfa 3 but not for anyone else.

Now I always check if wmnet0, wmnet1 and wmnet8 is running before I start a guest and if not I just start vmware in MCC befor I start a guest.
Command: ifconfig.
When I do it this way everything works OK.
The problem begun suddenly at dec 17.

[wintpe]

well vmware is set to start in run level 5, which is same as X starts

so if its not starting at boot time you shoud try and find out why.

maybe its starting to early, because of mageias new systemd and a dependant service is not up when it starts.

be worth adding a sleep at the top of the /etc/init.d/vmware to slow down its start up and see if that helps

regards peter

[janpihlgren]

Well, I shutdown vmware (the program) before I shutdown the computer.
When I then started the computer the service vmware doesn't start (as before). I have to start (restart the vmware service manually and it started.

wintpe » Dec 19th, '12, 19:50
be worth adding a sleep at the top of the /etc/init.d/vmware to slow down its start up and see if that helps

I don't know where and what do do int inside the script.
For now I think I can live with this situation and manually start vmware service each tim I need to use VMware Workstation.
Thanks for your time.

[wintpe]

looks like you have exactly same problem as this, several fixes are proposed

problem is not mageia its vmware, effects opensuse and debian

http://forums.opensuse.org/english/get- ... rvice.html

before starting it run the following
ps -ef|grep -i vmware.

and lsmod |grep -i vmware

and adding a sleep to a startup script, surly you know how to do that?

just edit the script and add

sleep 5

at the begining of a script, just after the #!/bin/bash

perhaps you should do some shell scripting as part of your learning



regrads peter

[janpihlgren]

Thanks.
I'll see if I have to do a bugreport or if there already excist one.

[wintpe]

no just try some of there suggestions

[janpihlgren]

Well I removed S19vmware from rc2.d and rc3.d but no result.
Same as earlier, no start of vmware service.
I can't find out anything else to change.

[wintpe]

How about the commands i asked you to run?

and the sleep

regards peter

[janpihlgren]

Here is what I have done just now:
added sleep 5 to /etc/init.d/vmware
restarted the computer
did this:

Code: Select all

[root@Humlan jan]# ps -ef|grep -i vmware
root      2364     1  0 13:59 ?        00:00:00 /usr/bin/vmware-usbarbitrator
root      2931     1  0 13:59 ?        00:00:00 /usr/lib/vmware/bin/vmware-wsx-server --pidfile=/var/run/vmware-wsx-server.pid
root      2933  2931  0 13:59 ?        00:00:00 /usr/lib/vmware/bin/vmware-wsx-server --pidfile=/var/run/vmware-wsx-server.pid
root      3250     1  0 13:59 ?        00:00:01 /usr/lib/vmware/bin/vmware-hostd -a /etc/vmware/hostd/config.xml
root      4410  4191  0 14:03 pts/1    00:00:00 grep --color -i vmware
[root@Humlan jan]#

[root@Humlan jan]# lsmod |grep -i vmware
[root@Humlan jan]#


Run ifconfig
No vmnet0, vmnet1 or vmnet8

Starting Vmware Workstation
Trying to start client
faild with the same error as previus

Starting vmware service (inside MCC)
Discover a longer time before it started
Starting Vmware Workstation
starting client succeeded

Run ifconfig
vmnet0, vmnet1 and vmnet8 excist

The problem still exist

[janpihlgren]

For some reason I begun looking at systemd. When I search through the different files I did not discover VMware.
Then I run

Code: Select all

systemctl list-units -t service --all

I cut this line from a long list:

Code: Select all

VMware.service                          error  inactive dead        VMware.service

Then I run:

Code: Select all

root@Humlan jan]# systemctl status VMware.service
VMware.service
          Loaded: error (Reason: No such file or directory)
          Active: inactive (dead)

[root@Humlan jan]#


Now I supect that the VWware service is missing in somewhere in /etc/systemd/system.
I looked in /etc/systemd/system/multi-user.target.wants/sshd.service but don't understand how to do the same thing for VMware.

If I have to write one myself i need help to write it (layout) and where to put it.

[tom_]

Now I supect that the VWware service is missing in somewhere in /etc/systemd/system.

you can copy it from the italian forum, chapter "Workaround per systemd":

http://www.mageiaonline.it/doc/doku.php?id=doc:vmware_player_4

it is in italian but should be easy to understand