@Sergei_Shablovsky said in Screen fonts & mode in local terminal issue:

Already have in /etc/loader.conf

:charset=UTF-8:
:lang=en_US.UTF-8:
:setenv=LC_COLLATE=C:
:umask=022:

But unsuccessfully, - the result You able to see above….

Those are not loader.conf configuration directives, those look like /etc/login.conf configuration. (And read the note at the top of that file, especially the part where you have to run cap_mkdb /etc/login.conf after any edits)

It does seem like you have some sort of issue/mismatch with UTF-8 handling somewhere, but it's hard to say exactly where. I have no issues with UTF-8 in my terminals over serial or SSH but I have no idea what that KVM setup might be doing.

@tim4532 said in Proxmox SR-IOV VF pass-through to pfSense VM:

FYI: My board got 2x 1G and 2x 10G ports.

I would definitely use one of the 10G for pfSense WAN set for vtnet0 connected directly to your ISP modem. Once you assigned say ens2f0 to vtnet0, you don't need to passthrough the entire NIC, just plug the cable from your ISP and it will automatically passthrough...same goes for LAN if you have an external switch, do the same as you did with WAN and connect Proxmox's management port to the switch...you would have one port available for whatever you want.

@viragomann said in Running pfSense 2.4.4 over a KVM VM in PROXMOX 6.1.5.:

You will get the best benefits of the processor features, when using host type. This passes all the features of the processor through to the VM, while KVM64 provides only a small amount of common features. For instance, KVM64 doesn't make use of AES-NI, even if your host CPU supports it.

with kvm64 you can set extra cpu flags though, including AES. All via proxmox gui.