Preparing a VM for pfSense 2.8

G

gusto

Well-Known Member
Feb 10, 2018
107
3
58
25
I recently installed the latest PVE 9.1 and migrated the VM and LXC to the new PVE.
I also migrated the pfSense 2.7.2 VM.
I am not a fan of upgrading, but I like to install the latest system.
Here is the recommended installation of pfSense on proxmox.
I assume this documentation is quite old.
Does anyone have a best practice on how to prepare a VM for pfsense 2.8.0?

BTW
I just recently got around to installing a debian VM using cloud init (qcow2, raw) and it is a great help.
I am looking for something similar for pfsense, but I have no problem installing manually from an ISO as well
 
I understand, but I need to prepare the VM for Proxmox VE.
The pfSense forum doesn't give me any advice on how to prepare the VM.
 
gusto said:
Does anyone have a best practice on how to prepare a VM for pfsense 2.8.0?
Click to expand...

Its all documented in the article you linked. Its still just an ordenary ISO like any other OS. The VM settings are documented just fine aswell.
 
  • Like
Reactions: Johannes S and news
As I wrote at the beginning, I don't like upgrades. After all, I've been using pfSense since 2020 and I've already done one upgrade.
It seems to me that I have some ballast in psSense, so I'd rather use a clean install and restore the configuration via xml.
 
AI prepared a working script for me.
You only need to set
VM_NAME
STORAGE
ISO_PATH
Click to expand...
VM ready in 3 seconds

Code: 
#!/bin/bash

VM_ID=$(pvesh get /cluster/nextid)
VM_NAME="pfSense-2.8.0"
STORAGE="local-zfs"
ISO_PATH="local:iso/netgate-installer-v1.1.1-RELEASE-amd64.iso"

echo "Create VM $VM_ID ($VM_NAME)..."

qm create $VM_ID \
  --name "$VM_NAME" \
  --memory 2048 \
  --cores 2 \
  --sockets 1 \
  --cpu host \
  --ostype other \
  --machine q35 \
  --scsihw virtio-scsi-single \
  --net0 virtio,bridge=vmbr0 \
  --net1 virtio,bridge=vmbr1 \
  --onboot 1 \
  --tablet 1


qm set $VM_ID --virtio0 "$STORAGE:10",iothread=1
qm set $VM_ID --ide2 "$ISO_PATH",media=cdrom
qm set $VM_ID --boot order="virtio0;ide2;net1"
 
See if this post helps at all

S

Thread 'Proxmox management GUI not reachable when using OPNsense and VLANs'

I have the following network configuration: an ISP router connected via cable to the server’s network port eno1, where Proxmox is installed, and a second port eno2 coming out of Proxmox that will be connected to a switch for network management (VLANs, etc.). Nothing is connected on the outgoing side yet because I am still doing some tests.

On the Proxmox node there are vmbr0 and vmbr1; only vmbr1 has an IP address automatically assigned by my ISP router.

I created a virtual machine with OPNsense.
OPNsense is configured with vnet0 as WAN...
 
You must log in or register to reply here.
Top Bottom