Hipchat Server OVA import to VirtualBox fails with Phenom II X4 processor
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
This version of Hipchat Server is no longer supported
This article applies to a version of Hipchat Server which is beyond the Atlassian End of Life policy, and is no longer supported.
You should upgrade to a more recent version of Hipchat Server as soon as you can to take advantage of new features, and security and bug fixes. If possible, you should also consider deploying Hipchat Data Center instead.
Problem
When importing Hipchat Server OVA to a VirtualBox, the console output has ceased after the messages, "Starting CPU interrupts balancing daemon" and "Done", and does not accept input while the expectation is admin should be able to log onto the main console for the first time after server deployment with the following credentials:
Username: admin
Password: hipchat
As a result of this, Hipchat Server first-time boot initialization process doesn't complete. You may also notice there are several VMWare processes running, including vmware_checkvm and vmtoolsd, each of which consumes an entire CPU the whole time the server is running. Also, Admin may be able to log onto the server as admin user through SSH however the "hipchat network" command would hang and never completes.
Diagnosis
Your machine is running on Phenom II X4 processor.
Cause
This is a hardware dependent issue which happened only if VirtualBox guest settings has paravirtualization enabled with KVM on Phenom II X4 processor. Further discussion on this can be found in this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1251656
Resolution
Update paravirtualization setting to "legacy".
Alternatively, the problem may be resolved by deploying Hipchat Server on other VMWare products, such as VMWare Fusion. This problem has only been observed when deploying Hipchat Server to VirtualBox with AMD Phenom II X4 processors.