From: Launchpad Bug Tracker <1617385@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1617385] Re: No snapshot possible with virtio-gpu activated
Date: Sun, 06 Nov 2016 04:17:28 -0000 [thread overview]
Message-ID: <20161106041728.3974.11405.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20160826155556.27103.59439.malonedeb@gac.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1617385
Title:
No snapshot possible with virtio-gpu activated
Status in QEMU:
Expired
Bug description:
I'm using "Qemu" and "Virtual Machine Manager" on Debian-8-Stretch -
both newest versions out of the Debian-testing-repository (state
26.08.2016).
If I try to save a virtual machine, it fails and I'll get the
following error:
libvirtError: internal error: unable to execute QEMU command
'migrate': State blocked by non-migratable device '0000:00:02.0
/virtio-gpu'
This only happens, if I chose "Virtio" as graphics-driver (no matter
if I use "Spice" or "Vnc" as Server by the way). If I switch to any
other driver (Cirrus, Qxl, Vga, VMvga...) there is no problem to take
a snapshot and save the virtual machine.
Unfortunately "virtio-gpu" (together with "Spice-Server") is the only
driver that provides proper working/running my virtual machines on my
PC.
feuerkogel1
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1617385/+subscriptions
next prev parent reply other threads:[~2016-11-06 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 15:55 [Qemu-devel] [Bug 1617385] [NEW] No snapshot possible with virtio-gpu activated feuerkogel1
2016-09-05 14:56 ` [Qemu-devel] [Bug 1617385] " Dr. David Alan Gilbert
2016-09-06 14:12 ` feuerkogel1
2016-11-06 4:17 ` Launchpad Bug Tracker [this message]
2023-06-21 23:58 ` 林博仁(Buo-ren, Lin)
2023-06-22 7:19 ` Thomas Huth
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=20161106041728.3974.11405.malone@loganberry.canonical.com \
--to=1617385@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.