There are a few posts here, but I could not find any other info anywhere else.

My system runs on XP host and Fedora 7 is the guest. I just don't know why I upgraded. If it ain't broke don't fix it. Right!

I hope someone from VMWare is reading this.

Z

FC7 host, vmware server v1.04 running FC7 VMs

Solution above did not help

I attached a screenshot of the message I get on boot

Thnak you very much in advance for any help

I have the same Issue, but a different environment.

My host runs openSuse 10.2 x_64 and the guest is Fedora5 i386 with a buslogic virtual scsi adapter.

I run cacti on the Fedora VM, all other VMs are either Windows or Suse, and they continue to work without problems.

Fedora scans all possible sd* and finally boots up.

I don't think changing the scsi adapter type from buslogic to lsilogic would work; how do you get the initrd updated ?

Cheers from Vienna, Austria

Albert

setting scsi0.virtualDev = "lsilogic" in my .vmx initially caused a kernel panic...probably because the kernel did not have the lsilogic driver loaded.

I opted to do an upgrade to FC5 over my existing installation (only took a few minutes) and the VM booted fine after that.

of course I also had to update all 93 packages that reverted back to previous versions