VirtualBox

Changes between Initial Version and Version 1 of Ticket #2060


Ignore:
Timestamp:
09/04/08 14:28:56 (6 years ago)
Author:
frank
Comment:

Thanks for this report. This is a 2.0.0 regression which we can reproduce. The workaround is to use VBoxManage to create a new VM.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2060

    • Property Summary changed from VirtualBox crashes when creating new image on Mac OS X to VirtualBox crashes when creating new image
  • Ticket #2060 – Description

    initial v1  
    1 1. Installed VirtualBox 2.0 on MacBook Pro running Mac OS X 10.5.4. 
    2 2. Choose to create a new Ubuntu VM. 
    3 2. Attempt to create new image for that VM between 23 and 25 GB in size. 
    4 3. Virtualbox crashes. 
     1 1. Installed VirtualBox 2.0 on MacBook Pro running Mac OS X 10.5.4. 
     2 2. Choose to create a new Ubuntu VM. 
     3 2. Attempt to create new image for that VM between 23 and 25 GB in size. 
     4 3. Virtualbox crashes. 
    55 
     6{{{ 
    679/4/08 10:13:12 AM VirtualBox[47267] VirtualBox(47267,0xa003afa0) malloc: *** mmap(size=2147487744) failed (error code=12) 
    78*** error: can't allocate region 
     
    14159/4/08 10:13:14 AM com.apple.launchd[80] ([0x0-0x209209].org.virtualbox.app.VirtualBox[47267]) Stray process with PGID equal to this dead job: PID 47268 PPID 1 VBoxXPCOMIPCD  
    15169/4/08 10:13:14 AM com.apple.launchd[80] ([0x0-0x209209].org.virtualbox.app.VirtualBox[47267]) Exited abnormally: Bus error  
     17}}} 

www.oracle.com
ContactPrivacy policyTerms of Use