Changes between Initial Version and Version 1 of Ticket #12262, comment 4

Timestamp:: Apr 4, 2014 7:19:48 AM (11 years ago)
Author:: smbear

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #12262, comment 4

-              initial
+              v1
 I've encountered the same problem on Ubuntu 12.04 LTS. The solution proposed by atixk works for auto-start, but it doesn't work for auto-shutdown. The problem is that if there is an host-only interface configured, system is unable to `rmmod vboxnetadp` on reboot or poweroff of the host.
+I've encountered the similar problem on Ubuntu 12.04 LTS. The solution proposed by atixk works for auto-start, but it doesn't work for auto-shutdown - on auto-shutdown, //e.g. when host is going to reboot//, `vboxdrv stop` hangs and blocks shutdown of the host. The problem seems to be that if there is an host-only interface configured, host system is unable to do `rmmod vboxnetadp` (host hangs) on reboot or poweroff of the host.
 In `dmesg` one can see:
 …
 ''Basically: `vboxdrv` has to be '''started before''' `vboxautostart-service` and it has to be '''stopped after''' `vboxautostart-service`.''
+Another problem is that if I connect to guest using SSH (//guest OS is also Ubuntu 12.04 LTS, guest has two interfaces configured: a bridged and a host-only interface, ssh connection uses the bridged interface//), guest receives ACPI shutdown signal, SSH client informs that connection is lost, but host is unable to reboot - it again hangs trying to unload vboxnetadp. In processes running on host I can see that `VBoxHeadless` didn't exit. Killing it makes possible to unload the module.
+For this I've applied a '''workaround''': in `vboxautostart-service` in function `stop()` I've added `sleep 3` just before `return $RETVAL`. This seems to resolve the problem.
 Details of `virtualbox-4.3` package:
   {{{
 …
 (...)
 }}}