Labs

Hello There,

I am new to Juniper Networks, and I am doing my CCNA to JNCIA. I am trying to deploy a vSRX instance on Proxmox VE to act as a Router/Firewall that connects my Lab VMs to my LAN for Internet access. I had spun up a VM with the vSRX 23.2R2.21 qcow2 image with 4 vCPU and 4 GB RAM. When it starts to boot, it comes the below stage and stops booting. I had tried various combination of processor types and a few different versions of vSRX images and i keep on landing at this stage. If anyone had success with deploying a vSRX in Proxmox VE, kindly share your experiences and please give some pointers to fix this issue. Many thanks!

Booting [/packages/sets/pending/boot/os-kernel/kernel]...               
GDB: debug ports: uart
GDB: current port: uart
KDB: debugger backends: ddb gdb ndb
KDB: current backend: ddb
---<<BOOT>>---
Copyright (c) 1998-2024 Juniper Networks, Inc.
Copyright (c) 1992-2020 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD JNPR-12.1-20240103.68b4802_builder_stable_12_232 #0 r356482+68b4802bbad(stable/12_232): Thu Jan 11 08:36:15 PST 2024
    builder@qnc-jre-fbsd01:/volume/build/junos/occam/llvm-13.0/sandbox-232-20240103-68b4802/freebsd/stable_12_232/20240103.192550_builder_stable_12_232.68b4802/obj/amd64/juniper/kernels/JNPR-AMD64-PRD/kernel amd64
Juniper clang version 13.0.1 (git@eng-gitlab.juniper.net:tools-tot/llvm 544c4172eb64cc08971439913565b388db21a680)
VT(vga): text 80x25
module crypto already present!
module vmbus already present!
CPU: QEMU Virtual CPU version 2.5+ (2592.06-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x60fb1  Family=0xf  Model=0x6b  Stepping=1
  Features=0x1783fbfd<FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x82b82201<SSE3,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,AESNI,HV>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
Hypervisor: Origin = "KVMKVMKVM"
real memory  = 5368709120 (5120 MB)
avail memory = 4069834752 (3881 MB)
mtx_platform_early_bootinit: M/T/EX/SRX Series Early Boot Initialization
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff8057d1b0
stack pointer           = 0x28:0xffffffff836c9cd0
frame pointer           = 0x28:0xffffffff836c9cd0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = resume, IOPL = 0
current process         = 0 ()
trap number             = 12
panic: page fault
cpuid = 0
time = 1
Uptime: 1s

------------------------------
Thanks and regards,
Bhuvanesh Kumar N J
------------------------------

Can you find/share the QEMU/KVM command line being run by Proxmox in this instance?

Art

This is what i got before trying @jad's Solution

root@pve01:/junos# qm list
      VMID NAME                 STATUS     MEM(MB)    BOOTDISK(GB) PID       
       100 gns3-vm              stopped    14336              0.00 0         
       101 debian-test          stopped    2048              32.00 0         
       102 test-vSRX            stopped    4092              18.01 0         
root@pve01:/junos# ps aux | grep kvm | grep 102
root@pve01:/junos#


And this is after trying his solution:

root@pve01:~# qm list
      VMID NAME                 STATUS     MEM(MB)    BOOTDISK(GB) PID       
       100 gns3-vm              stopped    14336              0.00 0         
       101 debian-test          stopped    2048              32.00 0         
       102 test-vSRX            running    4092              18.01 3954      
root@pve01:~# ps aux | grep kvm | grep 102
root        3954 96.2 25.9 6080304 4216436 ?     Sl   03:16   0:55 /usr/bin/kvm -id 102 -name test-vSRX,debug-threads=on -no-shutdown -chardev socket,id=qmp,path=/var/run/qemu-server/102.qmp,server=on,wait=off -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control -pidfile /var/run/qemu-server/102.pid -daemonize -smbios type=1,uuid=8c44a85c-c8f7-49f2-bce4-54d2e18752eb -smp 4,sockets=1,cores=4,maxcpus=4 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg -vnc unix:/var/run/qemu-server/102.vnc,password=on -cpu host,+kvm_pv_eoi,+kvm_pv_unhalt -m 4092 -object iothread,id=iothread-virtioscsi0 -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-bridge,id=pci.3,chassis_nr=3,bus=pci.0,addr=0x5 -device vmgenid,guid=1dfac410-1587-4283-8dda-7d48d7c025ab -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -chardev socket,id=serial0,path=/var/run/qemu-server/102.serial0,server=on,wait=off -device isa-serial,chardev=serial0 -device VGA,id=vga,bus=pci.0,addr=0x2 -chardev socket,path=/var/run/qemu-server/102.qga,server=on,wait=off,id=qga0 -device virtio-serial,id=qga0,bus=pci.0,addr=0x8 -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on -iscsi initiator-name=iqn.1993-08.org.debian:01:3c204e8f72a6 -drive if=none,id=drive-ide2,media=cdrom,aio=io_uring -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2 -device virtio-scsi-pci,id=virtioscsi0,bus=pci.3,addr=0x1,iothread=iothread-virtioscsi0 -drive file=/dev/pve/vm-102-disk-0,if=none,id=drive-scsi0,discard=on,format=raw,cache=none,aio=io_uring,detect-zeroes=unmap -device scsi-hd,bus=virtioscsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,rotation_rate=1,bootindex=100 -netdev type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=BC:24:11:16:81:1D,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256 -machine type=pc+pve0 -machine smbios-entry-point-type=32
root@pve01:~# 

Recent QEMU 8.1 changed the default to SMBIOS 3.0, using a 64-bit entry point, while older uses a 32-bit entry point.

In Proxmox you can go back to 32-bit entry point using one of two different ways:

1. Change the Machine Version to 8.0 or below
2. Add the following line to the VM config file (under /etc/pve/qemu-server/): "args: -machine smbios-entry-point-type=32"

I have not tested vsrx 24.2 images but it should not have that problem but I haven't tested it yet.

Thanks @jad this solution got the machine working, but I want to  monitor the vSRX instance to ensure its working.