Custom Query (16363 matches)
Results (496 - 498 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14510 | obsolete | vboxadd.service startup times out on Fedora 22 boot | ||
| Description |
I recently started getting the following when booting my Fedora 22 guest system on my Windows 7 host. [...] systemd[1]: vboxadd.service start operation timed out. Terminating. [...] systemd[1]: Failed to start VirtualBox Linux Additions kernel modules. [...] systemd[1]: Unit vboxadd.service entered failed state. [...] systemd[1]: vboxadd.service failed. After some poking around I determined that the timeout occurred while executing the following in the vboxadd init script: if $MODPROBE -c 2>/dev/null | grep -q '^allow_unsupported_modules *0'; then
MODPROBE="$MODPROBE --allow-unsupported-modules"
fi
I changed the timeout specified in the vboxadd.service config file from 5 minutes to 10 minutes and the timeout no longer occurred. I should note that this timeout started happening only after some recent Fedora 22 updates. I had no problems previously. |
|||
| #3715 | fixed | vboxadd-timesync sets the guest os clock ahead of host by 1 hour | ||
| Description |
I have the following configuration. Vista 64 Host OS Ubuntu 9.0.4 Guest OS. The guest os clock is exactly one hour ahead of host clock. Both have right time zones set and I have turned off UTC in /etc/default/rcS file (UTC=NO). everytime i correct the date/time, after about 10 seconds, it resets the guest OS clock to be one hour ahead of host OS. I traced this problem to vboxadd-timesync. If this program is stopped, then clock stays correct. vboxadd-timesync adds one hour to guest os clock for unknown reasons. |
|||
| #2288 | fixed | vboxadd-timesync makes Etch/64 guests Xorg crash | ||
| Description |
After installing the Guest Additions in Debian Etch 64-bit, I find that X continuously restarts every few seconds. The problem is exasperated by typing on the keyboard into a guest window (like bash, or into gedit). The workaround I've discovered is to disabled timesync. Once the VirtualBox timesync is disabled, X no longer restarts. For example, if I run this, X wont restart anymore:
If at any point in time I run "/etc/init.d/vboxadd-timesync start", then X immediately starts crashing again. I've run into this exact problem with 2 different computers running Ubuntu 8.04-64bit and Debian Etch 64-bit as host. I've confirmed the "workaround" works the same in both situations. |
|||

