Custom Query (16363 matches)
Results (490 - 492 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4493 | fixed | vboxbnet disapear and/or change their ip => check with 3.0.4 | ||
| Description |
after setting 3 vboxnet with ip 192.168.1.1/15/155 (no dhcpd). I check in the cli with ifconfig and see only vboxnet0 and 1 with correct ip. I reopened the vbox manager and reentered all vboxnet and this time ifconfig shows them all. after starting the vm and checking the ip's - they are all changed to the ip of the first vboxnet0.... I'm running ubuntu jaunty with latest vbox (3.0.2) |
|||
| #12262 | fixed | vboxautostart-service is not executed correctly on startup in Debian | ||
| Description |
Somehow the startup script in the Debian dist does not auto start configured auto start engines. To fix this it is necessary to tweak the vboxautostart-service script not to exit when the modules are not detected. I don't know why but somehow the checking of loaded modules fails, probably it is because of some background startup. However the modules are loaded after start and also auto startup works when simply disabled the checking. Of course it breaks handling of real problems. Please see following discussion for some users haveing this issue: https://forums.virtualbox.org/viewtopic.php?f=11&t=51529 *** vboxautostart-service.orig 2013-10-26 22:28:25.000000000 +0200
--- vboxautostart-service 2013-10-26 22:09:13.000000000 +0200
*************** start() {
*** 271,277 ****
begin_msg "Starting VirtualBox VMs configured for autostart";
vboxdrvrunning || {
fail_msg "VirtualBox kernel module not loaded!"
! exit 0
}
PARAMS="--background --start --config $VBOXAUTOSTART_CONFIG"
--- 271,277 ----
begin_msg "Starting VirtualBox VMs configured for autostart";
vboxdrvrunning || {
fail_msg "VirtualBox kernel module not loaded!"
! ## exit 0
}
PARAMS="--background --start --config $VBOXAUTOSTART_CONFIG"
|
|||
| #4570 | fixed | vboxapisetup.py - No module named distutils.core => fixed in SVN | ||
| Description |
Attempting to install VirtualBox-3.0.2-SunOS-r49928.pkg on Solaris Nevada (snv_119) and saw this error: pkgadd -d VirtualBox-3.0.2-SunOS-r49928.pkg
[...]
## Executing postinstall script.
Loading VirtualBox kernel modules...
VirtualBox Host kernel module loaded.
VirtualBox NetAdapter kernel module loaded.
VirtualBox NetFilter kernel module loaded.
VirtualBox USB kernel module loaded.
Configuring services and drivers...
Installing Python bindings...
Traceback (most recent call last):
File "./vboxapisetup.py", line 17, in ?
from distutils.core import setup
ImportError: No module named distutils.core
Updating boot archive...
Done.
Installation of <SUNWvbox> was successful.
My system was installed with the SUNWCuser "cluster", ("End User System Support") not the "full distribution". The installed Python packages are: gwr# pkginfo |grep SUNWPython
GNOME2 SUNWPython The Python interpreter, libraries and utilities
GNOME2 SUNWPython-extra Supplemental Python libraries and utilities
GNOME2 SUNWPython25 The Python interpreter, libraries and utilities
GNOME2 SUNWPython26 The Python interpreter, libraries and utilities
GNOME2 SUNWPython26-extra Supplemental Python libraries and utilities
It looks like distutils.core file is part of this package: SUNWPython-devel This solved the problem for me: pkgadd -d ... SUNWPython-devel
pkgrm SUNWvbox
pkgadd -d VirtualBox-3.0.2-SunOS-r49928.pkg
|
|||

