questo vmware è una palla al piede ... ma mi serve ....

[Lucky_Luke]

Salve a tutti, utenti di hwupgrade. Vi spiego brevemente il problema: installato vmware da tar.gz su uuntu dapper drake 6.06, e ad ogni avvio del pc devo riconfigurarlo senno non parte. Vi copio qua i vari output del terminale, cosi (forse) ci capite qualcosa .... A me pare di averlo installato correttamente, difatti dopo averlo riconfigurato funziona anche internet, ma è una scocciatura ... ci metto meno a riavviare il pc quasi ....

Originariamente inviato da Lucky_Luke

stefano@Ubuntu:~$ vmware
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.

stefano@Ubuntu:~$ su
Password:
root@Ubuntu:/home/stefano# /usr/bin/vmware-config.pl
Making sure services for VMware Workstation are stopped.

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

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]


** (process:2024): CRITICAL **: egg_desktop_entries_add_group: assertion `egg_desktop_entries_lookup_group (entries, group_name) == NULL' failed

** (process:2064): CRITICAL **: egg_desktop_entries_add_group: assertion `egg_desktop_entries_lookup_group (entries, group_name) == NULL' failed
Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation 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? [/usr/src/linux-headers-2.6.15-25-686/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Workstation 5.5.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /usr/src/linux-headers-2.6.15-25-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.15-25-686'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config0/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/task.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but not for C++
include/asm/bitops.h: In function ‘int find_first_bit(const long unsigned int*, unsigned int)’:
include/asm/bitops.h:326: warning: comparison between signed and unsigned integer expressions
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$rip’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$rip’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageGSX25]’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$rip’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageGSX2]’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$rip’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV321]’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV32]’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMDriver*, Vcpuid)’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: ‘sysenterState$cs’ may be used uninitialized in this function
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
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-headers-2.6.15-25-686'
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/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.

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes]

Extracting the sources of the vmnet module.

Building the vmnet module.

Building for VMware Workstation 5.5.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /usr/src/linux-headers-2.6.15-25-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.15-25-686'
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/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
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-headers-2.6.15-25-686'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.

Starting VMware services:
Virtual machine monitor done
Virtual ethernet done
Bridged networking on /dev/vmnet0 done
Host-only networking on /dev/vmnet1 (background) done
Host-only networking on /dev/vmnet8 (background) done
NAT service on /dev/vmnet8 done

The configuration of VMware Workstation 5.5.1 build-19175 for Linux for this
running kernel completed successfully.

You can now run VMware Workstation by invoking the following command:
"/usr/bin/vmware".

Enjoy,

--the VMware team

root@Ubuntu:/home/stefano#

Alcune informazioni utili:

Originariamente inviato da Lucky_Luke

root@Ubuntu:/home/stefano# uname -a
Linux Ubuntu 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 2006 i686 GNU/Linux
root@Ubuntu:/home/stefano#

cmq nn capisco perchè smp ... nn mi pare di averlo messo di testa mia

Originariamente inviato da Lucky_Luke

root@Ubuntu:/home/stefano# vmware -v
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
VMware Workstation 5.5.1 build-19175

Parerebbe che ci sia un problema di dipendenze, ma quella libpng12.so.0 nn la trovo manco da sorgente ...

Ecco ... ehm .. scusate per il lungo post . Ripeto, questo devo farlo ad ogni avvio di ubuntu dapper 6.06 e nn capisco perchè .... qualcuno sa darmi una mano, per favore ? Ho gia provato nelle IRC di ubuntu ma senza esito (positivo ). Vi prego, che qualcuno mi aiuti
Grazie mille anticipatamente.
Cordialmente, Lucky Luke.

[manowar84]

non puoi capire quanto tempo ci ho perso con vmware!!
mi sarò ricompilato il kernel 6/7 volte...

La soluzione? con il 2.6.15.1 funziona, con altri non mi andava bene... persino il 2.6.15 non andava!!

[ArtX]

prova qemu+kqemu, va benissimo ed è anche abbastanza veloce. bellisima inoltre l'immagine qcow che ha le dimensioni solo di quello che c'è dentro e si ingrandisce man mano che la si riempie

[PeK]

noi abbiamo tutta la struttura delle rete di test basata su vmware. finchè avevamo la versione "workstation" funzionava tutto. poi per risparmiare un pò abbiamo messo ESX server... son 2 mesi che ci perdo la testa dietro. c'è SEMPRE qualcosa che non va: gran parte delle volte 'è il vmmon/vmnet o con le pam... sarò riuscito a farlo funzionare una decine di volte in tutto.
il bello è che ogni volta gli errori sono robe tipo "errore, il messaggio di errore è: fine del messaggio di errore"

chi mi sa dire perchè vmware-authd dalla version 27xxx va sempre, SEMPRE, in panic? (ovvio che ho controllato tutto, in xinit.d in pam.d in services.. non so dove sbattere la testa )

tutto questo per dire: non legarti a vmware. finchè sei in tempo usa altre soluzioni, altrimenti ti ritrovi con una libreria di immagini compatibili solo con vmware e che rifare costa di più che sprecare ore a cercare di risolvere problemi.

ps
anche vmware usa lo spazio nelle immagini a seconda di quanto gli serve

[PeK]

controllato e ricontrollato, cambiate le versioni di gcc, ricompilato il kernel con le opzioni più standard in assoluto (tutti i moduli caricabili, niente roba "experimental") per vedere se era un problema di versioni di gcc...

su una debian sarge e kernel 2.4.18-nonricordo, provato anche con un kernel 2.6.8, niente da fare.

mi dice "module loads perfectly in current kernel" lsmod me li lista, modprobe o insmod non protestano... insomma il problema non mi pare essere quello.