# Inside the vQFX console, interrupt the bootloader (press space at 'Hit space to stop') set currdev=disk0s1: edit /boot/loader.conf # Add: hw.jedec.memory_mapping=1 # Save and boot Symptom: Running commit takes 2 minutes. Solution: This is a known issue with vQFX 20.2. The "exclusive" build usually has a patch, but if not:
# Create a directory for your switch mkdir vqfx-leaf-01 cd vqfx-leaf-01 qemu-img create -b /path/to/vqfx202r110reqemuqcow2.exclusive -f qcow2 vqfx-leaf-01_disk.qcow2 vqfx202r110reqemuqcow2 exclusive
set interfaces fxp0 unit 0 family inet address 192.168.1.10/24 commit To truly leverage the exclusive nature of this QCOW2, apply these kernel-level tweaks on your KVM host. CPU Pinning Do not let the vQFX float on all cores. Pin it to physical cores. # Inside the vQFX console, interrupt the bootloader
set system commit factory-settings set system commit synchronize Why hunt for vqfx202r110reqemuqcow2 exclusive ? Because it is the preferred node for ContainerLab and EVE-NG topologies. CPU Pinning Do not let the vQFX float on all cores
<domain type='kvm'> <name>vqfx-exclusive</name> <memory unit='GB'>6</memory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <boot dev='hd'/> </os> <devices> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/vqfx-leaf-01_disk.qcow2'/> <target dev='vda' bus='virtio'/> </disk> <!-- Management Interface --> <interface type='bridge'> <source bridge='br0'/> <model type='virtio'/> <target dev='vnet0'/> </interface> <!-- Data Plane Interface --> <interface type='bridge'> <source bridge='br1'/> <model type='virtio'/> <target dev='vnet1'/> </interface> </devices> </domain> virsh define vqfx.xml virsh start vqfx-exclusive virsh console vqfx-exclusive Warning: The "exclusive" image may boot faster than standard images, but still expect 2-3 minutes for the Juniper CLI to appear. Log in with root (no password).