Ticket #7799 (closed defect: obsolete)
Modules cannot be unloaded on Solaris 10
|Reported by:||laurent||Owned by:|
Description (last modified by ramshankar) (diff)
On a patched Solaris 10U9, when trying to update from 3.2.10 to 3.2.12, the system refuses to unload the modules.
# modinfo | grep vbox 150 fffffffff04c9808 a90 226 1 vboxnet (VirtualBox NetAdp 3.2.10r66523) 152 fffffffff0524000 27db0 34 1 vboxdrv (VirtualBox HostDrv 3.2.10r66523) 216 fffffffff0e3c000 7230 227 1 vboxflt (VirtualBox NetDrv 3.2.10r66523) 216 fffffffff0e3c000 7230 - 1 vboxflt (VirtualBox NetMod 3.2.10r66523) # modunload -i 150 can't unload the module: Device busy # modunload -i 152 can't unload the module: Device busy # modunload -i 216 can't unload the module: Device busy
VirtualBox was closed before starting to pkgrm, and after uninstall, ifconfig -a reports no vboxnet anymore. FWIW, the same happened when upgrading from 3.2.8 to 3.2.10 on a patched S10u8 at the time. I know a reboot will clear this, but it is not always practical to reboot only for a virtualBox upgrade.
- Status changed from new to closed
- Resolution set to worksforme
- Status changed from closed to reopened
- Resolution worksforme deleted