Toon posts:

[VMWARE] wil niet netwerken na kernel upgrade

Pagina: 1
Acties:

Verwijderd

Topicstarter
Ik draaide VMware 5.0.0.13124 op Archlinux 0.7 met een standaardkernel, die me sinds kort erg geod bevalt. Ik upgrade de kernel en diens headers met de packacge manager van deze distributie, pacman. Alles werkte daarna prima, na lilo gedraaid en gereboot te hebben heb ik de vmware modules opnieuw gecompileerd. met

code:
1
/usr/bin/vmware-config.pl --compile


Er waren echter compileerfouten opgetreden, en er was een opmerking over dat eth0 al 'bridged' was. Ik gebruikte dus bridged networking tussen de host en vm.

Na het compileren start het script automatisch de services, maar de bridged networking (/dev/vmnet0) service wou niet starten.

Vmware draaide prima, de vmmon module deed het dus, maar netwerken vanuit de vm ho maar.

Hieronder volgt de - iets verkorte - output van het hercompileerproces:

code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
[root@Wombat vmware-distrib]# /usr/bin/vmware-config.pl --compile
Making sure services for VMware Workstation are stopped.

Stopping VMware services:
   Virtual machine monitor                                             done

You must read and accept the End User License Agreement to continue.
Press enter to display it. 

----licence gedoe----

Do you accept? (yes/no) yes

Thank you.

Configuring fallback GTK+ 2.4 libraries.

***
* Updating MIME database in /usr/share/mime...
***
In which directory do you want to install the mime type icons? 
[/usr/share/icons] 

In which directory do you want to install the application's icon? 
[/usr/share/pixmaps] 

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? [/lib/modules/2.6.12-ARCH/build/include] 

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.12-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.12-ARCH'
  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
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.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-2.6.12-ARCH'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.

Do you want networking for your virtual machines? (yes/no/help) [yes] 

Configuring a bridged network for vmnet0.

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

All your ethernet interfaces are already bridged.

Do you want to be able to use NAT networking in your virtual machines? (yes/no) 
[yes] no

Do you want to be able to use host-only networking in your virtual machines? 
[no] no

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.12-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.12-ARCH'
  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
/tmp/vmware-config0/vmnet-only/userif.c: In function `VNetUserIfMapUint32Ptr':
/tmp/vmware-config0/vmnet-only/userif.c:152: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
/tmp/vmware-config0/vmnet-only/userif.c:153: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
  CC [M]  /tmp/vmware-config0/vmnet-only/netif.o
  CC [M]  /tmp/vmware-config0/vmnet-only/bridge.o
/tmp/vmware-config0/vmnet-only/bridge.c: In function `VNetBridgeUp':
/tmp/vmware-config0/vmnet-only/bridge.c:716: warning: passing arg 3 of `sk_alloc' makes pointer from integer without a cast
/tmp/vmware-config0/vmnet-only/bridge.c:716: warning: passing arg 4 of `sk_alloc' makes integer from pointer without a cast
  CC [M]  /tmp/vmware-config0/vmnet-only/procfs.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST
Warning: could not open /tmp/vmware-config0/vmnet-only/includeCheck.h: Invalid argument
  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-2.6.12-ARCH'
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                                  failed

The configuration of VMware Workstation 5.0.0 build-13124 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


Snapt iemand hier wat er mis is gegaan ?

Hiermee lijkt verband te hebben dat het afsluiten van het systeem hangt bij het afsluiten van de network daemon...

Verwijderd

Warning: could not open /tmp/vmware-config0/vmnet-only/includeCheck.h: Invalid argument"
Geen idee hoe erg dit is, maar goed zal het niet zijn. :)

Verwijderd

Topicstarter
En /tmp is ook nog als tmpfs gemount, ramdisk dus. Dus het kan niet zijn dat er per ongeluk nog oude troep in de /tmp stond na een slechte reboot ofzo... En nee er was niet te weinig ruimte...

  • backupdevice
  • Registratie: November 2000
  • Laatst online: 10-02 11:32

backupdevice

No Risk , Full Push

vmnet0 is bridged to eth0

All your ethernet interfaces are already bridged. Dat is dus niet ok.

Haal hem even van bridged netwerk af, geef die VM rechtstreeks toegang tot het netwerk, kijk of die het dan wel doet :)

[ Voor 49% gewijzigd door backupdevice op 13-07-2005 16:17 ]

