Jack Yu

@harvester/dev please remember to review this PR when you're available, thanks!

I'll close this issue, use https://github.com/harvester/harvester/issues/6975 to track further progress and keep issue board clear. If you have any updates, please leave the comment in https://github.com/harvester/harvester/issues/6975, thanks!

@dfaltum What rancher version do you use?

@dfaltum I'm curious what you did to fix it. Did you do anything?

FYI, the mechanism and workaround of live migration has been added into official document (https://docs.harvesterhci.io/v1.4/vm/live-migration/#how-migration-works).

I think eventually we need to provide two features for users: 1. cluster-wide common CPU model to support ALL CPUs 2. ability of assigning a specific cpu model on GUI,...

I haven't deeply checked it because I don't have a heterogeneous cluster to test. There is a config called `unsafeMigrationOverride` in KubeVirt, maybe we can use it. reference: - https://github.com/kubevirt/kubevirt/blob/1350c6477ff728bb4799e5fa33acdb8ca2493403/pkg/virt-launcher/virtwrap/live-migration-source.go#L1038-L1041...

Backend TODO: - [ ] Provide a CPU migration capabilities API for frontend. - [x] Filter the nodes based on the selected CPU model when calling findMigratableNodesByVMI. -> by https://github.com/harvester/harvester/issues/8797...

BTW, about `CPUNodeDiscovery` feature gate, it had beed removed in this https://github.com/kubevirt/kubevirt/pull/7728. So, the default behavior is enabled CPUNodeDiscovery feature gate (https://github.com/kubevirt/user-guide/pull/762). These feature gates are enabled by default (https://github.com/kubevirt/kubevirt/blob/352416fe7c2b944486d14e226e746f0051b2d0f7/pkg/virt-config/featuregate/inactive.go#L101-L119)....

@ibrokethecloud @ihcsim Here are the new updates after the latest commit: - Goals: I've changed the goals. - CPU Feature Input: The CPU feature drop-down has been removed and replaced...