Juniper offers a 60 day trial version of the full vMX release on their site here. There's also a good set up guide on this blog.
There's a caveat here, though. Last I checked, it runs on Ubuntu with KVM. And honestly, I would run this on a dedicated server (or a beefy Ubuntu VM) for evaluation purposes. Since it uses two VMs to act as a single "instance", you'll need some pretty hefty system resources available:
5 cores for the the VMs (1 vCPU for the VCP, and 4 for the VFP)
8GB RAM (2 GB for VCP, 6 GB for VFP)
The network interfaces only use virtio-net.
Personally, I'd run this either in a dedicated Ubuntu VM, or on a dedicated Server with multiple high-speed NICs. I tried running 2 "instances" in an Ubuntu VM concurrently, and 1 would always hang.
That's great, is every feature appears to work, plus Juniper with give you a license to purchase, so you don't have to re-install the vMX router, without having to recreate it.
If you want to play with vMX devices in a GNS3 topology, you can use the leaked 14.1R1.10,14.1R3.5, or 14.1R4.8 releases via Qemu+KVM, and only need to use 2GB of RAM per instance. Some of the releases DO need the following, to enable the PICs:
Verify you need this first:
show chassis fpc pic-status (if PIC 0 is missing,or says Offline, you'll need this)
show interfaces ge-* terse (if ge-* intefaces missing, you need this)
fix it with:
[email protected]% echo 'vm_local_rpio="1"' >> /boot/loader.conf
[email protected]% grep vm_ /boot/loader.comf
vm_local_rpio="1" <-- if done correctly, grep should return this.
save, and reboot the VM. Give it a few minutes after the VM boots, and it should come online, and you'll be good to go.
Also, if you're using this in GNS3, the interfaces match a little differently:
Eth0 = internal
Eth1 = internal
Eth2 = ge-0/0/0
Eth3 = ge-0/0/1
Eth4 = ge-0/0/2
Eth5 = ge-0/0/3
Hope this helps!
Edited by HermanToothrot, 22 November 2015 - 07:45 PM.