On Wed, 2010-01-06 at 15:40 -0600, Dan Burkland wrote: > Here is a link to the blog post that helped me get the modules to compile properly on 2.6.32.2: http://sadevil.org/blog/2009/12/31/vmware-player-3-vs-linux-2-6-32/ > > Dan Burkland > > > > > -----Original Message----- > > From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list- > > bounces@xxxxxxxxxx] On Behalf Of John Austin > > Sent: Wednesday, January 06, 2010 2:02 PM > > To: Community assistance, encouragement, and advice for using Fedora. > > Subject: RE: vmware workstation 7 on 64-bit fedora 12? > > > > On Wed, 2010-01-06 at 12:39 -0600, Dan Burkland wrote: > > > I'm running it just fine on my installation of Fedora 12 x86_64. When I > > installed my custom kernel (2.6.32.2), > > > > > I had to do a bit of tinkering to get the network & vmci modules to > > compile/install. > > > > > You shouldn't have any problems though with the stock Fedora kernels. > > > > > > Regards, > > > > > > Dan > > > > > > > > > > -----Original Message----- > > > > From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list- > > > > bounces@xxxxxxxxxx] On Behalf Of Robert P. J. Day > > > > Sent: Wednesday, January 06, 2010 12:10 PM > > > > To: Fedora List > > > > Subject: vmware workstation 7 on 64-bit fedora 12? > > > > > > > > > > > > is anyone out there running vmware WS 7 on fedora 12? any gotchas i > > > > should know about? i'm downloading the full x86_64 bundle of vmware > > > > WS as we speak, but some googling turned up stuff like this: > > > > > > > > http://osdir.com/ml/fedora-test-list/2009-10/msg00618.html > > > > > > > > which doesn't give me the warm fuzzies. so ... thoughts? directions? > > > > warnings? > > > > > > > > rday > nes > > > > > Hi > > > > Yes running WS 7.0.0 fine on fully updated F12 > > w2k pro and Windows 7 pro clients > > > > I would be very interested in the tweaks needed for 2.6.32 kernel > > > > John > > > Running fine on my fully updated F12 system here - and has been since F12 and WS7 both were available. No kernel tweaks necessary so far. But I did find one simple thing that needed to be done to make the install work on the 1st try without issues: Make sure that, prior to launching the WS7 installer, you place selinux in permissive mode (assuming you haven't disabled it)! After install is complete, it's fine putting selinux back into enforcing mode if you like. IIRC, the problem seems to be that the selinux policy doesn't like something the WS7 installer does with portrelease. That causes problems later on. Switching to permissive mode flags the error but allows the portrelease stuff to happen, and the install completes normally. WS7 is then happy - even if you put selinux back into enforcing mode after the install is complete. Hope that helps! Cheers, Chris -- ====================== "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." -- Albert Einstein -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
