Page 1 of 1
Facing Issue in All qemu machines (fortigate, juniper vsrx, paloalto)
Posted: Fri Dec 01, 2017 6:39 pm
by faizan1985
Hi Guys
I have followed step by step procedure for the Juniper,Fortigate FW and Paloalto devices mentioned in eve-ng documentation, but unfortunately none of these devices are getting power on. Can any one help me on this please.
below is the link which I follow during paloalto deployment.
http://www.eve-ng.net/index.php/documen ... lto-vm-100
Re: Facing Issue in All qemu machines (fortigate, juniper vsrx, paloalto)
Posted: Sat Dec 02, 2017 11:29 pm
by ramindia
faizan1985 wrote: ↑Fri Dec 01, 2017 6:39 pm
Hi Guys
I have followed step by step procedure for the Juniper,Fortigate FW and Paloalto devices mentioned in eve-ng documentation, but unfortunately none of these devices are getting power on. Can any one help me on this please.
below is the link which I follow during paloalto deployment.
http://www.eve-ng.net/index.php/documen ... lto-vm-100
show us more information, topo, errors, and your hardware config how your setup is ?
R!
Re: Facing Issue in All qemu machines (fortigate, juniper vsrx, paloalto)
Posted: Tue Dec 05, 2017 7:15 pm
by faizan1985
Hi Guys,
I have not receive any error on eve gui when I start paloalto device its notify that the device is started after 5 sec it automatically getting power off and not coming on console access. kindly find the attached file for more details.
Below is the details of my setup
I have eve vm on vmware and which having 10G RAM and 40 GB hard disk
Below is the step by step procedure which I followed to built the paloalto device in eve-ng
EVE Image Name Downloaded Filename Version vCPUs vRAM Console
paloalto-7.0.1 PA-VM-ESX-7.0.1.ova 7.0.1 2 4096 Telnet
1 Method, converting from OVA VMDK disk.
1.1. Create temporary working directory and upload the downloaded image to the EVE using for example FileZilla or WinSCP. Then login as root using SSH protocol and uncompress it:
mkdir abc
cd abc
tar xf PA-VM-ESX-7.0.1.ova
1.2. Then convert the disk to the qcow2 format:
/opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 PA-VM-ESX-7.0.1-disk1.vmdk virtioa.qcow2
1.3. Create the folder for HDD image and move it:
mkdir /opt/unetlab/addons/qemu/paloalto-7.0.1
mv virtioa.qcow2 /opt/unetlab/addons/qemu/paloalto-7.0.1
1.4. Delete temporary directory abc and fix permissions:
cd ..
rm -rf abc
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Please help me I am facing the same issue in vsrx and fortigate firewall also
Re: Facing Issue in All qemu machines (fortigate, juniper vsrx, paloalto)
Posted: Wed Dec 06, 2017 1:07 am
by Uldis (UD)
first question if your eve VM has enabled Intel-VT-x option
show me output from eve cli:
kvm-ok
if you will see on output that KVM is not enabled then you simply didnt watch carefully EVE esxi installation video !!!
http://www.eve-ng.net/index.php/documen ... ne-install
UD
Re: Facing Issue in All qemu machines (fortigate, juniper vsrx, paloalto)
Posted: Wed Dec 06, 2017 6:34 pm
by faizan1985
Thanks Dear I think its Intel-VT-x option issue, I have opened vmx file on notepad and added below line in vmx file after that it start working
vhv.enable = "TRUE"