All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Dewey <larry.j.dewey@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1816189] Re: Unable to create or revert snapshots
Date: Fri, 15 Feb 2019 21:04:38 -0000	[thread overview]
Message-ID: <155026467831.1164.4821807274678267776.malone@gac.canonical.com> (raw)
In-Reply-To: 155026463486.6528.17912471655076346086.malonedeb@soybean.canonical.com

Adding System Information

** Attachment added: "System-Details.txt"
   https://bugs.launchpad.net/qemu/+bug/1816189/+attachment/5238921/+files/System-Details.txt

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1816189

Title:
  Unable to create or revert snapshots

Status in QEMU:
  New

Bug description:
  With an update to Qemu (3.1.x) I am unable to revert snapshots using
  virt-manager or virsh. Virtual Machines existing before the update
  seem to function properly. It is only after creating a new machine
  that snapshots are misbehaving. I tested spinning up vms of
  tumbleweed, leap15, and ubuntu 18.04. Each of them had the following
  issues:

  - With the machine running, live reversions act like they apply, but no changes are actually made.
  - With the machine paused, reversion also does not apply.
  - With the machine turned off, reversion is not possible. Virsh is unable to find the snapshot, and virt-manager errors out with:

  Error running snapshot 'FreshInstall': internal error: qemu
  unexpectedly closed the monitor: 2019-01-15T19:19:46.020247Z qemu-
  system-x86_64: Device 'drive-virtio-disk0' does not have the requested
  snapshot 'FreshInstall'

  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
      callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
      callback(*args, **kwargs)
    File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn
      ret = fn(self, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/domain.py", line 1105, in revert_to_snapshot
      self._backend.revertToSnapshot(snap.get_backend())
    File "/usr/lib64/python3.6/site-packages/libvirt.py", line 2024, in revertToSnapshot
      if ret == -1: raise libvirtError ('virDomainRevertToSnapshot() failed', dom=self)

  libvirt.libvirtError: internal error: qemu unexpectedly closed the
  monitor: 2019-01-15T19:19:46.020247Z qemu-system-x86_64: Device
  'drive-virtio-disk0' does not have the requested snapshot
  'FreshInstall'

  After doing some digging, the error occurs because of the following commit:
  d98f26073bebddcd3da0ba1b86c3a34e840c0fb8

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1816189/+subscriptions

  reply	other threads:[~2019-02-15 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 21:03 [Qemu-devel] [Bug 1816189] [NEW] Unable to create or revert snapshots Larry Dewey
2019-02-15 21:04 ` Larry Dewey [this message]
2019-02-15 21:06 ` [Qemu-devel] [Bug 1816189] " Larry Dewey
2021-02-17  8:20 ` Thomas Huth
2021-04-19  4:17 ` Launchpad Bug Tracker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=155026467831.1164.4821807274678267776.malone@gac.canonical.com \
    --to=larry.j.dewey@gmail.com \
    --cc=1816189@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.