This is the error I am getting...
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config3/vmnet-only'
make -C /lib/modules/2.6.22.1/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.22.1'
CC /tmp/vmware-config3/vmnet-only/driver.o
CC /tmp/vmware-config3/vmnet-only/hub.o
CC /tmp/vmware-config3/vmnet-only/userif.o
/tmp/vmware-config3/vmnet-only/userif.c: In function VNetCopyDatagramToUser:
/tmp/vmware-config3/vmnet-only/userif.c:630: error: const struct sk_buff has no member named h
/tmp/vmware-config3/vmnet-only/userif.c:630: error: const struct sk_buff has no member named nh
/tmp/vmware-config3/vmnet-only/userif.c:636: error: const struct sk_buff has no member named h
make[1]: *** \[_module_/tmp/vmware-config3/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.22.1'
make: *** \[vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config3/vmnet-only'
Unable to build the vmnet module.
I downloaded your patch and that enabled my vmware build to succeed and then run on Fedora 7 as of this date.
I went ahead configured my first virtual machine using the prebuilt Red Hat Enterprise Linux 5 guest template. Then I installed a CentOS 5 guest in that virtual machine. Bridged mode networking seems to work just fine, I fully updated CentOS 5 to current patch levels.
Thanks very much for taking the time to post this patch!
Message was edited by:
BobCochran
Yet another patch.
Full migration to new "struct sk_buff", some likely/unlikely, IMHO a little speedup 😕
PATCH: http://linux.nextmail.ru/vmnet-only-2.6.22.sk_buff.patch.bz2
any-any-update112 is out, so all your custom patches are unnecessary now
What is the URL that I can download any-any-update112?
Hi, i'm quite a newbie please help me use the patch on fc7
bye
What is the URL that I can download any-any-update112?
I have just installed any-any-update112
and running vmplayer from the console this is the output:
"/usr/lib/vmware/bin/vmplayer: symbol lookup error: /usr/lib/libglibmm-2.4.so.1: undefined symbol: g_regex_error_quark"
I'll try to return the favor. I just ran this on my FC7 system. Worked great.
run tar xvfz on the any-any-update... file. cd to the new directory. As root or sudo, run the runme.pl file. Answer the questions, the script compiles for you, done.
Thanks,
Ken
any-any-update112 is out, so all your custom patches are unnecessary now
view +1161 bridge.c
ipHdrLen = compat_skb_ip_header(skb)->ihl << 2;
tcpHdrLen = compat_skb_tcp_header(skb)->doff << 2
Heh \!!! RTFM - http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.22
\[IP]: Introduce ip_hdrlen()
For the common sequence "skb->nh.iph->ihl * 4", removing a good number of open
coded skb->nh.iph uses, now to go after the rest...
Just out of curiosity, here are the idioms found to get the same result:
skb->nh.iph->ihl << 2
skb->nh.iph->ihl<<2
skb->nh.iph->ihl * 4
skb->nh.iph->ihl*4
(skb->nh.iph)->ihl * sizeof(u32)
I'm afraid I had no luck with any-any-update112. It didn't seem to recognize my Fedora 7 setup at all.
For example, I've accepted all the default directory locations when using vmware-install.pl, but any-any's runme.pl was wired to look for /etc/vmware[/b] rather than vmware-install.pl's default /etc/vmware-tools[/b].
When I edited runme.pl to point to /etc/vmware-tools I then got errors complaining it couldn't find the directories for several of the modules.
I gave up on getting vmware 6.0's tools to build with Fedora 7's updated kernel 2.6.22.1-27.fc7 and reverted to booting from my prior 2.6.21-1.3228.fc7 kernel. VMware-tools builds and runs great with the older kernel.
In some of the postings above and in other threads, there has been push-back by VMware employees that Fedora Core is not a supported distribution. Paying customers (like myself) are naturally unhappy about this. Can someone from VMware explain (or post a link to) the rationale for not supporting a widely-used distribution like Fedora Core?
I'm afraid I had no luck with any-any-update112. It didn't seem to recognize my Fedora 7 setup at all.
This is only for the host and not designed to be used in a Linux guest OS of a VM.
It's for allowing you to install VMware on newer kernels.
>Can someone from VMware explain (or post a link to) the rationale for not supporting a widely-used distribution like Fedora Core?
Refer to earlier posts. Even Red Hat does NOT support FC! FC is meant as a bleeding-edge feature-testbed, to iron out bugs in new features/functions before they implement them into their RHEL Enterprise product. It is meant as a testing platform. It is NOT meant to be run as a production environment / primary host OS!!
ipHdrLen = compat_skb_ip_header(skb)->ihl << 2;
tcpHdrLen = compat_skb_tcp_header(skb)->doff << 2
Heh \!!! RTFM -
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.22
Thanks. I see tcp_hdrlen as well... Hm, maybe, sometime...
any-any-update112 works perfectly for me. I had severe problems running
WS6 on FC7 with Dual-Core Athlon 64-Bit before (kernel freeze).
Now everything seems to work perfectly.
mlt
Thanks for the information posted here. I was able to get VMware server 1.0.2 to run on Kubuntu 7.10 (Gutsy Gibbon) with 2.6.22-7 kernel using the vmware-any-any-update113 patch.
Steve
what about compiling the guest modules?
compiling modules on guest with 2.6.22 and vmware-tools-6.0.0. fails naturally ...
Thanks to KevinG for pointing out that any-any-update is for the host. I was trying to use it for a guest Fedora running under XP.
Since there was no solution that worked for me, I reverted to a version of the Fedora 7 kernel ( 2.6.21-1.3228) for which vmware-tools would build successfully. This gave me a working system for the last two months.
However today I upgraded to VMware Workstation 6.0.1 and also accepted Fedora's kernel updates, bringing the current kernel to 2.6.22.-91. I was hoping that 6.0.1's updated vmware-tools might work, or at least build, with the latest Fedora 7 kernel, but the vmhgfs module gets compile errors. So I have again reverted to kernel 2.6.21-1.3228 and successfully built the 6.0.1 vmware-tools against it.
I know Fedora is not officially supported, so the flamers out there can save themselves the effort of scolding me yet again. I am simply looking for anyone who might have patched vmware-tools 6.0.1 build-55017 to work with Fedora 7 kernel 2.6.22.-9.
Thanks,
-Steve