"This is it....This is it " | Gianpiero Lambiase | Lap 54 12-12-2021


Verwijderd

Topicstarter
Ik denk dat je bedoelt via NAT ?

Ik heb het compileren overnieuw gedaan, en bij NAT support JA gezegd. Bridged support geeft hij blijkbaar altijd, daar wordt niet om gevraagd. De vm instlelingen zet ik ook op NAT.

Moet er trouwens bij zeggen dat zodra ik iets deed met de vm, dat samba het ook niet meer doet. shares zijn niet toegankelijk, samba herstarten hangt, ik had ook een keer dat startx het niet eens deedd... het een of ander houdt mijn netwerkkaart bezet ofzo. Ik heb een deinstallatie gedaan van vmware, alle /dev/vm* entries waren dan weg, overnieuw geinstalleerd, maar het probleem blijft.

output van het hercompileren met NAT support:

code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
[root@Wombat gdt]# cd /usr/bin
[root@Wombat bin]# ./vmware-config.pl --compile
Making sure services for VMware Workstation are stopped.

Stopping VMware services:
   Virtual machine monitor                                             done
   Bridged networking on /dev/vmnet0                                   done
   Virtual ethernet                                                    done

Configuring fallback GTK+ 2.4 libraries.

***
* Updating MIME database in /usr/share/mime...
***
In which directory do you want to install the mime type icons? 
[/usr/share/icons] 

In which directory do you want to install the application's icon? 
[/usr/share/pixmaps] 

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? [/lib/modules/2.6.12-ARCH/build/include] 

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.12-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.12-ARCH'
  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
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.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-2.6.12-ARCH'
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/parport0, 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.

This program previously created the file /dev/vmnet0, 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) [no] 

Do you want networking for your virtual machines? (yes/no/help) [yes] 

This program previously created the file /dev/vmnet1, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet2, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet3, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet4, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet5, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet6, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet7, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet8, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet9, and was about to remove 
it.  Somebody else apparently did it already.

Would you prefer to modify your existing networking configuration using the 
wizard or the editor? (wizard/editor/help) [wizard] 

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

All your ethernet interfaces are already bridged.

Do you want to be able to use NAT networking in your virtual machines? (yes/no) 
[yes] yes

Configuring a NAT network for vmnet8.

Do you want this program to probe for an unused private subnet? (yes/no/help) 
[yes] 

Probing for an unused private subnet (this can take some time)...

The subnet 172.16.8.0/255.255.255.0 appears to be unused.

The following NAT networks have been defined:

. vmnet8 is a NAT network on private subnet 172.16.8.0.

Do you wish to configure another NAT network? (yes/no) [no] 

Do you want to be able to use host-only networking in your virtual machines? 
[yes] no

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.12-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.12-ARCH'
          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
/tmp/vmware-config0/vmnet-only/userif.c: In function `VNetUserIfMapUint32Ptr':
/tmp/vmware-config0/vmnet-only/userif.c:152: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
/tmp/vmware-config0/vmnet-only/userif.c:153: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
  CC [M]  /tmp/vmware-config0/vmnet-only/netif.o
  CC [M]  /tmp/vmware-config0/vmnet-only/bridge.o
/tmp/vmware-config0/vmnet-only/bridge.c: In function `VNetBridgeUp':
/tmp/vmware-config0/vmnet-only/bridge.c:716: warning: passing arg 3 of `sk_alloc' makes pointer from integer without a cast
/tmp/vmware-config0/vmnet-only/bridge.c:716: warning: passing arg 4 of `sk_alloc' makes integer from pointer without a cast
  CC [M]  /tmp/vmware-config0/vmnet-only/procfs.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST
Warning: could not open /tmp/vmware-config0/vmnet-only/includeCheck.h: Invalid argument
  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-2.6.12-ARCH'
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                                  failed
   Host-only networking on /dev/vmnet8 (background)                    done
   NAT service on /dev/vmnet8                                          done

The configuration of VMware Workstation 5.0.0 build-13124 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


De vm heeft nu geen internet en netwerktoegang.

Hierna zal ik proberen weer te hercompileren en weer zonder NAT support. Ik zal de vm's op bridged zetten. Ik post het niet in een keer want zodra ik iets met vmware doe sinds dat probleem, kan ik niet posten op t.net (weer zoiets vaags), sites bezoeken wel, maar bij Verstuur Bericht loopt zowel firefox als epiphany als galeon vast.

Verwijderd

