virtualbox.org

Help! I have a HP xw9400 with 2 dual-core Opteron 2200's running Win XP x64 Edition SP2 and 4 GB ram. Had previously played with 2.0.6 and could load Ubuntu 8.10 64-bit guest. OpenSolaris 2008.11 and Solaris 10 10/08 installed but only ran as 32-bit guests. All Extended CPU settings were enabled and Ubuntu was very fast while the Solaris releases had very poor speed response.

I upgraded yesterday to 2.1.0 and Ubuntu will no longer boot - complained that there was no x64 processor present but the logfile shows 2.1.0 definitely correctly recognizes the Opterons.

I killed all VM's, uninstalled, ran a clean install of 2.1.0 and still no success. Cannot install Ubuntu 8.10 because installer says I do not have x64 enabled processor! OpenSolaris install is still 32-bit guest on boot. Do I need to go back to 2.0.6 to at least get Linux 64-bit compatibility?

lovitzg wrote:Help! I have a HP xw9400 with 2 dual-core Opteron 2200's running Win XP x64 Edition SP2 and 4 GB ram. Had previously played with 2.0.6 and could load Ubuntu 8.10 64-bit guest. OpenSolaris 2008.11 and Solaris 10 10/08 installed but only ran as 32-bit guests. All Extended CPU settings were enabled and Ubuntu was very fast while the Solaris releases had very poor speed response.

I upgraded yesterday to 2.1.0 and Ubuntu will no longer boot - complained that there was no x64 processor present but the logfile shows 2.1.0 definitely correctly recognizes the Opterons.

I killed all VM's, uninstalled, ran a clean install of 2.1.0 and still no success. Cannot install Ubuntu 8.10 because installer says I do not have x64 enabled processor! OpenSolaris install is still 32-bit guest on boot. Do I need to go back to 2.0.6 to at least get Linux 64-bit compatibility?

Do you have the VT-x/AMD-v (hardware virtualisation) featured enabled as well as enabling hardware virtualisation in the BIOS? It's sad enough that a lot of notebook PCs do not have hardware virtualisation support in the BIOS even if certain processors have Intel VT and that it cannot be used.

If you're sure you haven't changed any of the AMD-V settings, could you create a defect on our bug tracker for this? Include the VBox.log of such a session.

Yes, virtualization is enabled in bios and all settings in vitualbox. Bug Ticket #2819 has been generated with log file as suggested.

Log file contents:
Modedit: Removed the log. If you attached it to the bug, why post it here too? It's too long. If we want to view it, we download it from the bug you reported. Else use pastebin.