vagrant up eos freezes system completely, not able to bring up eos












0















I am just learning to use the python NAPALM library. The tutorials suggest




set up a lab using VirtualBox and Vagrant, with a virtual Arista
device




I am not able to bring up eos.
I am having the following configuration :



ubuntu : 16.04 LTS, OS type 32-bit



virtual box : Version 5.2.22 r126460 (Qt5.6.1)



Vagrant 2.2.1



vEOS-lab-4.21.1.1F-virtualbox



My
Vagrantfile
contents are as follows :



VEOS_BOX = "vEOS-lab-4.21.1.1F-virtualbox"
Vagrant.configure(2) do |config|

config.vm.provider "virtualbox" do |vb|
vb.gui = true
end

config.vm.define "base" do |base|
base.vm.box = "hashicorp/precise64"
base.vm.network :forwarded_port, guest: 22, host: 12200, id: 'ssh'
base.vm.network "private_network", virtualbox__intnet: "link_1", ip: "10.0.1.100"
base.vm.network "private_network", virtualbox__intnet: "link_2", ip: "10.0.2.100"
base.vm.provision "shell", inline: "apt-get update; apt-get install lldpd -y"
end

config.vm.define "eos" do |eos|
eos.vm.box = VEOS_BOX
eos.vm.network :forwarded_port, guest: 22, host: 12201, id: 'ssh'
eos.vm.network :forwarded_port, guest: 443, host: 12443, id: 'https'
eos.vm.network "private_network", virtualbox__intnet: "link_1", ip: "169.254.1.11", auto_config: false
eos.vm.network "private_network", virtualbox__intnet: "link_2", ip: "169.254.1.11", auto_config: false
end
end


When I execute vagrant up, the system successfully starts the base, starts booting up eos, but finally freezes (is recoverable only through hard reset) after trying to do EOS initilization.



Please help. I have tried out lot of things after reading various suggestions on the internet










