Closed kbreit closed 2 years ago
And this is what happens when I try to automate a Jenga tower ;)
On a more serious note:
Finally, you can always connect to the virtual machines with virsh console vm-name (use virsh list to see VM names) and check what's going on.
vagrant plugin list
shows No plugins installed
. However, I did the install using netlab install ubuntu ansible libvirt
so I'd have expected it to be populated.
- We are running this on ESXi. I'm allocating 4 CPU, 8GB RAM, and 128GB of disk.
That's enough.
- I downloaded 4.24.8M from the Arista website and did a mutate on it. This was based on the documentation but if there's a better way to import the Arista image, I'm happy to go that way.
https://netsim-tools.readthedocs.io/en/latest/labs/eos.html
Yeah, I have to fix that tutorial and bring it in sync with the installation guide.
vagrant plugin list
showsNo plugins installed
. However, I did the install usingnetlab install ubuntu ansible libvirt
so I'd have expected it to be populated.
OK, in that case you most probably have the correct version of the plugin. BTW, did you use sudo netlab install? Vagrant plugins are installed into user's home directory (as I learned the hard way when fixing the installation scripts).
- I did login to the VMs and both are getting an IP address (192.168.121.101 and 102).
Did you try to SSH into those IP addresses?
I recreated the image using the instructions and the netlab libvirt package
command. Same results overall. I think I ran it as root and not using sudo
. But I did run a vagrant plugin list
and now it's showing.
root@e7ubnt0nstools01:/home/ubuntu# vagrant plugin list
vagrant-libvirt (0.4.1, global)
- Version Constraint: 0.4.1
vagrant-mutate (1.2.0, global)
==> r2: Creating shared folders metadata...
==> r1: -- Sound Type:
==> r1: -- Keymap: en-us
==> r2: Starting domain.
==> r1: -- TPM Backend: passthrough
==> r2: Waiting for domain to get an IP address...
==> r1: -- TPM Path:
==> r2: Waiting for SSH to become available...
==> r1: -- INPUT: type=mouse, bus=ps2
==> r1: Creating shared folders metadata...
==> r1: Starting domain.
==> r1: Waiting for domain to get an IP address...
==> r1: Waiting for SSH to become available...
localhost#show ip int br
Address
Interface IP Address Status Protocol MTU Owner
--------------- ---------------------- ---------- ------------ -------- -------
Management1 192.168.121.101/24 up up 1500
ubuntu@e7ubnt0nstools01:~$ ssh admin@192.168.121.101
The authenticity of host '192.168.121.101 (192.168.121.101)' can't be established.
ECDSA key fingerprint is SHA256:iL0RR7lihzfFH+svE0tKeDr+FY5CsclrtaXtqb57elw.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.121.101' (ECDSA) to the list of known hosts.
Password:
Last login: Thu Feb 17 16:32:14 2022
localhost#
I recreated the image using the instructions and the
netlab libvirt package
command.
Thank you for trying that out.
Same results overall.
Dang. I ran out of ideas... apart from the usual "reboot and try again". Now I sound like a $vendor TAC :((
I think I ran it as root and not using
sudo
. But I did run avagrant plugin list
and now it's showing.
OK, that's solved...
==> r1: Waiting for domain to get an IP address... ==> r1: Waiting for SSH to become available...
You're starting two devices, and whatever is the last line in the printout is not always the culprit as Vagrant starts devices in parallel. It could easily be r2 that's stuck. You can try starting the lab "manually" with vagrant up --no-parallel
(after running netlab create
to recreate the configuration files) so you'll know exactly which device is causing the problems.
Please note that I'm not a KVM/libvirt/Vagrant/Linux guru. Things mostly work, but when they don't I'm as lost as the next guy... I feel like a taxi driver trying to troubleshoot an engine problem on a friend's car over the phone :(
I ran it with vagrant up --no-parallel
and seeing the same behavior. r1 comes up but SSH isn't detected as available. I can even SSH into the box using 192.168.121.101
. If there aren't other troubleshooting ideas, I will try a Cisco CSR1000v image and see if it's specific to Arista. netlab test
did work.
I ran it with
vagrant up --no-parallel
and seeing the same behavior. r1 comes up but SSH isn't detected as available. I can even SSH into the box using192.168.121.101
.
That's totally weird, I've never seen it before. Do try a reload as a sacrifice to the Gods of Schroedinger Bugs.
Did you delete the old (mutated) Arista box (vagrant box remove name --box-version version). Also, I hope you used a different version number for the new box you built.
netlab test
did work.
That's nice to hear, so there's hope...
I didn't delete the old Arista box so trying it again. Doesn't seem to have fixed it but I'll let it run. CSR1000v image is downloading now.
Fixed the tutorial, recommending cEOS on Linux (that's a breeze compared to making your own boxes). Is there anything else I can to do help?
I redid the VM and it seems to be working properly. It came down to running things as root or sudo too much.
I am creating a topology on libvirt in Ubuntu 20.04 (VM in vSphere) but one of the routers fails to come up.
Output:
It sat at this step for at least 30 minutes.
Topology file: