VirtualBox

Changes between Initial Version and Version 5 of Ticket #6472


Ignore:
Timestamp:
04/09/10 07:47:21 (4 years ago)
Author:
frank
Comment:

Do I understand you correct that the guest computer is not directly involved into the network traffic? That is, a remote host has a directory of the VBox host mounted and the remote host writes to that mounted directory and after some time, the VBox host crashes? And I assume this does not happen if you don't have a VM running at the VBox host, correct?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6472 – Description

    initial v5  
    11 
    2 It appears that performing a lot of network traffic with the host computer while a VirtualBox image is running can cause the kernel to run out of memory. 
     2It appears that performing a lot of network traffic with the host computer while a !VirtualBox image is running can cause the kernel to run out of memory. 
    33 
    4 Host: 
    5 Running latest Fedora 12 
     4Host:[[BR]] 
     5Running latest Fedora 12[[BR]] 
    66kernel 2.6.32.10-90.fc12.x86_64 
    77 
    8 Guest: 
    9 Running Fedora 11 
     8Guest:[[BR]] 
     9Running Fedora 11[[BR]] 
    1010bridged networking 
    1111 
    12 Export a file system from the host computer 
    13 Mount the file system on a non-guest computer 
    14 Write a bunch of files to the file system from the non-guest 
     12 * Export a file system from the host computer 
     13 * Mount the file system on a non-guest computer 
     14 * Write a bunch of files to the file system from the non-guest 
    1515 
    1616Eventually the host computer starts to crash as the slab fails to allocate memory. 

www.oracle.com
ContactPrivacy policyTerms of Use