VMWare Player Install on Slackware 12.0

perry · 10-28-2007, 11:34 AM

Quote:

Originally Posted by niels.horn

I have used Windows from the very beginning (Windows 1.02) all the way through 95, NT, 98, 2000 up to XP.
For many years I have sustained my family being a Microsoft Certified Professional / System Engineer and always joked that I was happy with so many problems that I had to solve, securing my job.

In parallel, around 1993 I got introduced to *NIX (I only had used some Minix in the past for study-purposes) at a company that used Sun Workstations. I learned to write quite complex shell-scripts.
In 1996, after becoming displeased with Windows 95, I started using a dual-boot setup with Slackware. Using this distribution, I felt I was "in control" again - something I couldn't say about Windows.

I have been dual-booting between Windows and Slackware until I discovered VMware server. Now I exclusively boot to Slackware, using VMware whenever I need to run something that isn't available for Linux.

For me, Slackware has proved to be infinitely more stable and secure than Windows. I will definitely NOT install Vista at home. It reminds me too much of Windows ME.

Unfortunately, I still use Windows at the office, because they have some corporate systems that I can only use this way. But this will also change, as they are moving everything to web-based systems. My notebook I use at work has a dual-boot setup with XP and Slackware 11. Booting XP means getting coffee, having a chat with colleagues, etc. Booting Slackware means productivity, less crashes.

How much trouble is it to put VMware onto Slackware 12 ? And do I need a video card better than my ATI 9600, perhaps I'm confusing VMware with Beryl. But if I thought it would work without too much fuse I'd install it in no time. The impression I get from VMware is that it's an easy 28 step process, something I'm not too interested in spending the week trying to do. Could you elaborate on what's involved?

Thanks

- perry

ps.
I've been dual booting Slackware and Windows for quite some time using System Commander until that finally gave out on me and now I'm totally committed to getting things done with LILO. GRUB is ok, but Lilo seems to be much easier to deal with.

XavierP · 10-28-2007, 12:47 PM

Perry - I have moved your post to it's own thread in Slackware as it was a problem on it's own and seperate from the rest of the discussion.

niels.horn · 10-28-2007, 07:33 PM

Quote:

How much trouble is it to put VMware onto Slackware 12 ?

Actually, it's not too much trouble at all, just carefully follow these steps:

