Opened 14 years ago
Last modified 12 years ago
#6472 closed defect
vboxdrv runs kernel out of memory — at Version 5
| Reported by: | Daryll Strauss | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 3.1.6 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description (last modified by )
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.
Host:
Running latest Fedora 12
kernel 2.6.32.10-90.fc12.x86_64
Guest:
Running Fedora 11
bridged networking
- Export a file system from the host computer
- Mount the file system on a non-guest computer
- Write a bunch of files to the file system from the non-guest
Eventually the host computer starts to crash as the slab fails to allocate memory. Repeated the test three times and reproduced the problem each time. Stopped running the virtual machine and ran the same test and it worked fine.
I'm attaching one of the oops' when this happened.
Change History (6)
by , 14 years ago
follow-up: 3 comment:2 by , 14 years ago
I mean, is this TCP or UDP, any hint to reproduce? How long does it take for you to reproduce this host oops?
follow-up: 4 comment:3 by , 14 years ago
Replying to frank:
I mean, is this TCP or UDP, any hint to reproduce? How long does it take for you to reproduce this host oops?
Sorry I didn't see the follow up until now. I was writing files to the server file system using NFSv3. By default that's UDP as I recall.
comment:4 by , 14 years ago
Replying to daryll:
Replying to frank:
I mean, is this TCP or UDP, any hint to reproduce? How long does it take for you to reproduce this host oops?
Sorry I didn't see the follow up until now. I was writing files to the server file system using NFSv3. By default that's UDP as I recall.
Oh. And I can reproduce it pretty quickly (a few minutes), but I was writing a sequence of 12MB files, so it around a GB total.
comment:5 by , 14 years ago
| Description: | modified (diff) |
|---|
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?
Kernel oops