VirtualBox

Changes between Initial Version and Version 1 of Ticket #18302, comment 1


Ignore:
Timestamp:
Jan 12, 2019 1:53:11 AM (6 years ago)
Author:
Socratis

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18302, comment 1

    initial v1  
    111. It's usually better and faster, if issues get first addressed in the [https://forums.virtualbox.org/ VirtualBox forums], a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no  need for another ticket to keep track of. For example, yours is '''not a bug''' and someone from the developers has to deal with it and close it as "'''Invalid'''".
    22
    3  But, Vagrant is not really supported, it has its own support channels. Unless you have this problem with a Vagrant-less setup. And to address the "`modprobe vboxsf failed`" message, that's a red herring. It's a non-issue. Unless you have another indication of a failed Guest Additions (GAs) installation, __that's not a problem__.
     3 But, Vagrant is not really supported, it has its own support channels. Unless you have this problem with a Vagrant-less setup, then we could continue this discussion...
     4
     5 And to address the "`modprobe vboxsf failed`" message, that's a red herring. It's a non-issue. Unless you have another indication of a failed Guest Additions (GAs) installation, __that's not a problem__.
    46
    572. You were supposed to follow these steps [https://www.virtualbox.org/newticket when you filed the bug], and provide

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette