Summary: | vmware-server-2.0.1.156745-r3 congig script failed to start | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | lexx <lexxkind> |
Component: | Current packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | dREPLACEeLETTEReEjBYeLETTEReA, kripton |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
lexx
2009-10-29 13:34:33 UTC
I've got the same here on my ~amd64-machine and vmware-server-2.0.2.203138 Of course the script can't stop the vmware-server, it isn't yet configured or even running. Didn't yet dig further into it, gotta get away from PC now :/ Try /opt/vmware/server/bin/vmware-config.pl --skip-stop-start Yes, that works. At least I was able to complete that setup script. Don't have the time for further testing right now, maybe sometime during the weekend. I installed app-emulation/vmware-server-2.0.1.156745-r3, I found two big security concerns about remote access, and have solved them. If anyone shows interest, ask here and I will submit a patched .ebuild. ################################# Remote access 1 ####################### 1) after `/etc/init.d/vmware start`, `netstat -lp` have the following additional lines, showing that vmware-server and its eventual holes are accessible from remote: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:902 *:* LISTEN 27933/vmware-authdl tcp 0 0 *:8333 *:* LISTEN 28048/vmware-hostd tcp 0 0 *:8307 *:* LISTEN 28048/vmware-hostd tcp 0 0 *:8222 *:* LISTEN 28048/vmware-hostd tcp 0 0 *:8005 *:* LISTEN 27924/webAccess tcp 0 0 *:8009 *:* LISTEN 27924/webAccess tcp 0 0 *:8308 *:* LISTEN 27924/webAccess FIXED: I made a wrapper to /opt/vmware/server/sbin/vmware-authdlauncher (listening 902) and /opt/vmware/server/lib/bin/vmware-hostd (listening 8222 and 8333) using dev-python/python-ptrace-0.6 for their startup, and I patched /opt/vmware/server/lib/webAccess/tomcat/apache-tomcat-6.0.16/conf/server.xml (ports 8308, 8307, 8009 and 8005) so that I now have the following lines in `netstat -lp`: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 localhost.localdoma:902 *:* LISTEN 27933/vmware-authdl tcp 0 0 localhost.localdom:8333 *:* LISTEN 28048/vmware-hostd tcp 0 0 localhost.localdom:8307 *:* LISTEN 28048/vmware-hostd tcp 0 0 localhost.localdom:8222 *:* LISTEN 28048/vmware-hostd tcp 0 0 localhost.localdom:8005 *:* LISTEN 27924/webAccess tcp 0 0 localhost.localdom:8009 *:* LISTEN 27924/webAccess tcp 0 0 localhost.localdom:8308 *:* LISTEN 27924/webAccess Now vmware-server is only listening to 127.0.0.1. The users will access to vmware-server through ssh tunnel. ################################# Remote access 2 ####################### 2) The interface vmnet0 and all virtual machines will listen all packets on eth0 with default choices of "emerge vmware-server --config". FIXED: I emerged net-misc/bridge-utils-1.4, added "brctl addbr ethvmware0" in /etc/init.d/vmware and gave ethvmware0 to "emerge vmware-server --config". |