From: Thomas Huth <1452742@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1452742] Re: the option for vdagent communication needed for qxl scren resizing is not documented
Date: Thu, 17 Jun 2021 06:55:27 -0000 [thread overview]
Message-ID: <162391292721.11028.12986477358513036020.malone@soybean.canonical.com> (raw)
In-Reply-To: 20150507141247.29425.7775.malonedeb@soybean.canonical.com
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/424
** Changed in: qemu
Status: Incomplete => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #424
https://gitlab.com/qemu-project/qemu/-/issues/424
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1452742
Title:
the option for vdagent communication needed for qxl scren resizing is
not documented
Status in QEMU:
Expired
Bug description:
Hello,
I tried running a guest with vdagent which is supposed to resize the
guest screen to match client window size.
However, a special serial port needs to be created for the vdagent to
communicate with the client.
This patch adds a short note to the vga qxl option.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1452742/+subscriptions
prev parent reply other threads:[~2021-06-17 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 14:12 [Qemu-devel] [Bug 1452742] [NEW] the option for vdagent communication needed for qxl scren resizing is not documented Michal Suchanek
2016-10-18 8:42 ` [Qemu-devel] [Bug 1452742] " T. Huth
2021-04-22 4:53 ` Thomas Huth
2021-06-17 6:55 ` Thomas Huth [this message]
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=162391292721.11028.12986477358513036020.malone@soybean.canonical.com \
--to=1452742@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.