public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Subject: Re: More mbuto pain
Date: Tue, 05 Jul 2022 19:56:14 +0200	[thread overview]
Message-ID: <20220705195614.7e4b314b@elisabeth> (raw)
In-Reply-To: <YrqSKzP600gzFjB4@yekko>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

Hello again,

On Tue, 28 Jun 2022 15:31:23 +1000
David Gibson <david(a)gibson.dropbear.id.au> wrote:

> Now that the mbuto profile change is around, I tried getting the passt
> tests working.  I fixed a couple of minor problems, before hitting
> another mbuto issue.
> 
> On my host, mbuto isn't managing to find and include the virtio_net
> module.  I think this is because on current Fedora the modules in
> /lib/modules are compressed.  So it needs to include:
>     /lib/modules/5.18.6-200.fc36.x86_64/kernel/drivers/net/virtio_net.ko.xz
> but I think it's only looking for a plain '.ko' file.
> 
> I had a look at the mbuto code to see if I could fix it, but I'm
> afraid mbuto is a long way past the complexity level at which I find
> shell remotely comprehensible.

Sorry for the delay, I finally tried this out on a Fedora Cloud Base
image, 36-1.5.

There, mbuto actually finds virtio_net (because module paths are
obtained via 'modprobe'), but it won't parse the dependencies, so the
module would fail to load -- I just shared the patch to fix that part.

If it still fails for you, could you add a "set -x", "set +x" pair
around kmod_add() and share the result? Thanks,

-- 
Stefano


      parent reply	other threads:[~2022-07-05 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  5:31 More mbuto pain David Gibson
2022-06-28  7:17 ` Stefano Brivio
2022-06-28 19:06   ` Sevinj Aghayeva
2022-07-05 17:56 ` Stefano Brivio [this message]

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=20220705195614.7e4b314b@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=passt-dev@passt.top \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).