VirtualBox

Changes between Initial Version and Version 1 of Ticket #4256


Ignore:
Timestamp:
07/31/2009 09:09:02 AM (11 years ago)
Author:
frank
Comment:

It depends on your host how much memory you should assign to a VM. If there are many ressource-intensive applications running on your host then you should decrease the memory you assigned to the guest.

Apart from this, it is a known issue on Darwin that concurrent hard disk activity on the host will delay virtual hard disk operations in a VBox VM so that the guest gets confused because an IDE operation took too long. We are working on a workaround for that problem but the initial question for your system is where the high disk load comes from.

Btw, don't switch host and guest: The host is the physical machine (plus the operating system on it), the guest is living in the virtual machine.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4256

    • Property Summary changed from Host allocates more RAM than allowed and crashes to Guest allocates more RAM than allowed and crashes
  • Ticket #4256 – Description

    initial v1  
    1 the guest owns 2 gb RAM and the host is free to allocate 768MB of this. When I start ressource intensive operations on the guest, after a wgile all the RAM of the host is allocated. If there is no more free RAM available, the guest operation crashes. This phenomenon is reproducable, especially with different installer files. For example, it appeared with the Adobe Reader Installer or the Windows XP Service Pack 3. 
    2 First i thought, that the RAM-Module is damaged, but the after exchanging them from the old 2GB memory to new damage-free 4GB the same situation appeared after a while. 
     1The host owns 2GB RAM and the guest is free to allocate 768MB of this. When I start ressource intensive operations on the guest, after a wgile all the RAM of the host is allocated. If there is no more free RAM available, the guest operation crashes. This phenomenon is reproducable, especially with different installer files. For example, it appeared with the Adobe Reader Installer or the Windows XP Service Pack 3. 
    32 
    4 In the loggs there are the coresponding lines: 
    5 .... 
    6 00:03:33.373 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xca (9532623 usec ago) CmdIf1=0x00 (-1 usec ago) 
    7 00:03:33.526 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    8 00:03:33.537 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    9 00:03:33.547 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    10 00:03:33.557 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    11 00:03:33.567 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    12 00:03:33.577 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    13 00:03:33.587 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    14 00:03:33.598 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    15 00:03:33.609 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    16 00:03:33.619 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    17 00:03:33.630 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    18 00:03:33.640 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    19 00:03:33.653 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    20 00:03:33.664 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    21 00:03:33.675 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 
    22 00:03:35.599 PIIX3 ATA: execution time for ATA command 0xca was 11 seconds 
    23 00:03:35.599 PIIX3 ATA: Ctl#0: finished processing RESET 
    24 .... 
    25  
    26 (see attachement) 
     3First I thought, that the RAM-Module is damaged, but the after exchanging them from the old 2GB memory to new damage-free 4GB the same situation appeared after a while. 

www.oracle.com
ContactPrivacy policyTerms of Use