I tried to build the vmware modules for kernel 2.6.4 and got this oops
when loading vmmon.o:
vmmon: no version magic, tainting kernel.
vmmon: module license 'unspecified' taints kernel.
Unable to handle kernel NULL pointer dereference at virtual address 0000006e
printing eip:
c020160f
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c020160f>] Tainted: PF
EFLAGS: 00010206
EIP is at vsnprintf+0x43/0x4b9
eax: c6f11c53 ebx: c6f11c00 ecx: 0000006e edx: 0000006e
esi: c6f11c54 edi: c6f11c0c ebp: c6f11c67 esp: d2b61ee8
ds: 007b es: 007b ss: 0068
Process insmod (pid: 23426, threadinfo=d2b60000 task=d0f52720)
Stack: e89fe000 c0101e8c 00000202 c01468d5 00000202 c0338394 00000286 d2b61f38
00000014 c6f11c54 0000006e c6f11c00 fffffff4 c6f11c0c c162d180 c023c3e9
d2b61f54 00000000 6f6d6d76 e8a2dd90 6fed6d76 c036ae08 c022fb77 c162d180
Call Trace:
[<c01468d5>] unmap_vm_area+0x27/0x67
[<c023c3e9>] class_simple_device_add+0xa9/0xff
[<c022fb77>] misc_register+0xb2/0x186
[<e8a1a1d0>] init_module+0x144/0x1e8 [vmmon]
[<c013126e>] sys_init_module+0x105/0x211
[<c0108ffd>] sysenter_past_esp+0x52/0x71
Code: 80 3a 00 74 25 0f b6 02 3c 25 74 41 39 ee 77 06 88 06 8b 54
<4>vmmon: no version magic, tainting kernel.
Suggestions welcome.
--
M?ns Rullg?rd
[email protected]
On Wednesday 17 March 2004 00:39, M?ns Rullg?rd wrote:
Hi Mans,
> I tried to build the vmware modules for kernel 2.6.4 and got this oops
> when loading vmmon.o:
> vmmon: no version magic, tainting kernel.
> vmmon: module license 'unspecified' taints kernel.
> Unable to handle kernel NULL pointer dereference at virtual address
> Suggestions welcome.
what vmware version do you use? Please make sure you've updated to latest
any-any update from (1.)
1.) ftp://platan.vc.cvut.cz/pub/vmware
ciao, Marc
Marc-Christian Petersen <[email protected]> writes:
> On Wednesday 17 March 2004 00:39, M?ns Rullg?rd wrote:
>
> Hi Mans,
>
>> I tried to build the vmware modules for kernel 2.6.4 and got this oops
>> when loading vmmon.o:
>> vmmon: no version magic, tainting kernel.
>> vmmon: module license 'unspecified' taints kernel.
>> Unable to handle kernel NULL pointer dereference at virtual address
>> Suggestions welcome.
>
> what vmware version do you use? Please make sure you've updated to latest
> any-any update from (1.)
I installed vmware 4.5.1, and at first I got an oops from insmod
again. Then I build the modules manually instead of letting the
configure script do it, and now it's up and running.
--
M?ns Rullg?rd
[email protected]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> On Wednesday 17 March 2004 00:39, M?ns Rullg?rd wrote:
>
> Hi Mans,
>
> > I tried to build the vmware modules for kernel 2.6.4 and got this oops
> > when loading vmmon.o:
> > vmmon: no version magic, tainting kernel.
> > vmmon: module license 'unspecified' taints kernel.
> > Unable to handle kernel NULL pointer dereference at virtual address
> > Suggestions welcome.
>
> what vmware version do you use? Please make sure you've updated to latest
> any-any update from (1.)
What does this update actually do?
I'm currently running VMWare 4.5.1 on mandrake 10.0 Community with their 2.6.3
kernel and VMWare is working just fine. Any compilation of modules was all
performed by vmware-install.pl
Cheers.
Mark
- --
Mark Watts
Senior Systems Engineer
QinetiQ TIM
St Andrews Road, Malvern
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAWHqfBn4EFUVUIO0RAoxfAKDcilnCVu4OFBD8QAmx9BVmIJfgZACeMkGe
CBjhrmLC5D7l+Vch2SvM4As=
=X4Zb
-----END PGP SIGNATURE-----
On 17 Mar 04 at 16:19, Mark Watts wrote:
> > > Suggestions welcome.
> >
> > what vmware version do you use? Please make sure you've updated to latest
> > any-any update from (1.)
>
> What does this update actually do?
I would suggest reading changelog from any-any update. Entries after
update50 (and second half of update50) are ones which are NOT in modules
which come with WS4.5.1. If modules coming with WS4.5.1 work for you,
fine. If they do not work, you know where to find update...
Update does not handle GSX 3.0 yet, so if you are using GSX 3.0, you
should stick with officially supported host kernels (if you bought
GSX, you probably want to have support, and so you should use only
supported hosts anyway).
Petr Vandrovec
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> On 17 Mar 04 at 16:19, Mark Watts wrote:
> > > > Suggestions welcome.
> > >
> > > what vmware version do you use? Please make sure you've updated to
> > > latest any-any update from (1.)
> >
> > What does this update actually do?
>
> I would suggest reading changelog from any-any update. Entries after
> update50 (and second half of update50) are ones which are NOT in modules
> which come with WS4.5.1. If modules coming with WS4.5.1 work for you,
> fine. If they do not work, you know where to find update...
Ah great - we're using WS4.5.1 and I see that the any-any updates from -50
probably don't apply to Mandrake 10.0
>
> Update does not handle GSX 3.0 yet, so if you are using GSX 3.0, you
> should stick with officially supported host kernels (if you bought
> GSX, you probably want to have support, and so you should use only
> supported hosts anyway).
We're actually toying with getting a copy of GSX - does it support 2.6 at all?
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ TIM
St Andrews Road, Malvern
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAWIBKBn4EFUVUIO0RAukKAKCE1LW6WHqb2iKOVB8loU+d3GblCACgvoXZ
0VgSZZnbZLo3fA4y956QIcY=
=V4Vq
-----END PGP SIGNATURE-----
On 17 Mar 04 at 16:43, Mark Watts wrote:
> >
> > Update does not handle GSX 3.0 yet, so if you are using GSX 3.0, you
> > should stick with officially supported host kernels (if you bought
> > GSX, you probably want to have support, and so you should use only
> > supported hosts anyway).
>
> We're actually toying with getting a copy of GSX - does it support 2.6 at all?
Same way WS4.5.1. It should work, but it was not specifically tested,
and I did not add gsx3 emulation layer into vmware-any-any-updates yet.
If you'll use kernel 2.6.x in the guest, you'll have some minor troubles
with building hgfs & vmxnet modules for the guest, but if you have
some exprience with kernel code it is trivial to fix them - two oneliners
in hgfs & two twoliners in vmxnet.
Petr Vandrovec