Red Hat Bugzilla – Bug 1257644
Starting VM with snapshot with memory conflicts with later VM properties changes
Last modified: 2017-11-07 10:09:54 EST
Created attachment 1067759 [details]
Description of problem:
If you preview a snapshot (with memory) and then before you start the VM you make VM properties modification like removing/adding network card, engine backend won't take this changes immediately into account and it will start VM with VM settings from snapshot.
This brings surprises like having inside OS network interface with "old" hwaddr.
There should be two solutions:
- if previewing snapshot with memory, VM properties changes should be forbidden
- if previewing snapshot with memory, VM properties changes should drop VM
memory restoration and the user doing this should be informed with a dialog
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a VM with a network card
2. start VM, install some OS
3. make snapshot
4. power off the VM
5. preview snapshot, check "old" nic hwaddr, select include memory
(select snapshot -> right pane 'Network Interfaces/MAC')
6. remove nic
7. add nic with user defined hwaddr
9. start VM
10. check inside OS
11. check libvirt via dumpxml
old hwaddr, VM settings were restored from memory and user changes were not
accepted for (first) run
either changes should be forbidden or better there should be warning that modification of previewing snapshot with memory would cause memory restore to
to be dropped
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
I would say a Preview with memory should be restored as a running VM.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
(In reply to Michal Skrivanek from comment #2)
> I would say a Preview with memory should be restored as a running VM.
I suppose a "Paused" VM is even better
Too late for 4.0, but it was brought up several times in similar flows, and the behavior is really difficult to predict then