[libvirt-users] vm in qcow2 runs on host A but not on host B
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
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-crash... . Good luck! 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
-- Dominik Psenner
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-crash....
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
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
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
participants (3)
-
Dominik Psenner -
Marcos -
Marko Weber