Not able to install Fedora64 bit in VirtualBox 3.2

PrinceCruise · 06-01-2010, 03:25 PM

Hi ,

I'm using Mint9 (64 Bit) on my laptop.
My idea was to install Fedora and Open-Solaris as virtual machines for some serious R&D. I installed VirtualBox 3.2 as a deb package for Ubuntu 10.04 (Mint9 is based on that) and it worked properly.
Now I'm able to install Open-Solaris 32 bit on it successfully but at the time of booting Fedora13 64 bit , it gives me an error of "This guest requires a x86-64 CPU but only found a i686 one" , can not proceed...!
My laptop is a C2D T6400 , 3GB RAM , but it doesn't support VT (no setting in BIOS) , So does that mean I won't be able to install any 64 bit OS under VirtualBox or VMware ?

Please help , I'm very confused...!

Mr-Bisquit · 06-01-2010, 03:29 PM

Code:

cat /proc/cpuinfo

Have you tried paravirtualization with PAE instead?
If it's a 64bit cpu then that option can be used.

PrinceCruise · 06-01-2010, 04:11 PM

Quote:

Originally Posted by Mr-Bisquit

Code:

cat /proc/cpuinfo

Have you tried paravirtualization with PAE instead?
If it's a 64bit cpu then that option can be used.

Thanks mate for replying . I'm in office right now so will post the output when I'll be on my system.
Would you please throw some more light on "paravirtualization with PAE" ? I guess I didn't get it fully

.

syg00 · 06-01-2010, 05:57 PM

Never mind - didn't read the OP properly.

paulsm4 · 06-01-2010, 06:08 PM

When you create your VM (prior to installing an OS on top of it), you need to specify that it's a AMD-64 VM (not x86).

Quote:

http://forums.virtualbox.org/viewtopic.php?t=8669

Q: Does VB support 64 bit guests?

A: Support for 64 bit guests was introduced at version 2.0.0. If you wish to create 64 bit guests then we recommend that you upgrade to the latest version. Note that VirtualBox also supports 64-bit guest operating systems, under the following conditions:

1. You need a 64-bit processor with hardware virtualization support (see User Manual chapter 1.2, Software vs. hardware virtualization (VT-x and AMD-V), page 10) and a 64-bit host operating system.
NOTE: Since version 2.1.0, you can run 64 bit Guests while running a 32 bit Host. The prior requirement for Operating System is only for version 2.0.x. You still need the proper hardware.
2. You must enable hardware virtualization through your BIOS; software virtualization is not supported for 64-bit VMs.
Note: some HP BIOSES have a glitch, When You ENABLE VT-X/AMD-V, You DISABLE it, so do try both ways.

PrinceCruise · 06-02-2010, 05:13 AM

Hi Paul ,

In virtualbox 3.2.0 I can't seem to select any option for choosing 32 or 64 bit VM. It's pretty plain selection

!

This is the output of cpuinfo -

Quote:

prince@prince-mint9 ~ $ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz
stepping : 10
cpu MHz : 1200.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
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 pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm
bogomips : 3989.65
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz
stepping : 10
cpu MHz : 1200.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
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 pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm
bogomips : 3990.01
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

Now could you please suggest me what needs to be done?

paulsm4 · 06-02-2010, 10:57 AM

Hi -

Q: The "cpuinfo" you posted is from your physical host (and not your VM), correct? The issue is whether your *VM* is 32-bit or 64-bit.

Q: Here's the VBox download page:
http://download.virtualbox.org/virtu...oad.html#linux

You downloaded this:
virtualbox-3.2_3.2.0-61806~Ubuntu~lucid_amd64.deb

and NOT this:
virtualbox-3.2_3.2.0-61806~Ubuntu~lucid_i386.deb

Correct?

Mr-Bisquit · 06-02-2010, 11:07 AM

If your cpu set does not contain the proper flags, then no, you cannot support 64bit guests.
If you want a 64bit guest and don't mind the work, then qemu + kqemu- although "outdated" it is very useful- may be a solution.
I'm not sure; but, you may check with Xen and paravirtualized guests.

PrinceCruise · 06-03-2010, 09:08 AM

My answers in bold sir , thanks for bothering me

-

Quote:

Originally Posted by paulsm4

Hi -

Q: The "cpuinfo" you posted is from your physical host (and not your VM), correct? The issue is whether your *VM* is 32-bit or 64-bit.

A: The output is of Physical machine. And let me put it again ,while creating the VM it doesn't give the option of choosing 64 or 32 bit , though in VMware it used to.

Q: Here's the VBox download page:
http://download.virtualbox.org/virtu...oad.html#linux

You downloaded this:
virtualbox-3.2_3.2.0-61806~Ubuntu~lucid_amd64.deb

and NOT this:
virtualbox-3.2_3.2.0-61806~Ubuntu~lucid_i386.deb

Correct?

A: virtualbox-3.2_3.2.0-61806~Ubuntu~lucid_amd64.deb , yes !

PrinceCruise · 06-03-2010, 09:12 AM

Quote:

Originally Posted by Mr-Bisquit

If your cpu set does not contain the proper flags, then no, you cannot support 64bit guests.
If you want a 64bit guest and don't mind the work, then qemu + kqemu- although "outdated" it is very useful- may be a solution.
I'm not sure; but, you may check with Xen and paravirtualized guests.

Hi ,Yes,May be I need to reconsider options.
I'm not very much used to of Qemu, heard and seen it's tougher to manage , but let me atleast give it and Xen a shot.