⚠️ : The demo image typically has lower throughput, limited interface counts, and may lack advanced features like MPLS-TE, SR-PCE, or full-scale routing tables.
Since .qcow2 is a "copy-on-write" format, heavy logging or configuration changes can cause I/O wait spikes (visible as %wa in top ). 4. Troubleshooting High Utilization If the "top" report shows the instance is struggling: iosxrvk9demo613qcow2 top
Create a folder named iosxrvk9-6.1.3 in your EVE-NG directory. Upload the .qcow2 file and rename it to virtioa.qcow2 . Fix permissions via the EVE-NG CLI. ⚠️ : The demo image typically has lower
sudo apt install qemu-kvm libvirt-daemon-system virt-manager Troubleshooting High Utilization If the "top" report shows
When running top on a host machine (like Linux or a hypervisor), a single IOS XRv 9000 instance typically shows high consumption due to its architecture:
| Feature | Supported? | |---------|-------------| | BGP, OSPF, IS-IS | ✅ Yes | | MPLS L3VPN | ✅ Yes (control plane) | | MPLS forwarding | ❌ No | | Segment Routing | ✅ Partial (control) | | Traffic generation | ❌ No | | Netflow / SNMP | ✅ Limited | | Scale | ❌ ~10 routes, 1–2 VRFs |