Aha, you have an AMD processor... I'd say this is a bug in RedHat 5.2 but it's not clear to me what it is.
This sounds like the same problem with physical systems.
RedHat 5.2 Deluxe
-
michaln
- Oracle Corporation
- Posts: 2973
- Joined: 19. Dec 2007, 15:45
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Any and all
- Contact:
Re: RedHat 5.2 Deluxe
Aha. This is a bug in the antique Linux kernel (2.0.36). It is likely confused by the fact that your CPU reports itself as family 15 model 6. That explains why RedHat 5.2 also breaks on Pentium 4 CPUs. The guest is clearly confused and thinks that the CPU is a '?86' (yes, with a question mark). That then blows up the installer because it basically doesn't understand what architecture it's on. Needless to say, your CPU is at least 10 years newer than RH 5.2 so this was never an issue in practice.
But guess what! There is a workaround:
That changes the CPU family/model reported to the guest OS. It should work on your system. I have taken the line 'Gst: 00000001/0000 00100f62 00000800 00802009 078bfbbf' from your VBox.log and modified the 'eax' value.
But guess what! There is a workaround:
Code: Select all
VBoxManage modifyvm <yourvm> --cpuidset 1 00100601 00000800 00802009 078bfbbf-
jamie marchant
- Posts: 14
- Joined: 14. Mar 2016, 16:07
- Primary OS: Linux other
- VBox Version: OSE Fedora
- Guest OSses: Many Linux and older Windows's
Re: RedHat 5.2 Deluxe
It worked! Thanks a bunch 