SOS ~ Fedora 17 install failed on VMware Workstation 8.0.3 VM

[luicst]

Fedora 17 install failed on VMware Workstation 8.0.3 VM

picture below:

http://forum.icst.org.tw/phpbb/viewtopic.php?f=16&t=26284&p=77063#p77063

Fedora 17 is release version, not alpha , not beta

[mfelker]

Wht processor  do you have ?  AMD or Intel?.  AMD will give you problems

[luicst]

Intel CPU

[WoodyZ]

According to VMware Compatibility Guide Fedora 17 is not yet officially supported however have a look at: VMware Documentation for Fedora 17 Desktop Edition

[ringostar77]

Followed Instruction but as was getting on First boot after entering User information and then got this error

"

Oh no! Something have gone wrong.
>> A problem ocurred and the system can't recover. Please contact the
>> system administrator
"

this was on ESXI 5.0 Server with standard options for install

Found that running 
'yum remove fprintd' from the recovery Console and then restarted machine
Fixed the issue 
refer to as you might be hitting bug 810040 https://bugzilla.redhat.com/show_bug.cgi?id=810040

Thank to this Post Im working again..
http://lists.fedoraproject.org/pipermail/users/2012-June/419457.html





 

[Silyn]

Removing fprintd fixed it for me, ESX 4.1U2 with fresh Fedora 17 install.

[keshavp]

How do I get to the 'Recovery Console' that you mentioned? I'm having the same problem on ESXi 5.1.

[keshavp]

I should be asking ring0star77 - looks like you are running the version (5.0) closer to mine.

(perhaps, that doesn't matter?)

[michaelstump]

Posting here because I've run into this exact problem recently. You can expect to see this behavior on both ESXi 5.0 and 5.1. The fix above is correct: reboot the Fedora VM into the recovery console (you might have to select Advanced Options in the bootloader first), and run: yum -y remove fprintd. Note that the -y just saves you from having to hit y when yum is ready to remove the package. Reboot and you should get to your Fedora login screen without incident.

mike