@dobby_ there are no official packages for hyper-v..there are for vmware..which i am not using. The tools are enabled under hyper-v. this is a long standing issue under hyper-v 2019 and i have tried the fixes there on 2022 to no avail. I have seen no system package to address this under hyper-v 2022 that i can see. if you know of some individual patches if you could pint me to it i would be happy to try it..:)

I also noticed 23.05 is released but no mention of addressing this issue under 2019 or 2022 hvper-v int he latest release notes.

@johnpoz with or without SR-IOV? Maybe you're asking for both scenarios, but in the case with SR-IOV I don't even know if it's worth testing with what I'm able to tell at this point...

@johnpoz Patch (@Patch) was kind enough to make a manual instructions here: https://forum.netgate.com/topic/162083/pfsense-vm-on-proxmox-qemu-agent-installation/27

I have sucessfully added one more interface. Couple of reboots and it resolved the issue. Will try to do 1:1 NAT and update the status here.

@thebigbear We did not work on routing. This should work out of the box. Our backup is working now. But the waagent is not in a perfect condition for freebsd as mentioned...

4bc02d28-050a-4b3c-a904-8753c4d80f9a-image.png

Now, I got it right without the need to disable any firewall...my mistake was to move default gateway to pfSense. The default gateway is just for Proxmox management port to update itself and need to remain on the port originally assigned. Then, I made pfSense LAN that IP. Both accessible by my Mac Pro on the same browser tabs next to each other.

Screenshot 2023-05-06 at 3.14.07 PM.png

Thank you, I will try.
Sam

@bmeeks Ahh, yeah, I'm using N5105 so this is almost certainly it. I'll keep an eye over there, but I guess there's no solution yet...

@dobby_ I think I might have narrowed it down to an issue with the Intel I226-V ethernet controllers my mini PC has. Ended up disabling the offloading options within the driver settings-

IPv4 Checksum Offload Large Send Offload V2 (IPv4) Large Send Offload V2 (IPv6) TCP Checksum Offload (IPv4) TCP Checksum Offload (IPv6) UDP Checksum Offload (IPv4) UDP Checksum Offload (IPv6)

The issue hasn't came back yet, so hopefully that might be it fixed.

found the potential fix here

Thanks,
Gary

@jk-1 I found the problem, for whatever reason (probably self-inflicted) the subnet mask on the VLANs that did not work was set to 32... 🤦

Well, persistence paid off...the key is to start hitting the ESC key before clicking start .

Screen Shot 2023-04-10 at 10.31.23 PM.png
Screen Shot 2023-04-10 at 10.35.20 PM.png

@thebear 2 vCPUs and 8G memory.

The issue is fixed with 0x24000024 microcode:
https://forum.proxmox.com/threads/vm-freezes-irregularly.111494/post-538922

The issue is fixed with 0x24000024 microcode:
https://forum.proxmox.com/threads/vm-freezes-irregularly.111494/post-538922

The issue is fixed with 0x24000024 microcode:
https://forum.proxmox.com/threads/vm-freezes-irregularly.111494/post-538922

@nollipfsense Hey thanks, I did all of that and i am still getting the same problems. i would have to reload a snapshot or do a clean install and use a restore of a backup done from the backup and restore of the pfsense gui.

what am i missing?

Thanks.

@perrfect I just ran thru this not on proxmox but on VM on synology which uses qemu

[2.6.0-RELEASE][admin@pfSense.home.arpa]/usr/local/etc/rc.d: service qemu-guest-agent start Starting qemu_guest_agent. [2.6.0-RELEASE][admin@pfSense.home.arpa]/usr/local/etc/rc.d: service qemu-guest-agent status qemu_guest_agent is running as pid 15340. [2.6.0-RELEASE][admin@pfSense.home.arpa]/usr/local/etc/rc.d:

I just rebooted the pfsense vm to make sure everything came up on its own

qemu.jpg

Looks like everything is working here.. I don't currently have a proxmox to play with - but I did have one a while back, and was running both 2.6 and snapshot of 2.7 on it, and don't recall any issues installing the qemu agent.. Was working fine.

edit: I think I read somewhere that you might have to actually stop the VM and then start it vs just a "reboot" for proxmox - been awhile since did it on proxmox, and don't currently have one to test with..

Whatever virtio devices are being created by ovirt they are not supported by the operating system.

VirtIO devices on Proxmox VE/KVM and so on in general work fine, though, so it's most likely something in your hypervisor or hypervisor settings.

Going to need a lot more detail than just the crash report there.

That panic/backtrace looks like it would be hardware related, but it appears to be a vmware VM. So your version of VMware may not be compatible with FreeBSD 14/13, or you may need to upgrade the hardware version of the VM.

@viragomann the 1st post with the /etc/network/interfaces file is no longer used, as the VMM's GUI setup the bridges nicely.
Here are the current /etc/network/interfaces files I have tried to ping 192.168.1.1 on the VM router from 192.168.1.120 on the VMM host machine are:

# interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: auto lo iface lo inet loopback auto enp3s0 iface enp3s0 inet static address 192.168.1.120/24 gateway 192.168.1.1 # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: auto lo iface lo inet loopback auto enp2s0 iface enp2s0 inet static address 192.168.1.120/24 gateway 192.168.1.1 # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: auto lo iface lo inet loopback auto macvtap1@enp2s0 iface macvtap1@enp2s0 inet static address 192.168.1.120/24 gateway 192.168.1.1 # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: auto lo iface lo inet loopback auto macvtap1 iface macvtap1 inet static address 192.168.1.120/24 gateway 192.168.1.1 # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: auto lo iface lo inet loopback auto vtnet1 iface vtnet1 inet static address 192.168.1.120/24 gateway 192.168.1.1

I updated the network topology a little to make it clearer?
alt text