Opened 9 years ago
Last modified 9 years ago
#15697 new defect
Linux Additions should still be able to read network config without D-Bus
Reported by: | AxelFontaine | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 4.3.36 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | other |
Description
Currently lines 1472-1478 of /src/VBox/Additions/common/VBoxService/VBoxServiceVMInfo.cpp look like this:
rc = vgsvcVMInfoWriteUsers(); if (RT_FAILURE(rc))
break;
rc = vgsvcVMInfoWriteNetwork(); if (RT_FAILURE(rc))
break;
This unfortunately means that if vgsvcVMInfoWriteUsers() fails due to a missing system D-Bus, no network info is exposed as guest properties. There is no reason for this.
Suggestion: simply continue with vgsvcVMInfoWriteNetwork() even if vgsvcVMInfoWriteUsers() fails
This affects all currently supported VirtualBox versions.
You're right, the VM information / guest properties should continue to work, even in case some former enumeration part failed.
We're still interesting why this actually fails on your guest ...would you mind creating a verbose VBoxService log on your guest and attach that log to this defect then?
To start VBoxService in debug mode with verbose logging on a Linux guest (Debian-based, like Ubuntu etc):
Login as root, open a terminal window and do: # /etc/init.d/vboxadd-service stop Edit the file "/etc/init.d/vboxadd-service" by changing the line "daemon $binary > /dev/null" to "daemon $binary "-vvvv --logfile /var/log/VBoxService.log" > /dev/null" and save the file afterwards.
Then either the system needs to rebooted or VBoxService needs to be started again by doing a
# /etc/init.d/vboxadd-service start
This will start VBoxService in background, logging to /var/log/VBoxService.log. After the issue appeared again, please provide the logfile located in /var/log/VBoxService.log on the guest. Thanks!