Versions this guide is based on:

EVE Image Name Folder Downloaded Filename Version vCPUs vRAM
xrv9k-fullk9-6.2.3 fullk9-R-XRV9000-623-RR.tar fullk9-R-XRV9000-623-RR 4 16384
xrv9k-fullk9-6.5.1 fullk9-R-XRV9000-651.tar fullk9-R-XRV9000-651 4 16384

Other versions should also be supported following bellow's procedure.


Using any suitable archive program, unzip origonal fullk9-R-XRV9000-623-RR.tar to obtain image: xrv9k-fullk9-x.vrr-6.2.3.qcow2

Steps below are based on xrv9k-fullk9-x.vrr-6.2.3.qcow2 creation, for other image deployment, use proper names respectively.

SSH to EVE and login as root, from cli and create temporary working directory on the EVE's root:

mkdir /opt/unetlab/addons/qemu/xrv9k-fullk9-6.2.3/

Upload the  xrv9k-fullk9-x.vrr-6.2.3.qcow2 image to the EVE /opt/unetlab/addons/qemu/xrv9k-fullk9-6.2.3/ using for example FileZilla or WinSCP.

From cli go to created directory and rename image:

cd /opt/unetlab/addons/qemu/xrv9k-fullk9-6.2.3/
mv xrv9k-fullk9-x.vrr-6.2.3.qcow2 virtioa.qcow2

Fix permissions:

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

NOTE: When you will start node first time it can look like it is crashed, simply stop node and start again. It is happens because during first boot node image adopt for your system. It is observed on older Intel CPUs. New generation CPUs like E5-26XX series must be fine.

XRv9000 Node is very heavy and suitable for servers EVEs only. Boot time takes time, patience, just wait till in show run appears GE interfaces. Node is ready.