From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>,
qemu-block@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH 0/3] tests/qtest: add some tests for virtio-net failover
Date: Wed, 10 Nov 2021 14:56:13 +0100 [thread overview]
Message-ID: <20211110135616.1188725-1-lvivier@redhat.com> (raw)
This series adds a qtest entry to test virtio-net failover feature.
We check following error cases:
- check missing id on device with failover_pair_id triggers an error
- check a primary device plugged on a bus that doesn't support hotplug
triggers an error
We check the status of the machine before and after hotplugging cards and
feature negotiation:
- check we don't see the primary device at boot if failover is on
- check we see the primary device at boot if failover is off
- check we don't see the primary device if failover is on
but failover_pair_id is not the one with on (I think this should be changed)
- check the primary device is plugged after the feature negotiation
- check the result if the primary device is plugged before standby device and
vice-versa
- check the if the primary device is coldplugged and the standy device
hotplugged and vice-versa
- check the migration triggers the unplug
-> this one needs to be improved as we can't actualy unplug the
card as the qtest framework doesn't allow to really do
the OS level unplug. So we receive the UNPLUG_PRIMARY
event but nothing more.
There are two preliminary patches in the series:
- PATCH 1 makes available functions that helped me to debug
the qmp command result. I think it's a good point to have them
available widely
- PATCH 2 introduces a function to enable PCI bridge.
Failover needs to be plugged on a pcie-root-port and while
the root port is not configured the cards behind it are not
available
Laurent Vivier (3):
qdict: make available dump_qobject(), dump_qdict(), dump_qlist()
qtest/libqos: add a function to initialize secondary PCI buses
tests/qtest: add some tests for virtio-net failover
block/qapi.c | 82 +----
include/hw/pci/pci_bridge.h | 8 +
include/qapi/qmp/qdict.h | 2 +
include/qapi/qmp/qlist.h | 1 +
include/qapi/qmp/qobject.h | 1 +
qobject/qdict.c | 25 ++
qobject/qlist.c | 17 +
qobject/qobject.c | 35 ++
tests/qtest/libqos/pci.c | 118 +++++++
tests/qtest/libqos/pci.h | 1 +
tests/qtest/meson.build | 3 +
tests/qtest/virtio-net-failover.c | 567 ++++++++++++++++++++++++++++++
12 files changed, 779 insertions(+), 81 deletions(-)
create mode 100644 tests/qtest/virtio-net-failover.c
--
2.31.1
next reply other threads:[~2021-11-10 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 13:56 Laurent Vivier [this message]
2021-11-10 13:56 ` [PATCH 1/3] qdict: make available dump_qobject(), dump_qdict(), dump_qlist() Laurent Vivier
2021-11-10 16:17 ` Markus Armbruster
2021-11-10 17:11 ` Laurent Vivier
2021-11-10 13:56 ` [PATCH 2/3] qtest/libqos: add a function to initialize secondary PCI buses Laurent Vivier
2021-11-10 13:56 ` [PATCH 3/3] tests/qtest: add some tests for virtio-net failover 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=20211110135616.1188725-1-lvivier@redhat.com \
--to=lvivier@redhat.com \
--cc=armbru@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).