From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] hw/qxl: inject interrupts in any state
Date: Thu, 01 Nov 2012 10:19:43 +0100 [thread overview]
Message-ID: <50923EAF.90204@redhat.com> (raw)
In-Reply-To: <1351688023-18991-1-git-send-email-alevy@redhat.com>
On 10/31/12 13:53, Alon Levy wrote:
> I cannot find a reason we asserted that injecting interrupts happen only
> when the vm is running. This is right now the cause of spice crashing
> due to the new interface_client_set_capabilities being called when the
> vm is stopped, this happens if a user stops the vm or the vm reboots and
> a spice connection is dropped / created meanwhile.
>
> Sending as RFC since I'm not sure what the original reason for the
> assert is, git history is no help, it's in the first commit.
The problem is migration. qxl_send_events modifies guest state, and
there are phases during migration where modifying guest state is a
no-go. You'll loose events, either because the guest state update on
the source side came to late so it isn't send over or because the update
on the target side came to early so loadvm will overwrite it.
Disallowing events when the vm is stopped catches more cases than
needed, we could change it. But that wouldn't fix the bug at hand, it
would only make it harder to trigger.
IMO spice-server must not call interface_client_set_capabilities when
the vm is not running. After all we notify spice-server about the vm
stop/start events for a reason ...
cheers,
Gerd
next prev parent reply other threads:[~2012-11-01 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 12:53 [Qemu-devel] [RFC] hw/qxl: inject interrupts in any state Alon Levy
2012-11-01 9:19 ` Gerd Hoffmann [this message]
2012-11-01 9:45 ` Alon Levy
2012-11-01 9:55 ` Gerd Hoffmann
2012-11-01 10:22 ` Alon Levy
2012-11-01 10:33 ` Gerd Hoffmann
2012-11-01 11:48 ` Alon Levy
2012-11-01 12:32 ` Gerd Hoffmann
2012-11-01 12:44 ` Alon Levy
2012-11-01 12:47 ` Gerd Hoffmann
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=50923EAF.90204@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--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).