Component: CHR
106 changelog entries across 43 version(s)
Releases by channel (stacked)
- fixed guest OS type "Other Linux (64-bit)";
- added Chelsio VF driver for PCIID 5803;
- improved virtio_net performance;
- fixed limited upgrades for expired instances;
- added Chelsio VF driver for PCIID 5803;
- added support for licensing over IPv6 network;
- fixed incorrect disk size for ARM64;
- iavf updated driver to 4.9.1 version;
- increased OVA default RAM amount from 160MB to 256MB;
- fixed public SSH key pulling when running on AWS;
- fixed booting with added additional SCSI disk;
- fixed Cloud DDNS update after license renewal;
- improved system stability when writing into memory;
- temporarily suspended downgrade to RouterOS v6;
- improved system stability when writing into memory;
- temporarily suspended downgrade to RouterOS v6;
- fixed OS provisioning on Azure;
- improved stability when changing "flow-control" settings on interfaces with e1000 drivers;
- fixed SSH key import on Azure;
- fixed VLAN tagged packet transmit on bridge for Hyper-V installations;
- improved interface loading on startup on XEN;
- improved system stability when changing flow control settings on e1000;
- fixed file system quiescing;
- added support for file system quiescing;
- added support for hardware watchdog on ESXI;
- enabled support for VMBus protocol version 4.1;
- improved system stability when running CHR on Hyper-V;
- added support for file system quiescing;
- enabled support for VMBus protocol version 4.1;
- improved system stability when running CHR on Hyper-V;
- fixed graceful shutdown execution on Hyper-V (introduced in v6.46);
- improved stability when changing ARP modes on e1000 type adapters;
- improved stability when changing ARP modes on e1000 type adapters;
- added support for Azure guest agent;
- legacy adapters require "disable-running-check=yes" to be set;
- assign interface names based on underlying PCI device order on KVM;
- distribute NIC queue IRQ's evenly across all CPUs;
- fixed IRQ balancing when using more than 32 CPUs;
- improved system stability when insufficient resources are allocated to the guest;
- fixed possible memory allocation failure when using multiple CPUs or interfaces on Xen installations;