identifysun
Repos
54
Followers
21
Following
179

Events

started
Created at 1 week ago
issue comment
Vagrant 2.3.2 and Virtualbox 7.0.2 - Private Network Interface

I seem to have the same issue with Vagrant 2.3.2 and VirtualBox 6.1.40 on Fedora 36: vagrant up doesn't work anymore. I've downgraded to 6.1.36 and my vagrant boxes work again. I've tried the workaround with the virtualbox_intnet: true, but that didn't work for me. So, maybe not quite the same issue, but it seemed network related. I couldn't find any real errors in the logging. It just didn't boot properly.

Please use the latest versions of vagrant and virtualbox

$ vagrant --version
Vagrant 2.3.3

$ VBoxManage --version
7.0.2r154219
Created at 2 weeks ago
started
Created at 2 weeks ago
Created at 2 weeks ago
Created at 2 weeks ago
Created at 3 weeks ago
Created at 3 weeks ago
Created at 3 weeks ago
issue comment
Vagrant 2.3.2 and Virtualbox 7.0.2 - Private Network Interface

I found some solution. ss

Few steps: (https://apple.stackexchange.com/questions/408154/macos-big-sur-virtualbox-error-the-virtual-machine-has-terminated-unexpectedly-d) 1) sudo su csrutil clear 2) Unistall from official unistaller andre-install Vbox 3) If prompted, go to System Preferences - Privacy - General and accept the extensions 4) Reebot 5) Add at Vagrant file virtualbox__intnet: true to your config.vm.network -> https://discuss.hashicorp.com/t/vagrant-up-fails-on-macos-13-x-ventura-with-latest-2-3-2-vagrant-release/46043/13 6) VirtualBoxVM --startvm vagrant vagrant up

This works for me.

Thanks @JakubSzczerba , It 's Ok for me.

Created at 4 weeks ago
Created at 4 weeks ago
identifysun delete branch dependabot/maven/org.jenkins-ci.plugins-plugin-4.49
Created at 1 month ago

Bump plugin from 4.48 to 4.49

Bumps plugin from 4.48 to 4.49.


updated-dependencies:

  • dependency-name: org.jenkins-ci.plugins:plugin dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #11 from identifysun/dependabot/maven/org.jenkins-ci.plugins-plugin-4.49

Bump plugin from 4.48 to 4.49

Created at 1 month ago
pull request closed
Bump plugin from 4.48 to 4.49

Bumps plugin from 4.48 to 4.49.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 1 month ago

Bump bom-2.332.x from 1643.v1cffef51df73 to 1654.vcb_69d035fa_20

Bumps bom-2.332.x from 1643.v1cffef51df73 to 1654.vcb_69d035fa_20.


updated-dependencies:

  • dependency-name: io.jenkins.tools.bom:bom-2.332.x dependency-type: direct:production ...

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #10 from identifysun/dependabot/maven/io.jenkins.tools.bom-bom-2.332.x-1654.vcb_69d035fa_20

Bump bom-2.332.x from 1643.v1cffef51df73 to 1654.vcb_69d035fa_20

Created at 1 month ago
pull request closed
Bump bom-2.332.x from 1643.v1cffef51df73 to 1654.vcb_69d035fa_20

Bumps bom-2.332.x from 1643.v1cffef51df73 to 1654.vcb_69d035fa_20.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 1 month ago
started
Created at 1 month ago
Created at 1 month ago
issue comment
Vagrant 2.3.2 and Virtualbox 7.0.2 - Private Network Interface

I tried reinstalling Vagrant and Virtualbox, but it still doesn't fix

$ brew reinstall virtualbox vagrant
Created at 1 month ago
issue comment
Vagrant 2.3.2 and Virtualbox 7.0.2 - Private Network Interface

I have same question,

Vagrant and Virtualbox Version

$ vagrant --version
Vagrant 2.3.2

$ vboxmanage --version
7.0.2r154219

I guess running the following command is caused by a failure

$ VBoxManage hostonlyif create
0%...NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 105 of file VBoxManageHostonly.cpp

Refer to the workaround on the internet, but I can't find the following file or command

  • /Library/StartupItems/VirtualBox/VirtualBox restart
  • /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart
Created at 1 month ago
[Bug]:

Contact Details

No response

What happened?

A bug happened!

Version

1.0.3 (Edge)

What browsers are you seeing the problem on?

Firefox

Relevant log output

No response

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct
Created at 1 month ago

Rename 02_bug_issue_template to 02_bug_issue_template.yml

Created at 1 month ago

Update 02_bug_issue_template

Created at 1 month ago

Create 02_bug_issue_template

Created at 1 month ago
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Created at 1 month ago
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
Created at 1 month ago
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Created at 1 month ago