qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Prívozník" <mprivozn@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Kostiantyn Kostiuk" <kkostiuk@redhat.com>
Cc: Jan Tomko <jtomko@redhat.com>,
	Yan Vugenfirer <yvugenfi@redhat.com>,
	QEMU <qemu-devel@nongnu.org>
Subject: Re: QGA installation issue on Windows
Date: Thu, 14 Aug 2025 10:06:13 +0200	[thread overview]
Message-ID: <23a9cb5f-dda8-403d-964d-b27338d6c94a@redhat.com> (raw)
In-Reply-To: <aJCTJf67oTZseYUr@redhat.com>

On 8/4/25 13:01, Daniel P. Berrangé wrote:
> On Mon, Aug 04, 2025 at 01:54:09PM +0300, Kostiantyn Kostiuk wrote:
>> Hi Michal,
>>
>> I want to discuss your patch
>> https://gitlab.com/qemu-project/qemu/-/commit/c6f5dd7ac8ef62dcdec4cdeda1467c658161afff
>>
>> Unfortunately, we found bad behaviour on Windows. On Windows, we run QGA
>> with `-d --retry-path` options by default, so we expect that QGA will start
>> even without the vioserial driver and will wait for communication
>> forever.
>>
>> This worked previously, but after your patch QGA service fails if the
>> vioserial communication channel is missing. This behavior is totally
>> unacceptable for us.
>>
>> You send this patch to fix a Linux problem, but it causes a Windows problem.
>> So, what we need on Windows, if --retry-path specified, we should ignore
>> any channel error and retry the connection. If -d and --retry-path are
>> specified, it should become a daemon first to make Windows Service Manager
>> happy.

The original problem I tried to fix was (and I am bit hazy on all the
details): when somebody built their own kernel but forgot to enable
virtio-serial then qemu-ga would fail to initialize but with a
completely irrelevant error message.

> 
> This looks pretty simple to fix - in the initialize_agent() method, if
> channel_init() fails, then simply ignore the failure if 'retry_path'
> is set, because the later code in run_agent() will already correctly
> retry the connection.

Yeah, do you want me to post such patch?

Michal



  reply	other threads:[~2025-08-14  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 10:54 QGA installation issue on Windows Kostiantyn Kostiuk
2025-08-04 11:01 ` Daniel P. Berrangé
2025-08-14  8:06   ` Michal Prívozník [this message]
2025-08-14  8:57     ` Kostiantyn Kostiuk

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=23a9cb5f-dda8-403d-964d-b27338d6c94a@redhat.com \
    --to=mprivozn@redhat.com \
    --cc=berrange@redhat.com \
    --cc=jtomko@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yvugenfi@redhat.com \
    /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).