ERROR Unable to connect to qemu monitor (port 5000)

[eayetsi]

I have installed containerlab on Ubuntu VM 24.0.4 using proxmox. I have installed Palo Alto VM 10.2.5 but anytime I deploy it, the Palo Alto docker enters into "exit" mode after running for some time. I tried to increase the RAM & CPU allocated in the launch.py file but still. Below is the logs.

docker logs d5b567d771d7
2025-02-26 07:58:57,280: launch DEBUG Environment variables: environ({'CLAB_INTFS': '2', 'CLAB_LABEL_CLAB_NODE_GROUP': '', 'CLAB_LABEL_CLAB_NODE_KIND': 'paloalto_panos', 'CLAB_LABEL_CLAB_NODE_LAB_DIR': '/home/dds55admin/LABS/PA/clab-palo/palo-01', 'CLAB_LABEL_CLAB_NODE_LONGNAME': 'palo-01', 'CLAB_LABEL_CLAB_NODE_NAME': 'palo-01', 'CLAB_LABEL_CLAB_NODE_TYPE': '', 'CLAB_LABEL_CLAB_OWNER': 'dds55admin', 'CLAB_LABEL_CLAB_TOPO_FILE': '/home/dds55admin/LABS/PA/palo.yml', 'CLAB_LABEL_CONTAINERLAB': 'palo', 'CONNECTION_MODE': 'tc', 'DOCKER_NET_V4_ADDR': '10.168.100.0/24', 'DOCKER_NET_V6_ADDR': '', 'HOME': '/root', 'HOSTNAME': 'palo-01', 'NO_PROXY': 'localhost,127.0.0.1,::1,.local,10.168.100.0/24,10.168.100.10,alpine-01,alpine-02,palo-01', 'PASSWORD': 'Admin@123', 'PATH': '/.venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin', 'RAM': '6144', 'TERM': 'xterm', 'USERNAME': 'admin', 'VCPU': '2', 'VIRTUAL_ENV': '/.venv', 'no_proxy': 'localhost,127.0.0.1,::1,.local,10.168.100.0/24,10.168.100.10,alpine-01,alpine-02,palo-01', 'LC_CTYPE': 'C.UTF-8'})
2025-02-26 07:58:57,282: vrnetlab DEBUG class: PAN_vm, disk_image: /PA-VM-KVM-10.2.5.qcow2, overlay: /PA-VM-KVM-10.2.5-overlay.qcow2
2025-02-26 07:58:57,282: vrnetlab DEBUG Creating overlay disk image
2025-02-26 07:58:57,327: vrnetlab DEBUG Starting vrnetlab PAN
2025-02-26 07:58:57,327: vrnetlab DEBUG VMs: [<main.PAN_vm object at 0x79e4c980e3f0>]
2025-02-26 07:58:57,327: vrnetlab DEBUG VM not started; starting!
2025-02-26 07:58:57,327: vrnetlab INFO ----------------START ENVIRONMENT VARIABLES-----------------
2025-02-26 07:58:57,327: vrnetlab INFO CLAB_INTFS: 2
2025-02-26 07:58:57,327: vrnetlab INFO CLAB_LABEL_CLAB_NODE_GROUP:
2025-02-26 07:58:57,327: vrnetlab INFO CLAB_LABEL_CLAB_NODE_KIND: paloalto_panos
2025-02-26 07:58:57,327: vrnetlab INFO CLAB_LABEL_CLAB_NODE_LAB_DIR: /home/dds55admin/LABS/PA/clab-palo/palo-01
2025-02-26 07:58:57,328: vrnetlab INFO CLAB_LABEL_CLAB_NODE_LONGNAME: palo-01
2025-02-26 07:58:57,328: vrnetlab INFO CLAB_LABEL_CLAB_NODE_NAME: palo-01
2025-02-26 07:58:57,328: vrnetlab INFO CLAB_LABEL_CLAB_NODE_TYPE:
2025-02-26 07:58:57,328: vrnetlab INFO CLAB_LABEL_CLAB_OWNER: dds55admin
2025-02-26 07:58:57,328: vrnetlab INFO CLAB_LABEL_CLAB_TOPO_FILE: /home/dds55admin/LABS/PA/palo.yml
2025-02-26 07:58:57,328: vrnetlab INFO CLAB_LABEL_CONTAINERLAB: palo
2025-02-26 07:58:57,328: vrnetlab INFO CONNECTION_MODE: tc
2025-02-26 07:58:57,328: vrnetlab INFO DOCKER_NET_V4_ADDR: 10.168.100.0/24
2025-02-26 07:58:57,328: vrnetlab INFO DOCKER_NET_V6_ADDR:
2025-02-26 07:58:57,328: vrnetlab INFO HOME: /root
2025-02-26 07:58:57,328: vrnetlab INFO HOSTNAME: palo-01
2025-02-26 07:58:57,328: vrnetlab INFO LC_CTYPE: C.UTF-8
2025-02-26 07:58:57,328: vrnetlab INFO NO_PROXY: localhost,127.0.0.1,::1,.local,10.168.100.0/24,10.168.100.10,alpine-01,alpine-02,palo-01
2025-02-26 07:58:57,328: vrnetlab INFO PASSWORD: Admin@123
2025-02-26 07:58:57,328: vrnetlab INFO PATH: /.venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
2025-02-26 07:58:57,328: vrnetlab INFO RAM: 6144
2025-02-26 07:58:57,328: vrnetlab INFO TERM: xterm
2025-02-26 07:58:57,329: vrnetlab INFO USERNAME: admin
2025-02-26 07:58:57,329: vrnetlab INFO VCPU: 2
2025-02-26 07:58:57,329: vrnetlab INFO VIRTUAL_ENV: /.venv
2025-02-26 07:58:57,329: vrnetlab INFO no_proxy: localhost,127.0.0.1,::1,.local,10.168.100.0/24,10.168.100.10,alpine-01,alpine-02,palo-01
2025-02-26 07:58:57,329: vrnetlab INFO -----------------END ENVIRONMENT VARIABLES------------------
2025-02-26 07:58:57,329: vrnetlab INFO Launching PAN_vm with 4,sockets=1,cores=4 SMP/VCPU and 8192 M of RAM
2025-02-26 07:58:57,329: vrnetlab INFO Scrapli: Disabled
2025-02-26 07:58:57,329: vrnetlab INFO Transparent mgmt interface: Disabled
2025-02-26 07:58:57,329: vrnetlab DEBUG number of provisioned data plane interfaces is 2
2025-02-26 07:58:57,329: vrnetlab DEBUG waiting for provisioned interfaces to appear...
2025-02-26 07:58:57,330: vrnetlab DEBUG highest allocated interface id determined to be: 2...
2025-02-26 07:58:57,330: vrnetlab DEBUG interfaces provisioned, continuing...
2025-02-26 07:58:57,332: vrnetlab DEBUG qemu cmd: qemu-system-x86_64 -enable-kvm -display none -machine pc -monitor tcp:0.0.0.0:4000,server,nowait -serial telnet:0.0.0.0:5000,server,nowait -m 8192 -cpu host,level=9 -smp 4,sockets=1,cores=4 -drive if=ide,file=/PA-VM-KVM-10.2.5-overlay.qcow2 -uuid aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa -device pci-bridge,chassis_nr=1,id=pci.1 -device virtio-net-pci,netdev=p00,mac=0C:00:1b:e7:fa:00 -netdev user,id=p00,net=10.0.0.0/24,host=10.0.0.2,dns=10.0.0.3,dhcpstart=10.0.0.15,hostfwd=tcp:0.0.0.0:22-10.0.0.15:22,hostfwd=udp:0.0.0.0:161-10.0.0.15:161,hostfwd=tcp:0.0.0.0:80-10.0.0.15:80,hostfwd=tcp:0.0.0.0:443-10.0.0.15:443,hostfwd=tcp:0.0.0.0:830-10.0.0.15:830,hostfwd=tcp:0.0.0.0:6030-10.0.0.15:6030,hostfwd=tcp:0.0.0.0:8080-10.0.0.15:8080,hostfwd=tcp:0.0.0.0:9339-10.0.0.15:9339,hostfwd=tcp:0.0.0.0:32767-10.0.0.15:32767,hostfwd=tcp:0.0.0.0:57400-10.0.0.15:57400,tftp=/tftpboot -device virtio-net-pci,netdev=p01,mac=0C:00:9e:5d:42:01,bus=pci.1,addr=0x2 -netdev tap,id=p01,ifname=tap1,script=/etc/tc-tap-ifup,downscript=no -device virtio-net-pci,netdev=p02,mac=0C:00:79:e3:20:02,bus=pci.1,addr=0x3 -netdev tap,id=p02,ifname=tap2,script=/etc/tc-tap-ifup,downscript=no
2025-02-26 07:58:59,911: vrnetlab INFO STDOUT:
2025-02-26 07:58:59,911: vrnetlab INFO STDERR: qemu-system-x86_64: error: failed to set MSR 0x345 to 0x2000
qemu-system-x86_64: ../../target/i386/kvm/kvm.c:3183: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

