FC4 on VMWare

[Patrick Nelson]

Patrick Nelson wrote:

>FC4 on VMware Workstation
>
>I've been running FC4 on VMware workstation instances for development. 
>This has worked fine up until the last 2 kernel updates.  I just tried
>to install the last kernel update (kernel-2.6.13-1.1532_FC4) and I am
>getting kernel panics.  The last working kernel update that works is
>kernel-2.6.12-1.1456_FC4).  The error that happen is during the kernel
>boot portion and looks something like:
>
>Bad Boot:
>---snip---
>uncompressing Linux... OK, booting
>PCI: Cannot allocate resource region 4
>Red Hat nash version 4.2.15 starting
> reading all physical volumes.  This may take awhile
> no volumes found
> unable to find volume group "VOLGROUP00"
>ERROR: /bin/lvm exited abnormally with val 5
>---snip---
>
>Past that there are more errors that I can't remember.  But then there
>is a kernel panic.
>
>
>If I boot off the 1456 kernel the same section looks like:
>---snip---
>uncompressing Linux... OK, booting
>PCI: Cannot allocate resource region 4
>Red Hat nash version 4.2.15 starting
> sda blah
> sda blah
> reading all physical volumes.  This may take awhile
>---snip---
>
>So it seems that the new kernels are not finding my sda drives in the
>VMware instance.  Has something changed in the later kernels to restrict
>finding the VMware sda?  This happens on the Guest OS (as above) whether
>the host OS is Windows or Linux so it is associated with the booting of
>FC4 kernels on the instance.  Anyone know if there is something I can do?
>  
>
Looking through FC kernel stuff I found that some recent FC kernels have
had broken support for LSILogic which might be the problem.  Looks like
this may be fixed int 16xx version FC4 kernels.