VirtualBox

Opened 14 years ago

Closed 14 years ago

#6899 closed defect (fixed)

Upgrade 3.1.8 to 3.2.0 and 3.2.2 - GMMR0AllocatePages error when starting existing VM => Fixed in SVN

Reported by: Jack Whitehead Owned by:
Component: VM control Version: VirtualBox 3.2.2
Keywords: GMMR0AllocatePages Cc:
Guest type: Windows Host type: Solaris

Description

I upgraded from 3.1.8 to 3.2.0. When starting an existing VM (WindowsXP or Linux (Fedora13) from the GUI, the VM console opens and then closes follwed by a popup window with the following error message... GMMR0AllocatePages failed to allocate 1 pages (VERR_NOT_SUPPORTED)

My host is OpenSolaris snv_134. This same behavour occurs with 3.2.0 and 3.2.2.

When I go back to 3.1.8, all is well.

I found a forum message describing a similar problem with a suggestion to check VDI and Machine paths. I did that and found them to be correct. I also checked the Storage controller as suggested and found it to be correct as well.

Attachments (4)

VBox322_Screenshot.png (158.9 KB ) - added by Jack Whitehead 14 years ago.
Screenshot
VBox.log (27.5 KB ) - added by Nicolai Schwindt 14 years ago.
Logfile of one machine which fails
cpuinfo (1.1 KB ) - added by Nicolai Schwindt 14 years ago.
prtdiag and psrinfo of the host
install-error (236 bytes ) - added by Nicolai Schwindt 14 years ago.
error while install 3.2.4

Download all attachments as: .zip

Change History (15)

by Jack Whitehead, 14 years ago

Attachment: VBox322_Screenshot.png added

Screenshot

comment:1 by Nicolai Schwindt, 14 years ago

Same effect here with solaris 10. I am getting the idea it depends on what processor use have. The machine which has this problem is a pentium-m, newer processors do work.

comment:2 by Jack Whitehead, 14 years ago

You may be correct regarding the processor type. I have been using an old AthlonXP 2600+ up until yesterday. I have coincidently had an OpenSolaris shutdown failure followed by the much feared and dreaded boot-archive sync problem that I couldn't recover from. Facing an OS reinstall I decided to do the long overdue hardware upgrade (AMD Phenom II 965 + 4GB) so I can run more VMs. That is all done now and I've just installed VirtualBox 3.2.4 as well. This is all working well now.

So, I do not know if 3.2.4 or the hardware upgrade (or both) fixed the problem for me but I do know it is fixed.

comment:3 by Nicolai Schwindt, 14 years ago

As I did try 3.2.4 on the same Hardware - I can say it the processor upgrade.

comment:4 by Sander van Leeuwen, 14 years ago

VBox.log from such a session would be helpful.

by Nicolai Schwindt, 14 years ago

Attachment: VBox.log added

Logfile of one machine which fails

by Nicolai Schwindt, 14 years ago

Attachment: cpuinfo added

prtdiag and psrinfo of the host

by Nicolai Schwindt, 14 years ago

Attachment: install-error added

error while install 3.2.4

comment:5 by Ramshankar Venkataraman, 14 years ago

This is most likely the case where the 32-bit vbox driver on Solaris trying to use unimplemented memory allocation methods. I'll try to get this fixed soon. Thank you for the report.

comment:6 by Ramshankar Venkataraman, 14 years ago

Summary: Upgrade 3.1.8 to 3.2.0 and 3.2.2 - GMMR0AllocatePages error when starting existing VMUpgrade 3.1.8 to 3.2.0 and 3.2.2 - GMMR0AllocatePages error when starting existing VM => Fixed in SVN

Fixed in SVN and will be part of the next VBox release. Thanks.

in reply to:  6 comment:7 by Scott, 14 years ago

Replying to ramshankar:

Fixed in SVN and will be part of the next VBox release. Thanks.

I have installed the latest release 3.2.4 on OpenSolaris 2009.06 and I am still seeing this problem. This is not an upgrade. Both the Host OS and VirtualBox are fresh installs.

comment:8 by Ramshankar Venkataraman, 14 years ago

The fix is not in 3.2.4, it was fixed yesterday and will be part of the next VirtualBox release.

comment:9 by Scott, 14 years ago

Do you have a release date for the next version?

comment:10 by Ramshankar Venkataraman, 14 years ago

(Un)fortunately no. If I get some free time tomorrow I will try upload a build with the fix for you guys, don't hold your breath for that though.

comment:11 by Sander van Leeuwen, 14 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use