All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Kostiantyn Kostiuk <kkostiuk@redhat.com>
Cc: Michal Privoznik <mprivozn@redhat.com>,
	Jan Tomko <jtomko@redhat.com>,
	Yan Vugenfirer <yvugenfi@redhat.com>,
	QEMU <qemu-devel@nongnu.org>
Subject: Re: QGA installation issue on Windows
Date: Mon, 4 Aug 2025 12:01:57 +0100	[thread overview]
Message-ID: <aJCTJf67oTZseYUr@redhat.com> (raw)
In-Reply-To: <CAPMcbCpSQS5yWUCcGum6nWq=+HTaxFmJjm57_cgmJp+fMtC1JQ@mail.gmail.com>

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.

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.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2025-08-04 11:18 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é [this message]
2025-08-14  8:06   ` Michal Prívozník
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=aJCTJf67oTZseYUr@redhat.com \
    --to=berrange@redhat.com \
    --cc=jtomko@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=mprivozn@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 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.