Support and News Forum

Hi,

I was trying to run Juniper Vqfx with EVE. Vqfx has two qemu image - routing engine (RE) and packet forwarding engine (PFE). I have made the correct qcow2 image and uploaded them to eve. The PFE boots correctly and I can get console access. But the RE; i do not get any console access. It just shows a blank console screen in putty. No error is not displayed in eve log files.

I knew from previous experience that if you run Juniper images in VMware, the console just show "BTX loading" after that nothing comes in console. We need to configure "named pipe" as serial port in Juniper VM and then connect to that named pipe from putty to get console issues. But these stuffs are taken care by EVE automatically.

Is it issues like this with Vqfx, preventing console access? If then how to solve this in EVE?

Any help is appreciated.

Hi,

i have no Problems with vQFX - what Version are you using? D60 or D63? Did you change anything in the template when creating the Node? Can you post your settings?
All the fuzz with "named pipe creation" and so on is not needed - that's why I love eve so much Waaaay simpler than ESX

Regards
Chris

I used all the default settings. Nothing changed in the template. Tried with both D63 and D60 version. Only thing I did was to convert the vmdk files to qcow2 files and uploaded them to EVE.

Vqfx is ditributed in qcow format....

Use this format instead.

E.

I am using AMD ryzen. It is working in GSN3. But no luck in eve. Another thing does switching works in vqfx. I mean port in layer2 processing not layer3. I tried simple topology with two virtual pcs connected with two different ports in vqfx. But no luck. they can not ping each other.

Both L2 and L3 work just fine - with both D60 and D63...
However - I use Intel CPU (Xeon).
Do you have VT enabled?

At last success. It was a easy fix. Maybe help someone in future. I was able to run it properly by changing qemu version. By default, it runs with qemu 2.4.0 in EVE-NG. I can changed it to 2.9.0. Now vqfx runs perfectly.

strange, good of course that it is working,
But eve version 86 it works with qemu 2.4 as well..

UD

I changed to qemu v 2.9.0 and all is good for my issue too.