Opened 14 years ago
Closed 14 years ago
#7893 closed defect (duplicate)
Fail to boot VM with 2048 MB of memory allocated
| Reported by: | pablo | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.0 |
| Keywords: | Windows 2003 | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
Hi,
I have 12 GB of RAM on my Host O/S. For some of my VM's, I give them 2 GiB of RAM. I noticed that with 4.0.0, these VM's fail to boot unless I decrease their memory to 1 GiB. I haven't attempted to find the right amount of RAM where the VM will boot but will do so if it's necessary.
I'm attaching to .log files: one where the VM fails to boot (2 GiB) and one where it succeeds (1 GiB)
I also observe when the VM fails to boot, the `Oracle VM VirtualBox Manager' fails to repaint. Other concurrently running VM's (with less RAM) continue to run.
Please let me know if there's additional data to collect.
Cheers, -pablo
Attachments (4)
Change History (14)
by , 14 years ago
| Attachment: | VBox-1024MB-of-RAM.log added |
|---|
comment:1 by , 14 years ago
So fails to boot means the VM crashes? In that case you should be able to create a core dump. If so, please contact me at frank _dot_ mehnert _at_ oracle _dot_ com and I will tell you a server where you can upload the core dump.
comment:2 by , 14 years ago
Hi Frank,
I'm sorry I wasn't clear. No, the VM doesn't crash, it hangs at the point listed above.
Can I send a signal to the process to core it? Not sure if that'd be useful.
Please advise.
comment:4 by , 14 years ago
Core'd and I've sent you an e-mail for the server credentials.
Thank you! -pablo
comment:6 by , 14 years ago
We found something. Could you check if this test build fixes your issue (boot with 2048MB)?
by , 14 years ago
| Attachment: | cpu_pegged.vbox.strace.bz2 added |
|---|
strace with 4.0.3 tests - CPU pegged on System (not User)
by , 14 years ago
VBox.log with 4.0.3 tests - CPU pegged on System (not User)
comment:8 by , 14 years ago
Howdy, unfortunately the latest build didn't address the issue. When I set the VM's memory to 2048, the VM pegged one of my CPU's. I've attached both strace' and VBox.log' Please let me know if you'd like me to collect additional data and/or try something different.
Cheers, -pablo
comment:9 by , 14 years ago
I forgot to mention with the latest build, when I revert the memory to, say 1024, the VM can boot.
comment:10 by , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Actually this is a duplicate of #7930. Disabling nested paging would work around this bug. Or use a non-PAE guest.
Successful boot