From: Gerd Hoffmann <1635339@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1635339] Re: qxl_pre_save assertion failure on vm "save"
Date: Mon, 10 Apr 2017 12:42:09 -0000 [thread overview]
Message-ID: <1491828129.30990.23.camel@redhat.com> (raw)
In-Reply-To: 20170410115617.12199.51724.malone@gac.canonical.com
On Mo, 2017-04-10 at 11:56 +0000, Frediano Ziglio wrote:
> Is this problem limited to commands or also to data attached to the commands?
Everything which contains QXLReleaseInfo and is released via release
ring.
> To me looks like a limitation Qemu should remove on the long run.
That is an option, but it is tricky backward-compatibility wise.
What was the reason to move the commands to bar1?
cheers,
Gerd
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1635339
Title:
qxl_pre_save assertion failure on vm "save"
Status in QEMU:
Confirmed
Bug description:
When I try and save my Windows 10 VM, I see an assertion failure, and
the machine is shut down.
I see the following in the log:
main_channel_handle_parsed: agent start
qemu-system-x86_64: /build/qemu-Zwynhi/qemu-2.5+dfsg/hw/display/qxl.c:2101: qxl_pre_save: Assertion `d->last_release_offset < d->vga.vram_size' failed.
2016-10-20 11:52:42.713+0000: shutting down
Please let me know what other information would be relevant!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1635339/+subscriptions
next prev parent reply other threads:[~2017-04-10 12:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 16:05 [Qemu-devel] [Bug 1635339] [NEW] qxl_pre_save assertion failure on vm "save" lethargy
2016-10-20 18:42 ` [Qemu-devel] [Bug 1635339] " Dr. David Alan Gilbert
2016-10-20 23:22 ` DocMAX
2016-10-20 23:51 ` DocMAX
2017-04-06 17:02 ` rubenvb
2017-04-07 8:56 ` Dr. David Alan Gilbert
2017-04-07 13:22 ` Gerd Hoffmann
2017-04-07 13:36 ` elmarco
2017-04-07 14:15 ` elmarco
2017-04-07 14:44 ` Peter Maydell
2017-04-07 15:48 ` Gerd Hoffmann
2017-04-07 16:23 ` Dr. David Alan Gilbert
2017-04-07 22:17 ` Gerd Hoffmann
2017-04-07 22:50 ` elmarco
2017-04-10 11:56 ` Frediano Ziglio
2017-04-10 12:42 ` Gerd Hoffmann [this message]
2017-04-11 11:52 ` Marc Pignat
2017-04-11 14:31 ` Gerd Hoffmann
2017-04-19 14:17 ` Frediano Ziglio
2017-05-02 16:04 ` Frediano Ziglio
2017-05-19 11:44 ` Frediano Ziglio
2020-11-18 10:39 ` 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=1491828129.30990.23.camel@redhat.com \
--to=1635339@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).