share|improve this question



























    0















    I am just learning to use the python NAPALM library. The tutorials suggest




    set up a lab using VirtualBox and Vagrant, with a virtual Arista
    device




    I am not able to bring up eos.
    I am having the following configuration :



    ubuntu : 16.04 LTS, OS type 32-bit



    virtual box : Version 5.2.22 r126460 (Qt5.6.1)



    Vagrant 2.2.1



    vEOS-lab-4.21.1.1F-virtualbox



    My
    Vagrantfile
    contents are as follows :



    VEOS_BOX = "vEOS-lab-4.21.1.1F-virtualbox"
    Vagrant.configure(2) do |config|

    config.vm.provider "virtualbox" do |vb|
    vb.gui = true
    end

    config.vm.define "base" do |base|
    base.vm.box = "hashicorp/precise64"
    base.vm.network :forwarded_port, guest: 22, host: 12200, id: 'ssh'
    base.vm.network "private_network", virtualbox__intnet: "link_1", ip: "10.0.1.100"
    base.vm.network "private_network", virtualbox__intnet: "link_2", ip: "10.0.2.100"
    base.vm.provision "shell", inline: "apt-get update; apt-get install lldpd -y"
    end

    config.vm.define "eos" do |eos|
    eos.vm.box = VEOS_BOX
    eos.vm.network :forwarded_port, guest: 22, host: 12201, id: 'ssh'
    eos.vm.network :forwarded_port, guest: 443, host: 12443, id: 'https'
    eos.vm.network "private_network", virtualbox__intnet: "link_1", ip: "169.254.1.11", auto_config: false
    eos.vm.network "private_network", virtualbox__intnet: "link_2", ip: "169.254.1.11", auto_config: false
    end
    end


    When I execute vagrant up, the system successfully starts the base, starts booting up eos, but finally freezes (is recoverable only through hard reset) after trying to do EOS initilization.



    Please help. I have tried out lot of things after reading various suggestions on the internet










    share|improve this question

























      0












      0








      0








      I am just learning to use the python NAPALM library. The tutorials suggest




      set up a lab using VirtualBox and Vagrant, with a virtual Arista
      device




      I am not able to bring up eos.
      I am having the following configuration :



      ubuntu : 16.04 LTS, OS type 32-bit



      virtual box : Version 5.2.22 r126460 (Qt5.6.1)



      Vagrant 2.2.1



      vEOS-lab-4.21.1.1F-virtualbox



      My
      Vagrantfile
      contents are as follows :



      VEOS_BOX = "vEOS-lab-4.21.1.1F-virtualbox"
      Vagrant.configure(2) do |config|

      config.vm.provider "virtualbox" do |vb|
      vb.gui = true
      end

      config.vm.define "base" do |base|
      base.vm.box = "hashicorp/precise64"
      base.vm.network :forwarded_port, guest: 22, host: 12200, id: 'ssh'
      base.vm.network "private_network", virtualbox__intnet: "link_1", ip: "10.0.1.100"
      base.vm.network "private_network", virtualbox__intnet: "link_2", ip: "10.0.2.100"
      base.vm.provision "shell", inline: "apt-get update; apt-get install lldpd -y"
      end

      config.vm.define "eos" do |eos|
      eos.vm.box = VEOS_BOX
      eos.vm.network :forwarded_port, guest: 22, host: 12201, id: 'ssh'
      eos.vm.network :forwarded_port, guest: 443, host: 12443, id: 'https'
      eos.vm.network "private_network", virtualbox__intnet: "link_1", ip: "169.254.1.11", auto_config: false
      eos.vm.network "private_network", virtualbox__intnet: "link_2", ip: "169.254.1.11", auto_config: false
      end
      end


      When I execute vagrant up, the system successfully starts the base, starts booting up eos, but finally freezes (is recoverable only through hard reset) after trying to do EOS initilization.



      Please help. I have tried out lot of things after reading various suggestions on the internet










      share|improve this question














      I am just learning to use the python NAPALM library. The tutorials suggest




      set up a lab using VirtualBox and Vagrant, with a virtual Arista
      device




      I am not able to bring up eos.
      I am having the following configuration :



      ubuntu : 16.04 LTS, OS type 32-bit



      virtual box : Version 5.2.22 r126460 (Qt5.6.1)



      Vagrant 2.2.1



      vEOS-lab-4.21.1.1F-virtualbox



      My
      Vagrantfile
      contents are as follows :



      VEOS_BOX = "vEOS-lab-4.21.1.1F-virtualbox"
      Vagrant.configure(2) do |config|

      config.vm.provider "virtualbox" do |vb|
      vb.gui = true
      end

      config.vm.define "base" do |base|
      base.vm.box = "hashicorp/precise64"
      base.vm.network :forwarded_port, guest: 22, host: 12200, id: 'ssh'
      base.vm.network "private_network", virtualbox__intnet: "link_1", ip: "10.0.1.100"
      base.vm.network "private_network", virtualbox__intnet: "link_2", ip: "10.0.2.100"
      base.vm.provision "shell", inline: "apt-get update; apt-get install lldpd -y"
      end

      config.vm.define "eos" do |eos|
      eos.vm.box = VEOS_BOX
      eos.vm.network :forwarded_port, guest: 22, host: 12201, id: 'ssh'
      eos.vm.network :forwarded_port, guest: 443, host: 12443, id: 'https'
      eos.vm.network "private_network", virtualbox__intnet: "link_1", ip: "169.254.1.11", auto_config: false
      eos.vm.network "private_network", virtualbox__intnet: "link_2", ip: "169.254.1.11", auto_config: false
      end
      end


      When I execute vagrant up, the system successfully starts the base, starts booting up eos, but finally freezes (is recoverable only through hard reset) after trying to do EOS initilization.



      Please help. I have tried out lot of things after reading various suggestions on the internet







      python vagrant eos






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 '18 at 3:50









      user3282758user3282758

      469213




      469213
























          1 Answer
          1






          active

          oldest

          votes


















          0














          In general, if you see the system is freezing, you can always turn debug trace to see what is going on, it might be that the system is looping on the same command or really freezing.



          vagrant up --debug


          In your case, I believe the issue is with the network, you should associate IP from the private IP range so changing the IP to a private IP will solve your case and you could boot the VM






          share|improve this answer
























          • I am already running with debug on. But I am new to networking and so I am not able to understand how to implement your suggestion

            – user3282758
            Nov 20 '18 at 14:03











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385955%2fvagrant-up-eos-freezes-system-completely-not-able-to-bring-up-eos%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          In general, if you see the system is freezing, you can always turn debug trace to see what is going on, it might be that the system is looping on the same command or really freezing.



          vagrant up --debug


          In your case, I believe the issue is with the network, you should associate IP from the private IP range so changing the IP to a private IP will solve your case and you could boot the VM






          share|improve this answer
























          • I am already running with debug on. But I am new to networking and so I am not able to understand how to implement your suggestion

            – user3282758
            Nov 20 '18 at 14:03
















          0














          In general, if you see the system is freezing, you can always turn debug trace to see what is going on, it might be that the system is looping on the same command or really freezing.



          vagrant up --debug


          In your case, I believe the issue is with the network, you should associate IP from the private IP range so changing the IP to a private IP will solve your case and you could boot the VM






          share|improve this answer
























          • I am already running with debug on. But I am new to networking and so I am not able to understand how to implement your suggestion

            – user3282758
            Nov 20 '18 at 14:03














          0












          0








          0







          In general, if you see the system is freezing, you can always turn debug trace to see what is going on, it might be that the system is looping on the same command or really freezing.



          vagrant up --debug


          In your case, I believe the issue is with the network, you should associate IP from the private IP range so changing the IP to a private IP will solve your case and you could boot the VM






          share|improve this answer













          In general, if you see the system is freezing, you can always turn debug trace to see what is going on, it might be that the system is looping on the same command or really freezing.



          vagrant up --debug


          In your case, I believe the issue is with the network, you should associate IP from the private IP range so changing the IP to a private IP will solve your case and you could boot the VM







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 20 '18 at 8:35









          Frédéric HenriFrédéric Henri

          33.6k55484




          33.6k55484













          • I am already running with debug on. But I am new to networking and so I am not able to understand how to implement your suggestion

            – user3282758
            Nov 20 '18 at 14:03



















          • I am already running with debug on. But I am new to networking and so I am not able to understand how to implement your suggestion

            – user3282758
            Nov 20 '18 at 14:03

















          I am already running with debug on. But I am new to networking and so I am not able to understand how to implement your suggestion

          – user3282758
          Nov 20 '18 at 14:03





          I am already running with debug on. But I am new to networking and so I am not able to understand how to implement your suggestion

          – user3282758
          Nov 20 '18 at 14:03


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385955%2fvagrant-up-eos-freezes-system-completely-not-able-to-bring-up-eos%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          SQL update select statement

          'app-layout' is not a known element: how to share Component with different Modules