2025-02-26 07:58:59,911: vrnetlab INFO STDOUT:
2025-02-26 07:58:59,911: vrnetlab INFO STDERR: qemu-system-x86_64: error: failed to set MSR 0x345 to 0x2000
qemu-system-x86_64: ../../target/i386/kvm/kvm.c:3183: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

2025-02-26 07:58:59,912: vrnetlab DEBUG KVM error, restarting
2025-02-26 07:58:59,912: vrnetlab INFO ----------------START ENVIRONMENT VARIABLES-----------------
2025-02-26 07:58:59,912: vrnetlab INFO CLAB_INTFS: 2
2025-02-26 07:58:59,912: vrnetlab INFO CLAB_LABEL_CLAB_NODE_GROUP:
2025-02-26 07:58:59,912: vrnetlab INFO CLAB_LABEL_CLAB_NODE_KIND: paloalto_panos
2025-02-26 07:58:59,912: vrnetlab INFO CLAB_LABEL_CLAB_NODE_LAB_DIR: /home/dds55admin/LABS/PA/clab-palo/palo-01
2025-02-26 07:58:59,912: vrnetlab INFO CLAB_LABEL_CLAB_NODE_LONGNAME: palo-01
2025-02-26 07:58:59,912: vrnetlab INFO CLAB_LABEL_CLAB_NODE_NAME: palo-01
2025-02-26 07:58:59,912: vrnetlab INFO CLAB_LABEL_CLAB_NODE_TYPE:
2025-02-26 07:58:59,912: vrnetlab INFO CLAB_LABEL_CLAB_OWNER: dds55admin
2025-02-26 07:58:59,913: vrnetlab INFO CLAB_LABEL_CLAB_TOPO_FILE: /home/dds55admin/LABS/PA/palo.yml
2025-02-26 07:58:59,913: vrnetlab INFO CLAB_LABEL_CONTAINERLAB: palo
2025-02-26 07:58:59,913: vrnetlab INFO CONNECTION_MODE: tc
2025-02-26 07:58:59,913: vrnetlab INFO DOCKER_NET_V4_ADDR: 10.168.100.0/24
2025-02-26 07:58:59,913: vrnetlab INFO DOCKER_NET_V6_ADDR:
2025-02-26 07:58:59,913: vrnetlab INFO HOME: /root
2025-02-26 07:58:59,913: vrnetlab INFO HOSTNAME: palo-01
2025-02-26 07:58:59,913: vrnetlab INFO LC_CTYPE: C.UTF-8
2025-02-26 07:58:59,913: vrnetlab INFO NO_PROXY: localhost,127.0.0.1,::1,.local,10.168.100.0/24,10.168.100.10,alpine-01,alpine-02,palo-01
2025-02-26 07:58:59,913: vrnetlab INFO PASSWORD: Admin@123
2025-02-26 07:58:59,913: vrnetlab INFO PATH: /.venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
2025-02-26 07:58:59,913: vrnetlab INFO RAM: 6144
2025-02-26 07:58:59,913: vrnetlab INFO TERM: xterm
2025-02-26 07:58:59,914: vrnetlab INFO USERNAME: admin
2025-02-26 07:58:59,914: vrnetlab INFO VCPU: 2
2025-02-26 07:58:59,914: vrnetlab INFO VIRTUAL_ENV: /.venv
2025-02-26 07:58:59,914: vrnetlab INFO no_proxy: localhost,127.0.0.1,::1,.local,10.168.100.0/24,10.168.100.10,alpine-01,alpine-02,palo-01
2025-02-26 07:58:59,914: vrnetlab INFO -----------------END ENVIRONMENT VARIABLES------------------
2025-02-26 07:58:59,914: vrnetlab INFO Launching PAN_vm with 4,sockets=1,cores=4 SMP/VCPU and 8192 M of RAM
2025-02-26 07:58:59,914: vrnetlab INFO Scrapli: Disabled
2025-02-26 07:58:59,914: vrnetlab INFO Transparent mgmt interface: Disabled
2025-02-26 07:58:59,914: vrnetlab DEBUG number of provisioned data plane interfaces is 2
2025-02-26 07:58:59,914: vrnetlab DEBUG waiting for provisioned interfaces to appear...
2025-02-26 07:58:59,915: vrnetlab DEBUG highest allocated interface id determined to be: 2...
2025-02-26 07:58:59,915: vrnetlab DEBUG interfaces provisioned, continuing...
2025-02-26 07:58:59,916: vrnetlab DEBUG qemu cmd: qemu-system-x86_64 -enable-kvm -display none -machine pc -monitor tcp:0.0.0.0:4000,server,nowait -serial telnet:0.0.0.0:5000,server,nowait -m 8192 -cpu host,level=9 -smp 4,sockets=1,cores=4 -drive if=ide,file=/PA-VM-KVM-10.2.5-overlay.qcow2 -uuid aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa -device pci-bridge,chassis_nr=1,id=pci.1 -device virtio-net-pci,netdev=p00,mac=0C:00:80:66:3f:00 -netdev user,id=p00,net=10.0.0.0/24,host=10.0.0.2,dns=10.0.0.3,dhcpstart=10.0.0.15,hostfwd=tcp:0.0.0.0:22-10.0.0.15:22,hostfwd=udp:0.0.0.0:161-10.0.0.15:161,hostfwd=tcp:0.0.0.0:80-10.0.0.15:80,hostfwd=tcp:0.0.0.0:443-10.0.0.15:443,hostfwd=tcp:0.0.0.0:830-10.0.0.15:830,hostfwd=tcp:0.0.0.0:6030-10.0.0.15:6030,hostfwd=tcp:0.0.0.0:8080-10.0.0.15:8080,hostfwd=tcp:0.0.0.0:9339-10.0.0.15:9339,hostfwd=tcp:0.0.0.0:32767-10.0.0.15:32767,hostfwd=tcp:0.0.0.0:57400-10.0.0.15:57400,tftp=/tftpboot -device virtio-net-pci,netdev=p01,mac=0C:00:24:ed:23:01,bus=pci.1,addr=0x2 -netdev tap,id=p01,ifname=tap1,script=/etc/tc-tap-ifup,downscript=no -device virtio-net-pci,netdev=p02,mac=0C:00:c0:fd:2f:02,bus=pci.1,addr=0x3 -netdev tap,id=p02,ifname=tap2,script=/etc/tc-tap-ifup,downscript=no
2025-02-26 07:59:01,920: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 1)
2025-02-26 07:59:02,924: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 2)
2025-02-26 07:59:03,925: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 3)
2025-02-26 07:59:04,926: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 4)
2025-02-26 07:59:05,927: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 5)
2025-02-26 07:59:06,929: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 6)
2025-02-26 07:59:07,930: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 7)
2025-02-26 07:59:08,931: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 8)
2025-02-26 07:59:09,932: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 9)
2025-02-26 07:59:10,933: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 10)
2025-02-26 07:59:11,934: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 11)
2025-02-26 07:59:12,935: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 12)
2025-02-26 07:59:13,936: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 13)
2025-02-26 07:59:14,937: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 14)
2025-02-26 07:59:15,938: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 15)
2025-02-26 07:59:16,939: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 16)
2025-02-26 07:59:17,940: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 17)
2025-02-26 07:59:18,941: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 18)
2025-02-26 07:59:19,942: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 19)
2025-02-26 07:59:20,943: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 20)
2025-02-26 07:59:21,944: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 21)
2025-02-26 07:59:22,945: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 22)
2025-02-26 07:59:23,945: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 23)
2025-02-26 07:59:24,946: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 24)
2025-02-26 07:59:25,947: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 25)
2025-02-26 07:59:26,948: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 26)
2025-02-26 07:59:27,949: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 27)
2025-02-26 07:59:28,950: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 28)
2025-02-26 07:59:29,952: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 29)
2025-02-26 07:59:30,953: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 30)
2025-02-26 07:59:31,954: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 31)
2025-02-26 07:59:32,955: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 32)
2025-02-26 07:59:33,956: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 33)
2025-02-26 07:59:34,957: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 34)
2025-02-26 07:59:35,957: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 35)
2025-02-26 07:59:36,958: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 36)
2025-02-26 07:59:37,960: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 37)
2025-02-26 07:59:38,961: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 38)
2025-02-26 07:59:39,962: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 39)
2025-02-26 07:59:40,963: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 40)
2025-02-26 07:59:41,964: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 41)
2025-02-26 07:59:42,965: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 42)
2025-02-26 07:59:43,966: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 43)
2025-02-26 07:59:44,967: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 44)
2025-02-26 07:59:45,968: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 45)
2025-02-26 07:59:46,969: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 46)
2025-02-26 07:59:47,970: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 47)
2025-02-26 07:59:48,971: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 48)
2025-02-26 07:59:49,972: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 49)
2025-02-26 07:59:50,973: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 50)
2025-02-26 07:59:51,974: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 51)
2025-02-26 07:59:52,975: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 52)
2025-02-26 07:59:53,976: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 53)
2025-02-26 07:59:54,977: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 54)
2025-02-26 07:59:55,978: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 55)
2025-02-26 07:59:56,979: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 56)
2025-02-26 07:59:57,980: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 57)
2025-02-26 07:59:58,982: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 58)
2025-02-26 07:59:59,983: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 59)
2025-02-26 08:00:00,984: vrnetlab ERROR Unable to connect to qemu monitor (port 5000), retrying in a second (attempt 60)
Traceback (most recent call last):
File "/launch.py", line 242, in
vr.start()
File "/vrnetlab.py", line 1035, in start
vm.work()
File "/vrnetlab.py", line 909, in work
self.check_qemu()
File "/vrnetlab.py", line 936, in check_qemu
self.start()
File "/vrnetlab.py", line 410, in start
raise QemuBroken(
vrnetlab.QemuBroken: Unable to connect to qemu monitor on port 5000

[hellt]

you will have to find out why your virtualization does not work

The symptoms you're having match this https://discord.com/channels/860500297297821756/1315707212114432092/1315707212114432092

[eayetsi]

Initially, I was having issues with nested virtualization. I fixed that on the Proxmox server.
After that, I started getting the error I posted above and I am struggling to resolve it.

[eayetsi]

I have checked the discord, the user finally switches to Debian and it solved his issue. I will try Debian.

[eayetsi]

I have installed Debian 12 but still I am having the same error.
Surprisingly, Juniper vMX works fine without any issues. It is the Palo Alto that I am facing this error.