Opened 14 years ago
Last modified 8 years ago
#7427 closed defect
Kernel panic when starting F5 Big-IP (not syncing: Fatal exception) — at Initial Version
| Reported by: | Thorsten Behrens | Owned by: | |
|---|---|---|---|
| Component: | virtual disk | Version: | VirtualBox 3.2.8 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
I spun up an F5 Big-IP trial VM on VirtualBox. It can be found here: https://www.f5.com/trial/. It's designed to run on VMWare.
The disk I use is the original VMDK that comes from F5. I've set up a virtual machine with PIIX4, I/O APIC. Base memory is 1GB, network interfaces are PCNet-II. This all matches the VMWare setup.
Upon boot, after Loading udev, I get "Kernel panic - not syncing: Fatal exception"
The interesting part is that this does not happen always. If you allow the VM to auto-reboot, eventually it will load successfully. This makes me think that we may have some sort of race condition here. I am assuming at this point that it has something to do with attaching the storage devices from /etc/fstab, though I do not know this for certain.
The one thing I can see that is slightly unusual is that /etc/fstab uses UUIDs, not /dev/hda references.
This should be easy to reproduce by downloading the F5 trial and using the attached machine XML.
F5 BigIP LTM Virtual Machine XML