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
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:
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...
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...