Description of problem: By some miracle a few Windows VMs got this error during start: ~~~ VM brq-w2k8r2 is down with error. Exit message: XML error: both maximum memory size and memory slot count must be specified. ~~~ engine=# select vm_name,mem_size_mb,max_memory_size_mb from vms where vm_name like 'brq-w2k%'; vm_name | mem_size_mb | max_memory_size_mb -------------+-------------+-------------------- brq-w2k12r2 | 4096 | 16384 brq-w2k8r2 | 2048 | 4194304 (2 rows) 'brq-w2k12r2' memory issue was corrected by a collegue, current problematic - brq-w2k8r2 - got my attention and thus here is bug report. No idea what did happen. Our env got odd after huge overload. We recently updated cluster compat level to 4.2 and the VMs probably were not power-cycled. The collegue says, those VMs are in paused state. Version-Release number of selected component (if applicable): ovirt-engine-4.2.2.1-0.1.el7.noarch How reproducible: 1 in 1 Steps to Reproduce: 1. 2. 3. Actual results: vms got paused, got odd max memory size and cannot be started Expected results: working vms Additional info: - attachment upload in progress...
I think it used to work, in case of 4TB the hot plug is supposed to be disabled
*** Bug 1565627 has been marked as a duplicate of this bug. ***
<memory>2097152</memory> <currentMemory>2097152</currentMemory> <maxMemory slots="16">0</maxMemory>
can you reproduce with debug logs enabled - just the VM run attempt?
Deferring due to capacity and a lack of customer tickets so far
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Re-targeting, because these bugs either do not have blocker+, or do not have a patch posted
right, I propose to close it. WDYS?
Lukas, still reproducible?
I've tested cluster upgrade in 4.1.11 -> 4.2.8 -> 4.3.2 with paused VM and it always ran again without any problem. So this BZ can be closed and reopen, when the problem appears again.