libvirt users - Aug 2017 - Re: vm in qcow2 runs on host A but not on host B

Hi Macros,

Am 2017-08-25 11:54, schrieb Marcos:
> Hi everyone,
> 
> Windows are very sensitive with hardware, mainly with CPU.
> 
> If you change, you break.
> It is not the virtualization system fault.
> 
> For libvirt/kvm you can use the CPU kvm64 that hidde some specifics
> features from the operational system.
> In this case it is easier to migrate VM from host to host.
> 
> You can use the migration feature from libvirt to test if the 2 hosts
> are compatible for migrating your windows VM.
> 
> If libvirt tells you that it is not compatible and you copy the VM -
> it would break your VM.
btw, its a linux vm i copied from host A to host B by rsync.
Its´s not windows

is the vm "bookamrking" the cpu features and all? if so, how can i
reset
this?


thanks

marko

<div dir='auto'>Well, linux is easier then windows.<div
dir="auto"><br></div><div
dir="auto">The host A is 64 or 32 bits ?</div><div
dir="auto">The host B is 64 or 32 bits ?</div><div
dir="auto">The VM is 64 or 32 ?</div><div
dir="auto"><br></div><div dir="auto">64
bits VM does not runs on 32 bits host</div><div
dir="auto"><br></div><div
dir="auto"><br></div></div>

yes!,

host A  x86_64
host B  x86_64
vm x86_64

i try now this: on 'host B' where vm runs,  compile
"generic_x86_64"
kernel reboot and recompile complete system with no CPU_FLAGS
and will see if 'vm' runs on 'host A'

marko


Am 2017-08-25 14:26, schrieb Marcos:
> Well, linux is easier then windows.
> 
> The host A is 64 or 32 bits ?
> The host B is 64 or 32 bits ?
> The VM is 64 or 32 ?
> 
> 64 bits VM does not runs on 32 bits host