VMware server 2 na Debian Squeeze 2.6.38

Založil polo, 13. 08. 2011, 23:28:06

Předchozí téma - Další téma

polo

Ahoj,
mate nekdo zkusenosti s instalaci VMware serveru 2 na Debianu Squeeze s jadrem 2.6.38? Ptam se proto, ze se mi nedari VMware nainstalovat. Delal jsem to podle tohoto http://radu.cotescu.com/how-to-install-vmware-server-ubuntu-fedora-opensuse/ navodu. Pred spustenim instalacniho skriptu jsem instaloval vse potrebne:

  • Debian Squeeze 2.6.38-bpo.2-686-bigmem
  • linux-headers-2.6.38-bpo.2-686-bigmem
  • build-essential (11.5 version)
   
Vysledek sputeni skriptu:

[/list]sudo ./vmware-server-2.0.x-kernel-2.6.3x-install.sh
You have VMware Server archive:
VMware-server-2.0.2-203138.i386.tar.gz
cat: /etc/*-release: Directory doesnt exits
cat: /etc/*-release: Directory doesnt exits
cat: /etc/*-release: Directory doesnt exits
Extracting the contents of VMware-server-2.0.2-203138.i386.tar.gz
Found .tar file for vsock module
Found .tar file for vmnet module
Found .tar file for vmci module
Found .tar file for vmmon module
Extracting .tar files in order to apply the patch...
Untarring /home/polo/vmware/vmware-server-distrib/lib/modules/source/vsock.tar
Untarring /home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet.tar
Untarring /home/polo/vmware/vmware-server-distrib/lib/modules/source/vmci.tar
Untarring /home/polo/vmware/vmware-server-distrib/lib/modules/source/vmmon.tar
Testing patch...
Creating some simlinks for the newer kernels...
Applying patch...
Preparing new tar file for vsock module
Preparing new tar file for vmnet module
Preparing new tar file for vmci module
Preparing new tar file for vmmon module
Checking that the compiling will succeed...
Trying to compile vmnet module to see if it works
Performing make in /home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only
Using 2.6.x kernel build system.
/home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only/driver.c: In function 'VNetFileOpUnlockedIoctl':
/home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only/driver.c:1190: error: implicit declaration of function 'lock_kernel'
/home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only/driver.c:1192: error: implicit declaration of function 'unlock_kernel'
make[4]: *** [/home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only/driver.o] Error 1
make[3]: *** [_module_/home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make: *** [vmnet.ko] Error 2
There is a problem compiling the vmnet module after it was patched.



Z chybove hlasky nejsme schopny si s tim poradit - alespon pro me je nic nerikajici.

Pokud nekdo mate jiny navod jak VMware server 2 instalovat, budu rad kdyz ho sem uvedete. Potrebuju to rozjet a na jine virtualizacni reseni prechazet nechci.

Ota Trkola

Zkus se kouknout sem:

http://wiki.debian.org/VMware

Kdesi dole je kapitola Installing VMware Server 2 on Squeeze. Třeba to pomůže.

polo

Ahoj,
to jsme sice taky nasel, ale ten navod je pro kernel 2.6.32 (ja mam 2.6.38), takze asi nepomuze. Navic jsem si vsimnul z chybove hlasky nasledujiciho:

/home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only/driver.c: In function 'VNetFileOpUnlockedIoctl':
/home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only/driver.c:1190: error: implicit declaration of function 'lock_kernel'
/home/polo/vmware/vmware-server-distrib/lib/modules/source/vmnet-only/driver.c:1192: error: implicit declaration of function 'unlock_kernel'


Vygooglil jsem, ze implicit declaration of function je zpousobeno:
CitaceYou forgot to provide a prototype for a function within the scope
visible to the compiler at the point where it was compiling a call to
that function.

Vypada to, ze nemuze najit deklarace techto funkci: unlock_kernel a lock_kernel. Ty nejsou v hlavickovych souborech linux-headers-2.6.38-bpo.2-686-bigmem ale jsou v linux-headers-2.6.38-bpo.2-common. Konretne v souboru /usr/src/linux-headers-2.6.38-bpo.2-common/include/linux/smp_lock.h.

Ten skript co spoustim bohuzel pouziva linux-headers-2.6.38-bpo.2-686-bigmem coz je spravne protoze takove je i oznaceni meho jadra... Tady uz nevim jak dal - tohle uz je, ale trosku vyssi liga.