[ovirt-users] Going crazy with emory hotplug on 3.6
Markus Stockhausen
stockhausen at collogia.de
Sun Feb 21 07:19:10 EST 2016
Hi there,
we upgraded Ovirt to 3.6, added the first Centos 7 host and created a new cluster
with compatibility level 3.6 around it. Until now we are running with Fedora nodes.
The first Linux VMs are already running in the new cluster. With the first Windows
VM migrated over we once again face the old Windows activation problem. The
system request us to reactivate the Windows license.
To make a long story short: I manually compiled OVirt/Centos qemu 2.3 and enabled
the old Fedora machine type pc-1.0. Afterwards I had to lower compatibility level
of the cluster to 3.5 because Ovirt tried to start the old machine type with memory
hotplug support -> FAIL. Finally everything is up and running.
Conclusion: OVirt always tries to start VMs with memory hotplug in a current 3.6
cluster. The machine type (e.g. rhel6.6.0) ist not checked and qemu will fail during
startup with the message: qemu-kvm: "-memory 'slots|maxmem'" is not supported"
Older post on mailing list: http://lists.ovirt.org/pipermail/users/2016-January/037034.html
Question: What is the desired way to disable the hotplug qemu parametrization
for single VMs in 3.6 cluster? It MUST be possible otherwise it would not make
sense to choos older machine types.
Markus
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160221/f04a3433/attachment.txt>
More information about the Users
mailing list