You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when moving VMs from hypervisors with incompatible CPU types, we should strip the CPU type field from the KVM XML domain metadata so we can just start VMs easily without having to virsh edit <domname> to fix the CPU information.
The text was updated successfully, but these errors were encountered:
+1 to this, could evenreplace it with the correct CPU type for the target hypervisor (for performance perhaps? Not sure how big the difference is there between generic and host CPUs)
when moving VMs from hypervisors with incompatible CPU types, we should strip the CPU type field from the KVM XML domain metadata so we can just start VMs easily without having to
virsh edit <domname>
to fix the CPU information.The text was updated successfully, but these errors were encountered: