If I don't have a host-only interface active on a given VM, it will stop cleanly. I have found that this problem (at least in my case) is caused by the host-only interface ("vboxnet0" on my machine). This is a Mavericks regression and finding the fix is more difficult. The other problem is that the VBoxNetAdp KExt has to be disabled. We fixed this problem and the fix will be available soon. The first problem is that VBoxNetDHCP does not terminate automatically and prevents VBoxSVC from shutting down (4.3.0 regression).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |