Search results

Update: Decided to put my UDM Pro into Recovery Mode and flash the firmware to it. It fixed it, must have gotten corrupted somehow???

Thanks for the help. I tried your fix/workaround earlier, but it didn't work for me, sadly.

The subnet in question is 10.2.4.0/24 this is where the additional bridge is being added, it's also where my computer is. The main Proxmox bridge is on subnet 10.4.4.0/24. I didn't find anything being blocked in the logs.

Glad you got something working @MarioG . I can't get anything to work, even your method, tried going back to PVE 8 too.

Very interesting! Looks like the same issue to me, ping and tracert look similar too. Hopefully someone will chime in who might know a fix, this is over my head.

@MarioG is the machine you are using to access Proxmox on a different subnet? I feel I'm having a very similar issue to yours. I can access the gui if my machine is on the same subnet, but as soon as I move to the other I loose everything, gui, ping, etc... But as soon as I remove that second...

Thank you, removing the pci-e devices, then adding them back in with out "all functions" selected worked.

Thanks for the help dcsapak! Interesting, looking at that it does look like I am passing through the same device/port. Going back and deleting the two nic ports, and adding all 4 ports from the same Intel card The output of qm config 100 is now: It looks like the .0 or the .1 at the end of...

# qm config 100 agent: 1 balloon: 0 boot: order=scsi0;ide2 cores: 2 cpu: qemu64 hostpci2: 0b:00 hostpci3: 0b:00 ide2: local:iso/pfSense-CE-2.5.1-RELEASE-amd64.iso,media=cdrom memory: 2048 name: pfsense numa: 0 onboot: 1 ostype: l26 scsi0: vm-storage:vm-100-disk-0,size=50G scsihw: virtio-scsi-pci...

Hello, I have been trying to get Pfsense CE 2.5 to boot in a vm for a couple of days now. I've gone over the wiki, and many other blogs and forum posts without success. As soon as I start the vm I get "Error: start failed: QEMU exited with code1". The output is: The only output that doesn't...