-
Notifications
You must be signed in to change notification settings - Fork 478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BoxManage.exe: error: Failed to create the host-only adapter (FPP) #288
Comments
ok I also found a fix the last error 👍 :
My laptop had a BIOS update like 3 days ago, it could be related. |
@brokedba The As you found, you can work around the issue by temporarily setting User Account Control to "Never notify". (But please don't leave it set that way--it could allow malware to run with administrator permissions.) I hope this helps. |
@PaulNeumann of course that's why I said "temporary" ;). thank you.
As the usual 12c zipped installables aren't images |
I don't think so. As far as I know, 12c images have to be created from an installed Oracle home. |
I thought so but I wanted to confirm. |
Thank you @PaulNeumann, I can create a new enhancement thread if it's more appropriate and since the OP is a not really related. |
Hello @brokedba , such request can not be implemented into the code as the main problem is that Oracle is shipping the 12.1 binaries in a form that the rhpctl import as zip can not works. Moreover the host2 is created as ready target w/o any oracle binaries as the idea is to offer the possibility to do practice on shipping the RDBMS to it (as documented on the bottom of the readme, see "FPP commands you could test postdeploy based on the configuration file above") |
Hi @rcitton . Thanks for the build and I actually tried them (importing and shippping homes). However, using it to practice on 18/19c releases won't reflect the current customers environments state where they're all being busy upgrading to 19c from 12c. I don't believe it's just me but waiting until everybody is migrated to 19c kind of loses its(FPP) main purpose . |
Hi @brokedba thank you for your feedback. FPP is not only an upgrade utility is doing much more. Sure the upgrade capability is one of the most important but as 11g, 12c shiphome are not in the "zip format" ive decided to skip them and show some other capabilities such a gold image import, workingcopy creation, db creation.... Having the vagrant env you are free to do practice with the upgrade too focusing on the FPP commands only. The VagrantFPP idea is to provide a simple env (in short time) where play with FPP. |
yes you can , but I wish Github can display the closed ones by default or when an issue has a fix it would recorded somewhere so people won't open duplicate question again . |
I am experiencing the same issue also, using Vagrant and I have the following output after a long wait time: There was an error while executing "VBoxManage" a CLI used by Vagrant Command: ["hostonlyif", "create"] Stderr: 0%... one of the guys on the team has a project and this means that I cannot assist him on this as I have the issue above, its my work laptop and I have tried everything from removing Hyper-V, uninstalling the Hyper-V interface in device management, My personal laptop works fine with this however. Edit: I have since realized that I have Crowdstrike Falcon Sensor installed as my AV and as such I think this is blocking the creation of the host only interface and I don't have the ability to disable albeit temporarily even to test, but I assume this is why I am receiving the message above, if anyone can confirm that would be great. |
closing with workaround defined as "brokedba commented on Aug 2, 2020" above:
|
Same issue here, Windows 11. In my case I get the UAC dialogs, select yes as usual, but still hangs.
|
Fixed by downgrading to 6.1.28 |
Description
Hi,
I am having a problem with the step that creates the HostOnly adapter .
The vagrant up hangs then throws the below error . I am almost certain that it's linked to both virtualBox and windows 10 as I saw a lot of threads on StackoverFlow describing the same network error. but I hoped someone had already gone through this and found a fix.
Environment (please complete the following information):
**- Host OS:**Windows 10 Home
- Vagrant version: Vagrant 2.2.7
- Vagrant provider: VirtualBox:
- VirtualBox version: 6.1.8r137981
Additional information
By the way , I tried to do it through the GUI console and it works there is just a windows confirmation pop up that I have to click on.
Thank you
The text was updated successfully, but these errors were encountered: