Installation freezes on VMWare

[new123]

Hey all,

I'm trying to install Fedora-17-Nightly-20120301.15-x86_64-Live-desktop.iso on a new VMWare VM.

However, I don't get past the loading screen:
http://img215.imageshack.us/img215/2705/capture1330787163.png

VMware is set to Fedora 64bit, 3d hardware acceleration is enabled.

Any idea what could be causing this?

Regards
new123

[nonamedotc]

Pressing F1 or F2 will show the items that are loading. This might give an indication as to where it is exactly stopping. This might be a good starting point in determining what the problem actually is .. may be.

[new123]

Thank you!

The last entry is "Started Display Manger [ OK ]".

Disabling 3d hardware acceleration doesn't help.

[chrismurphy]

In GRUB, remove rhgb and quiet kernel parameters. You should get more information on what aspect of display initialization is failing.

Are you able to get to a text console? Or is the VM hung?

[zukuvybz]

well ive not been able to install this to hdd thing since TC1...

[new123]

After playing with the settings of VMWare I was able to start the live-cd at least in basic graphic mode.

Now I was able to complete the installation but when I try to start F17 I get this:
http://img856.imageshack.us/img856/9009/capture1330793301.png

@chrismurphy: Yes, the VM freezes completely. The console does not open when I press the keys. Trying to edit GRUB now that the installation went through cannot not help, can it?

Guess I'll just have to wait a few days and try a new build then.

[marvin_ita]

I'm having the same problem with VirtualBox... I've upgraded a F16 virtual machine to F17, now the boot process simply stops, but the VM is not stucked: If I issue a ctrl-alt-del it goes in runlevel 6 and reboots.
I'm able to boot in rescue mode. I suspect something network related is stopping the boot process: sendmail agent takes a full minute to start and just before the boot process stops I can see high activity on the virtual ethernet card. I tried to disable sendmail from rescue mode and to disable the virtual network card in Virtual Box, but nothing solves the problem.

Removing the quiet kernel parameter doesn't show anything more... any ideas?

EDIT: sorry, I see you managed to solve the problem while I was typing my post.... I will open another thread ;-)

[chrismurphy]

Guess I'll just have to wait a few days and try a new build then.

Maybe, if you have common hardware or graphics card involved, this is a workable approach. But FWIW, even on CentOS (RHEL 6) which are designed to be rock solid releases, I get a kernel panic on boot on one of my Macs. The RHEL 6.0 kernel is fine, but the 6.1 and 6.2 kernels cause a panic. If you can't get more information and file a bug if necessary at some point, it's entirely possible your problem won't get fixed, is my point.

[AdamW]

That looks like Shell is failing to run via llvmpipe on VMware VMs, possibly...if you try the KDE or Xfce desktops instead, say, do those work?

[new123]

Maybe, if you have common hardware or graphics card involved, this is a workable approach. [...] If you can't get more information and file a bug if necessary at some point, it's entirely possible your problem won't get fixed, is my point.
I think it's unlikely my graphics card plays a role, I guess its rather a general problem with VMWare.

This bug report seems to be related:
https://bugzilla.redhat.com/show_bug.cgi?id=785572

Haven't had a chance to try the KDE/Xfce versions yet.