Bug 1311899
Summary: | Minimum guaranteed memory is higher than VM memory when hotplug fails | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Martin Sivák <msivak> |
Component: | BLL.Virt | Assignee: | jniederm |
Status: | CLOSED CURRENTRELEASE | QA Contact: | meital avital <mavital> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0.0 | CC: | bugs, jniederm, mavital, mgoldboi, michal.skrivanek, sbonazzo, tjelinek |
Target Milestone: | ovirt-3.6.5 | Flags: | rule-engine:
ovirt-3.6.z+
mgoldboi: planning_ack+ tjelinek: devel_ack+ mavital: testing_ack+ |
Target Release: | 3.6.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Consequence:
If vm was not running nor up and a memory was changed without "apply later" flag then engine could show different memory size of VM than it actually had.
Fix:
If vm is not running, the memory is changed immediately.
If vm is up and "apply later" flag is not selected, hotplug attempt is send to VDSM and memory is altered accordingly.
If VM is in any other state and "apply later" flag is not selected, the memory change request is ignored (warning is logged, other UpdateVmCommand changes are applied, correct next-run confituration created).
Result:
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-21 14:38:07 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Sivák
2016-02-25 09:56:48 UTC
I can't reproduce it following steps to reproduce from comment 0. Steps to reproduce that works for me: 4.0 master, commit 46c9875 (using real vdsm (master snapshots)) (Supposing that ConfigValues.HotPlugMemoryMultiplicationSizeMb = 256) 1. Create VM * 512 MB of memory (and guaranteed memory) * (to make it bootable) add network not nic1 * (to make it bootable) set firts boot device to "Network (PXE)" 2. Run that VM. 3. Edit the VM to increase memory to 768 MB (do NOT check "Apply later" in confirmation dialog). 4. Edit the VM to decrease memory to 256 MB. 5. Power off VM. 6. Open Edit VM dialog 7. Confirm Edit VM dialog using OK button. Actual results: Minimal guaranteed memory is highlighted as being incorrect. also, hotSetMemlog() uses auditLogDirector.log(logable, AuditLogType.FAILED_HOT_SET_NUMBER_OF_CPUS) which seems to by a copy-paste mistake (In reply to jniederm from comment #1) > Actual results: > Minimal guaranteed memory is highlighted as being incorrect. setting aside that you didn't do the original steps - isn't that the point, that it should not be incorrect? It turned out that even steps to reproduce in comment 1 are not reliable. The key is try to decrease the memory when VM is in state "Starting". This allows to achieve state when actual memory is less than guaranteed memory. (In reply to jniederm from comment #4) "Starting" ~ "PoweringUp" also comment #2 please;-) Regarging comment 2: yes, it's a bug. I've added a fix to the patch. Verified on version: 3.6.5.3-0.1.el6 Verified steps: 1. Run VM. 2. While the VM is starting (powering up status) open the Edit dialog 3. Increase its memory 4. Save the VM 5. Edit a VM again 6. Edit VM's name (for example), but do not touch the memory 7. Saving the VM |