virtualbox.org

I upgraded to 3.0.6 when I saw the update. When I tried to go back to my Ubuntu 64-bit guest install (running in VB on Vista 32), they lock up just after going to GRUB(2).

I also tried booting off of the Live CD for Karmic A5 as well as the LiveCD for 9.04, and none of them will boot past GRUB. I didn't change anything else with the settings for the devices before or after the upgrade. They worked fine on 3.0.4.

Anyone else have this problem?

Did you reboot the Host after the upgrade?

well, I didn't the first time, but saw in another post that people mentioned rebooting the host. I have rebooted the host and it will not boot 64-bit 9.04 or 9.10A5.

It will boot a 32-bit 9.04 LiveCD though. SO what seems to have broken in booting a 64-bit guest on a 32-bit host (I have a 64-bit processor and this was working fine under 3.0.4).

Look at the guest settings and make sure that the VT-x/AMD-v still has a check mark in it.
Do you see any error messages?
Try a 64 bit OS that is not an alpha version as there may be some conflicts until the mesh their builds.

VT-x/AMD-V is still checked.

Ubuntu 9.04 64-bit doesn't boot past GRUB
Ubuntu 9.10A5 64-bit doesn't boot past GRUB

BOTH worked correctly under VB 3.0.4. Now, 9.10A5 had some things wrong with it, but that was because it was A5. The Linux VMs that were 64-bit before upgrading to 3.0.6 worked. After the upgrade, they stopped booting.

By past GRUB, I mean that when you use the LiveCD and pick your language, then pick "Try Ubuntu on this computer", it goes to a blank black screen and does nothing.

an installed (not livecd) ubuntu 9.04 64-bit works fine for me, with and without guest additions.

fedora10 64-bit host, vt-x enabled, no smp, 3.0.6 final.

I think what seems to be broken is the 64-bit on the 32-bit host. I can run my 32-bit hosts just fine.

I also tried a clean reinstall of 3.0.6. It still did not work.

However, the 64-bit guest did do something a little bit different. when booting from the 9.04 LiveCD, the hard drive access light kept going. When I started up task manager to look at the VirtualBox process, it was using about 50% (of the dual core) CPU and the CPU time was just ticking up by the second (and nothing else was).

Something is definitely going on.

I have the exact same problem with 3.0.6. Even installed 64-bit linux guests won't boot. I've looked at the task manager and it keeps consuming 25% cpu (I have a quad core cpu) without doing anything. VT-x, PAE/NX, ACPI and IO APIC are all checked.

I am experiencing the exact some issue. I am unable to boot Ubuntu 9.04 64Bit guests from an Ubuntu 9.04 32Bit host. Reinstalling 3.0.4 fixes the problem for now. http://download.virtualbox.org/virtualbox/3.0.4/

whya re so many people running 32-bit operating systems on 64-bit cpu's on this forum?

and why use 64-bit guests if you're wary of a 64-bit host?

just wondering as it seems weird to me. is there something you fear won't work?

i can understand with windoze as you probably don't want to pay another license fee or run the incredibly naff xp64, but on linux its just another free download.

well, I am running 32-bit Windows, and as MS won't give me the media legally for a 64-bit install (and I don't fell like reinstalling at the moment anyway), I'm on a 32-bit host. Plus, I'm still experimenting with the 64-bit OS. Until only a few months ago, things like flash and Java didn't really work all that well in 64-bit without what to me seemed like too much finagling.

Anyway....64-bit guests on 32-bit hosts worked in 3.0.4 pretty flawlessly, and something obviously broke in 3.0.6, otherwise I wouldn't be the only one having the problem.

Running a 64-bit native host would be ideal, but not practical at the moment with all the MS/Linux corresponding shortfalls.

oguz286 wrote:I have the exact same problem with 3.0.6. Even installed 64-bit linux guests won't boot. I've looked at the task manager and it keeps consuming 25% cpu (I have a quad core cpu) without doing anything. VT-x, PAE/NX, ACPI and IO APIC are all checked.

seems like exactly what I'm seeing. It eats "one core" and VMs that worked before suddenly stop booting. Looks like back to 3.0.4 until a fix comes out.

sej7278 wrote:whya re so many people running 32-bit operating systems on 64-bit cpu's on this forum?

and why use 64-bit guests if you're wary of a 64-bit host?

just wondering as it seems weird to me. is there something you fear won't work?

i can understand with windoze as you probably don't want to pay another license fee or run the incredibly naff xp64, but on linux its just another free download.

I use 32-bit for my desktops, but use the 64-bit guests to build software for our servers. I occasionally run into a closed source app that I need/want on my desktop that does not yet distribute a 64-bit version, so I just run 32-bit to be safe.

sej7278 wrote:whya re so many people running 32-bit operating systems on 64-bit cpu's on this forum?

and why use 64-bit guests if you're wary of a 64-bit host?

just wondering as it seems weird to me. is there something you fear won't work?

i can understand with windoze as you probably don't want to pay another license fee or run the incredibly naff xp64, but on linux its just another free download.

There are other reasons for this. Here are two that I can think of.

1. Lack of 64-bit driver support for some hardware.

2. Lack of 64-bit software support. I had to install Vista 32 on my laptop, since the Cisco VPN client does not run under Vista 64.