vQFX start problem.

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
yokodzun
Posts: 2
Joined: Thu Apr 04, 2019 2:24 pm

vQFX start problem.

Post by yokodzun » Thu Apr 04, 2019 5:41 pm

I'm trying to run vQFX 10K on a freshly installed eve-ng node. I use EVE-NG version: 2.0.3-95 installed from OVA on VMware (6.5U2) platform.
Virtual Machine Settings - 4xvCPU,16GB RAM. For setup vQFX I use this manual:
https://www.eve-ng.net/documentation/ho ... niper-vqfx
And use exactly the same version of Juniper disk images. I create the lab, add RE and PFE, connect them via em1.
But when I run them, nothing happens. The icons are gray.
On /opt/unetlab/data/Logs/unl_wrapper.txt i see

Code: Select all

Apr 04 17:06:10 INFO: CWD is /opt/unetlab/tmp/0/f76472cf-3830-49ba-aef8-1df9d9477d60/1
Apr 04 17:06:10 INFO: starting /opt/unetlab/wrappers/qemu_wrapper -T 0 -D 1 -t "vQFX-RE" -F /opt/qemu/bin/qemu-system-x86_64 -d 0 --  -nographic -device virtio-net-pci,netdev=net0,mac=50:00:00:01:00:00 -netdev tap,id=net0,ifname=vunl0_1_0,script=no -device virtio-net-pci,netdev=net1,mac=50:00:00:01:00:01 -netdev tap,id=net1,ifname=vunl0_1_1,script=no -device virtio-net-pci,netdev=net2,mac=50:00:00:01:00:02 -netdev tap,id=net2,ifname=vunl0_1_2,script=no -device virtio-net-pci,netdev=net3,mac=50:00:00:01:00:03 -netdev tap,id=net3,ifname=vunl0_1_3,script=no -device virtio-net-pci,netdev=net4,mac=50:00:00:01:00:04 -netdev tap,id=net4,ifname=vunl0_1_4,script=no -device virtio-net-pci,netdev=net5,mac=50:00:00:01:00:05 -netdev tap,id=net5,ifname=vunl0_1_5,script=no -device virtio-net-pci,netdev=net6,mac=50:00:00:01:00:06 -netdev tap,id=net6,ifname=vunl0_1_6,script=no -device virtio-net-pci,netdev=net7,mac=50:00:00:01:00:07 -netdev tap,id=net7,ifname=vunl0_1_7,script=no -device virtio-net-pci,netdev=net8,mac=50:00:00:01:00:08 -netdev tap,id=net8,ifname=vunl0_1_8,script=no -device virtio-net-pci,netdev=net9,mac=50:00:00:01:00:09 -netdev tap,id=net9,ifname=vunl0_1_9,script=no -device virtio-net-pci,netdev=net10,mac=50:00:00:01:00:0a -netdev tap,id=net10,ifname=vunl0_1_10,script=no -device virtio-net-pci,netdev=net11,mac=50:00:00:01:00:0b -netdev tap,id=net11,ifname=vunl0_1_11,script=no -device virtio-net-pci,netdev=net12,mac=50:00:00:01:00:0c -netdev tap,id=net12,ifname=vunl0_1_12,script=no -device virtio-net-pci,netdev=net13,mac=50:00:00:01:00:0d -netdev tap,id=net13,ifname=vunl0_1_13,script=no -device virtio-net-pci,netdev=net14,mac=50:00:00:01:00:0e -netdev tap,id=net14,ifname=vunl0_1_14,script=no -smp 2 -m 2048 -name vQFX-RE -uuid 1da625a7-4098-4ae9-b973-f58f01eeb11d -hda hda.qcow2 -machine type=pc-1.0,accel=kvm -serial mon:stdio -nographic > /opt/unetlab/tmp/0/f76472cf-3830-49ba-aef8-1df9d9477d60/1/wrapper.txt 2>&1 &
Apr 04 17:06:24 INFO: tunctl -u unl0 -g root -t vunl0_2_0 2>&1
Apr 04 17:06:24 INFO: sysctl -w net.ipv6.conf.vunl0_2_0.disable_ipv6=1
Apr 04 17:06:24 INFO: tunctl -u unl0 -g root -t vunl0_2_1 2>&1
Apr 04 17:06:24 INFO: sysctl -w net.ipv6.conf.vunl0_2_1.disable_ipv6=1
Apr 04 17:06:24 INFO: CWD is /opt/unetlab/tmp/0/f76472cf-3830-49ba-aef8-1df9d9477d60/2
Apr 04 17:06:24 INFO: starting /opt/unetlab/wrappers/qemu_wrapper -T 0 -D 2 -t "vQFX-PFE" -F /opt/qemu/bin/qemu-system-x86_64 -d 0 -x -- -device e1000,netdev=net0,mac=50:00:00:02:00:00 -netdev tap,id=net0,ifname=vunl0_2_0,script=no -device e1000,netdev=net1,mac=50:00:00:02:00:01 -netdev tap,id=net1,ifname=vunl0_2_1,script=no -smp 2 -m 4096 -name vQFX-PFE -uuid e0089393-b950-4f97-9f4e-0243a499b1ed -vnc :26870 -hda hda.qcow2 -machine type=pc-1.0,accel=kvm -vga std -usbdevice tablet -boot order=dc > /opt/unetlab/tmp/0/f76472cf-3830-49ba-aef8-1df9d9477d60/2/wrapper.txt 2>&1 &
But the QEMU process does not start.

Are there any ideas how I can fix this or debug problem?

Thanks!

yokodzun
Posts: 2
Joined: Thu Apr 04, 2019 2:24 pm

[solved] Re: vQFX start problem.

Post by yokodzun » Fri Apr 05, 2019 6:46 am

Enabling "nested virtualization" for this VM solved my problem.

Post Reply