19 November 2025
20 November 2025
Romeo#check-vt
To check virtualization, do the following:
Run this:
kvm-ok
Then this:
grep -cw vmx /proc/cpuinfo
And check the results. If CPU returns 0 or KVM is not supported, then enable virtualization on your VM.
21 November 2025
Santosh GaireФотография
i am still waiting the help from those member who have solution and already faced such issue in this PNETLAB environment.
22 November 2025
Фотография
click to show
click to show
I got T5810 XEON (18c 36 vCPU) with 128 GB RAM. I use VMware worksation 17.
i am trying to run a fortigate LAB which requires extra vCPU for Forti manager and Forti Analyser. While setting up the resources for my PNETLAB, I cannot select more than 16 CPU. Moreover If I changes the "Number of cores per processor" to two I get error that number of processor cores exceed maximum supported value of 16.
could some one please comment on this
Replymessage unavailable
If you encounter issues with a node not starting or immediately stopping after clicking the start button, consider the following checklist and potential solutions:
Common Checks:
1. Image Integrity:
- Verify that the image is not corrupted. Compare the size of the image on your server with the size of the image from the source (e.g., LabHub).
For IOL Images:
1. Generate License File:
- Ensure that the license file is generated. Send #generate_license in this chat to receive instructions on how to generate the license file.
For QEMU Images:
1. Virtualization Support:
- Confirm that virtualization is supported on your system. Send #check-vt in this chat to receive instructions on how to check for virtualization support.
2. Fix Permissions:
- Correct permissions either through the GUI (click the button under "Settings" on PNetLab) or by running the following command in the terminal:
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
3. Follow the naming conventions:
- Adhere to the naming conventions required for PNetLab to detect imported qcow2 files as VMs. Refer to the conventions outlined here: https://www.eve-ng.net/index.php/documentation/qemu-image-namings/
By following these steps, you can address potential issues related to image integrity, licensing for IOL images, virtualization support for QEMU images, and permissions. If the problem persists after performing these checks and fixes, please let us know.
Replymessage unavailable
ishare2:
ishare2 installation instructions
Ensure your DNS is functioning correctly by pinging GitHub or Google:
ping raw.githubusercontent.com
0. (Optional) Remove old ishare2 configuration files:
rm -rf /opt/ishare2/ && rm -rf /usr/sbin/ishare2
1. Run the quick one-line installation command:
wget -O /usr/sbin/ishare2 https://raw.githubusercontent.com/ishare2-org/ishare2-cli/main/ishare2 && chmod +x /usr/sbin/ishare2 && ishare2
2. Enjoy ishare2!
Extra notes:
- If you face errors downloading images with ishare2 run:
ishare2 config
Then press enter in all questions to use the default configuration.
- If you encounter any errors while configuring ishare2 related to the site i-share.top, send #remove_ishare to this chat to learn how to fix it.
See more installation methods in the GitHub README
NeonI got T5810 XEON (18c 36 vCPU) with 128 GB RAM. I use VMware worksation 17.
i am trying to run a fortigate LAB which requires extra vCPU for Forti manager and Forti Analyser. While setting up the resources for my PNETLAB, I cannot select more than 16 CPU. Moreover If I changes the "Number of cores
run it baremetal or on esxi