generic blog of schmidi2

Error

# vmware-config.pl
The VMware VmPerl Scripting API was not installed.  Errors encountered during
compilation and installation of the module can be found here:
/tmp/vmware-config0

You will not be able to use the “vmware-cmd” program.

Errors can be found in the log file:
‘/tmp/vmware-config0/control-only/make.log’

Solution
# apt-get update
# apt-get install libssl-dev

Following packages are now new installed on the system:
libc6-dev libssl-dev linux-kernel-headers zlib1g-dev

# vmware-config.pl

After vmware is now properly configured, you can savely remove those packages again (but - let it be).

Source
http://www.linuxquestions.org/questions/linux-software-2/vmware-server-install-error-the-vmware-vmperl-scripting-api-was-not-installed.-476129/

Strange things can happen when having multiple ethernet adapters (including vpn connections) 
on the host system where you have installed and use VMware Player or VMware Server. If such adapters are not set as deactivated, all of the could be the one, which VMware chooses for bridging 
the network traffic. Most time, VMware is able to manage that correctly, but there are some circumstances, 
in which you should go for sure.

To do that goto:

1. Start -> Settings -> Network Connections
2. Right click on one of the connections, you don’t want a VMachine to be bridged to. Then select “Properties”.
3. Disable the service called “VMware Bridge Protocol” in the list by unchecking it.
4. Repeat step two and three for other connections, which should be ignored by VMware.

If you are using VMware server, you can do this also over the GUI application called “Manage Virtual Networks”.

When you first start a virtual machine (with a linux system) after moving, copying or downloading it from the internet, you will be prompted with the question whether you want to create a new identifier or not. If you click “Create”, you will probably don’t have network connection anymore in your virtual machine. This is because vmware changes the MAC-address of all ethernet-cards and linux detects a new but currently unconfigured network device.

$ sudo /etc/init.d/networking start
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth0: ERROR while getting interface flags: No such device
Failed to bring up eth0.

There are three ways to solve this problem:

Prevent
Click on the button “Keep” of the dialog prompted at the first start of the virtual machine after its store-position has changed (moving the directory of the virtual machine to a new location causes vmware to reshow this dialog).

Solve the right way
Edit the file “/etc/udev/rules.d/z25_persistent-net.rules”. You know by yourself what you have to do. If the file doesn’t exist,  go to “Solve the right way 2″. Else restart now udev with the command “/etc/init.d/udev restart” or reboot your system.

Solve the right way 2
Create the file “/etc/udev/rules.d/10_local.rules” and insert
KERNEL="eth*", SYSFS{address}="00:X0:18:ea:18:40", NAME="ethunten"
Don’t forget to replace the MAC-addres. Execute “udevtest /sys/class/net/eth0 net” and reboot your system.

Get backup
Replace the changed vmx-file with a backup (but I don’t belive you made one).

Live with it
When executing “ifconfig -a” you see the new network device (its probably called eth1, if you only have one network device).

 

Source:
http://www.debianhelp.co.uk/udev.htm
http://sicherheitsschwankung.de/post/jan/2005-10-13/renaming-network-devices-udev

 

Today I get the job to become acquainted with our .net projects (I dislike .net from microsoft because it’s a poor clone of java). First I had to install the vmware player to be able to run a windows system on my linux host and then install the visual studio stuff.

Sounds simple, but it was first impossible to compile runnable kernel modules required by vmware. And after I managed that with many dirty workarounds, vmplayer didn’t even start.

My workarounds:
I had to manually download and install the stable version (downgrade) of the packages cpp, gcc-4.1, gcc-4.1-base, libssp0 and module-init-tools. Now I have unmet dependencies (but I will upgrade them again immediately after successfully compiling the modules).

cpp-4.1_4.1.1-21_i386.deb
gcc-4.1_4.1.1-21_i386.deb
gcc-4.1-base_4.1.1-21_i386.deb
libssp0_4.1.1-21_i386.deb
module-init-tools_3.3-pre4-2_i386.deb

 

At least, trying to start vmplayer caused this error:

$ vmplayer
/usr/lib/vmware/bin/vmplayer: symbol lookup error: /usr/lib/vmware/lib/libvmwareui.so.0/libvmwareui.so.0: undefined symbol: _ZN3Gtk13RecentManager11get_defaultEv

I have already used too much time trying to solve this problem, I had to stop at this point.

Solution: Wait with upgrading your debian testing-system, if you wan’t a working vmware-environment. How long? Don’t know. I am sure the problem is because of one or more (many?) bug(s) in the current testing package-repository of debian.

Source:
http://www.vmware.com/community/thread.jspa?threadID=85481
http://www.vmware.com/community/thread.jspa?threadID=85612
http://www.vmware.com/community/thread.jspa?messageID=684669

 

For our VMachine-Hosts I used Debian Etch (as usual for linux systems). Linux kernel: 2.6.18-4-686

Quit fast I run into some problems with the rtc-interrupt. My syslog-file did contain nearly only these messages:

Jun 30 06:17:01 fakename kernel: rtc: lost some interrupts at 512Hz.
Jun 30 06:17:32 fakename last message repeated 1513 times

Also the hole screen was filled with the message “rtc: lost some interrupts at 512Hz”.

Well, actually I could ignore these messages because the VMachines run without problems. Except that the time ticked too slow (Daily ntp update, at midday the clock was about an hour behind the real time). But this could be fixed with hourly ntp updates. This was my temporary solution.

I found the final solution rather by the way (the first VMachine-Host was installed by my boss and he installed Sidux (after knoppix, kanotix, pclinux he prefers now sidux), there didn’t occour a problem like that). It seems that those two kernel images/modules are a little bit different (not only the version).

Solution: Get the newest sidux kernel (I use 2.6.20.1-slh-smp-2), the modules and headers.

 

Source:
www.sidux.com
www.vmware.com