Changes

From SME Server
Jump to navigationJump to search
6,382 bytes added ,  06:37, 19 October 2014
m
add note
Line 1: Line 1:  
{{Languages|vmware}}
 
{{Languages|vmware}}
 
+
{{usefulnote}}
== Vmware-server for SME Server ==
  −
{{Incomplete}}
  −
 
   
=== Maintainer ===
 
=== Maintainer ===
 
Sme Developers
 
Sme Developers
Line 14: Line 11:     
http://forums.contribs.org/index.php?topic=30838.msg162804#msg162804
 
http://forums.contribs.org/index.php?topic=30838.msg162804#msg162804
 +
===VMware Server 1.x and 2.x===
 +
====Installation====
 +
Obtain a license key from the VMWare website (you need this during installation in vmware-config.pl) ([http://www.vmware.com/freedownload/login.php?product=server20 VMWare Server 2 Website]).
 +
 +
Get shell access (with Putty, Gnome-terminal or similar ssh-client) and log in as root.
 +
 +
Decide which VMWare Server version you want and do one of the following. Note unless you have a specific need you should use VMWare Server 2.
 +
 +
* Download the VMWare-server 1.x RPM from the VMWare website to your machine ([http://register.vmware.com/content/download.html VMWare Server 1 Website])
 +
 +
wget http://download3.vmware.com/software/vmserver/VMware-server-1.0.9-156507.i386.rpm
 +
 +
* VMware Server 2.x can't be downloaded directly from VMware servers, so get it to your server in some other way. Obtain the correct version for your architecture (32bit or 64bit)  ([http://www.vmware.com/freedownload/login.php?product=server20 VMWare Server 2 Website])
 +
 +
=====SME7=====
 +
Issue the following command to install VMware together with the contrib:
 +
 +
yum install /path/to/VMware-server.rpm smeserver-vmware-server --enablerepo=smedev
 +
 +
The above should also install xinetd for dependency.
 +
 +
=====SME8=====
 +
The contrib introduces a dependency that cannot be resolved. This dependency is not necessary for sme8.
 +
yum install xinetd
 +
For SME8 32bit:
 +
yum localinstall <path-to--rpm-file>/VMware-server-2.0.2-203138.i386.rpm
 +
For SME8 64bit:
 +
yum localinstall <path-to--rpm-file>/VMware-server-2.0.2-203138.x86_64.rpm
 +
 +
configure vmware:
 +
vmware-config.pl
 +
and set vmware to autostart and reboot:
 +
ln -s ../init.d/vmware /etc/rc7.d/S19vmware
 +
signal-event post-upgrade; signal-event reboot
 +
 +
Watch the console for a correct start of vmware services. Features like maintenance from external networks, vmware configuration db commands described in the contrib [[vmware]] do not work. Use
 +
/etc/init.d/vmware start|stop|restart
 +
to manage the vmware services. If you do not want vmware server to autostart, remove the symbolic link .
 +
 +
 +
====Updating====
 +
Updating is similar to installation. You will need to download the latest rpm for example:
 +
 +
wget http://download3.vmware.com/software/vmserver/VMware-server-1.0.9-156507.i386.rpm
 +
 +
Issue the following command:
 +
 +
yum localupdate path/to/VMWare-server.rpm
 +
 +
You will also likely have to rerun the '''Configuration''' steps (below)
 +
 +
====Configuration====
 +
Go to VMware web site and get a free serial number for VMware Server, linux version [http://register.vmware.com/content/registration.html here].
 +
{{Note box|msg=The requirement for GCC is currently optional. Depending on your kernel at the time you may find the the included modules load and run perfectly (it will give you a message to this effect).
 +
Enabling repos help resolve dependencies.
 +
yum install gcc}}
 +
 +
To finish the installation run the following command:
 +
vmware-config.pl
 +
 +
{{Warning box|msg=Leaving gcc on a production server is considered a security risk, if you do not really need it you should not install it, if you need it you should seriously consider uninstalling gcc when you no longer need it. Removing gcc can be done using the following command:
 +
yum remove gcc}}
 +
 +
Clean up after the installation:
 +
signal-event post-upgrade; signal-event reboot
 +
 +
=== Management UI for VMWare Server 1.x ===
 +
====Installation====
 +
VMware Server Web-based management interface. It's optional, you can also use VMware Console from a client computer.
 +
wget http://download3.vmware.com/software/vmserver/VMware-mui-1.0.9-156507.tar.gz
 +
tar -xzvf VMware-mui-1.0.9-156507.tar.gz
 +
 +
cd vmware-mui-distrib/
 +
====Configuration====
 +
Configuration of the management user interface is done with a script that can be run like this:
 +
./vmware-install.pl
   −
The requirement for GCC is an optional maybe. Depending on your kernel at the time you may find the the included modules load and run perfectly (it will give you a message to this effect).
+
=== Remote access ===
 +
The VMware Server will only be accessible from the local network. If you want to be able to access the VMware Server from internet, run these commands:
 +
====Console====
 +
To allow console access from your local network:
 +
config set vmware service access private status enabled TCPPort 902
   −
Also, be aware that a yum update that includes a new kernel may cause a failure of VMware-server. In this case, you will have to re-run vmware-config.pl and rebuild the modules.
+
{{Warning box|The command below will open the ports of the Management Console to the internet, this means a serious security implication}}
 +
To allow console access from all over the internet:
 +
config set vmware service access public status enabled TCPPort 902
   −
related: [[bugzilla 1723]]
+
Update the remote access settings and reload changes:
 +
signal-event remoteaccess-update
   −
It may be easier to just use vmware player or workstation on your client PC.
+
Substitute "disabled" instead of "enabled" in the above commands to disable access.
 +
 
 +
====Management UI====
 +
To allow Management UI access from your local network:
 +
config set httpd.vmware service TCPPorts 8222,8333 access private status enabled
 +
 
 +
{{Warning box|The command below will open the ports of the Management UI to the internet, this means a serious security implication}}
 +
To allow Management UI access from all over the internet:
 +
config set httpd.vmware service TCPPorts 8222,8333 access public status enabled
 +
 
 +
After defining the service we need to make the service start at boot time
 +
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S91httpd.vmware
 +
 
 +
Now we can manually start the service
 +
/etc/rc7.d/S91httpd.vmware restart
 +
signal-event remoteaccess-update
 +
 
 +
Substitute "disabled" instead of "enabled" in the above commands to disable access.
 +
 
 +
=== Usage ===
 +
==== Management Console for VMware Server 1.x ====
 +
Download and install the VMware console from the VMware web site, or the MUI webpage, on a client machine or use the existing console if you already have VMware (Server) installed.
 +
 
 +
Run Console on your client and connect to your_server and start to play...
 +
 
 +
====Management UI for 1.x ====
 +
Open a web browser and go to https://your_server:8333/vmware/en/
 +
 
 +
Log in as root and you will find VMware Management interface.
 +
 
 +
====Management UI for 2.x ====
 +
Open a web browser and go to http://ip.of.your.server:8308/ui/# or https://ip.of.your.server:8333/ui/#
 +
 
 +
Log in as the user you specified during configuration, and you will find VMware Management interface.
 +
 
 +
=== Uninstallation ===
 +
vmware-uninstall-mui.pl
 +
yum remove VMware-server gcc smeserver-vmware-server
 +
 
 +
=== Check installed versions ===
 +
yum info installed smeserver-vmware-server VMware-server
    
=== Additional information ===
 
=== Additional information ===
 
More information about vmware can be found on the vmware website http://www.vmware.com/products/server/
 
More information about vmware can be found on the vmware website http://www.vmware.com/products/server/
 +
 +
If some setting went wrong during installation, just rerun
 +
vmware-config.pl
    
NB. VMware-server benefits from a lot of ram.
 
NB. VMware-server benefits from a lot of ram.
Line 30: Line 153:  
=== Bugs ===
 
=== Bugs ===
 
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-vmware-server component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-vmware-server|title=this link}}.
 
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-vmware-server component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-vmware-server|title=this link}}.
 +
 +
==== Known problems ====
 +
Be aware that a yum update that includes a new kernel may cause a failure of VMware-server. In this case, you will have to re-run vmware-config.pl and rebuild the modules.
 +
 +
Virtual machines created in a Windows host probably need further customization to work fully under SMEserver (Linux) host.
 +
 +
Installing VMware Server 2 without the contrib smeserver-vmware-server will likely result in failure to start VMware after a reboot.
 +
<br />If that is your case you probably have to reinstall the whole server before attempting to install VMware again.
 
   
 
   
 
----
 
----
 
[[Category: Contrib]]
 
[[Category: Contrib]]
 +
[[Category: Virtualisation]]

Navigation menu