VirtualBox

Opened 13 years ago

Last modified 8 years ago

#7799 closed defect

Modules cannot be unloaded on Solaris 10 — at Version 6

Reported by: Laurent Blume Owned by:
Component: host support Version: VirtualBox 3.2.10
Keywords: Cc:
Guest type: other Host type: Solaris

Description (last modified by Ramshankar Venkataraman)

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.

Change History (7)

comment:1 by Ramshankar Venkataraman, 13 years ago

When you performed a pkgrm what error did you get? Could you paste the output of pkgrm? Was there any VBox processes still running?

by Laurent Blume, 13 years ago

Attachment: vbox_unload_error.txt added

modunload issue on pkgrm

comment:2 by Laurent Blume, 13 years ago

I attached a file showing the issue with version 4.0.6.

I rebooted the system without VBox, so nothing loaded on boot. I did a pkgadd then immediately a pkgrm, without starting anything: module unloading failed.

comment:3 by Ramshankar Venkataraman, 13 years ago

Resolution: worksforme
Status: newclosed

Is this problem still persistent with latest VirtualBox versions? If so please re-open it. Closing for now as it was never reproducible and no other users report this issue on S10.

comment:4 by LAGoldstein, 11 years ago

I am having this same problem on unpatched Solaris 10u6 trying to remove 4.0.4 so I can install 4.2.4. Now I can't install either version without getting the modunload errors at the end of pkgadd (pkgrm shows the same error at the start of the run). It's good to know that a reboot will clear this, but it is an inconvenience.

Checking for older bits...
   - Unloaded: Web service
   - Unloaded: Balloon control service
   - Unloaded: Zone access service
can't unload the module: Device busy
   - Unloading: NetAdapter module ...FAILED!
## ERROR!! Failed to remove older/partially installed bits.
pkgadd: ERROR: postinstall script did not complete successfully

Installation of <SUNWvbox> failed.

And here's the output of modinfo and modunload:

lucid<131># modinfo|grep vbox
142 ffffffffef9ff730    b00 226   1  vboxnet (VirtualBox NetAdp 4.0.4r70112)
144 ffffffffefb1a000  2c058 225   1  vboxdrv (VirtualBox HostDrv 4.0.4r70112)
lucid<132># modunload -i 142
can't unload the module: Device busy
lucid<133># modunload -i 144
can't unload the module: Device busy

comment:5 by Giacomo, 11 years ago

Resolution: worksforme
Status: closedreopened

Sorry but it doesn't "worksforme" either. Solaris 10u11.

pkgrm fails with:

...
## Executing preremove script.
Removing VirtualBox services and drivers...
   - Unloaded: Web service
   - Unloaded: Balloon control service
   - Unloaded: Autostart service
   - Unloaded: Zone access service
can't unload the module: Device busy
   - Unloading: NetAdapter module ...FAILED!
can't unload the module: Device busy
   - Unloading: Host module ...FAILED!
Done.
...

and leaves:

# modinfo | grep vbox
216 fffffffff8a67000  34f00 258   1  vboxdrv (VirtualBox HostDrv 4.2.6r82870)
217 fffffffff89785a0    ce0 259   1  vboxnet (VirtualBox NetAdp 4.2.6r82870)

# modunload -i 216
can't unload the module: Device busy

which stops me installing any versions. Hints on how to clear manually without reboot welcomed.

comment:6 by Ramshankar Venkataraman, 11 years ago

Description: modified (diff)

That doesn't look right, looks like something is holding vboxnet0 referenced.

Anyway, you can forcefully unload the drivers after kicking out vboxnetX.

Try this as root:

ifconfig vboxnet0 unplumb
/opt/VirtualBox/vboxconfig.sh --preremove
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use