Hi All,
I have an odd problem on VMware ESX Server 2.5.3 build-35703, and was
wondering if anyone else had this issue.
I have created a new VM with 1G of ram and 8G of disk space, using the
LSILogic SCSI controller with virtual bus sharing.
When I import the Centos 5.3 i386 DVD iso into Cobbler and do an PXE install
with that imported distro, the system installs (with one slight problem) and
then reboots. When it reboots after installation, it gets to a point where
the remote console tells me :
...
mptbase: ioc0: Initiating bringup
ioc0: LIS53C1030 B0: Capabilities={Initiator}
and then there's a popup dialog that says the following:
VMware ESX Server unrecoverable error: (vcpu-0)
NOT_IMPLEMENTED F(5411):3237
Please request support and include the contents of the log file:
"/root/vmware/linux/vmware.log". We will respond on the basis of your
support entitlement.
When I look in the aforementioned file, it tells me something that seems
important:
Nov 11 16:51:19: vcpu-0| LSILogic: Adapter 0 Port 0 Operational.
Nov 11 16:51:19: vcpu-0| LSILogic: LSILogicProcessSDRMessage: Unhandled
Message Function 0x7
Nov 11 16:51:19: vcpu-0| NOT_IMPLEMENTED F(5411):3237
The LSILogic SCSI adapter is the only one that Centos will use from my vast
list of two (vmxlsilogic and vmxbuslogic). The vmxbuslogic doesn't produce
visible partitions when installing so it's not particularly usefule. The
LSILogic install completes, but with the above symptoms after the
post-install reboot.
Now for the weirdish part:
When I mount the iso the Centos 5.3 DVD as a DVD ISO device on the same VM
and install from virtual DVD, the system seems to work rather well. It
installs and reboots and comes up (eventually, after running firstboot) to a
login prompt.
I've spent the last couple of hours searching the interwebs about such
things. I would (and will) send my request to the vmware communities, but
since the disparity seems to be between Cobbler and a regular DVD install, I
figured I'd try here first and see if anyone had similar experiences.
Could this be an issue around the create-repo issue that is supposed to be
solved in Cobbler 2.0? That appears to be the only difference between the
two installs (i.e. the state of the repo at install time).
Any advice would be greatly appreciated.
Mykel
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
