VirtualBox

Opened 8 years ago

Closed 7 years ago

#15080 closed defect (fixed)

Issue with Oracle Virtual Box installation on VM

Reported by: naveenlekhwar Owned by:
Component: installer Version: VirtualBox 5.0.14
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

HI Team,

We have HP Intel Xenon Server in which our tech team have created VM's using hypervisor. We are using these VM's as blade(Citrix) windows machine. We installed oracle virtual box in these however facing issues. 1) Firstly we are not seeing any option for 64bit option for any OS. In hypersior bios doesnt have settings for "Intel (R) Virtualization Technology" and "Intel (R) VT-d Feature". Tech team is telling its becoz the Sever is running on pentium processor. What can be done to enable 64 bit ? Does these VM support Oracle Virtual box.

2) We tried installing vagrant image for 64bit Ubuntu and CentOS however while starting these seeing below error. "This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot – please use a kernel appropriate for your CPU"

3) We are able to install 32bit ubuntu on this.

Attachments (8)

VBox.log (81.1 KB ) - added by naveenlekhwar 8 years ago.
VBox.log.1 (81.1 KB ) - added by naveenlekhwar 8 years ago.
VBox.log.2 (85.8 KB ) - added by naveenlekhwar 8 years ago.
DebianError.PNG (13.9 KB ) - added by John De Witt 7 years ago.
Debian Install Error
Intel VT-x.PNG (115.9 KB ) - added by John De Witt 7 years ago.
Intel Utility Screen Shot
VBox.2.log (93.7 KB ) - added by John De Witt 7 years ago.
VLOG.TXT
Hyper V.PNG (80.1 KB ) - added by John De Witt 7 years ago.
Debian Logon.PNG (20.6 KB ) - added by John De Witt 7 years ago.

Download all attachments as: .zip

Change History (21)

comment:1 by Frank Mehnert, 8 years ago

This information is not sufficient. If "in which our tech team have created VM's using hypervisor" means that you try to run VirtualBox as a guest of another hypervisor then that probably means that the other hypervisor cannot support nested virtualization. A VBox.log file of a 32-bit VM session would probably show the problem.

by naveenlekhwar, 8 years ago

Attachment: VBox.log added

by naveenlekhwar, 8 years ago

Attachment: VBox.log.1 added

by naveenlekhwar, 8 years ago

Attachment: VBox.log.2 added

comment:2 by naveenlekhwar, 8 years ago

HI Team,

PFA the logs for 64bit CentOS installation in which we are seeing issue.

Our physical machines are low end in process and memory also due to policy issue we are not suppose to use personal computer for virtualization. Hence we are trying this in blade PC which are nothing but Windows machine built on VM's. Do you know if anyone else is using same approach mean using virtual machine to setup virtual desktop

comment:3 by Frank Mehnert, 8 years ago

Resolution: invalid
Status: newclosed

Sorry, this bug tracker is to report problems with VirtualBox. You log files clearly show that

  1. You are running VirtualBox as VMware guest and
  2. VT-x is not availble

That means that your VMware setup does not support/enable nested virtualization. VT-x (on Intel processors) is required to support 64-bit guests with VirtualBox. This is NOT a VirtualBox bug.

by John De Witt, 7 years ago

Attachment: DebianError.PNG added

Debian Install Error

by John De Witt, 7 years ago

Attachment: Intel VT-x.PNG added

Intel Utility Screen Shot

comment:4 by John De Witt, 7 years ago

Same Error. Have included screen shots. I have a Windows 10 PC using Oracle VM trying to install Debian 32 bit. Please help. Thanks.

comment:5 by John De Witt, 7 years ago

Resolution: invalid
Status: closedreopened

comment:6 by Frank Mehnert, 7 years ago

Please attach the VBox.log file of such a VM session.

in reply to:  6 comment:7 by John De Witt, 7 years ago

Replying to frank:

Please attach the VBox.log file of such a VM session.

How do I do that?

by John De Witt, 7 years ago

Attachment: VBox.2.log added

VLOG.TXT

comment:8 by Frank Mehnert, 7 years ago

The log file contains the following line:

HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes

So even if your CPU is capable of VT-x (yes, it is, see also here), your BIOS settings are probably not correct. It might be also necessary to disable Hyper-V in your Windows installation.

by John De Witt, 7 years ago

Attachment: Hyper V.PNG added

by John De Witt, 7 years ago

Attachment: Debian Logon.PNG added

comment:9 by John De Witt, 7 years ago

Hi Frank. It worked. I enabled the Virtualization under sysconfig in BIOS. Disabled ALL Hyper V services in Windows 10. And installed Debian. Thank you so much. John

comment:10 by Socratis, 7 years ago

@JDe Witt
May I suggest something for future reference? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours was not a bug and someone from the developers has to deal with it and close it again as "Invalid".

comment:11 by John De Witt, 7 years ago

Couldn't find anything regarding my error in that arena. Sorry for the confusion.

comment:12 by Socratis, 7 years ago

It's not about the confusion, it's about taking the burden out of the developers and onto the volunteers in the forums, they have a great success rate. Think of it as a triage in the emergency room; everyone needs attention, but not everyone needs a surgery ;)

comment:13 by Frank Mehnert, 7 years ago

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use