virtualbox.org

In Normal Linux OEL 5 Installation we do install of 64 bit OS OEL 5 linux on 32 bit processor machines.
However 64bit Virtualbox installed on 32 bit processor with 64 Bit OEL5 throws error as please use 32 bit OS OEL5, I was expecting it virtualbox will work with 64 bit OS image on 32 bit processor.

vg wrote:I was expecting it virtualbox will work with 64 bit OS image on 32 bit processor.

I can't imagine why. VirtualBox could never run 64-bit software on a 32-bit CPU (not the same as a 32-bit OS!) and almost certainly never will.

You accept that normal OEL5 install works on 32 bit processor machine, though this is supported but virtualbox will not support right.

By definition: you can't install a 64bit OS on a 32bit PC, whether physical or virtual. You are mistaken.

Some OS's may have one installer which chooses which platform to install at install time. I suspect that is what has confused you.

Hi,

Can some one please let me know how to check processor is 64 bit ot 32 bit.
Google search shows lots of results, however non of them is convincing.

ok I confirmed the processor is 64 bit and OS is also 64 Bit.
I installed 64 bit virtual box on 64 bit OS and 64 Bit processor
Then selected 64 bit Linux Image file and booted the same for installation,
I see message as
"You CPU does not support long mode. Use a 32 bit distribution"

Please let me know do we need to pass any extra parameter to virtualbox ?

Here is /proc/cpuinfo | grep flags output and you can see both tm (32 bit) and lm (64 bit), processor supports both 32 bit os and 64 bit OS.

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm

Here is the uname -a output

2.6.18-238.0.0.0.1.el5 #1 SMP Tue Jan 4 09:29:38 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

Moved to Linux Guests.

Post a VM log file for the 64bit Linux guest in question. For details read: Minimum information needed for assistance.

attached VBox.log,

You can message as
00:00:20.229396 ALSA: ADC frequency 44100Hz, period size 940, buffer size 3763
00:00:20.231670 ALSA: DAC frequency 44100Hz, period size 940, buffer size 3763
00:00:20.233798 AIOMgr: Flush failed with VERR_INVALID_PARAMETER, disabling async flushes
00:00:20.233816 DevPcBios: SATA LUN#0 LCHS=1024/255/63
00:00:20.233957 PGM: The CPU physical address width is 36 bits
00:00:20.233964 PGMR3InitFinalize: 4 MB PSE mask 0000000fffffffff
00:00:20.246648 VMM: Thread-context hooks enabled!
00:00:20.246663 VMM: fUsePeriodicPreemptionTimers=false
00:00:20.247361 Logical host processors: 2 present, 2 max, 2 online, online mask: 0000000000000003
00:00:20.247393 Physical host cores: 2

VBox.log wrote: 00:00:19.152693 HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS.

In order to run 64bit guests you need to :-

1. Have a 64bit CPU which supports VT-x or AMD-v (your Core 2 Duo E6550 supports VT-x).
2. Have Virtualization Technology Support enabled in your host BIOS (your BIOS may call it something different. If you see Virtual Directed I/O, that isn't the same thing).
3. Have no other software already using VT-x (e.g. no other VM software running at the same time. Some system level debuggers may also use this feature).
4. Have the VT-x/AMD-v feature enabled in the VirtualBox settings for the VM.
5. When installing a 64bit guest, make sure to select the 64bit version of the template for that OS.

mpack wrote:In order to run 64bit guests you need to :-

1. Have a 64bit CPU which supports VT-x or AMD-v.
2. Have Virtualization Technology Support enabled in your host BIOS (your BIOS may call it something different. If you see Virtual Directed I/O, that isn't the same thing).
3. Have no other software already using VT-x (e.g. no other VM software running at the same time. Some system level debuggers may also use this feature).
4. Have the VT-x/AMD-v feature enabled in the VirtualBox settings for the VM.
5. When installing a 64bit guest, make sure to select the 64bit version of the template for that OS.

Can you please make this a sticky post? In bold? And eye-hurting-red? It would cover more than 40% of the questions in the forums...

socratis wrote:Can you please make this a sticky post? In bold? And eye-hurting-red? It would cover more than 40% of the questions in the forums...

That's assuming people read the sticky, bold, red topics before posting... and that assumption is demonstrably false

You might as well suggest putting this information in the manual!

michaln wrote:You might as well suggest putting this information in the manual!

You are going wild here... So daring... so trusting in the people!

noteirak wrote:

michaln wrote:You might as well suggest putting this information in the manual!

You are going wild here... So daring... so trusting in the people!

I hadn't have my coffee coming through my nostrils for a looooong time! You both owe me a monitor wipe and a kleenex! (I know... I started it...)