after upgrading from 2.4.7-pre6-xfs to 2.4.7-pre8-xfs I found VMWare can't compile it's modules anymore. Any hint? Making sure VMware's services are stopped. Stopping VMware services: Virtual machin
That URL is probably a good start; contacting VMware or checking their news server would also be advisable. VMware has been troublesome for me in the past, and isn't really suitable to use in an envi
after upgrading from 2.4.7-pre6-xfs to 2.4.7-pre8-xfs I found VMWare can't compile it's modules anymore. Any hint? I rather suspect normal kernel breakage that can be expected with things like vmware
There's a suggestion in vmware.for-linux.configuration, but it doesn't help: Path: news.vmware.com!not-for-mail Message-ID: <3B570E9C.E92BFE8A@xxxxxxxxxx> From: Petr Vandrovec <vandrove@xxxxxxxxxx>
Petr Vandrovec seems to know his stuff. ;-) I saw a message (think it was on /. of all places) in conjunction with the official 2.4.7 release, that it VMware breaks. Wait for an update from VMware, I
Ok, this must have happened around 2.4.7pre6 or so. The earlier one that I'm running (2.4.6pre3 from cvs.20010708) is fine. Seems as though a structure changed. I've looked at the patch and it looks
after upgrading from 2.4.7-pre6-xfs to 2.4.7-pre8-xfs I found VMWare can't compile it's modules anymore. Any hint? Making sure VMware's services are stopped. Stopping VMware services: Virtual machin
That URL is probably a good start; contacting VMware or checking their news server would also be advisable. VMware has been troublesome for me in the past, and isn't really suitable to use in an envi
after upgrading from 2.4.7-pre6-xfs to 2.4.7-pre8-xfs I found VMWare can't compile it's modules anymore. Any hint? I rather suspect normal kernel breakage that can be expected with things like vmware
There's a suggestion in vmware.for-linux.configuration, but it doesn't help: Path: news.vmware.com!not-for-mail Message-ID: <3B570E9C.E92BFE8A@xxxxxxxxxx> From: Petr Vandrovec <vandrove@xxxxxxxxxx>
Petr Vandrovec seems to know his stuff. ;-) I saw a message (think it was on /. of all places) in conjunction with the official 2.4.7 release, that it VMware breaks. Wait for an update from VMware, I
Ok, this must have happened around 2.4.7pre6 or so. The earlier one that I'm running (2.4.6pre3 from cvs.20010708) is fine. Seems as though a structure changed. I've looked at the patch and it looks