Re: [vagrant-up] HyperV provider - Vagrant could not detect VirtualBox!
I have had the provider specified, but it did not help. I reinstaled vagrant, vbox to no avail. But anyway I gave up and switched off hyperV and set back to VBox completely. On Tuesday, March 17, 2020 at 4:54:26 PM UTC+1, Jeff Bonhag wrote: > > Hi there, > > Vagrant doesn't require VirtualBox, but if you have Hyper-V and VirtualBox > installed at the same time, it will prioritize VirtualBox over Hyper-V. > This means that running `vagrant up` will try to bring up a > VirtualBox-backed machine when both providers are installed. (Note that you > can request a specific provider like `vagrant up --provider hyperv`). > > It sounds like you may still have a VirtualBox-backed VM on your Windows > machine. Can you please check the output of `vagrant global-status`? > > If you see something like: > > 0eedc3c default virtualbox poweroff C:/Users/vagrant/vbox-test > > then Vagrant is going to keep trying to use VBoxManage to interact with > that VM. I'd suggest that you reinstall VirtualBox, run a `vagrant destroy` > on the VirtualBox-backed machine, and then uninstall VirtualBox again. > > Hope this helps! > > Jeff > > On Tue, Mar 17, 2020 at 5:27 AM zveratko > wrote: > >> Does vagrant need VirtualBox to run? >> I have switched to WIN10 and I am forced to run hyperV. I found out that >> VBox will not work with hyperV enabled so I decided to remove it. But now >> I'm getting >> >> Vagrant could not detect VirtualBox! Make sure VirtualBox is properly >> installed. >> Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and >> requires >> this to be available on the PATH. If VirtualBox is installed, please find >> the >> `VBoxManage` binary and add it to the PATH environmental variable. >> >> Why is that? Does vagrant have dependency on VBox even when I am using >> 'hyperv' provider? >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to vagra...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/6d799979-657b-41d1-ae2e-08d7d2b44021%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/6d799979-657b-41d1-ae2e-08d7d2b44021%40googlegroups.com?utm_medium=email_source=footer> >> . >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/e3376020-a450-47d9-8033-d43629b6f8e4%40googlegroups.com.
[vagrant-up] Re: HyperV provider - Vagrant could not detect VirtualBox!
The whole think happened after I uninstalled VBox because I decided to go for HyperV ( and I had of course hyperv provider specified in my vagrant file) After realizing that vagrant will no take care of static IP, I have disabled the whole hyperV thingy and went back for VBox. Which of course gave me another hard time getting "guru meditation state" when using more than one CPU. I will be fine with VBox now, but I disabled Windows 10 Bitlocker, which I thought need some hyperV support. I am not able to say if the bitlocker and hyperV are somehow connected. If I remember swiching off virtualization in BIOS led to Bitlocker stopped working. Do you know if the Bitlocker requires hyperV support? I really don't know where I got the impression that VBox will not run with Windows10 and Bitlocker enabled. On Wednesday, March 18, 2020 at 7:33:08 PM UTC+1, dragon788 wrote: > > If you are using the latest version of Vagrant the Hyper-V provider is > built in. As mentioned if the box you have supports your provider it should > start without prompting, but if you have a box that supports multiple > providers the default is Virtualbox, another possibility is the box that > you tried to grab does NOT support HyperV a a provider, in which case the > odds are good that it does support the default Virtualbox provider. > > Depending on how you install Vagrant though, some package providers > _helpfully_ install Virtualbox automatically even though it should be an > optional dependency. Vagrant comes with Virtualbox, HyperV and Docker > support out of the box because these "plugins" are maintained by Hashicorp > so they make sense to be bundled, but there are many other provider plugins > available for libvirt and AWS and parallels and may others, and these are > distributed separately so that they can be updated independently of Vagrant > itself. > > The "easy" way to avoid getting Virtualbox boxes when trying to `vagrant > init somebox` is to set the VAGRANT_DEFAULT_PROVIDER environment variable > to your preferred provider at a user or system level so that it always uses > the one you have available. > > https://www.vagrantup.com/docs/providers/default.html > > On Tuesday, March 17, 2020 at 4:27:42 AM UTC-5, zveratko wrote: >> >> Does vagrant need VirtualBox to run? >> I have switched to WIN10 and I am forced to run hyperV. I found out that >> VBox will not work with hyperV enabled so I decided to remove it. But now >> I'm getting >> >> Vagrant could not detect VirtualBox! Make sure VirtualBox is properly >> installed. >> Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and >> requires >> this to be available on the PATH. If VirtualBox is installed, please find >> the >> `VBoxManage` binary and add it to the PATH environmental variable. >> >> Why is that? Does vagrant have dependency on VBox even when I am using >> 'hyperv' provider? >> >> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/5336e6ba-2055-45ad-badd-644f31163b6d%40googlegroups.com.
[vagrant-up] HyperV provider - Vagrant could not detect VirtualBox!
Does vagrant need VirtualBox to run? I have switched to WIN10 and I am forced to run hyperV. I found out that VBox will not work with hyperV enabled so I decided to remove it. But now I'm getting Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires this to be available on the PATH. If VirtualBox is installed, please find the `VBoxManage` binary and add it to the PATH environmental variable. Why is that? Does vagrant have dependency on VBox even when I am using 'hyperv' provider? -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6d799979-657b-41d1-ae2e-08d7d2b44021%40googlegroups.com.
Re: [vagrant-up] Do I need port-forwarding to communicate from host to guest?
I am asking because I am not sure how those public/bridged etc. networking between host/guest works. Sometime I cannot see the port on the host. Maybe it is because the app in the VM is restricted to accept localhost connection only, but I always strugling to find the exact place of the error. Are those option equal ? call 192.168.10.101:80 on host machine make port-forward 80:80 and call localhost:80 on host machine Is the first option using NAT while the second is not? On Saturday, March 7, 2020 at 12:59:34 PM UTC+1, Alvaro Miranda Aguilera wrote: > > hello > > if you want to access something on port 80 then you can use 192.168. > 10.101:80 > > http://192.168.10.101 > > > On Fri, Mar 6, 2020 at 12:17 PM zveratko > wrote: > >> I have set up some vagrant box and I want to connect to some services >> running on it. I used this to set up the networking >> >> config.vm.network "private_network", ip: "192.168.10.101" >> >> >> I checked in VirtualBoxUI and the machine has two interfaces NAT with >> port forwarding ->22(probably the eth0) and HOST_ONLY(eth1?) >> >> eth0: flags=4163 mtu 1500 >> inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 >> inet6 fe80::a00:27ff:fec2:4a97 prefixlen 64 scopeid 0x20 >> ether 08:00:27:c2:4a:97 txqueuelen 1000 (Ethernet) >> RX packets 27643 bytes 24238095 (23.1 MiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 11304 bytes 1136140 (1.0 MiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> >> eth1: flags=4163 mtu 1500 >> inet 192.168.10.101 netmask 255.255.255.0 broadcast 192.168. >> 10.255 >> inet6 fe80::a00:27ff:fe19:fc5 prefixlen 64 scopeid 0x20 >> ether 08:00:27:19:0f:c5 txqueuelen 1000 (Ethernet) >> RX packets 3053 bytes 278689 (272.1 KiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 2380 bytes 683097 (667.0 KiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> >> Do I need port forwarding to access some service running inside on port >> ie.80? I have just tested that I can putty in by localhost: or >> 192.168.10.101:22 >> >> In which setting I can ommit port forwarding and just call guest with its >> ip? I have some problems connecting to another service and I am not sure >> whather it just listen to localhost only or something else is wrong. >> >> Is this sentence I noted some time ago correct >> >> port forwarding is not needed when using private network and accessing >> guest from host with guest private ip, port forwarding is used to access >> guest with localhost/127.0.0.1 the ports are then forwarded >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to vagra...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/63a27481-91a3-42b4-a93a-4aa7c49a424f%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/63a27481-91a3-42b4-a93a-4aa7c49a424f%40googlegroups.com?utm_medium=email_source=footer> >> . >> > > > -- > Alvaro > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/679b3a9b-72e1-4d42-99ca-08860553bc23%40googlegroups.com.
[vagrant-up] Do I need port-forwarding to communicate from host to guest?
I have set up some vagrant box and I want to connect to some services running on it. I used this to set up the networking config.vm.network "private_network", ip: "192.168.10.101" I checked in VirtualBoxUI and the machine has two interfaces NAT with port forwarding ->22(probably the eth0) and HOST_ONLY(eth1?) eth0: flags=4163 mtu 1500 inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::a00:27ff:fec2:4a97 prefixlen 64 scopeid 0x20 ether 08:00:27:c2:4a:97 txqueuelen 1000 (Ethernet) RX packets 27643 bytes 24238095 (23.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11304 bytes 1136140 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=4163 mtu 1500 inet 192.168.10.101 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::a00:27ff:fe19:fc5 prefixlen 64 scopeid 0x20 ether 08:00:27:19:0f:c5 txqueuelen 1000 (Ethernet) RX packets 3053 bytes 278689 (272.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2380 bytes 683097 (667.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Do I need port forwarding to access some service running inside on port ie.80? I have just tested that I can putty in by localhost: or 192.168.10.101:22 In which setting I can ommit port forwarding and just call guest with its ip? I have some problems connecting to another service and I am not sure whather it just listen to localhost only or something else is wrong. Is this sentence I noted some time ago correct port forwarding is not needed when using private network and accessing guest from host with guest private ip, port forwarding is used to access guest with localhost/127.0.0.1 the ports are then forwarded -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/63a27481-91a3-42b4-a93a-4aa7c49a424f%40googlegroups.com.
