Vmx 17.X Image Boot in Qemu and Observations
Aug 20
Hi,
I had to test some of the available features for Vmx 17.x image, 17.2 R1 Image and here are my observations when tested in Qemu Emulator based on Eve-Ng.
Two Node Topology.
Image and Memory Details –
-> One Router – Split into Two Qemu Instances – VCP/VFP (Control Plane / Forwarding Plane) so you need to have both of them.
-> VCP – I have allocated 2 Vcpus and 2048MB of RAM / VFP – 3 Vcpu and 6096MB of RAM
-> You can go with the lower Memory / Cpu allocations, I had the resources so allocated them just to be on a higher side.
Requirement – EM1 Should be connected for both VFP and VCP without that these will not function.
The boot process took more than 20 minutes to me, may be because I was using a USB drive to load the image and Disk IO must have been slower, else 11-15 minutes should do.Β The auto-image upgrade will irriate you and hence I disabled it.
Lets look at routing engine and forwarding plane, PFE is booting into a Local Linux shell Mode. We wont access this box unless required for troubleshooting, all the Access is on VCP.
You can log into the forwarding plane for an instance but the speed of interaction with VFP is very slow, understandably it has to fetch it from another Qemu Image via EM1 interface.
Performance over Qemu Simulation is satisfactory and should be a good tool for JNCIE-Lab preperations, needless to say it will help all other types of study requirements as well. With an enhanced processor and with SSD disks, i guess the performance will improve dramatically.
I shall be shortly testing VQFX image as well and will update with similar Findings.
-R
Jul 10, 2018 @ 23:11:17
Hello Rakesh. Is it fine to wait for VFP to boot to a long time and at the end I am seeing only two rows about some Linux process like initrd initialized?
Otherwise VCP is working fine.
Jul 11, 2018 @ 00:16:21
Hi Nikolay, As long as you are good with FPC status in VCE “show chassis fpc” online and lists all the interfaces in “show int terse” I wouldn’t worry much. Alternatively, you can disable logging at the system level
Jul 11, 2018 @ 00:17:19
Secondly, I would recommend you use 16.x vmx image instead of 17.x, i had some problems with 17 when i was trying it and 16.x images works perfectly fine and should suffice most of the protocol replications
Jul 11, 2018 @ 01:01:54
Hello Rakesh,
Thanks for your quick answer. I am pretty new to Juniper and wanted to add the images to EVE , but was not sure if they are working correctly.
I think that VFP is not having enough resources to load properly. ( 3 cpus and 4gb of RAM currently. But that should be enough)
I am seeing that all the interfaces are up under “show int terse” except the GE ones. ( as shown on EVE’s site)
If you do not mind , would it be a problem to share the vmx image for version 16 , because I have found only vmx 17.2R1.13 and vsrx 15 images.
Thanks in advance.
Jul 18, 2018 @ 04:54:29
Thatβs the only thing that I canβt do buddy, if you look hard you should be good to find π
Jul 19, 2018 @ 21:46:23
Thanks Rakesh. I appreciate your answers.
Sep 26, 2019 @ 18:00:00
[root@VMX vmx]# ./vmx.sh -lv –install
==================================================
Welcome to VMX
==================================================
Date……………………………………….09/26/19 06:21:59
VMX Identifier………………………………vmx1
Config file…………………………………/root/vmx/config/vmx.conf
Build Directory……………………………../root/vmx/build/vmx1
Assuming kvm hypervisor………………………
Virtualization type………………………….kvm
Junos Device type……………………………virtio
Environment file……………………………./root/vmx/env/centos_virtio.env
Junos Device Type……………………………virtio
Initialize scripts…………………………..[OK]
[OK]
[OK]
==================================================
VMX Environment Setup Completed
==================================================
==================================================
VMX Install & Start
==================================================
Linux distribution…………………………..centos
Check GRUB………………………………….[Disabled]
Installation status of qemu-kvm……………….[OK]
Installation status of libvirt-client………….[OK]
Installation status of bridge-utils……………[OK]
Installation status of python…………………[OK]
Installation status of libyaml-devel…………..[OK]
Installation status of numactl………………..[OK]
Installation status of numactl-devel…………..[OK]
Installation status of parted-devel……………[OK]
Installation status of libpciaccess-devel………[OK]
Installation status of yajl-devel……………..[OK]
Installation status of libxml2-devel…………..[OK]
Installation status of glib2-devel…………….[OK]
Installation status of libnl-devel…………….[OK]
Check Kernel Version…………………………[Disabled]
Check Qemu Version…………………………..[Disabled]
Check libvirt Version………………………..[Disabled]
Check virsh connectivity……………………..[OK]
[OK]
[OK]
==================================================
Pre-Install Checks Completed
==================================================
Check RE state………………………………[Not Running]
[OK]
Check for VM vfp-vmx1………………………..[Not Running]
[OK]
Check if bridge br-ext exists…………………[No]
Cleanup VM bridge br-ext……………………..[OK]
Cleanup VM bridge br-int-vmx1…………………[OK]
Cleanup VM bridge br-fab-vmx1…………………[OK]
==================================================
VMX Stop Completed
==================================================
Check VCP image……………………………..[OK]
Check VFP image……………………………..[OK]
Check VCP Config image……………………….[OK]
Check management interface……………………[OK]
Setup huge pages to 8192……………………..[OK]
Attempt to kill libvirtd……………………..[OK]
Attempt to start libvirtd…………………….[OK]
Sleep 2 secs………………………………..[OK]
Check libvirt support for hugepages……………[OK]
==================================================
System Setup Completed
==================================================
Get Management Address of eth0………………..[OK]
Generate libvirt files……………………….[OK]
Sleep 2 secs………………………………..[OK]
Find configured management interface…………..eth0
Find existing management gateway………………eth0
Check if eth0 is already enslaved to br-ext…….[No]
Gateway interface needs change………………..[Yes]
Create br-ext……………………………….[OK]
Get Management Gateway……………………….1.1.1.1
Flush eth0………………………………….[OK]
Start br-ext………………………………..[OK]
Bind eth0 to br-ext………………………….[OK]
Get Management MAC…………………………..8a:2b:b8:59:c0:fc
Assign Management MAC 8a:2b:b8:59:c0:fc………..[OK]
Add default gw 110.93.250.185…………………[OK]
scripts/common/vmx_common_utils.sh: line 597: [: missing `]’
Create br-int-vmx1…………………………..[OK]
Start br-int-vmx1……………………………[OK]
[OK]
Define vcp-vmx1……………………………..[OK]
Start vcp-vmx1………………………………[Failed]
error: Failed to start domain vcp-vmx1
error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
Log file……………………………………/root/vmx/build/vmx1/logs/vmx_1569493319.log
==================================================
Aborted!. 1 error(s) and 0 warning(s)
==================================================
Hi Rakesh,
I am having below error while installing vmx on Centos. Please help me out in this case.,
Oct 12, 2019 @ 17:13:40
Hi Siddiqui, The logs are complaining about access to KVM / host virtualization, can you verify if KVM is enabled on the system or not.