From: Thomas Huth <thuth@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Warnings during the virtio-net-failover test
Date: Mon, 20 Dec 2021 11:16:21 +0100 [thread overview]
Message-ID: <fcbae7f4-ff58-bb5d-fd5d-8b0145a6ee21@redhat.com> (raw)
Hi Laurent,
today I noticed that there are quite a bunch of warnings during the
virtio-net-failover test:
$ QTEST_QEMU_BINARY=./qemu-system-x86_64 tests/qtest/virtio-net-failover
/x86_64/failover-virtio-net/hotplug_1: qemu-system-x86_64: warning: Primary
device not found
Virtio-net failover will not work. Make sure primary device has parameter
failover_pair_id=standby0
OK
/x86_64/failover-virtio-net/hotplug_1_reverse: OK
/x86_64/failover-virtio-net/hotplug_2: qemu-system-x86_64: warning: Primary
device not found
Virtio-net failover will not work. Make sure primary device has parameter
failover_pair_id=standby0
OK
[...]
/x86_64/failover-virtio-net/migrate/out: qemu-system-x86_64: warning:
Primary device not found
Virtio-net failover will not work. Make sure primary device has parameter
failover_pair_id=standby0
OK
/x86_64/failover-virtio-net/migrate/in: OK
/x86_64/failover-virtio-net/migrate/abort/wait-unplug: qemu-system-x86_64:
warning: Primary device not found
Virtio-net failover will not work. Make sure primary device has parameter
failover_pair_id=standby0
OK
/x86_64/failover-virtio-net/migrate/abort/active: qemu-system-x86_64:
warning: Primary device not found
Virtio-net failover will not work. Make sure primary device has parameter
failover_pair_id=standby0
OK
/x86_64/failover-virtio-net/multi/out: OK
/x86_64/failover-virtio-net/multi/in: OK
I assume they are false positives? If so, could you please come up with a
patch to silence them, since they are quite confusing...?
Thanks,
Thomas
next reply other threads:[~2021-12-20 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 10:16 Thomas Huth [this message]
2021-12-20 13:32 ` Warnings during the virtio-net-failover test Laurent Vivier
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=fcbae7f4-ff58-bb5d-fd5d-8b0145a6ee21@redhat.com \
--to=thuth@redhat.com \
--cc=lvivier@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).