Page 1 of 1

XRv console blank

Posted: Sun Mar 25, 2018 5:49 am
by prime
Hi,

I've EVE running in a VM Workstation and I'm facing an issue that when I start XRv boxes, they show up as blue, but when I open the console it's blank. I've reinstalled EVE twice now, made sure Intel Vt-d is enabled in BIOS. My 7200 dynamips image is working fine though. I've tried copying some other qcow2 images also from a different installation, which is also not working. I also have old version of UNL in VM, which also have problem with XRv now. Couple of months back, when I last used these (both UNL and EVE) XRv was working fine. After stopping XRv in web page, I'm getting some logs like this.
eve.png
Any idea what to do?

Re: XRv console blank

Posted: Sun Mar 25, 2018 12:58 pm
by Uldis (UD)
Only answer is: improperly prepared XRv image

this one is how to prep image from VMDK
http://www.eve-ng.net/index.php/documen ... -from-virl

this one for XRv node from ova:
http://www.eve-ng.net/index.php/documen ... -cisco-xrv

UD

Re: XRv console blank

Posted: Mon Mar 26, 2018 6:07 pm
by prime
Thanks for your reply.

I had working UNL as well as EVE couple of months back. XR (5.2.2 and 6.x) was also working fine in that. I just tried opening it again recently for practice that's when it started this behavior. So I'm pretty sure XRv images were prepared properly. Anyway I reinstalled EVE twice now, XRv was prepared from the OVA using the same link that you pasted, but console is blank.

Re: XRv console blank

Posted: Mon Mar 26, 2018 8:34 pm
by Uldis (UD)
It can be Antivirus issue as well, if is turned on virtualization check on it.
AVG for example..
Go to menu>settings>troubleshooting, then, under "enable hardware-assisted vertualization" uncheck "use nested virtualization where available". That allows a VM to use its own virtualization.

Ud

Re: XRv console blank

Posted: Wed Mar 28, 2018 6:46 pm
by prime
That was it! Thanks a lot.

I had installed Avast a few months back, when I was not using EVE, so that's why it stopped working. Changed that setting and after reboot it's working again. Thanks again :)