Topicstarter
Hier de output van het opnieuw compileren zonder NAT:

code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
[root@Wombat bin]# ./vmware-config.pl --compile
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/vmnet8                                          done
   NAT service on /dev/vmnet8                                          done
   Host-only networking on /dev/vmnet8                                 done
   Virtual ethernet                                                    done

Configuring fallback GTK+ 2.4 libraries.

***
* Updating MIME database in /usr/share/mime...
***
In which directory do you want to install the mime type icons? 
[/usr/share/icons] 

In which directory do you want to install the application's icon? 
[/usr/share/pixmaps] 

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? [/lib/modules/2.6.12-ARCH/build/include] 

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.12-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.12-ARCH'
  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
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.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-2.6.12-ARCH'
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/parport0, 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.

This program previously created the file /dev/vmnet0, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet8, 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) [no] 

Do you want networking for your virtual machines? (yes/no/help) [yes] 

This program previously created the file /dev/vmnet1, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet2, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet3, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet4, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet5, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet6, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet7, and was about to remove 
it.  Somebody else apparently did it already.

This program previously created the file /dev/vmnet9, and was about to remove 
it.  Somebody else apparently did it already.

Would you prefer to modify your existing networking configuration using the 
wizard or the editor? (wizard/editor/help) [wizard] 

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

All your ethernet interfaces are already bridged.

Do you want to be able to use NAT networking in your virtual machines? (yes/no) 
[yes] no

Removing a NAT network for vmnet8.

Do you want to be able to use host-only networking in your virtual machines? 
[no] 

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.12-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.12-ARCH'
  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
/tmp/vmware-config0/vmnet-only/userif.c: In function `VNetUserIfMapUint32Ptr':
/tmp/vmware-config0/vmnet-only/userif.c:152: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
/tmp/vmware-config0/vmnet-only/userif.c:153: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105)
  CC [M]  /tmp/vmware-config0/vmnet-only/netif.o
  CC [M]  /tmp/vmware-config0/vmnet-only/bridge.o
/tmp/vmware-config0/vmnet-only/bridge.c: In function `VNetBridgeUp':
/tmp/vmware-config0/vmnet-only/bridge.c:716: warning: passing arg 3 of `sk_alloc' makes pointer from integer without a cast
/tmp/vmware-config0/vmnet-only/bridge.c:716: warning: passing arg 4 of `sk_alloc' makes integer from pointer without a cast
  CC [M]  /tmp/vmware-config0/vmnet-only/procfs.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST
Warning: could not open /tmp/vmware-config0/vmnet-only/includeCheck.h: Invalid argument
  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-2.6.12-ARCH'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.

This program previously created the file /etc/vmware/not_configured, and was 
about to remove it.  Somebody else apparently did it already.

Starting VMware services:
   Virtual machine monitor                                             done
   Virtual ethernet                                                    done
   Bridged networking on /dev/vmnet0                                  failed

The configuration of VMware Workstation 5.0.0 build-13124 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


zoals je ziet hele gekke dingen, files in /dev die hij wil verwijderen maar die al niet meer bestonden...

  • backupdevice
  • Registratie: November 2000
  • Laatst online: 10-02 11:32

backupdevice

No Risk , Full Push

Het probleem zit in de vmnet. Dat is een virtual netwerkkaart. DIe loopt te bokken. Ik begrijp niet waarom er 9 vmnets gemaakt zijn :?

Heb je misschien meerdere physieke netwerkadapters in je machine zitten?

Je hebt in ieder geval Workstation niet goed verwijdert. Kijk anders even het Vmware forum .

"This is it....This is it " | Gianpiero Lambiase | Lap 54 12-12-2021


  • AlterEgo
  • Registratie: Juli 2001
  • Niet online
Kernel 2.6.12: heb je vmware gepatched met de Vmware any update?
Anders wordt het niets.

Tevens heb ik ruzie gehad met vmware en 2.6.12

Verwijderd

Topicstarter
Bedankt voor de patch ! Er waren wel wat compileer warnings, maar het werkt nu iig!

Waar zou zoiets nu aan liggen ? ik heb niet zoveel verstand van kernelontwikkeling, maar zou er iets fundamenteels veranderd zijn in de manier waarop de kernel met devfs omgaat ofzo ? (gezien het gebok met de vmnet modules) of is het een gaatje in vmware wat in de kernel gelapt is of andersom ? En zouden mensen met udev er geen last van hebben ?
Pagina: 1