Description of problem: When a snapshot (with memory) is created, the engine runs MemoryStorageHandler to decide where to place the memory volume. But when the VMs disks are moved, the memory volume is not relocated (MemoryStorageHandler is not evaluated again). This can lead to the VM living in a completely different set of SDs than the memory volume(s), causing a few problems: 1) SD with memory volume can be detached: if I detach the memory volume SD and try to preview the VM, I get this when starting the VM, which doesn't make any sense: 2017-11-06 16:44:02,510+10 WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [8ffaa3e8-45ea-4c7f-84cb-aea0e928195a] Validation of action 'RunVm' failed for user admin@internal. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS 2) If I detach the SD of the memory volume (A) and also the SD of the VM (B), then attach back B to try to import the VM, I get this: "Cannot import VM. Storage Domain doesn't exist" due to the missing SD of the memory volume. Not sure if the memory volumes should follow the disks via MemoryStorageHandler, but this doesn't seem right. Version-Release number of selected component (if applicable): ovirt-engine-4.1.6 How reproducible: 100% Steps to Reproduce: 1. Create VM with disk on SD A 2. Snapshot it (include memory) 3. Move VM disk to SD B 4. Memory volume still on SD A 5. Detach SD A and B 6. Attach SD B and try to import the VM AND 1. Create VM with disk on SD A 2. Snapshot it (include memory) 3. Move VM disk to SD B 4. Memory volume still on SD A 5. Detach SD A 6. Try to preview the VM and start it
The memory volumes should be treated as any other disk and not be moved automatically but the option to move them manually should indeed be added as requested in RFE 1150245 *** This bug has been marked as a duplicate of bug 1150245 ***
(In reply to Tal Nisan from comment #2) > The memory volumes should be treated as any other disk and not be moved > automatically but the option to move them manually should indeed be added as > requested in RFE 1150245 > > *** This bug has been marked as a duplicate of bug 1150245 *** Reopening to track issue downstream
We now display memory disk as vDisk and allow to move memory volume like vDisks. Please use these flows.