VirtualBox

Ticket #6899 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

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

Reported by: jcw40 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

VBox322_Screenshot.png Download (158.9 KB) - added by jcw40 11 years ago.
Screenshot
VBox.log Download (27.5 KB) - added by nschwindt 11 years ago.
Logfile of one machine which fails
cpuinfo Download (1.1 KB) - added by nschwindt 11 years ago.
prtdiag and psrinfo of the host
install-error Download (236 bytes) - added by nschwindt 11 years ago.
error while install 3.2.4

Change History

Changed 11 years ago by jcw40

Screenshot

comment:1 Changed 11 years ago by nschwindt

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 Changed 11 years ago by jcw40

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 Changed 11 years ago by nschwindt

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

comment:4 Changed 11 years ago by sandervl73

VBox.log from such a session would be helpful.

Changed 11 years ago by nschwindt

Logfile of one machine which fails

Changed 11 years ago by nschwindt

prtdiag and psrinfo of the host

Changed 11 years ago by nschwindt

error while install 3.2.4

comment:5 Changed 11 years ago by ramshankar

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 follow-up: ↓ 7 Changed 11 years ago by ramshankar

  • Summary changed from Upgrade 3.1.8 to 3.2.0 and 3.2.2 - GMMR0AllocatePages error when starting existing VM to Upgrade 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.

comment:7 in reply to: ↑ 6 Changed 11 years ago by scottphares

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 Changed 11 years ago by ramshankar

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

comment:9 Changed 11 years ago by scottphares

Do you have a release date for the next version?

comment:10 Changed 11 years ago by ramshankar

(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 Changed 11 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use