| Area | Limitation | |------|-------------| | Forwarding performance | PFE is software-emulated – <1 Gbps, high latency. | | EVPN | Partial support – use 21.x or later for production-like EVPN. | | VXLAN routing | May require rebooting PFE after changes. | | SNMP bulk walks | Can cause RE CPU spikes. | | Graceful Routing Engine Switchover (GRES) | Not supported in single-RE images. | | Upgrade path | Must upgrade both RE and PFE images together; 20.2 → 21.2 is possible but nontrivial. |
| Attribute | Value |
| :--- | :--- |
| Hypervisor | QEMU / KVM (Linux KVM, Proxmox, OpenStack) |
| Disk Format | QCOW2 (supports snapshots, compression, backfiles) |
| Default CPU | 1-2 vCPU (vQFX RE is not CPU heavy) |
| Default RAM | 4 GB (Minimum) to 8 GB (Recommended for 20.2) |
| Disk Size | Typically ~2 GB compressed, ~8-12 GB uncompressed |
| Architecture | x86_64 (AMD64) |
| OS Inside | Junos OS (FreeBSD kernel-based) |
| Data Plane | Not in this file (Requires separate vqfx-pfe image) | Vqfx-20.2r1.10-re-qemu.qcow2
Upload your .qcow2 files to this directory using WinSCP, FileZilla, or the scp command from your computer. | Area | Limitation | |------|-------------| | Forwarding
Should you use Vqfx-20.2r1.10-re-qemu.qcow2? Without a linked PFE, this image is functionally
This is a critical distinction. The vQFX architecture is split:
Without a linked PFE, this image is functionally a "route reflector" or a management node – it cannot forward traffic.