I guess its a bug: https://github.com/opnsense/core/issues/8324
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: Patrick M. Hausen on October 23, 2024, 01:54:25 PM
Try this:
1. System > Settings > Tunables
2. Add tunable, name=hw.vtnet.csum_disable, value=1
3. Save and reboot
Quote from: Patrick M. Hausen on October 23, 2024, 01:43:50 PMYes, https://yandex.cloud/en/docs/vpc/concepts/software-accelerated-network#reg-vm and https://yandex.cloud/en/docs/compute/operations/image-create/custom-image#requirements
KVM based cloud and VirtIO network interfaces? Please check and report back.
Quote2.3. Network protocols that require a single virtual IP address (VIP) across VMs, such as HSRP, VRRP, or GLBP, are not supported.There is also no functionality to create virtual interface(only binded to specific network)
Quote
Boot disk images must meet the following requirements:
The virtio-net, virtio-blk, and virtio-pci drivers are installed. If you are going to attach file storages to your VM, you also need to install the virtiofs driver. For more information, refer to this guide.
The ttyS0 terminal (COM1 port) is set up as a serial console. For more information, refer to this guide.
The network interface runs correctly when starting a VM and obtains the IP address via DHCP.
The cloud-init package is installed and configured to work with our metadata service. To install the package for CentOS, run the sudo yum install cloud-init command. To install it for Debian or Ubuntu, run sudo apt update && sudo apt install -y cloud-init.
If you created an image based on an Amazon Machine Image (AMI), verification of the cloud platform where the VM instance is run is disabled in the cloud-init settings. For more information, refer to this guide.
In the system firewall settings, the minimum required set of ports for running your applications and a port for SSH access (by default, 22 TCP) are open.
The SSH server starts automatically at VM startup.
Services running your application are resistant to VM reboots.
The boot disk uses MBR partitioning.
The disk is mounted by its UUID rather than by name.
The file system is not encrypted.