virtualbox.org

One thing I did notice is you have not installed the Extension Pack How to install Extension Pack Which you should have received a warning that it was needed if the USB2 was enabled in the guest settings. Maybe you should install that and see if it works.

Exactly.

Boot Ubuntu: all guests work fine.
Boot Windows: guests don't work at all (nothing happens).

Perryg wrote:One thing I did notice is you have not installed the Extension Pack How to install Extension Pack Which you should have received a warning that it was needed if the USB2 was enabled in the guest settings. Maybe you should install that and see if it works.

Installed it, no difference.

OK but I need information to be able to figure out why. Can you post a log file of an Ubuntu guest that you have installed while in Windows after you have installed the ExtPack and tried to boot the guest.

I'm not able to install any guest, so that includes Ubuntu. Here's the log.

00:00:01.097 Host RAM: 3066MB RAM, available: 483MB
00:00:01.215 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)

You are assigning more RAM to the guest than you have available. You need to free up memory.

Perryg wrote:00:00:01.097 Host RAM: 3066MB RAM, available: 483MB
00:00:01.215 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)

You are assigning more RAM to the guest than you have available. You need to free up memory.

I know, but freeing op RAM really doesn't change anything. I've tried freeing up my RAM like a 100 times, it does not change anything. RAM is not the issue, I can be pretty sure of that. I can 100% guarantuee you that if I free up about 1.5GB RAM, the log will exactly look the same. Again, RAM is not the issue, I've double/triple/quadruple checked that myself like a 100 times. It's not like I haven't been trying to find out the cause of the problems myself, if RAM was the issue I would be able to at least boot a guest OS properly at least once. Again: I have never ever ever succesfully booted a 64-bit guest OS or the installer of a 64-bit guest OS. Never. VirtualBox doesn't just "sometimes" not work, it nevers works and it never has on this Windows installation. Not a single time, and I've tried it about a 100 times (not emphasizing here).

Here's a log without the RAM error, still shows exact the same behaviour. RAM is definitely not the issue. Please remember this.

Then don't send logs that show the low memory. I can guarantee that if you try to install with the available memory lower than the assigned it will fail every time.

All the second log shows is the guest entered a console power down. Meaning not an S5 power down (user asked to shut down the system). At this point I am not sure why you can not install 64-bit guests. The log shows VMX as available and you have proven that you can in fact install when booted in Linux so hardware is not the issue.

What exactly do you see when you are trying to install? Are there any error messages, or does the guest just power down?

Perryg wrote:Then don't send logs that show the low memory. I can guarantee that if you try to install with the available memory lower than the assigned it will fail every time.

All the second log shows is the guest entered a console power down. Meaning not an S5 power down (user asked to shut down the system). At this point I am not sure why you can not install 64-bit guests. The log shows VMX as available and you have proven that you can in fact install when booted in Linux so hardware is not the issue.

What exactly do you see when you are trying to install? Are there any error messages, or does the guest just power down?

The console power down is me shutting down the VM because it's not showing any sign of life, again . I don't see anything, just a black screen. I know what you're saying about RAM, but the install doesn't fail, it doesn't even start.

Do you have XP mode installed in the Windows 7 host?

Perryg wrote:Do you have XP mode installed in the Windows 7 host?

No.

I am having the exact same problem. Trying to install 64-bit Debian 6.0.5 guest from the standard debian-6.0.5-ia64-netinst.iso

I get to the same place, "Guest Log: BIOS: Booting from CD-ROM..." and no further.

Installing the 32-bit version goes fine. Seems like the exact same issue marcoc is having. Windows 7 32-bit host.

Okay, issue was I was using the ia64 installer when I need the amd64 installer (this is on an Intel i5).

The debian-6.0.5-amd64-netinst.iso installer is working fine.

Sorry for the noise. marcoc, perhaps you have the same issue?

No, he has the low memory issue as indicated by the log he posted - so there's no need to speculate about his problem.

mpack wrote:No, he has the low memory issue as indicated by the log he posted - so there's no need to speculate about his problem.

RAM is not the cause of the problem. I've proven that.

marcoc wrote:

Perryg wrote:00:00:01.097 Host RAM: 3066MB RAM, available: 483MB
00:00:01.215 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)

You are assigning more RAM to the guest than you have available. You need to free up memory.

I know, but freeing op RAM really doesn't change anything. I've tried freeing up my RAM like a 100 times, it does not change anything. RAM is not the issue, I can be pretty sure of that. I can 100% guarantuee you that if I free up about 1.5GB RAM, the log will exactly look the same. Again, RAM is not the issue, I've double/triple/quadruple checked that myself like a 100 times. It's not like I haven't been trying to find out the cause of the problems myself, if RAM was the issue I would be able to at least boot a guest OS properly at least once. Again: I have never ever ever succesfully booted a 64-bit guest OS or the installer of a 64-bit guest OS. Never. VirtualBox doesn't just "sometimes" not work, it nevers works and it never has on this Windows installation. Not a single time, and I've tried it about a 100 times (not emphasizing here).

Here's a log without the RAM error, still shows exact the same behaviour. RAM is definitely not the issue. Please remember this.

Or do you really need me to try to boot a lightweight Linux distribution with 2GB free of RAM, so that I can show you a log that shows exactly the same behaviour? Because I can do that if you don't believe me . It really does make much much more sense that two seperate causes cause my system to not be able to boot any 64-bit .iso or .vhd at all... .

More than 2GB of free RAM, trying to boot Lubuntu, again, nothing happens. Tell me how this is a RAM issue. Especially because everything works fine under Ubuntu (and no, I don't add extra RAM every time I boot Ubuntu).