Vqfx-full issues

[Mierdin]

I think that the xe interfaces still aren't there.

Creating config drive (configdrive.img) ...
adding config file /tmp/config.txt
mount: /mnt: failed to setup loop device for /metadata.img.
umount: /mnt: not mounted.
-rw-r--r--. 1 root root 393216 Mar 20 07:48 /tmp/configdrive.qcow2

vqfx1 rpio_tunnel_br[1985]: SCHED: Thread 28 (cmqfx_pseudo) aborted, hogged 5841 ms

Message from syslogd@vqfx1 at Mar 20 18:46:05  ...
vqfx1 rpio_tunnel_br[1985]: SCHED: Thread 28 (cmqfx_pseudo) aborted, hogged 9161 ms

Message from syslogd@vqfx1 at Mar 20 18:46:49  ...
vqfx1 rpio_tunnel_br[1985]: SCHED: Thread 28 (cmqfx_pseudo) aborted, hogged 9901 ms

Message from syslogd@vqfx1 at Mar 20 18:48:40  ...
vqfx1 rpio_tunnel_br[1985]: SCHED: Thread 28 (cmqfx_pseudo) aborted, hogged 25223 ms

The previous may be fixed by deactivate system syslog user * according to https://forums.juniper.net/t5/Junos/Cannot-not-stop-real-time-syslog-messages-from-displaying-in/m-p/297223#M10628.

Also the error message I've emailed Toad and Marcel about.

[mwiget]

Failed to setup loop device indicates a missing kernel module allowing to mount a filesystem. It should get loaded automatically on Ubuntu. Looking at our other discussion at
nre-learning/antidote-core#93, we might just pre-build the config drive, avoiding the need to build it at runtime. It will just contain a static config file (fixed em0 IP).
Not having a config drive might explain the errors reported. I‘ll first address the syringe pull request by adding static em0 IP and use a pre-built config drive.