Acknowledgement sent
to treaki <[email protected]>:
New Bug report received and forwarded. Copy sent to Debian Virtualbox Team <[email protected]>.
(Fri, 12 Dec 2014 14:15:07 GMT) (full text, mbox, link).
Subject: virtualbox: bug with vboxnet0, network-manageer and kernel messages
Date: Fri, 12 Dec 2014 15:08:01 +0100
Package: virtualbox
Version: 4.3.18-dfsg-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
some time it came up that my network manager grafical interface where it was circeling internely. as i klicked it i found out that it has to do with vboxnet0.
* What exactly did you do (or not do) that was effective (or
ineffective)?
i opened virtualbox to remove the not anymore needed network interface which resoultet in a freeze of the virtualbox gui. also ive got manny kernel error massages periodicly. After i recognised that output i killed the virtualbox gui using killall and the output stopped. i will attach the last lines of my dmesg in here...
* What was the outcome of this action?
for now it is working but i dont know if it will happen again if i add again a vboxnet0 device...
* What outcome did you expect instead?
that network manager dosnt get confused with vboxnet0, default configured manually without networkmanager maybe, and that i would be able to remove network interfaces without freezing guis and losts of dmesg errors.
here is the output
essage from syslogd@treakis-tp at Dec 12 14:58:32 ... 7:29
kernel:[90972.468070] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 14:58:43 ...
kernel:[90982.596077] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 14:58:53 ...
kernel:[90992.716040] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 14:59:03 ...
kernel:[91002.856082] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 14:59:13 ...
kernel:[91012.980054] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 14:59:23 ...
kernel:[91023.096067] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 14:59:33 ...
kernel:[91033.232076] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 14:59:43 ...
kernel:[91043.364077] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 14:59:54 ...
kernel:[91053.512060] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 15:00:04 ...
kernel:[91063.636053] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 15:00:14 ...
kernel:[91073.796085] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
Message from syslogd@treakis-tp at Dec 12 15:00:24 ...
kernel:[91083.940230] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
$ dmesg | tail
[91012.980054] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
[91023.096067] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
[91033.232076] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
[91043.364077] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
[91053.512060] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
[91063.636053] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
[91073.796085] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
[91083.940230] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
[91089.083913] device vboxnet0 left promiscuous mode
[91089.088161] vboxnetflt: 3 out of 284 packets were not sent (directed to host)
tahanks a lot and keep up the good work
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages virtualbox depends on:
ii adduser 3.113+nmu3
ii dpkg 1.17.21
ii libc6 2.19-12
ii libcurl3 7.38.0-3
ii libdmtx-python [python] 20140917-1
ii libgcc1 1:4.9.1-19
ii libgsoap5 2.8.17-1
ii libpng12-0 1.2.50-2+b1
ii libpython2.7 2.7.8-11
ii libsdl1.2debian 1.2.15-10
ii libssl1.0.0 1.0.1j-1
ii libstdc++6 4.9.1-19
ii libvncserver0 0.9.9+dfsg-6+b2
ii libvpx1 1.3.0-3
ii libx11-6 2:1.6.2-3
ii libxcursor1 1:1.1.14-1+b1
ii libxext6 2:1.3.3-1
ii libxml2 2.9.1+dfsg1-4
ii libxmu6 2:1.1.2-1
ii libxt6 1:1.1.4-1+b1
ii python 2.7.8-2
ii python2.7 2.7.8-11
ii zlib1g 1:1.2.8.dfsg-2
Versions of packages virtualbox recommends:
ii libgl1-mesa-glx [libgl1] 10.3.2-1
ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii virtualbox-dkms 4.3.18-dfsg-1
ii virtualbox-qt 4.3.18-dfsg-1
Versions of packages virtualbox suggests:
ii vde2 2.3.2+r586-1
ii virtualbox-guest-additions-iso 4.3.18-1
-- no debconf information
On 12/12/2014 07:38 PM, treaki wrote:
> $ dmesg | tail
> [91012.980054] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
> [91023.096067] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
> [91033.232076] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
> [91043.364077] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
> [91053.512060] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
> [91063.636053] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
> [91073.796085] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
> [91083.940230] unregister_netdevice: waiting for vboxnet0 to become free. Usage count = 1
> [91089.083913] device vboxnet0 left promiscuous mode
> [91089.088161] vboxnetflt: 3 out of 284 packets were not sent (directed to host)
This usually happens when you have reference count to the corresponding
module > 0.
In this case, I believe it is the vboxnet module. You should only see
the message, if you have active guest VMs, and you try to do a
virtualbox service restart. Are you doing anything of that sort ? If
yes, why ?
As for network manager, I have no clue if that can interfere. I don't
use network manager.
But I don't see any reason why it should.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
Acknowledgement sent
to Gevorg Abrahamian <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Virtualbox Team <[email protected]>.
(Wed, 10 Jun 2015 03:30:04 GMT) (full text, mbox, link).
Subject: vboxnet0 causes my XFCE suspend resume problems
Date: Tue, 09 Jun 2015 23:27:56 -0400
I have the same problem but there's more to this. After searching around
I came across a vbox ticket where I posted a comment
https://www.virtualbox.org/ticket/13873#comment:10 with my experience.
After this I kept searching and came across this bug. I hope this
information will help debug the issue further.
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.