virtualbox.org

Since upgrading to VB 5.0.5, I have been getting a number of
VBoxNetFlt: failed to allocate packet buffer
errors in my system log. The host is an OpenSuse 13.1 system with a 3.17 kernel. I was not getting these errors with an earlier version of VB. The host system software has not changed.

The current release of VirtualBox is 5.0.8. 5.0.5 was a test build.

I have a lot of "VBoxNetFlt: failed to allocate packet buffer" with VB 5.0.14 r105127 in my messages file. The system is a CentOS 7.2.1511 with a 3.10.0-327.4.5.el7.x86_64 kernel.
I somebody out who can help me, please?
Eberhard

Not with the information given so far. Please post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

Ok, here comes the logfile. And here is the last appearance in our messages log:

Feb  3 13:12:08 ikffws1 kernel: VBoxNetFlt: Failed to allocate packet buffer, dropping the packet.

Thanks a lot.

Eberhard

I don't see any "failed to allocate packet buffer" errors in the log provided. I do see is a lot of AsyncCompletion messages starting at 50 hours, but the log continues on to 137 hours, so it doesn't seem to be fatal.

VBox.log wrote: 00:00:00.028659 Installed Extension Packs:
00:00:00.028672 None installed!
...
50:22:15.679941 AsyncCompletion: Task 0x007f51d31bc880 completed after 13 seconds
101:12:54.207363 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
137:37:58.012801 AsyncCompletion: Task 0x007f525c5a7ac0 completed after 11 seconds

If I was you I would install the extension pack, that way you won't be restricted to talking OHCI (a.k.a. USB 1.1) for whatever (backup task?) starts up after 50 hours. Perhaps that will improve I/O throughput and reduce glitches in general.

If your problem persists then you'll have to raise a BugTracker ticket.

I'm seeing this as well. If I change the guest VM (windows) to use a NAT-ed interface rather than bridged across the physical nic, the problem goes away. So this appears to be an issue only when using a bridged interface in a guest.

I don't even need to have much network traffic to/from the guest but just a lot of network traffic on the host system.

I'm seeing this as well. If I change the guest VM (windows) to use a NAT-ed interface rather than bridged across the physical nic, the problem goes away. So this appears to be an issue only when using a bridged interface in a guest.

I don't even need to have much network traffic to/from the guest but just a lot of network traffic on the host system.

I see the same as ehagberg. Running Virtualbox 5.0.14 on Linux with a Linux VM (bridged NIC).

I, too, am seeing this issue. Thousands of errors:

kernel: VBoxNetFlt: Failed to allocate packet buffer, dropping the packet.

in my syslog.

I'm running VirtualBox 5.0.16 r105871, Extension Pack 5.0.16r105871 and the host system is running Ubuntu 15.10. All of my guests are using Guest Additions 5.0.17 r105913 and are configured with Bridged networking.

-Jeff

same

using bridged networking, yes vbox guest additions are installed

virtualkbox Version 5.0.24 r108355

[76492.273909] VBoxNetFlt: Failed to allocate packet buffer, dropping the packet.
[76492.273926] VBoxNetFlt: Failed to allocate packet buffer, dropping the packet.

any other information valuable to offer?

host = Fedora22, 4.4.13-200.fc22.x86_64
guest = Win10

Same here.

Host = Ubuntu 16.04
Guest = Ubuntu 16.04

I changed the guest network adapter to Virtio (was Intel). That improved the situation a bit.

Now it seems this only occurs when the host is under heavy load. I'm not running the guest OS as root.

I see this too with 5.0.26 r108824 on same U16.04 host and two guests with bridged network interfaces. Usually under heavy disk-IO.