# 20220112_coreos-status-aws-m4-instances Subject: Networking loss on some AWS instance types in testing 35.20220103.2.0 and next 35.20220103.1.0 There is a networking regression in the latest releases of Fedora CoreOS `testing` (`35.20220103.2.0`) and `next` (`35.20220103.1.0`) that causes a high percentage of affected AWS instances to boot without network connectivity. The issue affects instance types that use Enhanced Networking with the Intel 82599 VF interface [1], including C3, C4, D2, I2, M4 (except m4.16xlarge), and R3. Within the next 24 hours, we plan to issue new `testing` and `next` releases that avoid the problem by downgrading the kernel. Until then, we've updated the AMI list on the download page [2] and in stream metadata to point to previous releases. For updates and more information, including progress toward an upstream fix, see [3]. To recover access to an instance that has lost connectivity after an upgrade, consult the workaround steps [4] in the tracker issue. Benjamin Gilbert, for the Fedora CoreOS team [1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sriov-networking.html [2] https://getfedora.org/en/coreos/download [3] https://github.com/coreos/fedora-coreos-tracker/issues/1066 [4] https://github.com/coreos/fedora-coreos-tracker/issues/1066#issuecomment-1011516609 Subject: Networking loss on some AWS instance types in testing 35.20220103.2.0 and next 35.20220103.1.0 *Cross posted with [this](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fedoraproject.org/message/FS3X6JOUNLKKF2W5EKV3WLBFAOS7RNKE/) coreos-status email.* There is a networking regression in the latest releases of Fedora CoreOS `testing` (`35.20220103.2.0`) and `next` (`35.20220103.1.0`) that causes a high percentage of affected AWS instances to boot without network connectivity. The issue affects instance types that use [Enhanced Networking with the Intel 82599 VF interface](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sriov-networking.html), including C3, C4, D2, I2, M4 (except m4.16xlarge), and R3. Within the next 24 hours, we plan to issue new `testing` and `next` releases that avoid the problem by downgrading the kernel. Until then, we've updated the AMI list on the [download page](https://getfedora.org/en/coreos/download) and in stream metadata to point to previous releases. For updates and more information, including progress toward an upstream fix, follow [this issue](https://github.com/coreos/fedora-coreos-tracker/issues/1066). To recover access to an instance that has lost connectivity after an upgrade, consult the [workaround steps](https://github.com/coreos/fedora-coreos-tracker/issues/1066#issuecomment-1011516609) in the tracker issue.