Versions this guide is based on:
| EVE Image Foldername | Downloaded Filename | Version | vCPUs | vRAM | Qemu version | Interface |
|---|---|---|---|---|---|---|
| xrv8102-24.1.1 | fullk9-R-XRV9000-2411-RR.tar | fullk9-R-XRV9000-2411-RR | 8 | 20480 | 5.2.0 | Hu |
| xrv8102-XR-25.2.1 | fullk9-R-XRV9000-2521-RR.tar | fullk9-R-XRV9000-2521 | 8 | 20480 | 5.2.0 | Ge |
| xrv8102-26-1-1-CML | Cisco CML XRV9000 26.1.1 | CML XRV9000 26.1.1 | 8 | 20480 | 6.0.0 | Ge |
XRv 9000 versions 24.x and higher are using UEFI boot, therefore, need extra EFI boot files to be used for proper image running.
| Instructions |
|---|
| Other versions should also be supported following bellow’s procedure. Using a ready-made original KVM image from vendor.
Steps below are based on fullk9-R-XRV9000-2521-RR creation, for other image deployment, use proper names respectively. Using any suitable archive program, unzip original fullk9-R-XRV9000-2521-RR.tar to obtain KVM image. 1. SSH to EVE and login as root, from cli and create image directory on the EVE: mkdir /opt/unetlab/addons/qemu/xrv8102-XR-25.2.1
2. Upload the xrv9k-fullk9-x.vrr-25.2.1.qcow2 image to the EVE /opt/unetlab/addons/qemu/xrv8102-XR-25.2.1/ using, for example, FileZilla or WinSCP. 3. From cli, go to created directory and rename original filename xrv9k-fullk9-x.vrr-25.2.1.qcow2 to the virtioa.qcow2: cd /opt/unetlab/addons/qemu/xrv8102-XR-25.2.1/
mv xrv9k-fullk9-x.vrr-25.2.1.qcow2 virtioa.qcow2
4. Download EFI boot files, unzip it, and load EFI boot files in the image directory, using, for example, FileZilla or WinSCP. root@eve-master:/opt/unetlab/addons/qemu/xrv8102-XR-25.2.1# ls
OVMF.fd OVMF_CODE.fd OVMF_VARS.fd virtioa.qcow2
5. Fix permissions /opt/unetlab/wrappers/unl_wrapper -a fixpermissions
6. Template settings. When adding your xrv8102 image on the topology, make sure you have adjusted interface names accordingly the screen below. The name of main interfaces are G0/0/0/x
First three interfaces of this node are reserved for image internal use.  |