Re: [Cooker] VMware under linux
On Saturday 07 April 2001 09:45, Jason Straight wrote: > Of course I didn't - where the heck did you find this? :) Fire up knode and point yourself at the vmware newsgroups at news.vmware.com. That's where the support is mostly taking place. > It always worked with 2.4.x without a problem. The change happened at the 2.4.2 release. Applying the patch by itself isn't enough, though, as I pointed out in my earlier post. > Well, I'll give this a try. > > On Friday 06 April 2001 23:29, you wrote: > > and have you applied the patch below ? It's for 2.4 kernels. > > > >Jan > > > > > On Fri, 6 Apr 2001, Jason Straight wrote: > > > > I freshened up my mirror this morning and updated, about 36 hours > > > > since my last update. My vmware is now broken under linux. :( > > > > > > > > I am not, nor have I been running the mdk kernels since way before > > > > beta-1, so I know it wasn't a kernel update that caused it. I'm > > > > wondering if it was egcs stuff that I know was updated recently. > > > > > > > > Anyone else having problems like this? -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED]
Re: [Cooker] VMware under linux
I don't even have that file to patch it actually. On Friday 06 April 2001 23:29, you wrote: > and have you applied the patch below ? It's for 2.4 kernels. > >Jan > > > On Fri, 6 Apr 2001, Jason Straight wrote: > > > I freshened up my mirror this morning and updated, about 36 hours since > > > my last update. My vmware is now broken under linux. :( > > > > > > I am not, nor have I been running the mdk kernels since way before > > > beta-1, so I know it wasn't a kernel update that caused it. I'm > > > wondering if it was egcs stuff that I know was updated recently. > > > > > > Anyone else having problems like this? -- Jason Straight
Re: [Cooker] VMware under linux
On Friday 06 April 2001 21:14, Jason Straight wrote: > make: Entering directory `/tmp/vmware-config3/vmnet-only' > make: Leaving directory `/tmp/vmware-config3/vmnet-only' > Unable to make a vmnet module that can be loaded in the running kernel: > insmod: a module named vmnet already exists > There is probably a light difference of kernel configuration between the > set of > C header files you specified and your running kernel. You may want to > rebuild a > kernel based on that directory, or specify another directory. rpm -e kernel-source rpm -e VMware rpm -i kernel-source* rpm -i VMware* apply patch that somebody else posted: cd to the directory that contains vmnet.tar tar xvf vmnet.tar cd vmnet-only apply patch cd .. mv vmnet.tar vmnet.tar.orig tar cf vmnet.tar vmnet-only/* vmware-config.pl I'm doing this from memory, but should get you going again. This has worked for me and for others (thanks again, Pete!). I don't know if it's overkill somewhere along the line, but it does work. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED]
Re: [Cooker] VMware under linux
Of course I didn't - where the heck did you find this? :) It always worked with 2.4.x without a problem. Well, I'll give this a try. On Friday 06 April 2001 23:29, you wrote: > and have you applied the patch below ? It's for 2.4 kernels. > >Jan > > > On Fri, 6 Apr 2001, Jason Straight wrote: > > > I freshened up my mirror this morning and updated, about 36 hours since > > > my last update. My vmware is now broken under linux. :( > > > > > > I am not, nor have I been running the mdk kernels since way before > > > beta-1, so I know it wasn't a kernel update that caused it. I'm > > > wondering if it was egcs stuff that I know was updated recently. > > > > > > Anyone else having problems like this? -- Jason Straight
Re: [Cooker] VMware under linux
and have you applied the patch below ? It's for 2.4 kernels. Jan > On Fri, 6 Apr 2001, Jason Straight wrote: > > > I freshened up my mirror this morning and updated, about 36 hours since my > > last update. My vmware is now broken under linux. :( > > > > I am not, nor have I been running the mdk kernels since way before beta-1, so > > I know it wasn't a kernel update that caused it. I'm wondering if it was egcs > > stuff that I know was updated recently. > > > > Anyone else having problems like this? -- -- Gospel of Jesus is the saving power of God for all who believe -- ## To some, nothing is impossible. ## http://Honza.Vicherek.com/ diff -urN vmnet-only.orig/vnetInt.h vmnet-only/vnetInt.h --- vmnet-only.orig/vnetInt.h Mon Feb 12 23:57:51 2001 +++ vmnet-only/vnetInt.hMon Feb 26 20:41:00 2001 @@ -16,9 +16,17 @@ # define KFREE_SKB(skb, type)kfree_skb(skb) # define DEV_KFREE_SKB(skb, type)dev_kfree_skb(skb) # define SKB_INCREF(skb) atomic_inc(&(skb)->users) -# define SKB_IS_CLONE_OF(clone, skb) ( \ - skb_datarefp(clone) == skb_datarefp(skb) \ - ) +# ifdef skb_shinfo + /* zerocopy kernel */ +#define SKB_IS_CLONE_OF(clone, skb) ( \ +skb_shinfo(clone) == skb_shinfo(skb) \ + ) +# else + /* pre-zerocopy */ +#define SKB_IS_CLONE_OF(clone, skb)( \ +skb_datarefp(clone) == skb_datarefp(skb) \ + ) +# endif # define SK_ALLOC(pri) sk_alloc(0, pri, 1) # define DEV_QUEUE_XMIT(skb, dev, pri) ( \ (skb)->dev = (dev), \
Re: [Cooker] VMware under linux
I did - when I fresh boot and it tries to start the services it says it's not compiled for my kernel. to run vmware-config. vmnet and vmmon seem to be compiled ok, but for whatever reason won't load. When I try to run vmware I get a segfault. On Friday 06 April 2001 22:24, you wrote: > On Fri, 6 Apr 2001, Jason Straight wrote: > > Yeah, as a matter of fact it fails building, what I mean is that I have > > been running the same kernel with vmware for quite a few weeks now. > > Something else just caused it to die unexpectedly. > > > > When compiling the vmware mods this happens: > > The "Extra tokens at end of #endif" aren't fatal to the build, just the > vmware people forgetting to comment out the text after #endif. > > > Unable to make a vmnet module that can be loaded in the running kernel: > > insmod: a module named vmnet already exists > > > > Your vmnet module is loaded when it tries to load the new one, try > '/etc/rc.d/init.d/vmware stop' then 'lsmod' to make sure vmnet is gone > before running vmware-config.pl. > > -dwild -- Jason Straight
Re: [Cooker] VMware under linux
On Fri, 6 Apr 2001, Jason Straight wrote: > Yeah, as a matter of fact it fails building, what I mean is that I have been > running the same kernel with vmware for quite a few weeks now. Something else > just caused it to die unexpectedly. > > When compiling the vmware mods this happens: > The "Extra tokens at end of #endif" aren't fatal to the build, just the vmware people forgetting to comment out the text after #endif. > Unable to make a vmnet module that can be loaded in the running kernel: > insmod: a module named vmnet already exists Your vmnet module is loaded when it tries to load the new one, try '/etc/rc.d/init.d/vmware stop' then 'lsmod' to make sure vmnet is gone before running vmware-config.pl. -dwild
Re: [Cooker] VMware under linux
Yeah, as a matter of fact it fails building, what I mean is that I have been running the same kernel with vmware for quite a few weeks now. Something else just caused it to die unexpectedly. When compiling the vmware mods this happens: make[2]: Entering directory `/tmp/vmware-config3/vmmon-only/driver-2.4.3' In file included from .././linux/driver.c:44: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../include/vm_asm.h:19, from .././linux/driver.c:48: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../linux/driver.h:12, from .././linux/driver.c:54: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from .././linux/hostif.c:46: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../include/modulecall.h:17, from .././linux/hostif.c:50: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from .././common/vmx86.c:29: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../common/vmx86.h:15, from .././common/vmx86.c:33: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../include/modulecall.h:17, from .././common/task.c:41: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../include/vm_asm.h:19, from ../include/taskswitch.h:20, from .././common/task.c:46: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../common/vmx86.h:15, from ../common/hostif.h:16, from .././common/memtrack.c:28: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from .././common/memtrack.c:29: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../common/vmx86.h:15, from .././common/phystrack.c:31: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive make[2]: Leaving directory `/tmp/vmware-config3/vmmon-only/driver-2.4.3' make[2]: Entering directory `/tmp/vmware-config3/vmmon-only/driver-2.4.3' In file included from .././linux/driver.c:44: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../include/vm_asm.h:19, from .././linux/driver.c:48: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../linux/driver.h:12, from .././linux/driver.c:54: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from .././linux/hostif.c:46: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../include/modulecall.h:17, from .././linux/hostif.c:50: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from .././common/vmx86.c:29: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../common/vmx86.h:15, from .././common/vmx86.c:33: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../include/modulecall.h:17, from .././common/task.c:41: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../include/vm_asm.h:19, from ../include/taskswitch.h:20, from .././common/task.c:46: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../common/vmx86.h:15, from ../common/hostif.h:16, from .././common/memtrack.c:28: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from .././common/memtrack.c:29: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive In file included from ../common/vmx86.h:15, from .././common/phystrack.c:31: ../include/x86.h:837:8: warning: extra tokens at end of #endif directive make[2]: Leaving directory `/tmp/vmware-config3/vmmon-only/driver-2.4.3' make: Entering directory `/tmp/vmware-config3/vmnet-only' make: Leaving directory `/tmp/vmware-config3/vmnet-only' Unable to make a vmnet module that can be loaded in the running kernel: insmod: a module named vmnet already exists There is probably a light difference of kernel configuration between the set of C header files you specified and your running kernel. You may want to rebuild a kernel based on that directory, or specify another directory. On Friday 06 April 2001 21:55, you wrote: > Forgive my stupidity, but did u run vmware-config.pl after upgrading > kernel? > > On Fri, 6 Apr 2001, Jason Straight wrote: > > I freshened up my mirror this m
Re: [Cooker] VMware under linux
Forgive my stupidity, but did u run vmware-config.pl after upgrading kernel? On Fri, 6 Apr 2001, Jason Straight wrote: > I freshened up my mirror this morning and updated, about 36 hours since my > last update. My vmware is now broken under linux. :( > > I am not, nor have I been running the mdk kernels since way before beta-1, so > I know it wasn't a kernel update that caused it. I'm wondering if it was egcs > stuff that I know was updated recently. > > Anyone else having problems like this? > > >
