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

hey dominik,

Am 2017-08-24 18:14, schrieb Dominik Psenner:
> This might be related to the configuration of the virtual machine. A
> machine configured to have cpu X might not start up when it is changed
> to cpu Y. We also observed that a windows host does not boot on a
> ubuntu host with the default kvm configuration.
>
https://github.com/dpsenner/libvirt-administration-tools#windows-guest-crashes-with-a-blue-screen-after-migrating-the-virtual-machine-to-another-host.
> 
> Good luck!
that doesn´t solved it :-(

marko
> 
> 2017-08-24 17:57 GMT+02:00 Marko Weber <weber@zbfmail.de>:
> 
>> hello,
>> a vm in format qcow2 on host A  (Intel Xeon CPU E5-1650 v4)
>> do not start on host B ( Intel Core i7-2600 CPU @ 3.40GHz )
>> 
>> i get on host B by starting the vm  "trap errors" Opcode.
>> 
>> anyone here has an idea how to solve this?
>> 
>> kind regards
>> marko
>> 
>> --
>> zbfmail - Mittendrin statt nur Datei!
>> 
>> OpenDKIM, SPF, DSPAM, Greylisting, POSTSCREEN, AMAVIS, Mailgateways
>> Mailfiltering, SMTP Service, Spam Abwehr, MX-Backup, Mailserver
>> Backup
>> Redundante Mailgateways, HA Mailserver, Secure Mailserver
>> 
>> _______________________________________________
>> libvirt-users mailing list
>> libvirt-users@redhat.com
>> https://www.redhat.com/mailman/listinfo/libvirt-users [1]
> 
> --
> 
> Dominik Psenner
> 
> 
> Links:
> ------
> [1] https://www.redhat.com/mailman/listinfo/libvirt-users

<div dir='auto'>Hi everyone,<div
dir="auto"><br></div><div
dir="auto">Windows are very sensitive with hardware, mainly with
CPU.</div><div dir="auto"><br></div><div
dir="auto">If you change, you break.</div><div
dir="auto">It is not the virtualization system
fault.</div><div dir="auto"><br></div><div
dir="auto">For libvirt/kvm you can use the CPU kvm64 that hidde
some specifics features from the operational system.</div><div
dir="auto">In this case it is easier to migrate VM from host to
host.</div><div dir="auto"><br></div><div
dir="auto">You can use the migration feature from libvirt to test
if the 2 hosts are compatible for migrating your windows VM.</div><div
dir="auto"><br></div><div dir="auto">If
libvirt tells you that it is not compatible and you copy the VM - it would break
your VM.</div><div
dir="auto"><br></div><div
dir="auto"><br></div></div>

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