我使用EVEng community 5.0.1-13，hypervisor是VMware Workstation 17 Pro，為方便將實驗中的節點連接真實網路，我會對虛擬網卡做一些調整，如下
我建議以系統管理員身分開啟vmware，再參考我的操作。安裝完成vmware後，VMnet1網卡預設應該是host-only，我的習慣是VMnet1用來直連真實網路(意味著使用VM做PPPoE)、VMnet8用來做管理網路並重設定DHCP範圍。
匯入EVE後，資源請自行調整，主要是我會將EVE原網卡改為NAT，再新增一張網卡連接VMnet1
啟動eve後，預設CLI帳號是root / eve，GUI是admin / eve，首次登入需要做簡單初始化，GUI部分我習慣用native console，原因是terminal可以用putty，而html5會用瀏覽器新分頁，占用記憶體資源難免會比putty高一些。
eve網卡pnet0是NAT管理網路、pnet1應該可直連真實網路，如果你的直連真實網路就像家用網路有分享器，那應該也有DHCP，你可以用dhclient pnet1來確認是否連接。
登入EVE新建並進入實驗室，新增網路，如下截圖；
bridge可以當作是無網管交換器，DHCP client連接bridge是抓不到IP的。
Management(Cloud0)是連接VMnet8，我的示範是192.168.123.0 / 24。
Cloud1是直連真實網路，我的家用網路是192.168.57.0 / 24；注意！如果你仍然抓不到DHCP，請重啟EVE。
接著我將示範導入Cisco IOS 15.3 router、Cisco c9800 17.06.04、Cisco vIOS 15.2 L3 switch、Cisco Nexus 9000 switch、Cisco DCNM 11.5.1、Cisco Viptela、Cisco ISE 3.0、Cisco ASA 9.8(4)10、Cisco FTD 6.6.1 / FMC 7.0.4 / NGIPS 7.0.4、Aruba VMC 8.6.0.15、Fortigate 6.4 、Paloalto 8.0.0、Paloalto 10.1.3、Checkpoint R81-T392、F5 BIG-IP LTM 16.0.0.1、ubuntu 16.04、Windows 11 21H2、WindowsServer 2019。
Cisco IOS 15.3 router:
使用c7200-adventerprisek9-mz.153-3.XB12.bin，可以用SCP等方式傳輸；在本示範中，傳輸完成後檔案在家目錄/root下。
cd /opt/unetlab/addons/dynamips/
mv ~/c7200-adventerprisek9-mz.153-3.XB12.bin ./
unzip -p c7200-adventerprisek9-mz.153-3.XB12.bin > c7200-adventerprisek9-mz.153-3.XB12.image
rm c7200-adventerprisek9-mz.153-3.XB12.bin
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
計算IDLE-PC
dynamips -P 7200 /opt/unetlab/addons/dynamips/c7200-adventerprisek9-mz.153-3.XB12.image
組合鍵「ctrl+]+i」，顯示建議值；組合鍵「ctrl+]+q」，離開Cisco IOS回到EVE。
Cisco vIOS L3 switch：
使用vios-adventerprisek9-m.SPA.152.T.qcow2
mkdir /opt/unetlab/addons/qemu/vios-adventerprisek9-m.SPA.152.T
cd /opt/unetlab/addons/qemu/vios-adventerprisek9-m.SPA.152.T/
mv ~/vios-adventerprisek9-m.SPA.152.T.qcow2 ./sataa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Cisco Nexus 9000 switch:
使用nexus9500v.9.3.3.qcow2
mkdir /opt/unetlab/addons/qemu/nxosv9k-9500v-9.3.3
cd /opt/unetlab/addons/qemu/nxosv9k-9500v-9.3.3/
mv ~/nexus9500v.9.3.3.qcow2 ./sataa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Cisco c9800 17.06.04：
mkdir /opt/unetlab/addons/qemu/c9800cl-17.06.04
cd /opt/unetlab/addons/qemu/c9800cl-17.06.04/
mv ~/C9800-CL-universalk9.17.06.04.iso ./
/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 16G
/opt/qemu-2.2.0/bin/qemu-system-x86_64 -nographic -drive file=virtioa.qcow2,if=virtio,bus=0,unit=0,cache=none -machine type=pc-1.0,accel=kvm -serial mon:stdio -nographic -nodefconfig -nodefaults -rtc base=utc -cdrom C9800-CL-universalk9.17.06.04.iso -boot order=dc -m 4096
首次啟動，可以選serial console；啟動過程需等待一下，terminal將看到「Rebooting from HD」，然後組合鍵ctrl+a+c進入qemu提示符號，再輸入quit回到EVE。
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Cisco DCNM 11.5.1：
使用dcnm-va.11.5.1.iso
mkdir /opt/unetlab/addons/qemu/dcnm-va11.5.1
cd /opt/unetlab/addons/qemu/dcnm-va11.5.1/
mv ~/dcnm-va.11.5.1.iso cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 50G
Cisco viptela：
1)viptela vManage 18.4.5
mkdir /opt/unetlab/addons/qemu/vtmgmt-18.4.5
cd /opt/unetlab/addons/qemu/vtmgmt-18.4.5/
mv ~/viptela-vmanage-18.4.5-genericx86-64.qcow2 ./virtioa.qcow2
2)viptela vSmart 18.4.5
mkdir /opt/unetlab/addons/qemu/vtsmart-18.4.5
cd /opt/unetlab/addons/qemu/vtsmart-18.4.5/
mv ~/viptela-smart-18.4.5-genericx86-64.qcow2 ./virtioa.qcow2
3)viptela vBond與vEdge是相同image，19.2.3
mkdir /opt/unetlab/addons/qemu/vtbond-19.2.3
cd /opt/unetlab/addons/qemu/vtbond-19.2.3/
mv ~/viptela-edge-19.2.3-genericx86-64.qcow2 ./virtioa.qcow2
mkdir /opt/unetlab/addons/qemu/vtedge-19.2.3
cd /opt/unetlab/addons/qemu/vtedge-19.2.3/
mv ~/viptela-edge-19.2.3-genericx86-64.qcow2 ./virtioa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Cisco ISE3.0：
mkdir /opt/unetlab/addons/qemu/ise-3.0.0.458
cd /opt/unetlab/addons/qemu/ise-3.0.0.458/
mv ~/ise-3.0.0.458.SPA.x86_64.iso ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 50G
Cisco ASA 9.8(4)10：
使用asav984-10.qcow2
mkdir /opt/unetlab/addons/qemu/asav-984-10
cd /opt/unetlab/addons/qemu/asav-984-10/
mv ~/asav984-10.qcow2 ./virtioa.qcow2
提醒：建議以VNC當作開啟terminal。
Cisco FTD 6.6.1 / FMC 7.0.4 / NGIPS 6.2.3：
使用Cisco_Firepower_Threat_Defense_Virtual-6.6.1-91.qcow2
mkdir /opt/unetlab/addons/qemu/firepower-FTD-6.6.1-91
cd /opt/unetlab/addons/qemu/firepower-FTD-6.6.1-91/
mv ~/Cisco_Firepower_Threat_Defense_Virtual-6.6.1-91.qcow2 ./virtioa.qcow2
使用Cisco_Firepower_Mgmt_Center_Virtual_KVM-7.0.4-55.qcow2
mkdir /opt/unetlab/addons/qemu/firepower-FMC-7.0.4
cd /opt/unetlab/addons/qemu/firepower-FMC-7.0.4/
mv ~/Cisco_Firepower_Mgmt_Center_Virtual_KVM-7.0.4-55.qcow2 ./virtioa.qcow2
使用firepower-NGIPS-7.0.4-55.tar.gz
mkdir /opt/unetlab/addons/qemu/firepower-NGIPS-7.0.4-55
cd /opt/unetlab/addons/qemu/firepower-NGIPS-7.0.4-55/
mv ~/firepower-NGIPS-7.0.4-55.tar.gz ./
tar xvf Cisco_Firepower_NGIPS_VMware-7.0.4-55.tar.gz
/opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 Cisco_Firepower_NGIPS_VMware-7.0.4-55-disk1.vmdk sataa.qcow2
Aruba VMC 8.6.0.15：
mkdir /opt/unetlab/addons/qemu/aruba-VMC-8.6.0.15-81969
cd /opt/unetlab/addons/qemu/aruba-VMC-8.6.0.15-81969
mv ~/ArubaOS_VMC_8.6.0.15_81969.ova ./
tar xf ArubaOS_VMC_8.6.0.15_81969.ova
/opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 ArubaOS_VMC_8.6.0.15_81969-disk1.vmdk hda.qcow2
/opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 ArubaOS_VMC_8.6.0.15_81969-disk2.vmdk hdb.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
cumulus-vx-4.2.0：
mkdir /opt/unetlab/addons/qemu/cumulus-vx-4.2.0
cd /opt/unetlab/addons/qemu/cumulus-vx-4.2.0
mv cumulus-vx-4.2.0.qocw2 virtioa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Fortigate 6.4:
使用fortios6.4-IDE.qcow2
mkdir /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010
cd /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010/
mv ~/fortios6.4-IDE.qcow2 ./virtioa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
提醒：由於license限制，無法調整Fortigate的資源(核心數與記憶體)。
此Fortigate VM，如要啟用PPPoE功能，需額外設定如下(以port1為例)
config system interface
edit port1
set mode pppoe
end
Paloalto 8.0.0：
使用Paloalto-PA-VM-KVM-8.0.0.qcow2
mkdir /opt/unetlab/addons/qemu/paloalto-8.0.0
cd /opt/unetlab/addons/qemu/paloalto-8.0.0/
mv ~/Paloalto-PA-VM-KVM-8.0.0.qcow2 ./virtioa.qcow2
Paloalto 10.1.3：
使用PA-VM-KVM-10.1.3.qcow2
mkdir /opt/unetlab/addons/qemu/paloalto-10.1.3
cd /opt/unetlab/addons/qemu/paloalto-10.1.3/
mv ~/PA-VM-KVM-10.1.3.qcow2 ./virtioa.qcow2
Checkpoint R81-T392：
mkdir /opt/unetlab/addons/qemu/cpsg-R81-T392
cd /opt/unetlab/addons/qemu/cpsg-R81-T392/
mv ~/Check_Point_R81_T392.iso ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 80G
F5 BIG-IP LTM 16.0.0.1：
使用BIGIP-16.0.0.1-0.0.3.qcow2
mkdir /opt/unetlab/addons/qemu/BIGIP-16.0.0.1
cd /opt/unetlab/addons/qemu/BIGIP-16.0.0.1/
mv ~/BIGIP-16.0.0.1-0.0.3.qcow2 ./virtioa.qcow2
ubuntu 16.04：
mkdir /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.7
cd /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.7/
mv ~/ubuntu-16.04.7-desktop-amd64.iso ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 50G
提醒：往後新增此ubuntu 16.04節點，需要重新安裝；請自行衡量磁碟空間。
若你需要可直接使用跳過安裝步驟的VM，在首次安裝完成後，將已安裝完成的作業系統覆蓋原來的空虛擬硬碟，如下
cd /opt/unetlab/tmp/0/[UUID]/[node ID]/
/opt/qemu/bin/qemu-img commit hda.qcow2
EVE將回應訊息「Image committed.」
如何查看UUID、node ID？ 如下
那麼未來新增的VM節點(以ubuntu 16.04為例)，都是完成安裝系統的節點，無需重裝；
若又想要乾淨的OS、自主重新安裝呢? 下面是解決方案
cd /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.7/
rm virtioa.qcow2
上面的Checkpoint R81-T392、下面的Windows 11 21H2、Windows Server 2019亦同。
Windows 11 21H2：
mkdir /opt/unetlab/addons/qemu/win-11test
cd /opt/unetlab/addons/qemu/win-11test/
mv ~/'Win11_21H2_Chinese(Traditional)_x64.iso' ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 50G
安裝過程中，如果遇到無法辨識磁碟，請參考如下步驟
Windows Server 2019：
mkdir /opt/unetlab/addons/qemu/winserver-2019
cd /opt/unetlab/addons/qemu/winserver-2019/
mv ~/'Windows Server 2019.iso' ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 50G
安裝過程中，如果遇到無法辨識磁碟，請參考如上Windows 11安裝步驟。
可以在QEMU custom options欄位修改參數，以提升VM效能，也可以調整Windows解析度
-machine type=pc,accel=kvm -cpu qemu64,+fsgsbase -vga std -usbdevice tablet -boot order=dc -drive file=/opt/qemu/share/qemu/virtio-win-drivers.img,index=1,if=floppy,readonly
任何問題或討論，可在下方留言評論或聯繫我：buddhaya7@gmail.com
I'm use EVEng community 5.0.1-13, my hypervisor is VMware Workstation 17 Pro. For connecting real network from EVE lab, we need adjust setting about virtual adapter, it like...
I'm suggest start vmware by administrator permission, and then to look my demo. If you finished install vmware, VMnet1 adapter should host-only by default. My habit that VMnet1 is connecting real network(means VM(s) is able to enable PPPoE feature), the VMnet8 adapter is management network and re-adjust DHCP parameters.
[image]
After import EVE, you can adjust resource of EVE. I will adjust that adapter is NAT, and then add an adapter is VMnet 1.
[image]
Started EVE, CLI is root / eve, GUI is admin / eve by default. In first login, EVE will auto to do basic initializing. In GUI, I like use native console, the reason terminal is putty-based, but html5 used browser, maybe its resource overhead is more high than putty.
EVE adapter, pnet0 is NAT management network, pnet1 is direct connect real network. If your real network is like home-router, it should has DHCP feature, you can use 「dhclient pnet1」to confirm.
Login EVE, add a lab and enter. add a new network, it like screenshot:
The bridge, it as hub, DHCP client(s) connect the bridge, they can not to get IP address.
Management(Cloud0) is VMnet8 based, my demo is 192.168.123.0 / 24.
Cloud1 is direct connect real network, my home-network is 192.168.57.0/24; ATTENTION! If you still can not to get IP address, please reboot EVE.
[image]
Next, I will demo how import Cisco IOS 15.3 router、Cisco c9800 17.06.04、Cisco vIOS 15.2 L3 switch、Cisco Nexus 9000 switch、Cisco DCNM 11.5.1、Cisco Viptela、Cisco ISE 3.0、Cisco ASA 9.8(4)10、Cisco FTD 6.6.1 / FMC 7.0.4 / NGIPS 6.2.3、Aruba VMC 8.6.0.15、Fortigate 6.4 、Paloalto 8.0.0、Paloalto 10.1.3、Checkpoint R81-T392、F5 BIG-IP LTM 16.0.0.1、ubuntu 16.04、Windows 11 21H2、WindowsServer 2019。
Cisco IOS 15.3 router:
I using c7200-adventerprisek9-mz.153-3.XB12.bin, you can transport file by SCP or anyway; In my demo, the file located home directory that is /root
cd /opt/unetlab/addons/dynamips/
mv ~/c7200-adventerprisek9-mz.153-3.XB12.bin ./
unzip -p c7200-adventerprisek9-mz.153-3.XB12.bin > c7200-adventerprisek9-mz.153-3.XB12.image
rm c7200-adventerprisek9-mz.153-3.XB12.bin
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Calculating IDLE-PC
dynamips -P 7200 /opt/unetlab/addons/dynamips/c7200-adventerprisek9-mz.153-3.XB12.image
Combo-key「ctrl+]+i」, show suitable value; Combo-key「ctrl+]+q」, leave Cisco IOS and back to EVE.
Cisco vIOS L3 switch：
I using vios-adventerprisek9-m.SPA.152.T.qcow2
mkdir /opt/unetlab/addons/qemu/vios-adventerprisek9-m.SPA.152.T
cd /opt/unetlab/addons/qemu/vios-adventerprisek9-m.SPA.152.T/
mv ~/vios-adventerprisek9-m.SPA.152.T.qcow2 ./sataa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Cisco Nexus 9000 switch:
I using nexus9500v.9.3.3.qcow2
mkdir /opt/unetlab/addons/qemu/nxosv9k-9500v-9.3.3
cd /opt/unetlab/addons/qemu/nxosv9k-9500v-9.3.3/
mv ~/nexus9500v.9.3.3.qcow2 ./sataa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Cisco c9800 17.06.04：
mkdir /opt/unetlab/addons/qemu/c9800cl-17.06.04
cd /opt/unetlab/addons/qemu/c9800cl-17.06.04/
mv ~/C9800-CL-universalk9.17.06.04.iso ./
/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 16G
/opt/qemu-2.2.0/bin/qemu-system-x86_64 -nographic -drive file=virtioa.qcow2,if=virtio,bus=0,unit=0,cache=none -machine type=pc-1.0,accel=kvm -serial mon:stdio -nographic -nodefconfig -nodefaults -rtc base=utc -cdrom C9800-CL-universalk9.17.06.04.iso -boot order=dc -m 4096
First start, you can chosse serial console; The start process that needs waiting about minutes, you will see「Rebooting from HD」 in terminal, and then combo-key「ctrl+a+c」to enter qemu prompt, press quit back to EVE.
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Cisco DCNM 11.5.1：
I using dcnm-va.11.5.1.iso
mkdir /opt/unetlab/addons/qemu/dcnm-va11.5.1
cd /opt/unetlab/addons/qemu/dcnm-va11.5.1/
mv ~/dcnm-va.11.5.1.iso cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 50G
Cisco viptela：
1)viptela vManage 18.4.5
mkdir /opt/unetlab/addons/qemu/vtmgmt-18.4.5
cd /opt/unetlab/addons/qemu/vtmgmt-18.4.5/
mv ~/viptela-vmanage-18.4.5-genericx86-64.qcow2 ./virtioa.qcow2
2)viptela vSmart 18.4.5
mkdir /opt/unetlab/addons/qemu/vtsmart-18.4.5
cd /opt/unetlab/addons/qemu/vtsmart-18.4.5/
mv ~/viptela-smart-18.4.5-genericx86-64.qcow2 ./virtioa.qcow2
3)viptela vBond and vEdge are same image, 19.2.3
mkdir /opt/unetlab/addons/qemu/vtbond-19.2.3
cd /opt/unetlab/addons/qemu/vtbond-19.2.3/
mv ~/viptela-edge-19.2.3-genericx86-64.qcow2 ./virtioa.qcow2
mkdir /opt/unetlab/addons/qemu/vtedge-19.2.3
cd /opt/unetlab/addons/qemu/vtedge-19.2.3/
mv ~/viptela-edge-19.2.3-genericx86-64.qcow2 ./virtioa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Cisco ISE3.0：
mkdir /opt/unetlab/addons/qemu/ise-3.0.0.458
cd /opt/unetlab/addons/qemu/ise-3.0.0.458/
mv ~/ise-3.0.0.458.SPA.x86_64.iso ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 50G
Cisco ASA 9.8(4)10：
I using asav984-10.qcow2
mkdir /opt/unetlab/addons/qemu/asav-984-10
cd /opt/unetlab/addons/qemu/asav-984-10/
mv ~/asav984-10.qcow2 ./virtioa.qcow2
Remind：I'm suggest as terminal by VNC.
Cisco FTD 6.6.1 / FMC 7.0.4 / NGIPS 7.0.4：
I using Cisco_Firepower_Threat_Defense_Virtual-6.6.1-91.qcow2
mkdir /opt/unetlab/addons/qemu/firepower-FTD-6.6.1-91
cd /opt/unetlab/addons/qemu/firepower-FTD-6.6.1-91/
mv ~/Cisco_Firepower_Threat_Defense_Virtual-6.6.1-91.qcow2 ./virtioa.qcow2
I using Cisco_Firepower_Mgmt_Center_Virtual_KVM-7.0.4-55.qcow2
mkdir /opt/unetlab/addons/qemu/firepower-FMC-7.0.4
cd /opt/unetlab/addons/qemu/firepower-FMC-7.0.4/
mv ~/Cisco_Firepower_Mgmt_Center_Virtual_KVM-7.0.4-55.qcow2 ./virtioa.qcow2
I using firepower-NGIPS-7.0.4-55.tar.gz
mkdir /opt/unetlab/addons/qemu/firepower-NGIPS-7.0.4-55
cd /opt/unetlab/addons/qemu/firepower-NGIPS-7.0.4-55/
mv ~/firepower-NGIPS-7.0.4-55.tar.gz ./
tar xvf Cisco_Firepower_NGIPS_VMware-7.0.4-55.tar.gz
/opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 Cisco_Firepower_NGIPS_VMware-7.0.4-55-disk1.vmdk sataa.qcow2
cumulus-vx-4.2.0：
mkdir /opt/unetlab/addons/qemu/cumulus-vx-4.2.0
cd /opt/unetlab/addons/qemu/cumulus-vx-4.2.0
mv cumulus-vx-4.2.0.qocw2 virtioa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Aruba VMC 8.6.0.15：
mkdir /opt/unetlab/addons/qemu/aruba-VMC-8.6.0.15-81969
cd /opt/unetlab/addons/qemu/aruba-VMC-8.6.0.15-81969
mv ~/ArubaOS_VMC_8.6.0.15_81969.ova ./
tar xf ArubaOS_VMC_8.6.0.15_81969.ova
/opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 ArubaOS_VMC_8.6.0.15_81969-disk1.vmdk hda.qcow2
/opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 ArubaOS_VMC_8.6.0.15_81969-disk2.vmdk hdb.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Fortigate 6.4:
I using fortios6.4-IDE.qcow2
mkdir /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010
cd /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010/
mv ~/fortios6.4-IDE.qcow2 ./virtioa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Remind：Because license restrict, you can not adjust recourse(processor & memory) in Fortigate.
This Fortigate VM, if you want to enable PPPoE feature, need these commands：(port1 is example)
config system interface
edit port1
set mode pppoe
end
Paloalto 8.0.0：
I using Paloalto-PA-VM-KVM-8.0.0.qcow2
mkdir /opt/unetlab/addons/qemu/paloalto-8.0.0
cd /opt/unetlab/addons/qemu/paloalto-8.0.0/
mv ~/Paloalto-PA-VM-KVM-8.0.0.qcow2 ./virtioa.qcow2
Paloalto 10.1.3：
I using PA-VM-KVM-10.1.3.qcow2
mkdir /opt/unetlab/addons/qemu/paloalto-10.1.3
cd /opt/unetlab/addons/qemu/paloalto-10.1.3/
mv ~/PA-VM-KVM-10.1.3.qcow2 ./virtioa.qcow2
Checkpoint R81-T392：
mkdir /opt/unetlab/addons/qemu/cpsg-R81-T392
cd /opt/unetlab/addons/qemu/cpsg-R81-T392/
mv ~/Check_Point_R81_T392.iso ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 80G
F5 BIG-IP LTM 16.0.0.1：
I using BIGIP-16.0.0.1-0.0.3.qcow2
mkdir /opt/unetlab/addons/qemu/BIGIP-16.0.0.1
cd /opt/unetlab/addons/qemu/BIGIP-16.0.0.1/
mv ~/BIGIP-16.0.0.1-0.0.3.qcow2 ./virtioa.qcow2
ubuntu 16.04：
mkdir /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.7
cd /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.7/
mv ~/ubuntu-16.04.7-desktop-amd64.iso ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 50G
Remind： If you want to add this node ubuntu 16.04 in future, you need re-install; Please to measure disk size self.
If you need VM of installed OS, first finished install OS, and then cover that original empty virtual disk, it like...
cd /opt/unetlab/tmp/0/[UUID]/[node ID]/
/opt/qemu/bin/qemu-img commit hda.qcow2
EVE will echo message「Image committed.」
How view UUID, node ID? follow me...
[image]
So, you add VM(example ubuntu 16.04) node(s) in future. They are installed OS, not need re-install;
However, if you want to get a clear OS? re-install self? Next is solution
cd /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.7/
rm virtioa.qcow2
Checkpoint R81-T392 in above, Windows 11 21H2、Windows Server 2019 in under, they are also.
Windows 11 21H2：
mkdir /opt/unetlab/addons/qemu/win-11test
cd /opt/unetlab/addons/qemu/win-11test/
mv ~/'Win11_21H2_Chinese(Traditional)_x64.iso' ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 50G
In install process, if VM can not verify disk / driver, please refer these steps
[image]
Windows Server 2019：
mkdir /opt/unetlab/addons/qemu/winserver-2019
cd /opt/unetlab/addons/qemu/winserver-2019/
mv ~/'Windows Server 2019.iso' ./cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 hda.qcow2 50G
In install process, if VM can not verify disk / driver, please refer Windows 11 step in previous section.
You can modify parameters in QEMU custom options, for improve VM performance. And you can modify Windows desktop resolution,
[image]
-machine type=pc,accel=kvm -cpu qemu64,+fsgsbase -vga std -usbdevice tablet -boot order=dc -drive file=/opt/qemu/share/qemu/virtio-win-drivers.img,index=1,if=floppy,readonly
Any issue or discuss, you can leave comment in under or contact me：buddhaya7@gmail.com
