From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/qxl: warn on sync io usage
Date: Thu, 11 Oct 2012 08:53:53 +0200 [thread overview]
Message-ID: <50766D01.2030509@redhat.com> (raw)
In-Reply-To: <1349885925-24216-1-git-send-email-alevy@redhat.com>
Hi,
> +static void sync_io_warning(PCIQXLDevice *qxl, uint32_t io_port)
> +{
> + fprintf(stderr, "qxl-%d: WARNING: sync io used, see (RHBZ 747011)",
> + qxl->id);
> + fprintf(stderr, "qxl-%d: WARNING: virt-viewer/remote-viewer can hang\n",
> + qxl->id);
> + if (qxl->revision < 3) {
> + fprintf(stderr, "qxl-%d: WARNING: revision >= 3 should be used\n",
> + qxl->id);
> + }
> +}
The message should also include hints how to fix that.
For the revision this probably means to update the machine type from
pc-0.12 (which sets rev=2 via compat properties) to something newer.
Telling the user what to do about it is tricky though as there seems to
be no simple GUI way to do that, at least not in virt-manager. In the
other hand if the user manages to find the message in
/var/log/libvirt/qemu/${guest}.log he might be experienced enough to
just "virsh edit ${guest}".
For the sync I/O it's easy, just say something like "Update qxl drivers
in the guest."
BTW: You can print multi-line messages this way ...
fprintf(stderr,
"long line one\n"
"long line two\n",
args, here);
... which I find more readable in the source code.
Do we wanna have a "suggest to update guest drivers for device $foo" qmp
message for management? Or has ovirt/rhev better ways (guest agent?) to
deal with that?
cheers,
Gerd
next prev parent reply other threads:[~2012-10-11 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 16:18 [Qemu-devel] [PATCH] hw/qxl: warn on sync io usage Alon Levy
2012-10-11 6:53 ` Gerd Hoffmann [this message]
2012-10-11 7:40 ` Alon Levy
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=50766D01.2030509@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).