From: Jakub Kicinski <kuba@kernel.org>
To: "Michalik, Michal" <michal.michalik@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"vadim.fedorenko@linux.dev" <vadim.fedorenko@linux.dev>,
"Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>,
"jonathan.lemon@gmail.com" <jonathan.lemon@gmail.com>,
"pabeni@redhat.com" <pabeni@redhat.com>, poros <poros@redhat.com>,
"Olech, Milena" <milena.olech@intel.com>,
mschmidt <mschmidt@redhat.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>
Subject: Re: [PATCH RFC net-next v4 2/2] selftests/dpll: add DPLL system integration selftests
Date: Mon, 4 Dec 2023 19:02:18 -0800 [thread overview]
Message-ID: <20231204190218.13d4e8cc@kernel.org> (raw)
In-Reply-To: <CH3PR11MB841424C185225EC7EB9DBE4DE386A@CH3PR11MB8414.namprd11.prod.outlook.com>
On Mon, 4 Dec 2023 12:44:44 +0000 Michalik, Michal wrote:
> > Hm, FWIW I manged to get virtme-ng to work (I was pointing it at a
> > vmlinux not bzImage which it expects). But vmtest is still unhappy.
> >
> > $ vmtest -k build/vmlinux "echo Running!"
> > => vmlinux
> > ===> Booting
> > Failed to connect QGA
> >
> > Caused by:
> > Timed out waiting for QGA connection
> >
>
> I have seen this before I got the proper qemu version, actually I
> compiled it from scratch:
> $ qemu-system-x86_64 --version
> QEMU emulator version 8.1.3
>
> Which version of qemu are you using?
7.2.6
Building Qemu from source won't work for me if the CI is supposed to
depend on it. I asked Daniel on GH, let's see what he says.
> Btw. I agree that logs for vmtest are not very helpful, the
> .vmtest.log file is basically empty for me every time.
>
> >
> > Are you on Ubuntu? I'm on Fedora. Maybe it has some distro deps :(
> >
>
> I'm using Rocky, so kind of similar to Fedora.
> $ cat /etc/rocky-release
> Rocky Linux release 9.2 (Blue Onyx)
>
> Also, installed qemu-guest-agent and edk2-ovmf packages according to
> vmtest instructions. Have you installed those?
Yup, I have those.
> > Calling out to YNL, manipulating network namespaces, manipulating
> > netdevsim instances, etc - will be fairly common for a lot of networking
> > tests.
> >
> > There's already some code in tools/testing/selftests/bpf/test_offload.py
> > which is likely Python-incompetent cause I wrote it. But much like YNL
> > it'd be nice if it was available for new tests for reuse.
> >
>
> I will familiarize myself with that - thanks for pointing that out.
To be clear - I'm not claiming that test_offload.py is beautiful
code :) Just that the problem of accessing shared code exists more
broadly.
> > Can we somehow "add to python's library search path" or some such?
>
> Yeah, we might consider using PYTHONPATH in this "new common lib place":
> https://docs.python.org/3/using/cmdline.html#envvar-PYTHONPATH
👍️
next prev parent reply other threads:[~2023-12-05 3:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 10:52 [PATCH RFC net-next v4 0/2] selftests/dpll: DPLL subsystem integration tests Michal Michalik
2023-11-23 10:52 ` [PATCH RFC net-next v4 1/2] netdevsim: implement DPLL for subsystem selftests Michal Michalik
2023-11-23 12:24 ` Jiri Pirko
2023-11-30 16:55 ` Michalik, Michal
2023-12-01 7:49 ` Jiri Pirko
2023-11-23 14:41 ` Simon Horman
2023-11-30 17:22 ` Michalik, Michal
2023-11-23 10:52 ` [PATCH RFC net-next v4 2/2] selftests/dpll: add DPLL system integration selftests Michal Michalik
2023-11-29 17:39 ` Jakub Kicinski
2023-11-30 17:46 ` Michalik, Michal
2023-12-01 6:51 ` Jakub Kicinski
2023-12-01 18:33 ` Michalik, Michal
2023-12-01 19:52 ` Jakub Kicinski
2023-12-04 12:44 ` Michalik, Michal
2023-12-05 3:02 ` Jakub Kicinski [this message]
2023-12-01 20:03 ` Jakub Kicinski
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=20231204190218.13d4e8cc@kernel.org \
--to=kuba@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=bvanassche@acm.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jonathan.lemon@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=michal.michalik@intel.com \
--cc=milena.olech@intel.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=vadim.fedorenko@linux.dev \
/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).