...
These instructions assume you have root access and are using a bash shell:
Panel |
---|
sudo bash |
Panel |
---|
yum groupremove "Virtualization" -y |
VMWare Server cannot be installed on a computer running a Xen kernel. To determine if a Xen kernel is being used:
Panel |
---|
uname -a |
The following output indicates a Xen kernel is being used:
Panel |
---|
Linux blade1g6-4 2.6.18-92.el5xen #1 SMP Tue Jun 10 19:20:18 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux |
If "xen" appears in the output of the previous command, replace the Xen Kernel with the following commands:
Panel |
---|
yum update ecryptfs-utils -y |
Check the grub.conf file to make sure it is not configured to boot using the Xen Kernel
Panel |
---|
less /boot/grub/grub.conf |
The grub.conf file should NOT look like this:
Panel |
---|
# grub.conf generated by anaconda |
The grub.conf file SHOULD look like this:
Panel |
---|
# grub.conf generated by anaconda |
After removing the Xen kernel, reboot the computer:
Panel |
---|
reboot |
Download the latest VMware Server 1.x RPM from http://www.vmware.com
(Note: these instructions assume you saved the RPM into /install)
Install the VMware Server RPM:
Panel |
---|
rpm -ivh /install/VMware-server-1.0.8-126538.i386.rpm |
Configure VMware Server:
Panel |
---|
vmware-config.pl |
Note: if you receive an error message you may need to install or update some libraries and then run vmware-config.pl again:
Panel |
---|
yum install glibc-devel -y |
VMware networking should be configured as follows after answering the questions asked by vmware-config.pl
The following lists the sequence of answers to be entered after issuing the vmware-config.pl command:
Panel |
---|
yum groupremove "Virtualization" -y |
VMWare Server cannot be installed on a computer running a Xen kernel. To determine if a Xen kernel is being used:
Panel |
---|
uname -a |
The following output indicates a Xen kernel is being used:
Panel |
---|
Linux blade1g6-4 2.6.18-92.el5xen #1 SMP Tue Jun 10 19:20:18 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux |
If "xen" appears in the output of the previous command, replace the Xen Kernel with the following commands:
Panel |
---|
yum update ecryptfs-utils -y |
Check the grub.conf file to make sure it is not configured to boot using the Xen Kernel
Panel |
---|
less /boot/grub/grub.conf |
The grub.conf file should NOT look like this:
Panel |
---|
# grub.conf generated by anaconda |
The grub.conf file SHOULD look like this:
Panel |
---|
# grub.conf generated by anaconda |
After removing the Xen kernel, reboot the computer:
Panel |
---|
reboot |
Download the latest VMware Server 1.x RPM from http://www.vmware.com
(Note: these instructions assume you saved the RPM into /install)
Install the VMware Server RPM:
Panel |
---|
rpm -ivh /install/VMware-server-1.0.8-126538.i386.rpm |
Configure VMware Server:
Panel |
---|
vmware-config.pl |
Note: if you receive an error message you may need to install or update some libraries and then run vmware-config.pl again:
Panel |
---|
yum install glibc-devel -y |
VMware networking should be configured as follows after answering the questions asked by vmware-config.pl
The following lists the sequence of answers to be entered after issuing the vmware-config.pl command:
Wiki Markup |
---|
In which directory do you want to install the mime type icons?
\[/usr/share/icons\] *ENTER* |
Wiki Markup |
---|
What directory contains your desktop menu entry files?
These files have a .desktop file extension. \[/usr/share/applications |
Wiki Markup |
---|
In which directory do you want to install the mime type icons?
\[/usr/share/icons\] *ENTER* |
Wiki Markup |
---|
What directory contains your desktop menu entry files?
These files have a .desktop file extension. \[/usr/share/applications\] *ENTER* |
Wiki Markup |
---|
In which directory do you want to install the application's icon?
\[/usr/share/pixmaps\] *ENTER* |
Wiki Markup |
---|
None of the pre-built vmmon modules for VMware Server is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? \[yes\] *ENTER* |
Wiki Markup |
---|
What is the location of the directory of C header files that match your running
kernel? \[/lib/modules/2.6.18-128.1.14.el5/build/include\] *ENTER* |
Wiki Markup |
---|
Do you want networking for your virtual machines? (yes/no/help) \[yes\] *ENTER* |
Wiki Markup |
---|
Your computer has multiple ethernet network interfaces available: eth0, eth1,
virbr0. Which one do you want to bridge to vmnet0? \[eth0\] *eth1* |
Wiki Markup |
---|
Do you wish to configure another bridged network? (yes/no) \[no\] *ENTER* |
Wiki Markup |
---|
Do you want to be able to use NAT networking in your virtual machines? (yes/no)
\[yes\] *no* |
Wiki Markup |
---|
Do you want to be able to use host-only networking in your virtual machines?
\[no\] *yes* |
Wiki Markup |
---|
Do you want this program to probe for an unused private subnet? (yes/no/help)
\[yes\] *no* |
Wiki Markup |
---|
Do you wish to configure another host-only network? (yes/no) \[no\] *ENTER* |
Wiki Markup |
---|
TheIn defaultwhich portdirectory :do 902you iswant notto free.install Wethe application's icon? \[/usr/share/pixmaps\] *ENTER* |
Wiki Markup |
---|
None of the pre-built vmmon modules for VMware Server is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? \[yeshave selected a suitable alternative port for VMware Server use. You may override this value now. Remember to use this port when connecting to this server. Please specify a port for remote console connections to use \[904\] *ENTER* |
Wiki Markup |
---|
InWhat whichis directorythe dolocation youof want to keep your virtual machine files? \[/var/lib/vmware/Virtual Machinesthe directory of C header files that match your running kernel? \[/lib/modules/2.6.18-128.1.14.el5/build/include\] *ENTER* |
Wiki Markup |
---|
TheDo path "/var/lib/vmware/Virtual Machines" does not exist currently. This program is going to create it, including needed parent directories. Is this what you want? you want networking for your virtual machines? (yes/no/help) \[yes\] *ENTER* |
Verify the host-only network was configured correctly:
Panel |
---|
/sbin/ifconfig |
You should see a vmnet1 interface using IP address 192.168.0.1:
Panel |
---|
vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01 |
Restart the vmware service (/sbin/service vmware restart), you should see the following:
Panel | ||
---|---|---|
|
Modify the /etc/hosts file to include entries for the VM host and guest computers:
Panel |
---|
vi /etc/hosts |
Add the entries in bold:
Panel |
---|
127.0.0.1 localhost |
Panel |
---|
vi /etc/ssh/sshd_config |
Add the following line to the end of the file:
Panel |
---|
ListenAddress 192.168.0.1 |
Restart the sshd service on the management node:
Panel |
---|
/sbin/service sshd restart |
Add the VM host's public key to its own authorized_keys file to allow it to SSH to itself without a password prompt:
Panel |
---|
cat /etc/vcl/vcl.key.pub >> /root/.ssh/authorized_keys |
The following command should execute without having to enter a password:
Panel |
---|
ssh localvmhost 'ls /' |
Configure the keys column in the managementnode table in the VCL database
Configure the vcld.conf file to use vcl.key:
Panel |
---|
vi /etc/vcl/vcld.conf |
Modify all of the IDENTITY lines to specify the vcl.key file:
Panel |
---|
IDENTITY_blade_linux=/etc/vcl/vcl.key |
Save a copy of the original dhcpd.conf file:
Panel |
---|
mv /etc/dhcpd.conf /etc/dhcpd.conf.orig |
Configure the dhcpd.conf file:
Panel |
---|
vi /etc/dhcpd.conf |
The dhcpd.conf file should contain the following:
No Format |
---|
ddns-update-style none;
ddns-update-style none;
shared-network vmnet1 {
subnet 192.168.0.0 netmask 255.255.0.0 {
ignore unknown-clients;
option routers 192.168.0.1; host vmguest-1 {
option host-name "vmguest-1";
hardware ethernet 00:50:56:1a:01:01;
fixed-address 192.168.1.1;
filename "/tftpboot/pxelinux.0";
option dhcp-server-identifier 192.168.0.1;
next-server 192.168.0.1;
}
}
}
|
The DHCP daemon should only listen on the virtual private network (vmnet1) to avoid conflicts with other production VCL networks. Configure the dhcpd service startup script to only listen on the vmnet1 interface:
Panel |
---|
vi /etc/init.d/dhcpd |
Add vmnet1 the to the daemon $dhcpd line as shown:
Code Block |
---|
start() {
[ -x $dhcpd ] || return 5
[ -f $conf ] || return 6 pidofproc $prog >/dev/null 2>&1
RETVAL=$?
[ $RETVAL -eq 0 ] && return $RETVAL echo -n $"Starting $prog: "
daemon $dhcpd vmnet1 $DHCPDARGS 2>/dev/null
RETVAL=$?
echo
[ $RETVAL = 0 ] && touch $lockfile
return $RETVAL
}
|
Configure the dhcpd service to automatically start at runlevels 3-5:
Panel |
---|
/sbin/chkconfig --level 345 dhcpd on |
Start the dhcpd service:
Panel |
---|
/sbin/service dhcpd start |
Wiki Markup |
---|
Your computer has multiple ethernet network interfaces available: eth0, eth1,
virbr0. Which one do you want to bridge to vmnet0? \[eth0\] *eth1* |
Wiki Markup |
---|
Do you wish to configure another bridged network? (yes/no) \[no\] *ENTER* |
Wiki Markup |
---|
Do you want to be able to use NAT networking in your virtual machines? (yes/no)
\[yes\] *no* |
Wiki Markup |
---|
Do you want to be able to use host-only networking in your virtual machines?
\[no\] *yes* |
Wiki Markup |
---|
Do you want this program to probe for an unused private subnet? (yes/no/help)
\[yes\] *no* |
Wiki Markup |
---|
Do you wish to configure another host-only network? (yes/no) \[no\] *ENTER* |
Wiki Markup |
---|
The default port : 902 is not free. We have selected a suitable alternative
port for VMware Server use. You may override this value now.
Remember to use this port when connecting to this server.
Please specify a port for remote console connections to use \[904\] *ENTER* |
Wiki Markup |
---|
In which directory do you want to keep your virtual machine files?
\[/var/lib/vmware/Virtual Machines\] *ENTER* |
Wiki Markup |
---|
The path "/var/lib/vmware/Virtual Machines" does not exist currently. This
program is going to create it, including needed parent directories. Is this
what you want? \[yes\] *ENTER* |
Verify the host-only network was configured correctly:
Panel |
---|
/sbin/ifconfig |
You should see a vmnet1 interface using IP address 192.168.0.1:
Panel |
---|
vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01 |
Restart the vmware service (/sbin/service vmware restart), you should see the following:
Panel | ||
---|---|---|
|
Modify the /etc/hosts file to include entries for the VM host and guest computers:
Panel |
---|
vi /etc/hosts |
Add the entries in bold:
Panel |
---|
127.0.0.1 localhost |
Panel |
---|
vi /etc/ssh/sshd_config |
Add the following line to the end of the file:
Panel |
---|
ListenAddress 192.168.0.1 |
Restart the sshd service on the management node:
Panel |
---|
/sbin/service sshd restart |
Add the VM host's public key to its own authorized_keys file to allow it to SSH to itself without a password prompt:
Panel |
---|
cat /etc/vcl/vcl.key.pub >> /root/.ssh/authorized_keys |
The following command should execute without having to enter a password:
Panel |
---|
ssh localvmhost 'ls /' |
Configure the keys column in the managementnode table in the VCL database
Configure the vcld.conf file to use vcl.key:
Panel |
---|
vi /etc/vcl/vcld.conf |
Modify all of the IDENTITY lines to specify the vcl.key file:
Panel |
---|
IDENTITY_blade_linux=/etc/vcl/vcl.key |
Save a copy of the original dhcpd.conf file:
Panel |
---|
mv /etc/dhcpd.conf /etc/dhcpd.conf.orig |
Configure the dhcpd.conf file:
Panel |
---|
vi /etc/dhcpd.conf |
The dhcpd.conf file should contain the following:
No Format |
---|
ddns-update-style none;
ddns-update-style none;
shared-network vmnet1 {
subnet 192.168.0.0 netmask 255.255.0.0 {
ignore unknown-clients;
option routers 192.168.0.1; host vmguest-1 {
option host-name "vmguest-1";
hardware ethernet 00:50:56:1a:01:01;
fixed-address 192.168.1.1;
filename "/tftpboot/pxelinux.0";
option dhcp-server-identifier 192.168.0.1;
next-server 192.168.0.1;
}
}
}
|
The DHCP daemon should only listen on the virtual private network (vmnet1) to avoid conflicts with other production VCL networks. Configure the dhcpd service startup script to only listen on the vmnet1 interface:
Panel |
---|
vi /etc/init.d/dhcpd |
Add vmnet1 the to the daemon $dhcpd line as shown:
No Format |
---|
start() {
[ -x $dhcpd ] || return 5
[ -f $conf ] || return 6
pidofproc $prog >/dev/null 2>&1
RETVAL=$?
[ $RETVAL -eq 0 ] && return $RETVAL
echo -n $"Starting $prog: "
daemon $dhcpd vmnet1 $DHCPDARGS 2>/dev/null
RETVAL=$?
echo
[ $RETVAL = 0 ] && touch $lockfile
return $RETVAL
}
|
Configure the dhcpd service to automatically start at runlevels 3-5:
Panel |
---|
/sbin/chkconfig --level 345 dhcpd on |
Start the dhcpd service:
Panel |
---|
/sbin/service dhcpd start |
...