question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VM snapshot lost after migration

See original GitHub issue

Description a vm snapshot (not disk snapshot) is broken/lost after live migration or power-off

To Reproduce

  • create a new virtual machine named test1 and start it

  • open the virtual machine in sunstone, navigate to “Snapshots” and create one

  • wait for the snapshot to finish

  • live migrate vm “test1” to an other hypervisor

  • the snapshot is still listed in sunstone, but with virsh snapshot-list <domain> we see that the snapshot is gone

  • there’s no way to remove that broken snapshot in sunstone anymore

  • create a new virtual machine named test2 and start it

  • open the virtual machine in sunstone, navigate to “Snapshots” and create one

  • wait for the snapshot to finish

  • power off vm “test2”

  • snapshot in sunstone is gone

  • power on vm “test2”

  • snapshot in sunstone is still gone, but with virsh snapshot-list <domain> you can still see the snapshot

Expected behavior In both cases I would expect the snapshot to be still there and correctly shown in Sunstone

Details

  • Affected Component: Sunstone, Storage, libvirtd
  • Hypervisor: KVM
  • Storage: shared fs - TM_MAD=“qcow2”
  • Version: 6.0.2

Additional context NaN

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
christian7007commented, Sep 9, 2021

Actually, that feature was never supported. Libvirt will fail if trying to migrate a VM with snapshots, so they needs to be removed, which is a different issue than the poweroff.

We’ve already scheduled this issue for 6.2.1 and we’ll look on what’s the best way of recreating the snapshots after the live migration.

0reactions
rsmonterocommented, Jan 14, 2022

Merged

Read more comments on GitHub >

github_iconTop Results From Across the Web

Solved: Unable to revert to snapshots after migration
After migrating a vm from 3.5 to 4.0, I'm getting this error when attempting to revert to a snapshot: "Detected an invalid snapshot...
Read more >
Recently migrated VM;s shutdown during/after snapshot
Just in the past 3-4 days - we have been getting notices of servers powering off after they receive a vm snap from...
Read more >
Failover cluster: Move or Migrate Virtual Machine breaks ...
If we move or migrate a VM to another node than where it was imported, all snapshots on the VM show a configuration...
Read more >
VMware Snapshot Best Practices Explained - NAKIVO
When you delete all snapshots, VMware snapshot files are consolidated and data is committed to the base disk (the new algorithm is used)....
Read more >
Dell Virtual Storage Manager for VMware Version 6.0 Release ...
You can manually remove the snapshot from the VMware Manage Snapshots dialog box. Dell also suggests renaming the VM/folder/datastore/cluster that you are using ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found