Installing VMware server 2.0.2 on debian 6.0.1 X64


Download VMware-server-2.0.2-203138.x86_64.tar.gz from the vmware website and place it in /usr/src (you need to register on the VMware website before you can download)

Download my install file below and unpack it to /usr/src:

cd /usr/src
wget http://www.troublenow.org/files/vmware/vmware2.0.2-on-debian6.0.1.tar.gz
tar xvzf vmware2.0.2-on-debian6.0.1.tar.gz
cd /usr/src/vmware2
sh install-vmware-2.0.2.sh

This wil unpack the files, patch them for debian 6.0.1 and start the vmware installation.
Answer all the questions during the vmware install and the installation should complete.

Now reboot the server and you should be ready to go.

The above vmware2.0.2-on-debian6.0.1.tar.gz file has the following content:

00-vmware-2.6.32_functional.diff
01-vmware-2.6.32_cosmetic.diff
02-vmnet-include.diff
install-vmware-2.0.2.sh
patch-vmware_2.6.3x.sh
vmware-config.pl.diff

All files except install-vmware-2.0.2.sh are from NerdbyNature.de with some small modifications.
install-vmware-2.0.2.sh is a simple setup script I created for easy install.

References:

40 replies on “Installing VMware server 2.0.2 on debian 6.0.1 X64”

  1. This works best of all the patches I’ve had so far .. most don’t seem to be ready for Debian 6.0.1.

    If only Networking would work… it builds the vmnet-module correctly an installs it successfully – The guest is even recognized by the server via vmware tools to have the right IP-address – but no connection can be made to the guest network in any of the network adapter Modes (nat, Hostonly, Bridged)

    Any idea what I am missing ? – It worked with lenny … thanks

  2. I used this method on 3 machines and had the same issue on all machines, you just have to reboot after installing VMware to fix it (he does mention it in the post to reboot)

    Somehow it loads the vmnet modules but they don’t work until after a reboot.

    1. Nope – Rebooted – several times – still nothing.
      Repeated the install process several times.
      Even did a manual uninstall with thorough cleanup.

    2. Have you tried upgrading the vmware’s to the latest hardware version? Also make sure you install the latest vmware tools (today I had a windows guest I booted but network didn’t work until I upgraded the hardware version and the latest vmware tools.)

      Might also be hardware or something. Today I setup my fourth machine using this page without any problems (got 5 simple test servers to run vmware’s for development testing.) so it does work 🙂

      I use a clean 64bit minimal debian 6 installation, going to try out 32bit tomorrow on my last machine.

    3. This was an existing VM on a working Debian installation. I upgraded Lenny to Squeeze and used the above code to get the VMWare Server working again.

      the vmnet module is running and working, but there doesn’t seem to be a connection.

      It seems to be some kind of low-level routing problem. From the Host i cannot ping the guest. I have gotten it as far as having an IP assigned to the guest – but then I get “destination Host unreachable” when pinging the host/gateway-IP from the guest.

      vmnet-sniffer gives me a lot of arp-requests which are never ever answered by the host.

      Next i will create a new VM and see if a new debian guest system has the same problems. The one I’m having problems with is an existing Windows 2008 Server R2 guest whose Exchange Services are desperately needed.

      Since this machine is sitting in a datacenter somewhere far from here and because of the specifics of this data center a bridged setup is not really an option – although i tested it too and i didn’t get any connection into the guest either.

      I am now convinced that it’s no a problem with this patch, but still flummoxed as to why the seems to be a thin layer of isolation between the guest system and the host – and no, it’s not the firewall either.

    4. Progress ! …
      But not done yet.
      It’s definite now: the HostOnly Virtual Hub is not working – Network mode “NAT” works but doesn’t solve my problem.
      I don’t expect help here (Thanks anyway, Mike 😉 ), just need a place to vent my frustration and see if I can find people with the same problem.

      OTOH – Does anybody have an idea how to use iptables to forward an external IP adress to a guest system while using the nat mode ? Bridge-mode doesn’t work with my ISP, since their routing is MAC-based and duplicating the external MAC-address for my virtual network adapter will only create more problems.

    5. Hello Philipp

      Looks like you are using vmware server the same way we are. We ran into exactly the same problem. If you sniff on the vmnet device you can see a lot of TX packets but zero RX packets. Also TX and RX bytes is 0. Strangely enough DHCP packets go through the interface and the vmware client gets the right IP configuration.
      Did you anything special to get the NAT device working? It also does not work in our case.

      Many thanks for your reply
      Josef Ender

    6. Hi, having the same problem aswell, cannot ping the gateway from host, pinging from guest works, aswell as the internet connection through NAT
      the only thing that doesn’t work is the host guest communication, and I need it done, not by routing packets through external address, port forwarding, or even VPN (i used openvpn and I’m connecting guest to the external host address which is listening for openvpn clients)

      but i need a stable fast connection between host and guest, not mentioning the traffic which my datacenter will probably charge me for (using ex IP)

  3. You should use VMware’s NAT portforwarding then.

    Edit the file /etc/vmware/vmnet8/nat/nat.conf

    find the section “[incomingtcp]” at the bottom of the file and add the ports you want to open up.

    So if you want port 22 forwarded to your vmware just add:
    22 = xxx.xxx.xxx.xxx:22

    (Where xxx is the IP of the virtual guest in NAT mode)

    Then restart the networking services:
    /usr/lib/vmware/net-services.sh restart

    1. Yes … but the Host has several IP-Adresses – and one of them is supposed to go into the guest system.

      The nat.conf doesn’t allow for a certain outside-IP to be used for outbound traffic and port forwarding, does it ? is there some iptables nat routing that could be used to handle this ?

      It used to work perfectly with the Hostonly network and some iptables nat routing

    2. As far as I know VMware just uses the main interface IP of the machine for NAT (eth0).

      Never tried using hostonly and iptables NAT but if that worked before I don’t see any reason why it shouldn’t work any more in Debian 6.

      Great patch by the way, installed the patches manually for the first time took me about 40 minutes, today used this method and 5 minutes later VMware was working perfectly. Thanks!

  4. No go for me 🙂
    I get the following errors:

    make[4]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1
    make[3]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2
    make[2]: *** [sub-make] Error 2
    make[1]: *** [all] Error 2
    make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-amd64′
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-config0/vmmon-only’
    Unable to build the vmmon module.

    And than a: Execution aborted.

  5. BEST PATCH EVER!!! spent 5 days trying other patches that broke my server …. had to reinstall OS 4 times..
    until i found this page….

    THANK YOU !!!!!!!

    keep up the good work!

    /Nadav

  6. He encontrado la solución para el problema de la red, hay que realizar unos parches en:

    vmci.tar
    vmmon.tar
    vmnet.tar
    vsock.tar

    Cuando hagais la instalación teneis que copiar estos ficheros en /vmware-server-distrib/lib/modules/source los sustituis y listo, podeis empezar la instalación y cuando acabeis podeis comprobar que el Nat y el Hostonly funcionan correctamente.

    Podeis descargar los archivos modificados de:

    http://www.exared.com/vmware-parches.zip

  7. It also works on Ubuntu 10.04 Server LTS with kernel 2.6.32-33-server.

    I just needed:
    sudo su
    apt-get install build-essential linux-headers-`uname -r`
    apt-get install make
    apt-get install gcc

    … and your install file.

    Thank you very much!

    Linux srv001lin 2.6.32-33-server #72-Ubuntu SMP Fri Jul 29 21:21:55 UTC 2011 x86_64 GNU/Linux

  8. Thank you for this excellent little guide and included patch and script! Works much easier than others I have tried. Just installed on Debian 6.0.2 on i386, only had to make a small change to the script to replace “x86_64” with “i386”.

    One suggestion: add “psmisc” to the list of packages that get installed, I had to put this in for the killall utility.

  9. Snazzy patch…. install worked like a charm… now if only i can get the browser/ui to open lol 🙂

  10. it’s work on Debian 6.0.3 amd64(linux 2.6.32-5-amd64)
    thx!!!
    root@debian:~# aptitude install linux-headers-$(uname -r) patch make build-essential
    root@debian:~# rm /usr/bin/gcc
    root@debian:~# ln -s /usr/bin/gcc-4.3 /usr/bin/gcc
    root@debian:~# cd /tmp
    root@debian:/tmp# tar -zxf /usr/src/VMware-server-2.0.2-203138.x86_64.tar.gz
    root@debian:/tmp# ./vmware-server-distrib/vmware-install.pl
    # install but not run vmware-config.pl
    root@debian:/tmp# wget http://www.troublenow.org/files/vmware/vmware2.0.2-on-debian6.0.1.tar.gz
    root@debian:/tmp# tar -zxf ./vmware2.0.2-on-debian6.0.1.tar.gz
    root@debian:/tmp# patch /usr/bin/vmware-config.pl < /tmp/vmware2/vmware-config.pl.diff
    root@debian:/tmp# cd /usr/lib/vmware/modules/source
    root@debian:/usr/lib/vmware/modules/source# for i in *.tar ; do tar xpf $i ; done
    root@debian:/usr/lib/vmware/modules/source# for i in /tmp/vmware2/00-vmware-2.6.32_functional.diff /tmp/vmware2/01-vmware-2.6.32_cosmetic.diff /tmp/vmware2/02-vmnet-include.diff; do patch -p1 < $i; done
    root@debian:/usr/lib/vmware/modules/source# for i in vmci vmmon vmnet vsock ; do tar cpf $i.tar $i-only ; done
    root@debian:/usr/lib/vmware/modules/source# /usr/bin/vmware-config.pl

  11. Big thanks from Belgium !!

    Been fighting with Vmware server 2 for a long time using multiple different configs and patches, but this one just ….. works …. 🙂 !!!

  12. Very well working. Great job – seriously!

    Only issue I had after a kernel-upgrade: a complete uninstall of all potions and a clean new install was the only solution which worked for me (on Squeez 64 bit 6.0.3 now).

    Nevertheless, system works perfectly now – even the web interface works well on Chrome.

    Thanks from Istanbul.

  13. This patch worked out smoother than I ever would have exptected a patch to work. Good work, and thanks a lot!

    Mvh
    Per Gunnar Hansø

  14. I tried the manual configuration from consatan but vmnet1 doesn’t work i can’t access to the host from vm with host only, have anybody a idea

    Philipp

Comments are closed.