virtualbox.org

I am running the new v2.1.2 virtual box.
I have an Ubuntu Intrepid 64-bit host, and am trying to install Ubuntu an Intrepid 64-bit client. As soon as I press enter to install from the CD image, the window is black and nothing happens. The cpu is at about 50% usage.
It works fine if I try to install 32-bit Intrepid.
My host machine is an Intel Core2 Quad.

I have tried all the combinations of networks, memory sizes and other options etc that I can think of.

Any ideas?

What do you see if you run the installer with some additional options? Hit F6 on the boot menu of the installer and change the boot parameters so it doesn't say 'quiet' anymore. You might want to remove 'splash' too, if it's listed.

I had already tried, that (I tried it again), same results

Here is the tail end of the log:

00:00:03.355 Guest Log: BIOS: Booting from CD-ROM...
00:00:03.404 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00007f534278b000 w=640 h=480 bpp=16 cbLine=0x500
00:00:29.854 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0
00:00:29.858 Guest Log: BIOS: *** int 15h function AX=EC00, BX=0002 not yet supported!
00:00:29.858 Guest Log: BIOS: KBD: unsupported int 16h function 03

Wilbur, (1) Send a Private Message to Sandervl, asking him to change your username. Don't use your email address in clear unless you want to be hit by even more spam. (2) This may be a 64 bit settings issue. Make sure that you've set your VM type to Linux/Ubuntu (64bit) so that PAE, etc are set correctly. You also need to have a VT-x / AMD-V enabled CPU + BIOS support to run a 64bit guest OS.

The installer bootstrap starts in 32bit mode and then toggles into 64-bit. It looks like you've stalled at this point so some of your settings are wrong.

Terry,
Thank you for your suggestions

I have my VM type set to Linux/Ubuntu (64bit)
I have VT-X / AMD-V enabled, without it the installer complains that I need a 64-bit capable CPU.
I disabled and reenabled, then tried flashing my BIOS to the most current version (a real pain when you only have Linux systems, unetbootin/freedos ended up being an easy solution).
I tried enabling PAE, the system did a hard hang and needed the reset button recover.
Same thing if I disable the write protect bit in the bios, it does a hard hang.

I am sure you are right because the i386 version installs without any problems, but I don't have any idea where the problem is.

Wilbur

Wilbur, the issue is that your BIOS must enable the use of VT-x. If you look at your VBox.log, it will tell you whether VB can access the VT-x functionality.

So I guess that the entry HwVirtExtForced being set to 0 is the problem?

I do have hardware virtualization enabled in the BIOS, but some people had reported that the BIOS setting lied, which was why I updated to the most recent BIOS.

Any ideas on how to get this enabled?

I have a Shuttle SX48P2E0 with the Q9650 3.0GHz Quad core CPU.

00:00:00.315 Name <string> = "vboxui64" (cch=9)
00:00:00.315 UUID <bytes> = "64 28 c6 21 d9 45 1b 4c 82 ce a0 2f 85 a4 79 22" (cb=16)
00:00:00.315 RamSize <integer> = 0x0000000042900000 (1116733440)
00:00:00.315 NumCPUs <integer> = 0x0000000000000001 (1)
00:00:00.315 TimerMillies <integer> = 0x000000000000000a (10)
00:00:00.315 RawR3Enabled <integer> = 0x0000000000000001 (1)
00:00:00.315 RawR0Enabled <integer> = 0x0000000000000001 (1)
00:00:00.315 PATMEnabled <integer> = 0x0000000000000001 (1)
00:00:00.315 CSAMEnabled <integer> = 0x0000000000000001 (1)
00:00:00.315 HwVirtExtForced <integer> = 0x0000000000000000 (0)
00:00:00.315 EnableNestedPaging <integer> = 0x0000000000000001 (1)
00:00:00.315 EnableVPID <integer> = 0x0000000000000000 (0)
00:00:00.315 EnablePAE <integer> = 0x0000000000000000 (0)
00:00:00.315

I verified that VT-x is being enabled in the BIOS by leaving it enabled in Virtualbox, but disabling it in the BIOS and I get the error that I don't have a 64-bit CPU, so it is being enabled in the BIOS.

For me at least, this option was incompatible with Intel Quick Boot (go figure). After disabling this option, I met with limited success virtualizing 64 bit OSes. My suggestion is to document the successes you meet with by enabling and disabling various options in your bios setup. It seems to me that VBox for linux and the newest intel virtualization aren't compatible (I have tried a few different releases it doesn't seem to be an isolated problem.

Hope something in here helps

Cheers

I don't know about the latest Intel processors. I have a new Core i7 at work and it seems t work fine with/without the Intel features turned on. Same OS, same updates, different motherboard an BIOS of course.