Step 1:
Get VMware-server-1.0.3-44356.tar.gz (*) from the official VMware site to the directory of your choice. Do get the .tar.gz file, not the RPM package. (didn't work for me)
* Note: there might be a newer version available, but the instructions should work the same way

Step 2:
Download "vmware-any-any-update113.tar.gz" if you have Slackware-stable,
or "vmware-any-any-update114.tar.gz" if you use Slackware-current, to the directory of your choice (same as above).
The 114 version might work on -stable as well, it just wasn't available at the time.
Do a Google search for the filename and you'll see some locations where it is available.

Step 3:
(This step is in my notes, but I am not sure if it is really necessary...)
Make the directory /etc/pam.d:

Code:

mkdir /etc/pam.d

Step 4:
First step of installation of VMware server.
From the directory where you downloaded the .tar.gz files:

Code:

tar -xzf VMware-server-1.0.3-44356.tar.gz
cd vmware-server-distrib
perl vmware-install.pl

(run install script, but when asked, do not run vmware-config.pl)

Step 5:
Now we'll install the any-any patch for our kernel:

Code:

cd ..
tar -xzf vmware-any-any-update113.tar.gz
cd vmware-any-any-update113
perl runme.pl

(install patch, run config script, now answer "yes" to run vmware-config.pl)

Step 6:
Here we'll do some automatic compiling...
Just hit enter to all questions...

Step 7:
Use your favorite text-editor to add this to /etc/rc.d/rc.local to start at boot:

Code:

# Start vmware-daemon if installed
if [ -x /etc/init.d/vmware ]; then
        sh /etc/init.d/vmware start
fi

Step 8:
Reboot...

Ready!

Just a last tip:
I had problems saving my virtual machines on non-Linux partitions, like NTFS (with NTFS-3G) or vfat.
I tried this originally to share my virtual machines between Windows VMware and Linux VMware, bu had no success.
On my ext3 partitions everything worked fine.

Hope this works for everybody like it worked for me!

digitalboy74 · 10-29-2007, 11:05 PM

that is an incredible documented install. i use the any-any but my notes are not nearly as pretty.

kudos neils

jong357 · 10-30-2007, 07:33 AM

The OP was refering to VMware Player I believe. Which is the stand alone package that runs images. It's been almost 2 years I think since I touched VMware anything. The Server needs PAM and Workstation shouldn't.

Historically, there was a problem with vmware-config.pl because it contained lines that only looked for SysVinit directories which earlier Slackware versions didn't have setup. This _shouldn't_ be a problem anymore with Slack 12. So the rc.local addition really shouldn't be necessary anymore. In fact, the install process for Workstation or Server should be the same as it is on any distro now.

Again, haven't tried lately. I used to ammend vmware-config.pl to work with the /etc/rc.d directory straight up. I still don't like using init.d directories on Slack for some reason.

dbnor · 10-30-2007, 08:10 AM

I am currently running vmware server 1.04 on slackware 12 - desktop opti gx620 and laptop insp 5160 -
have xp virtual plus a couple of different linux distros, running just fine.

shadowsnipes · 10-30-2007, 10:09 AM

Quote:

Originally Posted by niels.horn

Just a last tip:
I had problems saving my virtual machines on non-Linux partitions, like NTFS (with NTFS-3G) or vfat.
I tried this originally to share my virtual machines between Windows VMware and Linux VMware, bu had no success.
On my ext3 partitions everything worked fine.

I tried the same the thing a while back. The reason it does not work is because you cannot set proper permissions for NTFS or VFAT partitions. I have a theory that you can trick the virtual machine into running by having all the config files (including the files reserved for memory, etc) on linux including a symlink to the actual hard drive file on your windows based partition. I haven't tested this out yet, though. I decided Windows doesn't need anymore services and that Linux is what I'll be using 99% of the time anyways.

At any rate, I remember doing similar things to the instructions above for setting up VMware in Slackware 12. I also remember that I DID have to create the /etc/pam.d directory because the setup failed otherwise. When it fails because it can't find the directory it tells you why it failed, so there isn't really any mystery to this. Do note, however, that you can install VMware server without PAM. You can create and use virtual machines, but I don't think you can properly serve them if others want to use them remotely.

And NO, you don't need a good video card to run VMware server. I'm running VMware server 1.0.3 build-44356 (I haven't felt like upgrading to the very newest just yet) on Slack 12 with a humble old SiS 65x VGA Adapter and a 2GHz Celeron. Direct Rendering isn't even supported for my card, but virtual machines run just fine. As long as you have somewhat of a modern CPU and at least 512MB RAM you should be fine (though I'd recommend twice as much memory more ideal in case you don't want to start swapping like crazy).

niels.horn · 10-31-2007, 04:18 AM

Quote:

Originally Posted by jong357

The OP was refering to VMware Player I believe. Which is the stand alone package that runs images. It's been almost 2 years I think since I touched VMware anything. The Server needs PAM and Workstation shouldn't.

Well, actually Perry asked how to install "VMware" in another thread, but it was split into a separate one for being a different question.

VMware-player only "runs" virtual machines created on other computers.
VMware-server is a free product you can use to create, run and share virtual machines on your network.
VMware-desktop is a commercial product (not free).

VMware-server has developed into a very nice product over the years. If you haven't seen it for some time, do take a look a the newer versions.

I use it for running Windows apps without dual-booting (I can access the data on my Linux partitions over the 'virtual network') and testing on Slackware.
I have a VM with a clean install of Slackware that I can copy, test software, compile things, etc. When something goes wrong, I fall back to the clean install in a few steps.

perry · 10-31-2007, 12:22 PM

Quote:

Originally Posted by niels.horn

Well, actually Perry asked how to install "VMware" in another thread, but it was split into a separate one for being a different question.

VMware-player only "runs" virtual machines created on other computers.
VMware-server is a free product you can use to create, run and share virtual machines on your network.
VMware-desktop is a commercial product (not free).

VMware-server has developed into a very nice product over the years. If you haven't seen it for some time, do take a look a the newer versions.

I use it for running Windows apps without dual-booting (I can access the data on my Linux partitions over the 'virtual network') and testing on Slackware.
I have a VM with a clean install of Slackware that I can copy, test software, compile things, etc. When something goes wrong, I fall back to the clean install in a few steps.

neils:

thanks for getting back to me. i tried installing the player as per the instructions and ended up getting this message:

Code:

vmware is installed, but it has not been (correctly) configured
for this system. To (re-)configure it, invoke the following command:
/usr/bin/vmware-config.pl.

i've tried a couple of configurations and now according to you, i am probable going to be needing vmware-desktop in order to do what i want to do. so i don't know what to think. but i really do appreciate your trying to help me out. all i wanted to do is play a few windows games on my linux box without having to dual boot into windows, but it's ok. if the player alone can't do this then it's just as well.

appreciate your help though

- perry

XavierP · 10-31-2007, 12:42 PM

Perry - what happens when you run the command as per the error message? I recall that the last time I installed to Slack I had to run the same message and once done it was configured and installed.

niels.horn · 10-31-2007, 08:26 PM

Perry,
Which kernel are you using and which version of Slackware?

Did you run the 'runme.pl' script from vmware-any-any-update?
This should start the vmware-config.pl automatically.

If in doubt, go back to step 5 and try again.

You don't need the VMware-desktop product. VMware server can do everything you need, including creating and running virtual machines.

Feel free to contact me or ask more questions here!

Niels

cwizardone · 11-01-2007, 11:28 AM

Quote:

Originally Posted by niels.horn

...I use it for running Windows apps without dual-booting (I can access the data on my Linux partitions over the 'virtual network') and testing on Slackware.....

May I ask how you setup your virtual network?
I had XP running in a virtual machine in Slackware 12, but I couldn't figure out how to move files from the XP virtual machine to the Linux host. Samba is installed.
Thanks.

shadowsnipes · 11-01-2007, 11:57 AM

I don't use Samba shares so I just transfer files between my virtual machine and the host by using an sftp server on the virtual machine (yes, you can get one for windows- try openssh). gftp is a nice frontend that comes with Slackware.

perry · 11-02-2007, 11:56 AM

Quote:

Originally Posted by XavierP

Perry - what happens when you run the command as per the error message? I recall that the last time I installed to Slack I had to run the same message and once done it was configured and installed.

here's what i get:

Code:

root@slackware:/home/perry# cd /home/perry/vmware-any-any-update114
root@slackware:/home/perry/vmware-any-any-update114# ls
runme.pl* services.sh* update* update.c vmblock.tar vmmon.tar vmnet.tar
root@slackware:/home/perry/vmware-any-any-update114# ./runme.pl
Updating /usr/bin/vmware-config.pl ... already patched
Updating /usr/bin/vmware ... No patch needed/available
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.

Before running VMware for the first time after update, you need to configure it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the command for
you now? [yes]

Making sure services for VMware Server are stopped.

Stopping VMware services:
Virtual machine monitor [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet1 [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
Host-only networking on /dev/vmnet8 [ OK ]
Virtual ethernet [ OK ]

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the mime type icons?
[/usr/share/icons]

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]

In which directory do you want to install the application's icon?
[/usr/share/pixmaps]

Trying to find a suitable vmmon module for your running kernel.

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]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.21.5-smp/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.21.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.21.5'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
. . .
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2666: warning: 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2666: warning: 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2666: warning: 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this function
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciContext.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciDatagram.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciDriver.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciDs.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciGroup.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciHashtable.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciProcess.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciResource.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmciSharedMem.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config0/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config0/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.21.5'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.

This program previously created the file /dev/vmmon, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/parport0, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/parport1, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/parport2, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/parport3, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet0, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet1, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet8, and was about to remove
it. Somebody else apparently did it already.

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?

Do you want networking for your virtual machines? (yes/no/help) [yes]

This program previously created the file /dev/vmnet2, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet3, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet4, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet5, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet6, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet7, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet9, and was about to remove
it. Somebody else apparently did it already.

Would you prefer to modify your existing networking configuration using the
wizard or the editor? (wizard/editor/help) [wizard]

The following bridged networks have been defined:

. vmnet0 is bridged to wlan0

Do you wish to configure another bridged network? (yes/no) [no]

Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes] no

Removing a NAT network for vmnet8.

Do you want to be able to use host-only networking in your virtual machines?
[no] no

Removing a host-only network for vmnet1.

Extracting the sources of the vmnet module.

Building the vmnet module.

Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.21.5-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.21.5'
CC [M] /tmp/vmware-config0/vmnet-only/driver.o
CC [M] /tmp/vmware-config0/vmnet-only/hub.o
CC [M] /tmp/vmware-config0/vmnet-only/userif.o
CC [M] /tmp/vmware-config0/vmnet-only/netif.o
CC [M] /tmp/vmware-config0/vmnet-only/bridge.o
CC [M] /tmp/vmware-config0/vmnet-only/filter.o
CC [M] /tmp/vmware-config0/vmnet-only/procfs.o
CC [M] /tmp/vmware-config0/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-config0/vmnet-only/smac_linux.x386.o
LD [M] /tmp/vmware-config0/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.21.5'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.

Please specify a port for remote console connections to use [902]
You already have an entry for "/usr/sbin/vmware-authd" in the "/etc/inetd.conf"
file. No change will be made to it.

Hit enter to continue.

Configuring the VMware VmPerl Scripting API.

Building the VMware VmPerl Scripting API.

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Installing the VMware VmPerl Scripting API.

The installation of the VMware VmPerl Scripting API succeeded.

Generating SSL Server Certificate

In which directory do you want to keep your virtual machine files?
[/var/lib/vmware/Virtual Machines]

Do you want to enter a serial number now? (yes/no/help) [no]

Starting VMware services:
Virtual machine monitor [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]

The configuration of VMware Server 1.0.4 build-56528 for Linux for this running
kernel completed successfully.

root@slackware:/home/perry/vmware-any-any-update114#

maybe i'm just not starting it right...

like i don't really know what to do to from here and there is no icon on my desktop

any help would be greatly appreciated

thanks

- perry
ps.
you'll notice i said no to any nat configurations, i've tried both setups, nothing seems to work

shadowsnipes · 11-02-2007, 04:09 PM

It looks like to me that everything is set up just fine. To use it you need to run

Code:

/usr/bin/vmware

(it should be in your PATH so 'vmware' would suffice)

If it ever complains that the service isn't started just run (as root)

Code:

/etc/init.d/vmware start

'restart' and 'stop' are also useful options

From there connect to the localhost server and add your virtual machines or create new ones. Normally you would want to run this as your normal user. However, some host related options can only be set in the GUI if you run it as root. Just don't run it as root unless you need to.

No, it doesn't install an icon to your desktop, but there should be one in your KDE menu. The actual 'shortcut' is in /usrs/share/applications
Just run vmware - it takes less time to type it in a run box or command line than to find it on a menu.

Oh, and it looks like you didn't enter a serial number. They are free to obtain when you register. Go to http://register.vmware.com/content/registration.html
to register for serial numbers. There is an option in the GUI to enter it.

There are plenty of manuals on VMware's site if you have any trouble administering things in the GUI. Also, remember you can always

Code:

man vmware