Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: bas60 on September 25, 2009, 06:09:24 PM
-
I'm trying to install VMWare 2.0 on SME Server 7.4
Installed fresh copy and run the update. I've done this before on 7.4 about 3 months ago and it worked just fine... is this contrib broken due to updates??
Following this http://wiki.contribs.org/Vmware I an error
last few lines
--> Processing Dependency: VMware-server for package: smeserver-vmware-server
--> Finished Dependency Resolution
Error: Missing Dependency: VMware-server is needed by package smeserver-vmware-server
================================================================
No new rpms were installed. No additional commands are required.
================================================================
Same error with VMServer 1.0
Anyone tried following the above contrib??
-
You need to install the VMWare-server itself before you try to add the smeserver-vmware-server (which is not really necessary anymore).
Download vmware-server (version 2.0.1 is the current) from vmware.com as a rpm and run yum localinstall VMware-server-2.0.1-156745.i386.rpm
After the installation, run vmware-config.pl script and insert the serial number (obtained free from vmware.com)
-
Thansk that seemed to get to install vmserver
I installed and configured it.
I download load and installed MUI and did the auto start using ln -s etc..
But can't seem to connect!
Do I need to do anything about smecontribs??
I did notice doing cd /etc/rc7.d
then ls gives me flashing red S91httpd.vmware
-
1. Do not install the MUI that is for VMware server v1 only
2. The correct commands are:
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S91vmware
and
/etc/rc7.d/S91vmware restart
3. If you used the defaults when you ran vmware-config.pl
You can access the VMware Infrastructure Web Access page from
http://server-IP-address:8222 or https://server-IP-address:8333
Hope this helps
Phil Brearley
-
ok so new install of 7.4, apply update
download vmware - VMware-server-2.0.1-156745.i386.rpm
Then to install;
yum localinstall VMware-server-2.0.1-156745.i386.rpm
configure vmware with vmware-config.pl
To make vmware autostart on reboot
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S91vmware
to run manually
/etc/rc7.d/S91vmware restart
load http://server-IP-address:8222 on pc - I can add a pre-configured XP an run it
---------------------------
This works.
Only problem is vmware won't stat with pc even when I type /etc/rc7.d/S91vmware !
but... if I re-run vmware-config.pl taking defaults i.e no changes
then /etc/rc7.d/S91vmware works fine! until next reboot
any ideas whats going on?
-
I had the same problem.
Try:
ln -s /etc/rc.d/init.d/vmware /etc/rc7.d/S91vmware
You will need to delete /etc/rc7.d/S91vmware first or you will get an error when you try to create the link
MJ
-
Please read the last two lines from the wiki:
Installing VMware Server 2 without the contrib smeserver-vmware-server will likely result in failure to start VMware after a reboot.
I have done several installs of VMware server 2.0.1 in the last two weeks.
The following has worked everytime.
New install of 7.4, apply update
Download vmware - VMware-server-2.0.1-156745.i386.rpm
Then install both VMware-server-2.0.1 and smeserver-vmware-server
yum localinstall VMware-server-2.0.1-156745.i386.rpm smeserver-vmware-server --enablerepo=smecontribs
signal-event post-upgrade; signal-event reboot
configure vmware with vmware-config.pl
Make vmware autostart on reboot
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S91vmware
to run manually
/etc/rc7.d/S91vmware restart
Access using http://server-IP-address:8222
Phil Brearley
-
Thank Phil,
I did this 2 again TWICE yesterday from Scratch after your's and Mjonhson's suggetion about the startup.
I took your yum localinstall VMware-server-2.0.1-156745.i386.rpm - literally and it does work fine. Is the "smeserver-vmware-server --enablerepo=smecontribs" bit required??
Didn't seem to cause a problem. Can be applied afterwords!!!???
As the very last install is on the production box ...
Perhaps the wiki should be updated now ?
-
please post the output of
config show vmware
-
config show vmware - gives nothing
[root@server-lon ~]# config show vmware
but....
[root@server-lon ~]# config vmware show
usage:
/sbin/e-smith/db dbfile keys
/sbin/e-smith/db dbfile print [key]
/sbin/e-smith/db dbfile show [key]
/sbin/e-smith/db dbfile get key
/sbin/e-smith/db dbfile set key type [prop1 val1] [prop2 val2] ...
/sbin/e-smith/db dbfile setdefault key type [prop1 val1] [prop2 val2] ...
/sbin/e-smith/db dbfile delete key
/sbin/e-smith/db dbfile printtype [key]
/sbin/e-smith/db dbfile gettype key
/sbin/e-smith/db dbfile settype key type
/sbin/e-smith/db dbfile printprop key [prop1] [prop2] [prop3] ...
/sbin/e-smith/db dbfile getprop key prop
/sbin/e-smith/db dbfile setprop key prop1 val1 [prop2 val2] [prop3 val3] ...
/sbin/e-smith/db dbfile delprop key prop1 [prop2] [prop3] ...
-
config show vmware - gives nothing
[root@server-lon ~]# config show vmware
so tha's why vmware doesn't start at boot after you do
ln -s /etc/rd.d/init.d/e-smith-service /etc/rc7.d/S99vmware
try:
config set vmware service status enabled
hth
-
Oh Sorry
I wasn't clear.
Vmware does work with ln -s /etc/rc.d/init.d/vmware /etc/rc7.d/S91vmware
as suggested by Mjohnson
infact everything seems OK now - I was just asking about the "smeserver-vmware-server --enablerepo=smecontribs" - is that really necessary since it all works...
Now that I have it installed on my production I wanted to make sure.
-
Thanks for this instresting info.
What I actually use to do myself is to first install the Centos 64 as a small and minimized as possible host operating system. Then I install wmware server on this as "the host".
On the host system I install Smoothwall as a virtual gateway software, and behind that, at a virtual lan segment I use to install 2 sme servers (server only) and 1 Windows 2000 Pro workstation.
The idea is to combine "the best fram some different wolds" in one installaion. The Smoothwall does the "firewall things", the one sme server is the "production server" and the other is the "testing server". Then the Windows 2000 is the "local windows client".
I also tried to run one extra virtual Asterisk server, but I ended up in using a Asterisk server running "inside" the sme server.
For connecting to "the machine" for remote control I use www.logmein.com and the virtual Windows 2000 installation. Of course other "remote windows" alternatives can be used.
This installation using wmware smooththwall - sme server(s) - and windows 2000 har been running rock stable and more stable than the "sme server only" installations I used to use before.
(Reason: In the old days new software had to be tested on the "production server". Now all testing is done at "virtual server copies" that van be deleted after testing.)
I guess the idea of using a local Windows 2000 installation as the "local windows administrator" also can be used when wmware is running "under" the SME server, rather than "above it".
The reason tha I use Windows 2000 raher than the XP is just because i consume less ram as a virtual machine. Its more easy with licenses, updates, etc. A second hand Windows 2000 license might not be to expensive these days.
I run the virtual Smoothwall gateway, the 2 sme servers and the local Windows 2000 client on 4 Gig of RAM, but I guess that 2 GB could also be enough.
Just some ideas ..
-
Vmware does work with ln -s /etc/rc.d/init.d/vmware /etc/rc7.d/S91vmware
as suggested by Mjohnson
indeed, but if you follow my advice you can do something like
config setprop vmware status disabled
to stop vmware starting at boot time.. I mean, the functionality is pretty the same, but you've got a better integration with SME
my 2c
-
> This DOES NOT work ** As suggested by Phil above **
Most likely the SMEConrib is broken with recent updates
New install of 7.4, apply update
Download vmware - VMware-server-2.0.1-156745.i386.rpm
Then install both VMware-server-2.0.1 and smecontribs
yum localinstall VMware-server-2.0.1-156745.i386.rpm smeserver-vmware-server --enablerepo=smecontribs
signal-event post-upgrade; signal-event reboot
configure vmware with vmware-config.pl
Make vmware autostart on reboot
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S91vmware
to run manually
/etc/rc7.d/S91vmware restart
Access using http://server-IP-address:8222
=================================
New install of 7.4, apply update
Download vmware - VMware-server-2.0.1-156745.i386.rpm
Then install both VMware-server-2.0.1 and smeserver-vmware-server
yum localinstall VMware-server-2.0.1-156745.i386.rpm
signal-event post-upgrade; signal-event reboot
configure vmware with vmware-config.pl
Make vmware autostart on reboot
ln -s /etc/rc.d/init.d/vmware /etc/rc7.d/S91vmware
to run manually
/etc/rc7.d/S91vmware restart
Access using http://server-IP-address:8222
-
That mirrors my experience.
MJ
-
I suppose this is an update to the update
Just did another test install....
The line that needs correcting with Phils suggestion (with smecontribs) is
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S91vmware
it should be ...
ln -s /etc/rc.d/init.d/vmware /etc/rc7.d/S91vmware
:cool:
-
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S91vmware is the correct link.
The e-smith-service works only when this service is enabled in the configuration db (Database) of the SME.
you must type this in the console:
"config set vmware service access public status enabled TCPPort 902" and the httpd.vmware command
"config set httpd.vmware service TCPPorts 8222,8333 access public status enabled"
after signal-event post-upgrade and signal event reboot VMware should work.
Read this there http://wiki.contribs.org/Vmware (http://wiki.contribs.org/Vmware)
Igi