64 bit guests don't work

[rdhalstead]

I am currently running VB 4.04 on Solaris 11 Express 64 bit host. Prior to VB 4, 64 bit hosts would install and run with no problems. Now, with VB 4.x, new 64 bit guests crash during installation and existing 64 bit guests, that used to run OK prior to VB 4.x, either hang or crash. 32 bit hosts (Ubuntu is one) seem to be ok. I have reported this before but have had no replies. Do I have to abandon VB 4.x and revert to VB 3.x where everything just runs or will this problem be at least investigated. I can no longer recommend Virtual Box as a solution as long as this problem exists.

Ron Halstead

[mrpink]

I had the same issue with 4.0, this was apparently resolved in 4.0.4 which I can confirm.

[tomwaters]

Not what you want to hear...but work fine for me.

S11E, server2008r2guests.

If you have an issue, I suggest you log a bug in the bug tracker... Include the log and core dump...via email if large.

[mrpink]

Apparently I confirmed too fast... Windows 7 64 bit guest keeps freezing, also with v. 4.0.4 ... just annoying. 3.2 doesnt seem to work for me either due to some other issues on OS host. 3.1 running fine tho.

[rdhalstead]

As you can see from my original post, I'm using VB4.04 and have the problem. So your reply of
"I had the same issue with 4.0, this was apparently resolved in 4.0.4 which I can confirm." unfortunately does me no good.

Does anyone else have this problem? Have any of the moderators seen this thread? For a production application, this is
a show stopper! I have filed a bug report, #8581. Perhaps we'll see some action.

Ron Halstead

[rdhalstead]

I have been asked for a log file of a session which I provided. Hopefully.........

--ron

[leejunfan]

I guess, put me down as a "me too"

Running kubuntu Natty 32 bit, tried installing Win7 x64 and got the message at the beginning of install that I was trying to run x64 on unsupported hardware.

VMWare Workstation was able to install (Maverick 32bit at that time) Win7 x64, so I guess that means VT works on the machine fine.

[kebabbert]

I dont have any problems with VB v4.0.4 Solaris 11 Express host, and Win7 64bit as guest.

[TheLastBoyscout]

I dont have any problems with VB v4.0.4 Solaris 11 Express host, and Win7 64bit as guest.

Not sure why SE11 works (I haven't tried it yet and since the sources are closed it's hard to find out why...), but I have the same problems as everyone else:

I can confirm that 64 bit guest OSs do NOT work with VirtualBox 4.1.0 on OpenIndiana b_148.
I've tried MS Server 2008 R8, Win7 x64, Ubuntu 11.04 64 as well as OpenIndiana b_151 and all crash when trying to install.
On the other hand, there are no problems with the 32-bit versions of Win7 and Ubuntu 11.04.

I am puzzled that the bug ticket is not even assigned at this point...
-TLB

[Ramshankar]

Which bug ticket is it?

[TheLastBoyscout]

Which bug ticket is it?

I have filed a bug report, #8581.

-TLB

[TheLastBoyscout]

Hi,

Today I tried the same scenario with OpenIndiana b_151 (and latest updates) and again could not install 64-bit guests in VirtualBox 4.1.0. While previously Windows Home Server (or 2008R2) BSODd with STOP: 0x050, it now seems to always be 0x01A (Memory Management). Ubuntu 11.04 (64) also crashes with a kernel panic during installation. Now I realize that I am not using SE 11 (as the OP did), but the description of the problems observed leads me to believe that this is not a SE11 vs. OI b_151 issue.
The Solaris host OS is installed on real hardware (no nested VMs) and other than assigning an .iso file to the CD/DVD drive and adjusting the memory to 1 GB (I also tried 2 GB), I didn't modify the default settings for the guest VM.
I ran several iterations of Memtestx86+ on the 2x4GB RAM on this system and even tried twice with only one of the DIMMs installed - to no avail. It doesn't look like a hardware problem.

-TLB

[TheLastBoyscout]

Update: I've tried VB 3.2.12 and VB 4.0.12 and it didn't fix the problem. I tried SE 11 - nothing. Eventually I got a Win7_64 DVD and installed that as the host OS, then VB 4.1 and then a 64-bit OS and again: Crash/hang/BSOD.
I tried the same setup at work and had no problems installing OI b_148 in VB 4.1 on a Win7_64 host system.

-> This is NOT a Solaris host issue.
-> I have no idea why I can't seem to get 64-bit hosts running on this new system (ASUS E35M1-I). I ran about 4 iterations of Memtestx86+ on the installed memory, so that's not it. I tried different combinations of the CPU settings in the BIOS, but that didn't change things either. Maybe this is a hardware problem with this board?

Any suggestions?
-TLB

[TheLastBoyscout]

It seems the issue I am encountering is really a VirtualBox issue with AMD E-350 systems. Looks like it's going to be fixed with VirtualBox 4.1.2

This thread however is about a crash that happened on an Intel P4 or Celeron D.

-TLB

[Ramshankar]

Yes but the VBox.log from #8581 shows the reporter is using Intel and not AMD