HELP!!!Cannot Load 64bit guest on 32bit host

[confused5524]

Hi
I am anew user of VirtualBox and i tried to use it mainly because i want to use 64bit OS on my current pc and see what potential app conflicts might occur. However VB always fails to load any 64bit OS as guest. I am running 32bit vista ultimate on my pc. its configuration is
>intel E7300 processor
>Intel DG45ID motherboard
>4GB DDR2 800 ram

I have checked that both my mother board and processor support hardware virtualization and VB even reports that it is enabled....... here is a screenshot

VB1.GIF (36.51 KiB) Viewed 3418 times

However when i run the VM it says that the processor is not 64 bit capable ........... this is the screenshot

VB2.GIF (37.19 KiB) Viewed 3424 times

VB2.GIF (37.19 KiB) Viewed 3424 times

I tried google searches but came up with nothing specific ........... i am using VirtualBox as free for personal use under PUEL. Thats all the important info i think.......
oh and i have tried to load windows 7 ultimate 64bit and linux 9.04 64bit..........
It will be very helpful if someone helps me with this ...... and please excuse my english ...... its not my native language

[Perryg]

Is hardware-v turned on in the system bios?
The main screen saying it is does not count. All of them say it is enabled even when it is not.

[Sasquatch]

See VirtualBox FAQ for requirements to run 64 bit Guests.

[confused5524]

Thank you all for helping me this problem......... apparently even though intel claims E7300 has VT enabled its actually not there. It has EM64T which is not the same as VT-x. Here is a list I found for processors that are VT-x enabled........ http://forums.virtualbox.org/viewtopic.php?f=1&t=16557

And here is a link that provided useful do-it-yourself instruction for troubleshooting ...http://forums.virtualbox.org/viewtopic.php?f=4&t=18685


I hope this helps somebody else like me ........... Thank you all again for your efforts to help me

[ihatelolcats]

you can't run a 64bit OS on a 32bit machine.

[dmcgraw]

you can't run a 64bit OS on a 32bit machine.

If you mean you can't run a 64 bit guest under a 32 bit host, then you are mistaken.

I am running Vista 32 bit host with an Ubuntu 9.04 64 bit guest.

The only limitations I have seen is that the guest is limited to one core.

Dave

[sej7278]

you can't run a 64bit OS on a 32bit machine.

If you mean you can't run a 64 bit guest under a 32 bit host, then you are mistaken.

ihatelolcats was correct actually, if you don't have a 64-bit processor you can't run 64-bit guests. however if you are running a 32-bit operating system on a 64-bit cpu, then you can run 64-bit guests if you have vt-x.

you also need vt-x to run 64-bit guests on 64-bit hosts, e.g. a 64-bit cpu running a 64-bit os can't run a 64-bit guest unless you have vt-x. that's something i hope sun will fix, as it seems like an artificial limitation to me.

[dmcgraw]

you can't run a 64bit OS on a 32bit machine.

If you mean you can't run a 64 bit guest under a 32 bit host, then you are mistaken.

ihatelolcats was correct actually, if you don't have a 64-bit processor you can't run 64-bit guests. however if you are running a 32-bit operating system on a 64-bit cpu, then you can run 64-bit guests if you have vt-x.

you also need vt-x to run 64-bit guests on 64-bit hosts, e.g. a 64-bit cpu running a 64-bit os can't run a 64-bit guest unless you have vt-x. that's something i hope sun will fix, as it seems like an artificial limitation to me.

That is why I clarified my statement by saying "If you mean you can't run a 64 bit guest under a 32 bit host,".

Also, the processor specified by the OP is a 64-bit processor, although from a quick glance of Intel's website, it is not clear if it supports VT-x. Although, from the screenshots that the OP posted, VB seems to think that VT-x is enabled.

[Sasquatch]

VB enables VT-x by default. My AMD FX-60 socket 939 CPU was made long before hardware-V was even an option, yet VB still enables it. My laptop has a VT-x CPU, but the motherboard doesn't support it, here too does VB enable VT-x. If you check the changelogs, you will see that it will be enabled by default, but it won't be used if it's not detected upon VM start.