What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hello! I try to set up a dev environment on Windows 10 following this guide:

U0128MN5FT7
U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

Hello! I try to set up a dev environment on Windows 10 following this guide: https://documentation.spryker.com/docs/b2c-demo-shop-installation-windows-with-development-virtual-machine
When starting the VM I always get the error "Timed out while waiting for the machine to boot."
Does someone know how to solve this issue?

Comments

  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    The full error:

    philipp.paul@YODA MINGW64 /c/spryker/devvm
    $ VM_SKIP_SF="1" VM_PROJECT=b2c-demo-shop SPRYKER_REPOSITORY="<https://github.com/spryker-shop/b2c-demo-shop.git>" vagrant up
    
    The following settings will be used for the new VM:
    VM_PROJECT =         'b2c-demo-shop'
    VM_IP =              '10.10.0.234'
    VM_MEMORY =          '3200'
    VM_CPUS =            '4'
    VM_NAME =            'Spryker Dev VM (b2c-demo-shop)'
    VM_DOMAIN =          'b2c-demo-shop'
    VM_SKIP_SF =         '1'
    VM_IS_WINDOWS =      '1'
    SPRYKER_BRANCH =     'master'
    SPRYKER_REPOSITORY = '<https://github.com/spryker-shop/b2c-demo-shop.git>'
    Press return to save the settings or Ctrl+C to abort
    If you save the settings, they will be stored in a .vm file on your hard drive.
    To change a setting, interrupt now and modify the respective environmental variables.
    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Importing base box 'devvm3.0.0'...
    ==> default: Matching MAC address for NAT networking...
    ==> default: Setting the name of the VM: Spryker Dev VM (b2c-demo-shop)
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
        default: Adapter 1: nat
        default: Adapter 2: hostonly
    ==> default: Forwarding ports...
        default: 1080 (guest) => 1080 (host) (adapter 1)
        default: 3306 (guest) => 3306 (host) (adapter 1)
        default: 5432 (guest) => 5432 (host) (adapter 1)
        default: 5601 (guest) => 5601 (host) (adapter 1)
        default: 10007 (guest) => 10007 (host) (adapter 1)
        default: 22 (guest) => 2222 (host) (adapter 1)
    ==> default: Running 'pre-boot' VM customizations...
    ==> default: Booting VM...
    ==> default: Waiting for machine to boot. This may take a few minutes...
        default: SSH address: 127.0.0.1:2222
        default: SSH username: vagrant
        default: SSH auth method: private key
    Timed out while waiting for the machine to boot. This means that
    Vagrant was unable to communicate with the guest machine within
    the configured ("config.vm.boot_timeout" value) time period.
    
    If you look above, you should be able to see the error(s) that
    Vagrant had when attempting to connect to the machine. These errors
    are usually good hints as to what may be wrong.
    
    If you're using a custom box, make sure that networking is properly
    working and you're able to connect to the machine. It is a common
    problem that networking isn't setup properly in these boxes.
    Verify that authentication configurations are also setup properly,
    as well.
    
    If the box appears to be booting properly, you may want to increase
    the timeout ("config.vm.boot_timeout") value.
    
  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice

    Interesting, have never seen this.
    Could you please make sure that virtualization is enabled in BIOS?

  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    Yes, virtualization is active.

  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    If I try again, I get different error message:

    philipp.paul@YODA MINGW64 /c/spryker/devvm
    $  VM_SKIP_SF="1" VM_PROJECT=b2c-demo-shop SPRYKER_REPOSITORY="<https://github.com/spryker-shop/b2c-demo-shop.git>" vagrant up
    
    Loading VM settings file: .vm
    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: [vagrant-hostmanager:guests] Updating hosts file on active guest virtual machines...
    ==> default: [vagrant-hostmanager:host] Updating hosts file on your workstation (password may be required)...
    ==> default: Running provisioner: hostmanager...
    ==> default: Running provisioner: shell...
    An error occurred in the underlying SSH library that Vagrant uses.
    The error message is shown below. In many cases, errors from this
    library are caused by ssh-agent issues. Try disabling your SSH
    agent or removing some keys and try again.
    
    If the problem persists, please report a bug to the net-ssh project.
    
    timeout during server version negotiating
    
  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice

    Brief googling of this problem gives couple of possible solutions but mostly vagrant destroy and vagrant up once again.

  • UQ958DA4U
    UQ958DA4U Posts: 232 πŸ§‘πŸ»β€πŸš€ - Cadet

    What does the VM in VirtualBox say?

  • UQ958DA4U
    UQ958DA4U Posts: 232 πŸ§‘πŸ»β€πŸš€ - Cadet

    Vagrant is just automated VBoxCli, so you will have a new machine available there. Does it boot at all? Are you using Hyper-V in parallel?

  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    At virtuialbox, it shows only this 2 lines. I guess this is not what it should.

  • UQ958DA4U
    UQ958DA4U Posts: 232 πŸ§‘πŸ»β€πŸš€ - Cadet

    That means it has crashed before and is now fsck (file system checking) the volume.

  • UQ958DA4U
    UQ958DA4U Posts: 232 πŸ§‘πŸ»β€πŸš€ - Cadet

    (I would assume at least)

  • UQ958DA4U
    UQ958DA4U Posts: 232 πŸ§‘πŸ»β€πŸš€ - Cadet

    Does it not move any further into the boot?

  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice

    An idea to check and disable Hyper-V makes sense.
    As in Windows it's either docker with Hyper-V enabled or Vagrant with Hyper-V disabled.

  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    Hyper-V was active. I will restart and try again.

  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    Now I get a different error:

    philipp.paul@YODA MINGW64 /c/spryker/devvm
    $ VM_SKIP_SF="1" VM_PROJECT=b2c-demo-shop SPRYKER_REPOSITORY="<https://github.com/spryker-shop/b2c-demo-shop.git>" vagrant up
    
    The following settings will be used for the new VM:
    VM_PROJECT =         'b2c-demo-shop'
    VM_IP =              '10.10.0.234'
    VM_MEMORY =          '3200'
    VM_CPUS =            '4'
    VM_NAME =            'Spryker Dev VM (b2c-demo-shop)'
    VM_DOMAIN =          'b2c-demo-shop'
    VM_SKIP_SF =         '1'
    VM_IS_WINDOWS =      '1'
    SPRYKER_BRANCH =     'master'
    SPRYKER_REPOSITORY = '<https://github.com/spryker-shop/b2c-demo-shop.git>'
    Press return to save the settings or Ctrl+C to abort
    If you save the settings, they will be stored in a .vm file on your hard drive.
    To change a setting, interrupt now and modify the respective environmental variables.
    Bringing machine 'default' up with 'virtualbox' provider...
    
    ==> default: Importing base box 'devvm3.0.0'...
    ==> default: Matching MAC address for NAT networking...
    ==> default: Setting the name of the VM: Spryker Dev VM (b2c-demo-shop)
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
        default: Adapter 1: nat
        default: Adapter 2: hostonly
    ==> default: Forwarding ports...
        default: 1080 (guest) => 1080 (host) (adapter 1)
        default: 3306 (guest) => 3306 (host) (adapter 1)
        default: 5432 (guest) => 5432 (host) (adapter 1)
        default: 5601 (guest) => 5601 (host) (adapter 1)
        default: 10007 (guest) => 10007 (host) (adapter 1)
        default: 22 (guest) => 2222 (host) (adapter 1)
    ==> default: Running 'pre-boot' VM customizations...
    ==> default: Booting VM...
    ==> default: Waiting for machine to boot. This may take a few minutes...
        default: SSH address: 127.0.0.1:2222
        default: SSH username: vagrant
        default: SSH auth method: private key
    The guest machine entered an invalid state while waiting for it
    to boot. Valid states are 'starting, running'. The machine is in the
    'gurumeditation' state. Please verify everything is configured
    properly and try again.
    
    If the provider you're using has a GUI that comes with it,
    it is often helpful to open that and watch the machine, since the
    GUI often has more helpful error messages than Vagrant can retrieve.
    For example, if you're using VirtualBox, run `vagrant up` while the
    VirtualBox GUI is open.
    
    The primary issue for this error is that the provider you're using
    is not properly configured. This is very rarely a Vagrant issue.
    
  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    VirtualBox was installed with the default options. Is some configuration necessary?

  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice

    No, everything should be as described in the documentation.

  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    If I start the VM at the virtualbox GUI, it looks better:

  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice

    Interesting.
    @UKJMWLUKZ do you have any ideas?

  • U0128MN5FT7
    U0128MN5FT7 Posts: 13 πŸ§‘πŸ»β€πŸš€ - Cadet

    in the VirtualBox logs I found a hint that the versions do not match. I had installed VirtualBox 6.1.6. With VirtualBox 5.2.34 it works now...

  • Valerii Trots
    Valerii Trots SRE @ Spryker Sprykee Posts: 1,654 ✨ - Novice

    That is really strange. Latest virtualbox works with latest vagrant flawlessly.