Right now when users migrate the VMs with Raw Copy Mode the VM will always have compatibility mode bus (SATA, E1000E, USB) even if the VM already has the virtio drivers installed before migration. MTV should add an option to use the virtio drivers with Raw Copy mode. 

The plan will have new option `useCompatibilityMode` that controls whether to use VirtIO devices when skipGuestConversion is true (Raw Copy mode).
This setting has no effect when skipGuestConversion is false (V2V Conversion always uses VirtIO).

• true (default): Use compatibility devices (SATA bus, E1000E NIC) to ensure bootability
• false: Use high-performance VirtIO devices (requires VirtIO drivers already installed in source VM)

So as this new plan setting depends on Raw Copy Mode I would have this option in the Raw Copy Mode settings. If customer would set it to true we could show another toggle to specify the  useCompatibilityMode which by default is true and customer could disable it.

Overview

Currently, when performing a migration using Raw Copy Mode (skipGuestConversion: true), MTV defaults to using compatibility hardware (SATA disk buses and E1000E network interfaces). This ensures the VM boots on the destination without requiring additional driver injections.

However, many modern workloads already have VirtIO drivers installed on the source. For these cases, forcing a compatibility bus limits the VM's performance on OpenShift Virtualization. This task involves documenting a new UI toggle, useCompatibilityMode, which allows users to choose between maximum compatibility or maximum performance when using Raw Copy Mode.

Scope of Documentation

• Procedure Updates: Update the "Creating a Migration Plan" section to include the new toggle within the Raw Copy Mode settings.

• Technical Guidance: Clearly document the prerequisites for disabling compatibility mode—specifically, that the source VM must have VirtIO drivers pre-installed to avoid boot failure.

• Logic Explanation: Clarify that this setting is only relevant when skipGuestConversion is enabled. If standard V2V conversion is used, VirtIO is applied by default.

• UI Screenshots: Update documentation images to show the nested toggle logic:

1. 1. Select Raw Copy Mode.

1. 1. Toggle useCompatibilityMode (Default: True).

Technical Parameters for Reference

Targeted Personas

1. The Virtualization Administrator

Role Description: This persona is responsible for the migration of production workloads from legacy hypervisors to OpenShift. Their primary concern is that the VM boots successfully the first time.

• Documentation Need: Needs to understand that "Compatibility Mode" is the safe default and should only be changed if they are certain of the guest OS configuration.

2. The Infrastructure Performance Architect

Role Description: This persona focuses on the post-migration performance of the application. They want the migrated VM to take full advantage of the KVM hypervisor's capabilities.

• Documentation Need: Needs to know how to enable VirtIO for RCM migrations to ensure the IOPS and network throughput meet performance requirements without the overhead of emulated hardware.

Job to Be Done (JTBD) Statement

When I am migrating a Virtual Machine that already contains VirtIO drivers using Raw Copy Mode, I want to disable the compatibility mode bus in the UI, so that the migrated VM can utilize high-performance VirtIO disk and network devices immediately upon booting in OpenShift Virtualization.