|
Linux
|
|
Tuesday, 03 June 2008 16:16 |
After the last article about Running VMware Player on Linux I thought that it would be very nice to be able to create new and modify existing machines. Ergo, let's try the latest version of VMware Server on the same machine. Well, this installation doesn't need any modifications in source code but it is also not without pains.
The main difference for sure is that the VMware server runs as a service - well, actually it is invoked by xinetd - and can be administrated locally and remotely. But let's focus on the installation first. As mentioned we need xinetd on our system. This is done via apt, aptitude or any other APT install client that you prefer:
sudo apt-get install xinetd
After that we just run the standard procedure. Unpacking the archive and running the installation script like so:
tar xvzf VMware-server-1.0.6-91891.tar.gz
cd vmware-server-distrib
sudo ./vmware-install.pl
The installation process is nearly the same as for the VMware Player. Additionally you have to agree the EULA and enter the serial number for the server. The serial number is provided by the registration on VMware's website.
Alright, everything looks fine and we can try to fire up the VMware Server Console from the Applications :: System menu. In case that you don't get any reaction or feedback, open a terminal and run the command:
vmware
to see what's happening behind the scenes. I got several errors according to wrong version of gcc:
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4' not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4' not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4' not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)
and therefore I did a short research on the web to find a nice solution:
cd /usr/lib/vmware/lib/libgcc_s.so.1
sudo mv libgcc_s.so.1 libgcc_s.so.1.org
cd ../libpng12.so.0
sudo mv libpng12.so.0 libpng12.so.0.org
Attention: The destination paths on your system might vary depending on your entries during the installation procedure. Renaming the library files provides access to the existing library files of your Linux system.
After this little tweak I could run the VMware Server Console directly from the console and from the menu without any problems. Now, it is your time to enjoy and operate your virtual machines with VMware Server.
Sincerely, JoKi
|
|
|
Linux
|
|
Wednesday, 28 May 2008 11:21 |
A new article since a long time. Sorry, I was and still am very busy on my job but I need to write these lines first.
Since last month I modified my main development system a little bit and instead of running a native Windows operating system I gave xubuntu 7.10 a try. For developing purposes I installed VMware Player and therefore run virtual machines with Windows XP and Windows Vista. That's way more practical then a multiboot system. By the way, you can do this as well under Windows directly and use Microsoft Virtual PC instead of VMware, too.
As said, I started with xubuntu 7.10 and upgraded recently to 8.04 (Hardy Heron). Everything went smooth but VMware Player didn't start anymore. Fine, as VMware comes with predefined kernel modules which none of them fits for kernel version 2.6.24-16-generic you have to initiate the compile process yourself. No problem at all. Well, in general...
Sadly, the compile did not finish and interrupted with an error message according to a wrongly included header file. So, I looked around a bit and found a nice step-by-step guide on the VMware website to get it up and running. Here are the steps:
- cd /usr/lib/vmware/modules/source
- cp vmmon.tar vmmon.tar.orig
- sudo tar xvf vmmon.tar
- cd vmmon-only/include/
- sudo nano vcpuset.h (or use any other editor you prefer)
- change line 74 from: #include “asm/bitops.h†to: #include “linux/bitops.hâ€
- rm vmmon.tar (return to the folder where you decompressed the tar file)
- sudo tar cvf vmmon.tar vmmon-only/
- sudo rm -rf vmmon-only/
- sudo vmware-config.pl
If you try to install a fresh tarball of VMware Player then the path to the vmmon.tar archive varies depending on your download.
- cd <path/to/your/dir>/vmware-player-distrib/lib/modules/source/
The modification is the same but the last steps differ:
- cd ../../../
- sudo ./vmware-install.pl
This process should work for VMware Server and Workstation as well.
And this morning I had to do the same steps again due to an 'sudo apt-get dist-upgrade' that installed a new kernel version 2.6.24-17-generic. So, after all and now that you know how to get your VMware Player to fly, it's not a big deal.
Sincerely, JoKi
|
|
|
|
|
|
RSS 2.0 
