VirtualBox

Opened 10 years ago

Closed 10 years ago

#12326 closed defect (duplicate)

Machine left in dock that cant be shutdown in OSX Mavericks

Reported by: scaseman Owned by:
Component: network Version: VirtualBox 4.3.2
Keywords: Mavericks Cc:
Guest type: Windows Host type: Mac OS X

Description

Hi,

After upgrading to OSX Mavericks I cannot shutdown a 'ghost' VM that remains once I shutdown my VMs

reading the forums people are saying it is if you use the 'Host Only' network which I need to use.

The only way I can get my machine to shutdown is to press and hold the power until it forces shutdown

Regards

Change History (4)

comment:1 by KAZA51, 10 years ago

Same problem regardless of the network emulation mode (BRIDGED, NAT, even "not attached"). Macbook pro retina, OS X 10.9 "mavericks"

comment:2 by Frank Mehnert, 10 years ago

We are able to reproduce this problem. No fix in sight yet though but we see it only with hostif networking. It is sufficient if one hostif network interface is configured for a VM, the guest is booted and the guest retrieves an IP. When the VM is then terminated, the VBoxNetDHCP service continues to run and even after terminating it, there will be some 'ghost' dock icon which can only be removed by doing sudo kextunload -b org.virtualbox.kext.VBoxNetAdp

in reply to:  2 comment:3 by BeMathis, 10 years ago

Replying to frank:

We are able to reproduce this problem. No fix in sight yet though but we see it only with hostif networking. It is sufficient if one hostif network interface is configured for a VM, the guest is booted and the guest retrieves an IP. When the VM is then terminated, the VBoxNetDHCP service continues to run and even after terminating it, there will be some 'ghost' dock icon which can only be removed by doing sudo kextunload -b org.virtualbox.kext.VBoxNetAdp

While this command will shut down the VBoxNetDHCP service and remove the ghost dock icon it will also completely kill whatever process is serving up your host-only network adaptor. I tried to execute a sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist to restart whatever service had been halted but I was still missing my vboxnet0 network adaptor and had to restart my machine to get things back in working order.

I would not advise using the command @frank has posted unless you are trying to shut-down your machine.

I have tried sudo kextload -b org.virtualbox.kext.VBoxNetAdp but that command will fail with the error org.virtualbox.kext.VBoxNetAdp failed to load - (libkern/kext) not found; check the system/kernel logs for errors or try kextutil(8).

Last edited 10 years ago by BeMathis (previous) (diff)

comment:4 by Frank Mehnert, 10 years ago

Resolution: duplicate
Status: newclosed

Marking this as duplicate of #12241. We are working on a fix.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use