:_mod-docs-content-type: CONCEPT
[id="adoption-limitations_{context}"]

= Adoption limitations

[role="_abstract"]
Before you proceed with the adoption, check which features are Technology Previews or unsupported.

Technology Preview::
+
The following features are Technology Previews and have not been tested within the context of the {rhos_long} adoption:
+
* {key_manager_first_ref} adoption with Proteccio hardware security module (HSM) integration
+
The following {compute_service_first_ref} features are Technology Previews:
+
* NUMA-aware vswitches
* PCI passthrough by flavor
* SR-IOV trusted virtual functions
* vGPU
* Emulated virtual Trusted Platform Module (vTPM)
* UEFI
* AMD SEV
* Direct download from Rados Block Device (RBD)
* File-backed memory
* Defining a custom inventory of resources in a YAML file, `provider.yaml`

Unsupported features::
+
The adoption process does not support the following features:
+
* DNS-as-a-service (designate)
* {loadbalancer_first_ref}
* Adopting Border Gateway Protocol (BGP) environments to the {rhos_acro} data plane
* Adopting a Federal Information Processing Standards (FIPS) environment

//* When you adopt a {OpenStackShort} {rhos_prev_ver} FIPS environment to {rhos_acro} {rhos_curr_ver}, your adopted cluster remains a FIPS cluster. There is no option to change the FIPS status during adoption. If your cluster is FIPS-enabled, you must deploy a FIPS {rhocp_long} cluster to adopt your {OpenStackShort} {rhos_prev_ver} FIPS control plane. For more information about enabling FIPS in {OpenShiftShort}, see link:{defaultOCPURL}/installing/installation-overview#installing-fips[Support for FIPS cryptography] in the {OpenShiftShort} _Installing_ guide.
