[opensuse] VMware Player 2 & Kernel Modules Building Failure
Hi ! I have SuSE 10.2 and: kernel-default-2.6.22.2-ccj52 VMware-player-2.0.0-45731.i386 + kernel sources and kernel syms 2.6.22.2-ccj52 installed. For unknown reason compilation of vmware kernel modules fails: Path to kernel sources requied to compile vmware modules seems to be correct: "/usr/src/linux-2.6.22.2-ccj52-obj/i386/default/include" Anyone have any idea what went wrong? ---------------------- make[1]: Entering directory `/usr/src/linux-2.6.22.2-ccj52-obj/i386/default' make -C ../../../linux-2.6.22.2-ccj52 O=../linux-2.6.22.2-ccj52-obj/i386/default modules CC [M] /tmp/vmware-config4/vmnet-only/driver.o CC [M] /tmp/vmware-config4/vmnet-only/hub.o CC [M] /tmp/vmware-config4/vmnet-only/userif.o /tmp/vmware-config4/vmnet-only/userif.c: In function ‘VNetCopyDatagramToUser’: /tmp/vmware-config4/vmnet-only/userif.c:630: error: ‘const struct sk_buff’ has no member named ‘h’ /tmp/vmware-config4/vmnet-only/userif.c:630: error: ‘const struct sk_buff’ has no member named ‘nh’ /tmp/vmware-config4/vmnet-only/userif.c:636: error: ‘const struct sk_buff’ has no member named ‘h’ make[4]: *** [/tmp/vmware-config4/vmnet-only/userif.o] Error 1 make[3]: *** [_module_/tmp/vmware-config4/vmnet-only] Error 2 make[2]: *** [modules] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.22.2-ccj52-obj/i386/default' make: *** [vmnet.ko] Error 2 make: Leaving directory `/tmp/vmware-config4/vmnet-only' Unable to build the vmnet module. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 22 August 2007, Andrei Verovski (aka MacGuru) wrote:
Hi !
I have SuSE 10.2 and:
kernel-default-2.6.22.2-ccj52 VMware-player-2.0.0-45731.i386
+ kernel sources and kernel syms 2.6.22.2-ccj52 installed.
For unknown reason compilation of vmware kernel modules fails:
Path to kernel sources requied to compile vmware modules seems to be correct: "/usr/src/linux-2.6.22.2-ccj52-obj/i386/default/include"
Anyone have any idea what went wrong?
----------------------
make[1]: Entering directory `/usr/src/linux-2.6.22.2-ccj52-obj/i386/default' make -C ../../../linux-2.6.22.2-ccj52 O=../linux-2.6.22.2-ccj52-obj/i386/default modules CC [M] /tmp/vmware-config4/vmnet-only/driver.o CC [M] /tmp/vmware-config4/vmnet-only/hub.o CC [M] /tmp/vmware-config4/vmnet-only/userif.o /tmp/vmware-config4/vmnet-only/userif.c: In function â VNetCopyDatagramToUserâ: /tmp/vmware-config4/vmnet-only/userif.c:630: error: âconst struct sk_buffâ has no member named âhâ /tmp/vmware-config4/vmnet-only/userif.c:630: error: âconst struct sk_buffâ has no member named ânhâ /tmp/vmware-config4/vmnet-only/userif.c:636: error: âconst struct sk_buffâ has no member named âhâ make[4]: *** [/tmp/vmware-config4/vmnet-only/userif.o] Error 1 make[3]: *** [_module_/tmp/vmware-config4/vmnet-only] Error 2 make[2]: *** [modules] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.22.2-ccj52-obj/i386/default' make: *** [vmnet.ko] Error 2 make: Leaving directory `/tmp/vmware-config4/vmnet-only' Unable to build the vmnet module.
Compilation of the VMware module failed because of changes in the Linux kernel, i.e. your kernel is to new and you should fallback to the latest 2.6.18 kernel. Please, check the VMware forum for a discussion of these compilation problems. IIRC, the forum also contains some links to patches. Regards, Erwin Lam -- Erwin Lam (erwin.lam@gmx.net) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Erwin Lam wrote:
On Wednesday 22 August 2007, Andrei Verovski (aka MacGuru) wrote:
Hi !
I have SuSE 10.2 and:
kernel-default-2.6.22.2-ccj52 VMware-player-2.0.0-45731.i386
+ kernel sources and kernel syms 2.6.22.2-ccj52 installed.
For unknown reason compilation of vmware kernel modules fails:
<snip>
Unable to build the vmnet module.
Compilation of the VMware module failed because of changes in the Linux kernel, i.e. your kernel is to new and you should fallback to the latest 2.6.18 kernel.
Please, check the VMware forum for a discussion of these compilation problems. IIRC, the forum also contains some links to patches.
Regressing to 2.6.18 is not a viable option as 2.6.22 solves some issues with new motherboard hardware. The right solution is for VMware to update their product or lose the ability to have SUSE customers in the future. In the past, they have been responsive and I suspect they will be so in this case also. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 22 August 2007, Richard Creighton wrote:
Erwin Lam wrote:
On Wednesday 22 August 2007, Andrei Verovski (aka MacGuru) wrote:
Hi !
I have SuSE 10.2 and:
kernel-default-2.6.22.2-ccj52 VMware-player-2.0.0-45731.i386
+ kernel sources and kernel syms 2.6.22.2-ccj52 installed.
For unknown reason compilation of vmware kernel modules fails:
<snip>
Unable to build the vmnet module.
Compilation of the VMware module failed because of changes in the
Linux
kernel, i.e. your kernel is to new and you should fallback to the latest 2.6.18 kernel.
Please, check the VMware forum for a discussion of these compilation problems. IIRC, the forum also contains some links to patches.
Regressing to 2.6.18 is not a viable option as 2.6.22 solves some issues with new motherboard hardware.
The OP did not say he needed a bleeding edge kernel because of new hardware. He also did not say that a fallback of the kernel was not an option.
The right solution is for VMware to update their product or lose the ability to have SUSE customers in the future. In the past, they have been responsive and I suspect they will be so in this case also.
I agree, however, don't hold your breath:-) -- Erwin Lam (erwin.lam@gmx.net) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Erwin Lam wrote:
On Wednesday 22 August 2007, Richard Creighton wrote:
Erwin Lam wrote:
On Wednesday 22 August 2007, Andrei Verovski (aka MacGuru) wrote:
Hi !
I have SuSE 10.2 and:
kernel-default-2.6.22.2-ccj52 VMware-player-2.0.0-45731.i386
+ kernel sources and kernel syms 2.6.22.2-ccj52 installed.
For unknown reason compilation of vmware kernel modules fails:
<snip>
Unable to build the vmnet module.
Compilation of the VMware module failed because of changes in the
Linux
kernel, i.e. your kernel is to new and you should fallback to the latest 2.6.18 kernel.
Please, check the VMware forum for a discussion of these compilation problems. IIRC, the forum also contains some links to patches.
Regressing to 2.6.18 is not a viable option as 2.6.22 solves some
issues
with new motherboard hardware.
The OP did not say he needed a bleeding edge kernel because of new hardware. He also did not say that a fallback of the kernel was not an option.
The right solution is for VMware to update their product or lose the ability to have SUSE customers in the future. In the past, they have been responsive and I suspect they will be so in this case also.
I agree, however, don't hold your breath:-)
Let me clarify my previous post...I didn't say the poster I quoted had to have a bleeding edge kernel, I'm saying *I* need to have a bleeding edge kernel and right now the only way I can run 10.3 and VMWare is under 10.2 in a virtual machine running 10.3....it should be the other way around :( I have a new ASUS motherboard with 2.45 TB of raid5 hardware disk drives and running an AMD 5000+ Dual cpu and the new kernel solves several problems so I don't really want to go backward. I want VMWare to move forward. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Richard C Creighton a écrit :
Erwin Lam wrote:
On Wednesday 22 August 2007, Richard Creighton wrote:
Erwin Lam wrote:
On Wednesday 22 August 2007, Andrei Verovski (aka MacGuru) wrote:
Hi !
I have SuSE 10.2 and:
kernel-default-2.6.22.2-ccj52 VMware-player-2.0.0-45731.i386
+ kernel sources and kernel syms 2.6.22.2-ccj52 installed.
For unknown reason compilation of vmware kernel modules fails:
<snip>
Unable to build the vmnet module.
Compilation of the VMware module failed because of changes in the
Linux
kernel, i.e. your kernel is to new and you should fallback to the latest 2.6.18 kernel.
Please, check the VMware forum for a discussion of these compilation problems. IIRC, the forum also contains some links to patches.
Regressing to 2.6.18 is not a viable option as 2.6.22 solves some
issues
with new motherboard hardware.
The OP did not say he needed a bleeding edge kernel because of new hardware. He also did not say that a fallback of the kernel was not an option.
The right solution is for VMware to update their product or lose the ability to have SUSE customers in the future. In the past, they have been responsive and I suspect they will
be so in this case also.
I agree, however, don't hold your breath:-)
Let me clarify my previous post...I didn't say the poster I quoted had to have a bleeding edge kernel, I'm saying *I* need to have a bleeding edge kernel and right now the only way I can run 10.3 and VMWare is under 10.2 in a virtual machine running 10.3....it should be the other way around :( I have a new ASUS motherboard with 2.45 TB of raid5 hardware disk drives and running an AMD 5000+ Dual cpu and the new kernel solves several problems so I don't really want to go backward. I want VMWare to move forward.
Did you try : http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update113.tar.gz when I've problems with vmware, the last update always solve it. Michel. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Catimimi wrote:<snip>
Let me clarify my previous post...I didn't say the poster I quoted had to have a bleeding edge kernel, I'm saying *I* need to have a bleeding edge kernel and right now the only way I can run 10.3 and VMWare is under 10.2 in a virtual machine running 10.3....it should be the other way around :( I have a new ASUS motherboard with 2.45 TB of raid5 hardware disk drives and running an AMD 5000+ Dual cpu and the new kernel solves several problems so I don't really want to go backward. I want VMWare to move forward.
Did you try :
http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update113.tar.gz
when I've problems with vmware, the last update always solve it.
Michel. Thanks for the pointer...at the risk of sounding utterly stupid: This appears to be a patch; At what point in the installation of VMWare is it run? Before running the VMWare RPM, Before the VMWare config.pl? Does it have to be run from a particular location? I didn't see a 'readme' in the tarball. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Richard Creighton a écrit :
Catimimi wrote:<snip>
Let me clarify my previous post...I didn't say the poster I quoted had to have a bleeding edge kernel, I'm saying *I* need to have a bleeding edge kernel and right now the only way I can run 10.3 and VMWare is under 10.2 in a virtual machine running 10.3....it should be the other way around :( I have a new ASUS motherboard with 2.45 TB of raid5 hardware disk drives and running an AMD 5000+ Dual cpu and the new kernel solves several problems so I don't really want to go backward. I want VMWare to move forward.
Did you try :
http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update113.tar.gz
when I've problems with vmware, the last update always solve it.
Michel.
Thanks for the pointer...at the risk of sounding utterly stupid: This appears to be a patch; At what point in the installation of VMWare is it run? Before running the VMWare RPM, Before the VMWare config.pl? Does it have to be run from a particular location? I didn't see a 'readme' in the tarball.
Hi, As far as I remember, there is in the patch a script called runme.pl, make it executable and run it before running vmware-config.pl Michel. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Andrei Verovski (aka MacGuru) -
Catimimi -
Erwin Lam -
Richard C Creighton -
Richard Creighton