1
24.1 Production Series / Re: Opnsense (Virtualized) - very high CPU utilization (System Interrupt)
« on: April 18, 2024, 10:02:16 am »
So here is my conf file, as you can see the BIOS is "seabios" and I have also disabled ballooning - without these the VM would never get more that 2GB RAM and was a known issue at the time I created the machine.
Also of note, the local LAN connection is the only one using a bridge to allow the correct accesses to the main network and other VMs, the other 3 ports are directly passed through to OPNsense so they remain fully under its control.
Code: [Select]
agent: 1
args: -vnc 0.0.0.0:10
balloon: 0
bios: seabios
boot: order=scsi0
cores: 4
cpu: host
hostpci0: 0000:01:00,pcie=1
hostpci1: 0000:03:00,pcie=1
hostpci2: 0000:04:00,pcie=1
hotplug: disk,network,usb,cpu
machine: q35
memory: 8192
meta: creation-qemu=8.1.2,ctime=1701086589
name: BART
net0: virtio=BC:**:**:**:**:**,bridge=vmbr0
numa: 1
onboot: 1
ostype: l26
scsi0: local-zfs:vm-100-disk-1,discard=on,iothread=1,size=64G
scsihw: virtio-scsi-single
smbios1: uuid=eea6ccd6-1219-4c51-9197-1ba191093aa5
sockets: 1
startup: order=2
tags: linux;vm
usb0: host=051d:0003
vmgenid: 80e66679-5bdc-4270-93ed-fa9338dbb336
Also of note, the local LAN connection is the only one using a bridge to allow the correct accesses to the main network and other VMs, the other 3 ports are directly passed through to OPNsense so they remain fully under its control.