hello. I can't comment on if VMWre should be faster then Virtualbox, or why is not.
I personally use Virtualbox and runs fine. If you can run commands with time, we can compare times. here goes what I mean. On Thu, Nov 1, 2018 at 4:41 PM Christopher Alevizopoulos <calev...@gmail.com> wrote: > So I installed vagrant 2.2.0, vmware utility 1.0.5 and upgraded the > plugins, > but homestead is still booting slow. > > Then I tried the hashicorp/precise64 box, and its also taking more than 2 > minutes to boot > > On Wednesday, 31 October 2018 17:13:24 UTC+2, Christopher Alevizopoulos > wrote: >> >> Hi Alvaro, >> >> I will try that when I get some time on my hands. >> >> I'm still unable to find why booting has been so slow, and I still get >> random errors that resolve themselves like the following: >> >> Vagrant encountered an error while attempting to prune unused >> >> port forward entries: >> >> Failed to delete port forward >> >> my best guess: ist OSX Mojave related, I was unable to find any solution >> so far and I will probably go back to using Virtual Box. >> >> I opened a ticket with support and if I get a response I will post it >> here for future reference. >> >> >> On Saturday, 27 October 2018 20:49:01 UTC+3, Alvaro Miranda Aguilera >> wrote: >>> >>> hello >>> >>> if you are familiar installing homestead, i would suggest if you can try >>> with a different box. >>> >>> Alvaro >>> >>> On Fri, Oct 26, 2018 at 1:59 PM Christopher Alevizopoulos < >>> cale...@gmail.com> wrote: >>> >>>> Hello, >>>> >>>> I'm using Vagrant with VMWare, I installed VMWare Fusion Pro v11.0.0 >>>> (10120384) on macOS 10.14 (18A391), >>>> then installed Vagrant v2.2.0 and vagrant-vmware-desktop 2.0.0, after >>>> that the license was also successfully added and I followed the >>>> instructions in the Laravel documentation to install Homestead. >>>> >>>> Up until now homestead seems to work fine but the time it takes to boot >>>> (>2min) seems to me very slow and I'm wondering if something is wrong. When >>>> I boot homestead it takes a-lot of time to move past the "*Verifying >>>> vmnet devices are healthy...*" message and then it also gets stuck >>>> after the "*Forwarding ports...*" message. >>>> >>>> Once, when I tried to halt the VM I got the following error: >>>> >>>> Vagrant encountered an error while attempting to inspect VMware >>>> >>>> for current version information: >>>> >>>> >>>> >>>> Failed attempting to check VMware version >>>> >>>> then I tried to halt the machine again and it was successfully halted. >>>> >>>> I was using vagrant with VirtualBox before I bought the plugin to boost >>>> performance, and in my old setup VirtualBox Homestead would boot alot >>>> faster on a older MAC, I was expecting Homestead to boot alot faster with >>>> the new setup and this behaviour makes me worry that I might have problems >>>> with my installation, maybe some incompatibility with the Mojave OS. >>>> >>>> Has anyone experienced something similar with their setup? >>>> >>>> Thank you for your time >>>> Chris >>>> >>>> I'm attaching a vagrant info log. >>>> >>>> -- >>>> 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+...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/vagrant-up/0e40e23a-48f6-4d68-8f44-7690d079a05d%40googlegroups.com >>>> <https://groups.google.com/d/msgid/vagrant-up/0e40e23a-48f6-4d68-8f44-7690d079a05d%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> -- >>> 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/6329e05d-aee8-4da5-a9e3-8cc91f711f51%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/6329e05d-aee8-4da5-a9e3-8cc91f711f51%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAHqq0ex32Nqtg_KERaEjXSHz02kVmt076qFO7Rfwpqk7raGWPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
