[libvirt-users] Limiting instructions for guest to help with migration to different host
Hello, I am migrating a suspended x86-64 guest (disk & state) across different x86-64 hosts with small differences in the available CPU instructions and when I try to resume the guest on the different host libvirt reports an error like this "CPU feature XXX not found" and fails. My question is, is there a way to limit the instructions that are used on the "origin" host when creating the guest to avoid this error? I am pretty sure there is a set of basic instructions that are available across all hosts which could be used for this purpose. Thank you! /R
Hello, Does anybody have an answer for the question below? Should I provide any additional information? Thanks! /R On Wed, Jan 3, 2018 at 5:54 PM, R <r@mille4.com> wrote:
Hello,
I am migrating a suspended x86-64 guest (disk & state) across different x86-64 hosts with small differences in the available CPU instructions and when I try to resume the guest on the different host libvirt reports an error like this "CPU feature XXX not found" and fails. My question is, is there a way to limit the instructions that are used on the "origin" host when creating the guest to avoid this error? I am pretty sure there is a set of basic instructions that are available across all hosts which could be used for this purpose.
Thank you!
/R
On 01/04/2018 02:54 AM, R wrote:
Hello,
I am migrating a suspended x86-64 guest (disk & state) across different x86-64 hosts with small differences in the available CPU instructions and when I try to resume the guest on the different host libvirt reports an error like this "CPU feature XXX not found" and fails. My question is, is there a way to limit the instructions that are used on the "origin" host when creating the guest to avoid this error? I am pretty sure there is a set of basic instructions that are available across all hosts which could be used for this purpose.
Thank you!
You want to take a look at specifying the guest CPU: https://libvirt.org/formatdomain.html#elementsCPU Michal
participants (2)
-
Michal Privoznik -
R