2:51 p.m.
Not strictly a general FC2 problem, but I've been testing under VMware
with reasonably good success. The latest arjanv kernel-2.6.5-1.326
(with the reiserfs fix) generates the following error on boot:
*** VMware Workstation internal monitor error ***
NOT_IMPLEMENTED at 602 (7568)
Code:
00000602-00001d90-e3bfafe0-afff81e7-f1cba686-bfd69288-82c2a5cb-e0fb
Have filed it with VMware.
Phil
3:57 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 15 April 2004 19:51, Phil Schaffner wrote:
Not strictly a general FC2 problem, but I've been testing under
VMware
with reasonably good success. The latest arjanv kernel-2.6.5-1.326
(with the reiserfs fix) generates the following error on boot:
*** VMware Workstation internal monitor error ***
For Fedora as the host for vmware, with 322 I am unable to build the vmware
modules, even with the latest vmware-any-any from http://ftp.cvut.cz/vmware/
....
Building the vmmon module.
Building for VMware Workstation 4.5.x or VMware GSX Server 3.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.5-1.322/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/.
modules
make[1]: Entering directory `/lib/modules/2.6.5-1.322/build'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.h:19,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:41:
/tmp/vmware-config1/vmmon-only/include/compat_wait.h:60: error: conflicting
types for `poll_initwait'
include/linux/poll.h:44: error: previous declaration of `poll_initwait'
/tmp/vmware-config1/vmmon-only/linux/driver.c:141: warning: initialization
from incompatible pointer type
/tmp/vmware-config1/vmmon-only/linux/driver.c:145: warning: initialization
from incompatible pointer type
make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1
make[1]: *** [/tmp/vmware-config1/vmmon-only] Error 2
make[1]: Leaving directory `/lib/modules/2.6.5-1.322/build'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to build the vmmon module.
- -Andy
- --
Automatic actions for USB cameras, cardreaders, memory sticks, MP3 players
http://warmcat.com/usbautocam
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAfvdOjKeDCxMJCTIRAj33AJ9tBhSzK0VlANjqy9QyEtk2Z2Y1VwCdH7Xk
cMmQkXo+eL93XPZTfa/aR7A=
=N+1q
-----END PGP SIGNATURE-----
3:12 p.m.
On Thu, 2004-04-15 at 16:57, Andy Green wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 15 April 2004 19:51, Phil Schaffner wrote:
> Not strictly a general FC2 problem, but I've been testing under VMware
> with reasonably good success. The latest arjanv kernel-2.6.5-1.326
> (with the reiserfs fix) generates the following error on boot:
>
> *** VMware Workstation internal monitor error ***
For Fedora as the host for vmware, with 322 I am unable to build the vmware
modules, even with the latest vmware-any-any from http://ftp.cvut.cz/vmware/
May not have been clear - FC1 is the host, FC2T2 is the guest. Haven't
been able to get VMware to work under FC2 recent kernels either.
Phil
8:54 a.m.
I had a similar problem (posted to the list before) and was fixed by
installing the latest VMWare version (4.5). It is a free upgrade if you have
a 4.x license. I blelieve they also have a 30 day trial version.
My setup is:
Host: Windows 2003
VM: Workstation 4.5
FC: FC2T2
Ivan
ilemus(a)onfin.com
----- Original Message -----
From: "Phil Schaffner" <Philip.R.Schaffner(a)NASA.gov>
To: "For testers of Fedora Core development releases"
<fedora-test-list(a)redhat.com>
Sent: Thursday, April 15, 2004 4:12 PM
Subject: Re: VMware error with kernel-2.6.5-1.326
On Thu, 2004-04-15 at 16:57, Andy Green wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thursday 15 April 2004 19:51, Phil Schaffner wrote:
> > Not strictly a general FC2 problem, but I've been testing under VMware
> > with reasonably good success. The latest arjanv kernel-2.6.5-1.326
> > (with the reiserfs fix) generates the following error on boot:
> >
> > *** VMware Workstation internal monitor error ***
>
> For Fedora as the host for vmware, with 322 I am unable to build the
vmware
> modules, even with the latest vmware-any-any from
http://ftp.cvut.cz/vmware/
May not have been clear - FC1 is the host, FC2T2 is the guest. Haven't
been able to get VMware to work under FC2 recent kernels either.
Phil
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
11:58 p.m.
Kernel: 2.6.5-1.322
VMWare: 4.0.5 6030
patch: vmware-any-any-update59
The drivers compiled and worked ok for me after updating to
any-any-update59.
Encountered problem "Permission denied" error running vmware-config.pl.
setenforce 0, then
./runme.pl did the trick.
After any change in the enforcing mode, vmware doesn't work anymore and I
get
[root@Purgatory root]# service vmware start
VMware Workstation is installed, but it has not been (correctly) configured
for the running kernel. To (re-)configure it, invoke the
following command: /usr/bin/vmware-config.pl.
in enforcing Mode:
[root@Purgatory root]# vmware-config.pl
Apr 15 22:44:37 Purgatory kernel: audit(1082083477.160:0): avc: denied
{ read } for pid=3599 exe=/usr/bin/perl name=urandom dev=hda2 ino=596039
scontext=root:system_r:vmware_t
tcontext=system_u:object_r:urandom_device_t tclass=chr_file
Apr 15 22:44:37 Purgatory kernel: audit(1082083477.218:0): avc: denied
{ search } for pid=3599 exe=/usr/bin/perl name=bin dev=hda2 ino=1126081
scontext=root:system_r:vmware_t tcontext=system_u:object_r:bin_t tclass=dir
[root@Purgatory root]# service vmware start
Starting VMware services:
Virtual machine monitor [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [FAILED]
Host-only networking on /dev/vmnet1 (background) [ OK ]
Host-only networking on /dev/vmnet8 (background) [ OK ]
NAT networking on /dev/vmnet8 [FAILED]
Apr 15 23:36:21 Purgatory kernel: vmmon: module license 'unspecified'
taints kernel.
Apr 15 23:36:21 Purgatory kernel: parport0: PC-style at 0x3bc (0x7bc)
[PCSPP,TRISTATE]
Apr 15 23:36:21 Purgatory kernel: parport0: irq 7 detected
Apr 15 23:36:22 Purgatory kernel: vmnet: module license 'unspecified'
taints kernel.
Apr 15 23:36:22 Purgatory kernel: audit(1082086582.122:0): avc: denied
{ read write } for pid=4713 exe=/usr/bin/vmnet-bridge name=vmnet0
dev=hda2 ino=587584 scontext=root:system_r:vmware_t
tcontext=root:object_r:device_t tclass=chr_file
Apr 15 23:36:22 Purgatory kernel: audit(1082086582.286:0): avc: denied
{ read write } for pid=4735 exe=/usr/bin/vmnet-natd name=vmnet8 dev=hda2
ino=587740 scontext=root:system_r:vmware_t tcontext=root:object_r:device_t
tclass=chr_file
Apr 15 23:36:32 Purgatory kernel: audit(1082086592.141:0): avc: denied
{ read write } for pid=4992 exe=/usr/bin/vmnet-netifup name=vmnet1
dev=hda2 ino=587689 scontext=root:system_r:vmware_t
tcontext=root:object_r:device_t tclass=chr_fileApr 15 23:36:32 Purgatory
VMware[init]: /dev/vmnet1: Permission denied
Apr 15 23:36:32 Purgatory kernel: audit(1082086592.227:0): avc: denied
{ read write } for pid=4993 exe=/usr/bin/vmnet-netifup name=vmnet8
dev=hda2 ino=587740 scontext=root:system_r:vmware_t
tcontext=root:object_r:device_t tclass=chr_fileApr 15 23:36:32 Purgatory
VMware[init]: /dev/vmnet8: Permission denied
Apr 15 23:36:41 Purgatory kernel: audit(1082086601.098:0): avc: denied
{ execute } for pid=4996 path=/home/max4/.netscape/plugins/rpnp.so
dev=hda2 ino=2138106 scontext=user_u:user_r:user_t
tcontext=system_u:object_r:user_mozilla_rw_t tclass=file
With setenforce 0, running vmware-config.pl everything works again but i
get these avcs
(see next msg ... too long listing)
Hope these help
2:02 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 16 April 2004 04:58, Efthym wrote:
Kernel: 2.6.5-1.322
VMWare: 4.0.5 6030
patch: vmware-any-any-update59
The drivers compiled and worked ok for me after updating to
any-any-update59.
Encountered problem "Permission denied" error running vmware-config.pl.
setenforce 0, then
./runme.pl did the trick.
I really owe that Czech guy a beer ot two, but even v59 of his patch (at the
time of my last mail, v58 was the latest) is not working here on kernel .322
...
Building the vmmon module.
Building for VMware Workstation 4.5.x or VMware GSX Server 3.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmmon-only'
make -C /lib/modules/2.6.5-1.322/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/.
modules
make[1]: Entering directory `/lib/modules/2.6.5-1.322/build'
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config2/vmmon-only/linux/hostif.o
In file included from /tmp/vmware-config2/vmmon-only/linux/hostif.c:3332:
/tmp/vmware-config2/vmmon-only/linux/hostif_compat.h: In function
`HostIF_MarkPageDirty':
/tmp/vmware-config2/vmmon-only/linux/hostif_compat.h:193: error: too few
arguments to function `HostIFGetUserPage'
make[2]: *** [/tmp/vmware-config2/vmmon-only/linux/hostif.o] Error 1
make[1]: *** [/tmp/vmware-config2/vmmon-only] Error 2
make[1]: Leaving directory `/lib/modules/2.6.5-1.322/build'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config2/vmmon-only'
Unable to build the vmmon module.
- -Andy
- --
Automatic actions for USB cameras, cardreaders, memory sticks, MP3 players
http://warmcat.com/usbautocam
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAf4USjKeDCxMJCTIRAih9AJ4mI9ymdpMh2YhKgdVW6lvcTjbDFgCfV8aT
ulgj3fDDx9B4LIie2g6wAxw=
=C+mJ
-----END PGP SIGNATURE-----
4:46 a.m.
On Fri, 16 Apr 2004 07:02:38 +0000, Andy Green <fedora(a)warmcat.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 16 April 2004 04:58, Efthym wrote:
> Kernel: 2.6.5-1.322
> VMWare: 4.0.5 6030
> patch: vmware-any-any-update59
>
> The drivers compiled and worked ok for me after updating to
> any-any-update59.
> Encountered problem "Permission denied" error running vmware-config.pl.
> setenforce 0, then
> ./runme.pl did the trick.
I really owe that Czech guy a beer ot two, but even v59 of his patch (at
the
time of my last mail, v58 was the latest) is not working here on kernel
.322
Just upgraded to 4.5.1 Build 7568.
[root@Purgatory vmware-any-any-update59]# setenforce 0
[root@Purgatory vmware-any-any-update59]# ./runme.pl
Driver compiles and workes OK !
Did you check /var/log/messages for any errors ?
Make sure you are running runme.pl from the any-any update and not
vmware-config.pl. runme.pl replaces the sources for the vmmon and vmnet
modules, and then calls vmware-config.pl
8:02 a.m.
New subject: VMware error with kernel-2.6.5-1.326 ... selinux
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 16 April 2004 09:46, Efthym wrote:
Hi Efthym -
Make sure you are running runme.pl from the any-any update and not
vmware-config.pl. runme.pl replaces the sources for the vmmon and vmnet
modules, and then calls vmware-config.pl
[root@fastcat vmware-any-any-update59]# ll
total 1204
- -r--r--r-- 1 root root 322 Apr 16 11:54 cpuinfo
- -rwxr-xr-x 1 884 201 21866 Mar 31 2002 runme.pl
- -rwxr-xr-x 1 884 201 28141 Apr 20 2003 services2.sh
- -rwxr-xr-x 1 884 201 29175 Apr 20 2003 services.sh
- -rwxr-xr-x 1 root root 21271 Apr 10 19:19 update
- -rw-r--r-- 1 884 201 18769 Apr 10 19:19 update.c
- -rw-r--r-- 1 884 201 778240 Apr 15 20:18 vmmon.tar
- -rw-r--r-- 1 884 201 276480 Apr 15 20:18 vmnet.tar
[root@fastcat vmware-any-any-update59]# ./runme.pl
Updating /usr/bin/vmware ... Unknown version
Sorry, there is no binary patch available for your version of vmware.
VMware modules in "/usr/lib/vmware/modules/source" has been updated.
Before running VMware for the first time after update, you need to configure
it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the command for
you now? [yes]
Making sure VMware Workstation's services are stopped.
Stopping VMware services:
Virtual machine monitor [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Virtual ethernet [ OK ]
Trying to find a suitable vmmon module for your running kernel.
None of VMware Workstation's pre-built vmmon modules 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? [/lib/modules/2.6.5-1.322/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Building for VMware Workstation 4.5.x or VMware GSX Server 3.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config3/vmmon-only'
make -C /lib/modules/2.6.5-1.322/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/.
modules
make[1]: Entering directory `/lib/modules/2.6.5-1.322/build'
CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config3/vmmon-only/linux/hostif.o
In file included from /tmp/vmware-config3/vmmon-only/linux/hostif.c:3332:
/tmp/vmware-config3/vmmon-only/linux/hostif_compat.h: In function
`HostIF_MarkPageDirty':
/tmp/vmware-config3/vmmon-only/linux/hostif_compat.h:193: error: too few
arguments to function `HostIFGetUserPage'
make[2]: *** [/tmp/vmware-config3/vmmon-only/linux/hostif.o] Error 1
make[1]: *** [/tmp/vmware-config3/vmmon-only] Error 2
make[1]: Leaving directory `/lib/modules/2.6.5-1.322/build'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config3/vmmon-only'
Unable to build the vmmon module.
For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html"
and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".
Execution aborted.
[root@fastcat vmware-any-any-update59]# vmware -v
VMware Workstation 4.5.1 build-7568
Did you check /var/log/messages for any errors ?
GAH!!! Well spotted. This is the first time I really got bit by selinux,
then.
Apr 16 12:56:34 fastcat kernel: audit(1082120194.494:0): avc: denied
{ search } for pid=31038 exe=/usr/bin/perl dev=hdc2 ino=2
scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t tclass=dir
Apr 16 12:56:34 fastcat kernel: audit(1082120194.494:0): avc: denied
{ read } for pid=31038 exe=/usr/bin/perl name=libperl.so dev=hdc2
ino=3926355 scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t
tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.494:0): avc: denied
{ getattr } for pid=31038 exe=/usr/bin/perl
path=/usr/lib/perl5/5.8.3/i386-linux-thread-multi/CORE/libperl.so dev=hdc2
ino=3926355 scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t
tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.494:0): avc: denied
{ execute } for pid=31038
path=/usr/lib/perl5/5.8.3/i386-linux-thread-multi/CORE/libperl.so dev=hdc2
ino=3926355 scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t
tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.496:0): avc: denied
{ ioctl } for pid=31038 exe=/usr/bin/perl
path=/usr/lib/perl5/5.8.3/strict.pm dev=hdc2 ino=2698384
scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.601:0): avc: denied
{ getattr } for pid=31038 exe=/usr/bin/perl path=/etc/vmware/locations
dev=hdc2 ino=4449408 scontext=root:system_r:vmware_t
tcontext=root:object_r:file_t tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.601:0): avc: denied
{ read } for pid=31038 exe=/usr/bin/perl name=locations dev=hdc2 ino=4449408
scontext=root:system_r:vmware_t tcontext=root:object_r:file_t tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.601:0): avc: denied
{ ioctl } for pid=31038 exe=/usr/bin/perl path=/etc/vmware/locations
dev=hdc2 ino=4449408 scontext=root:system_r:vmware_t
tcontext=root:object_r:file_t tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.606:0): avc: denied
{ append } for pid=31038 exe=/usr/bin/perl name=locations dev=hdc2
ino=4449408 scontext=root:system_r:vmware_t tcontext=root:object_r:file_t
tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.634:0): avc: denied
{ execute_no_trans } for pid=31040 exe=/usr/bin/perl path=/bin/bash dev=hdc2
ino=441894 scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t
tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.719:0): avc: denied
{ search } for pid=31040 exe=/sbin/ifconfig name=net dev= ino=4198
scontext=root:system_r:vmware_t tcontext=system_u:object_r:sysctl_net_t
tclass=dir
Apr 16 12:56:34 fastcat kernel: audit(1082120194.725:0): avc: denied
{ execute } for pid=31041 exe=/bin/bash name=vmware dev=hdc2 ino=4235207
scontext=root:system_r:vmware_t tcontext=root:object_r:file_t tclass=file
Apr 16 12:56:34 fastcat kernel: audit(1082120194.725:0): avc: denied
{ execute_no_trans } for pid=31041 exe=/bin/bash
path=/etc/rc.d/init.d/vmware dev=hdc2 ino=4235207
scontext=root:system_r:vmware_t tcontext=root:object_r:file_t tclass=file
Apr 16 12:56:42 fastcat kernel: audit(1082120202.489:0): avc: denied
{ getattr } for pid=31364 exe=/usr/bin/gcc path=/usr dev=hdc2 ino=4022593
scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t tclass=dir
Apr 16 12:56:42 fastcat kernel: audit(1082120202.548:0): avc: denied
{ read } for pid=31038 exe=/usr/bin/perl name=asm dev=hdc2 ino=3959774
scontext=root:system_r:vmware_t tcontext=system_u:object_r:modules_object_t
tclass=lnk_file
Apr 16 12:56:44 fastcat kernel: audit(1082120204.370:0): avc: denied
{ write } for pid=31038 exe=/usr/bin/perl name=tmp dev=hdc2 ino=1896833
scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t tclass=dir
Apr 16 12:56:44 fastcat kernel: audit(1082120204.371:0): avc: denied
{ add_name } for pid=31038 exe=/usr/bin/perl name=vmware-config3
scontext=root:system_r:vmware_t tcontext=system_u:object_r:file_t tclass=dir
Apr 16 12:56:44 fastcat kernel: audit(1082120204.452:0): avc: denied
{ create } for pid=31415 exe=/bin/tar name=geninclude.c
scontext=root:system_r:vmware_t tcontext=root:object_r:file_t tclass=file
Apr 16 12:56:44 fastcat kernel: audit(1082120204.452:0): avc: denied
{ write } for pid=31415 exe=/bin/tar
path=/tmp/vmware-config3/vmmon-only/autoconf/geninclude.c dev=hdc2
ino=1962327 scontext=root:system_r:vmware_t tcontext=root:object_r:file_t
tclass=file
Apr 16 12:56:44 fastcat kernel: audit(1082120204.452:0): avc: denied
{ setattr } for pid=31415 exe=/bin/tar name=geninclude.c dev=hdc2
ino=1962327 scontext=root:system_r:vmware_t tcontext=root:object_r:file_t
tclass=file
Apr 16 12:56:51 fastcat kernel: audit(1082120211.594:0): avc: denied
{ unlink } for pid=31510 exe=/bin/rm name=.driver.o.d dev=hdc2 ino=1962411
scontext=root:system_r:vmware_t tcontext=root:object_r:file_t tclass=file
Apr 16 12:56:51 fastcat kernel: audit(1082120211.696:0): avc: denied
{ rename } for pid=31511 exe=/bin/mv name=.driver.o.tmp dev=hdc2 ino=1962412
scontext=root:system_r:vmware_t tcontext=root:object_r:file_t tclass=file
Apr 16 12:57:23 fastcat kernel: audit(1082120243.498:0): avc: denied
{ unix_read unix_write } for pid=27170 exe=/usr/X11R6/bin/Xorg key=0
scontext=system_u:system_r:kernel_t tcontext=root:sysadm_r:sysadm_t
tclass=shm
Apr 16 12:57:23 fastcat kernel: audit(1082120243.498:0): avc: denied { read
write } for pid=27170 exe=/usr/X11R6/bin/Xorg key=0
scontext=system_u:system_r:kernel_t tcontext=root:sysadm_r:sysadm_t
tclass=shm
Apr 16 12:57:23 fastcat kernel: audit(1082120243.498:0): avc: denied { use }
for pid=27170 path=/SYSV00000000 (deleted) dev= ino=28803072
scontext=system_u:system_r:kernel_t tcontext=root:sysadm_r:sysadm_t tclass=fd
Apr 16 12:57:23 fastcat kernel: audit(1082120243.498:0): avc: denied
{ getattr associate } for pid=27170 exe=/usr/X11R6/bin/Xorg key=0
scontext=system_u:system_r:kernel_t tcontext=root:sysadm_r:sysadm_t
tclass=shm
[root@Purgatory vmware-any-any-update59]# setenforce 0
I have pretty much no understanding of selinux yet, other than the general
idea of what it is trying to do (which potentially sounds great). Is
setenfore <- 0 going to cause troubles when I want to turn it back on, in
which case I should maybe wait for a better policy file? Or vmware not being
part of the distro, can we expect no policy support for it?
- -Andy
- --
Automatic actions for USB cameras, cardreaders, memory sticks, MP3 players
http://warmcat.com/usbautocam
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAf9l8jKeDCxMJCTIRAvKtAJ9UaHn9Q7dvSu8m0F6le77OfS5MzQCghdTx
dL9SLqkoh20B56Yeobh75VA=
=QW63
-----END PGP SIGNATURE-----
10:53 p.m.
Hello,
This is regarding this old post(I know IM SORRY!).
I have followed all the instructions given in all these correspondences
here, and am still having a problem installing vmware 4.05-6030.
I untared the vmware-any-any-update59 into the VMWARE dircetory in my
/home/sponger directory. Then I cd'ed into that update directory and
ran ./runme.pl and it asks me for the directory of my C header files,
and per the directions in one of the emails this is what I gave it:
/lib/modules/2.6.5-1.332/build/kernel/
and this is the msg it gives me:
"The kernel defined by this directory of header files does not have the same
address space size as your running kernel."
So then being a noob I tried all the other directories in /lib/modules
of the other kernels installed on my system, but then it complains thats
not the right kernel and wants the .332 version....but it gives me that
error.....
Any ideas?
TIA
Dave
Efthym wrote:
On Fri, 16 Apr 2004 07:02:38 +0000, Andy Green
<fedora(a)warmcat.com>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Friday 16 April 2004 04:58, Efthym wrote:
>
>> Kernel: 2.6.5-1.322
>> VMWare: 4.0.5 6030
>> patch: vmware-any-any-update59
>>
>> The drivers compiled and worked ok for me after updating to
>> any-any-update59.
>> Encountered problem "Permission denied" error running
vmware-config.pl.
>> setenforce 0, then
>> ./runme.pl did the trick.
>
>
> I really owe that Czech guy a beer ot two, but even v59 of his patch
> (at the
> time of my last mail, v58 was the latest) is not working here on
> kernel .322
>
Just upgraded to 4.5.1 Build 7568.
[root@Purgatory vmware-any-any-update59]# setenforce 0
[root@Purgatory vmware-any-any-update59]# ./runme.pl
Driver compiles and workes OK !
Did you check /var/log/messages for any errors ?
Make sure you are running runme.pl from the any-any update and not
vmware-config.pl. runme.pl replaces the sources for the vmmon and
vmnet modules, and then calls vmware-config.pl
1:56 p.m.
On Wed, 2004-05-05 at 20:53 -0700, Sponger wrote:
Hello,
This is regarding this old post(I know IM SORRY!).
I have followed all the instructions given in all these correspondences
here, and am still having a problem installing vmware 4.05-6030.
I untared the vmware-any-any-update59 into the VMWARE dircetory in my
/home/sponger directory. Then I cd'ed into that update directory and
ran ./runme.pl and it asks me for the directory of my C header files,
and per the directions in one of the emails this is what I gave it:
/lib/modules/2.6.5-1.332/build/kernel/
and this is the msg it gives me:
"The kernel defined by this directory of header files does not have the same
address space size as your running kernel."
So then being a noob I tried all the other directories in /lib/modules
of the other kernels installed on my system, but then it complains thats
not the right kernel and wants the .332 version....but it gives me that
error.....
Any ideas?
Late response to a late post - get the free upgrade to VMware 4.5.1-7568
and the vmware-any-any-update65 and try again. If you have properly
installed both the kernel and corresponding kernel-source RPMS, VMware
should find the correct headers itself and provide that as the default
selection. Some posts have indicated that kernel-source is not required
but I can't verify that.
Phil
8:49 a.m.
On Sat, 2004-05-08 at 14:56 -0400, Phil Schaffner wrote:
<snip>
Late response to a late post - get the free upgrade to VMware
4.5.1-7568
and the vmware-any-any-update65 and try again. If you have properly
installed both the kernel and corresponding kernel-source RPMS, VMware
With the 2.6 kernels you don't need the kernel-source .rpm to build
external modules.
should find the correct headers itself and provide that as the
default
selection. Some posts have indicated that kernel-source is not required
but I can't verify that.
Phil
Tono
10:10 a.m.
It took a little digging, but here's at least a temporary fix for
VMware module build problem. It involves one fix in the
vmware-any-any-update59 patch and one fix in the kernel
scripts/Makefile.modpost file.
---cut here---
bash-2.05b# cd /lib/modules/$(uname -r)/build/scripts
bash-2.05b# mv Makefile.modpost{,.orig}
bash-2.05b# cp -p Makefile.modpost{.orig,}
bash-2.05b# vi Makefile.modpost
Find these lines:
---
51: quiet_cmd_modpost = MODPOST
52: cmd_modpost = scripts/modpost \
53: $(if $(filter vmlinux,$^),-o,-i) $(objtree)/Module.symvers \
54: $(filter-out FORCE,$^)
---
delete line 53
bash-2.05b# cd
bash-2.05b# tar xzf vmware-any-any-update59.tar.gz
bash-2.05b# cd vmware-any-any-update59
bash-2.05b# tar xf vmmon.tar
bash-2.05b# cd vmmon-only/linux
bash-2.05b# vi hostif_compat.h
Find these lines:
192: #elif defined(CONFIG_X86_4G) ||
defined(CONFIG_X86_UACCESS_INDIRECT)
193: HostIFGetUserPage(addr, NULL);
194: return 0;
195: #else
Change line 193 to:
HostIFGetUserPage(addr, NULL, NULL);
bash-2.05b# cd ../..
bash-2.05b# tar cf vmmon.tar vmmon-only
bash-2.05b# ./runme.pl
Updating /usr/bin/vmware ... Unknown version
Sorry, there is no binary patch available for your version of vmware.
VMware modules in "/usr/lib/vmware/modules/source" has been updated.
Before running VMware for the first time after update, you need to
configure it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the
command for
you now? [yes]
Making sure VMware Workstation's services are stopped.
Stopping VMware services:
Virtual machine monitor [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Virtual ethernet [ OK ]
Trying to find a suitable vmmon module for your running kernel.
None of VMware Workstation's pre-built vmmon modules 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? [/lib/modules/2.6.5-1.322/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Building for VMware Workstation 4.5.x or VMware GSX Server 3.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.5-1.322/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/lib/modules/2.6.5-1.322/build'
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: "-Wdeclaration-after-statement" is valid for C/ObjC
but not
for C++
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/compilercheck.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 `/lib/modules/2.6.5-1.322/build'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.
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.5-1.322/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/lib/modules/2.6.5-1.322/build'
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
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 `/lib/modules/2.6.5-1.322/build'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as
they are?
(yes/no) [yes]
Do you want this program to automatically configure your system to allow
your
virtual machines to access the host's filesystem? (yes/no/help) [no]
Starting VMware services:
Virtual machine monitor [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
The configuration of VMware Workstation 4.5.1 build-7568 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
--
-Paul Iadonisi
Senior System Administrator
Red Hat Certified Engineer / Local Linux Lobbyist
Ever see a penguin fly? -- Try Linux.
GPL all the way: Sell services, don't lease secrets
7289
days inactive
7314
days old
12 comments
8 participants
participants (8)
-
Andy Green -
Anthony Joseph Seward -
Efthym -
Ivan Lemus -
Paul Iadonisi -
Phil Schaffner -
Phil Schaffner -
Sponger