What is not a limitation of a virtual machine change host live migration operation in FusionCompute?

When performing a live migration of a virtual machine in FusionCompute, the process allows for the virtual machine to be moved from one physical host to another while it is still running. The key factor that makes the choice about mounting "shared" disks not a limitation is that during live migration, it is indeed possible to use shared storage that is accessible by both the source and destination hosts. This enables the virtual machine to maintain its disk access during the migration process without interruption, facilitating a smoother transition.

The other options pertain to restrictions that exist during live migrations. For instance, a virtual machine must be operating (status "running") in order to perform the migration without disruption, and if the destination host is in maintenance mode, it cannot accept new virtual machines for operation, including those being migrated. Additionally, limitations are placed on "raw device" type storage because it often requires direct access to the physical devices, which can complicate migrations since the data paths need to be re-established post-migration.

Thus, the ability to effectively work with "shared" disks during a live migration is a significant aspect that sets it apart from the other restrictions noted in the choices.