public inbox for passt-user@passt.top
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: James Sinton <jksinton@gmail.com>
Cc: David Gibson <david@gibson.dropbear.id.au>, passt-user@passt.top
Subject: Re: Port Forwarding between host-guest via passt using QEMU-libvirt
Date: Thu, 6 Nov 2025 13:37:36 +0100	[thread overview]
Message-ID: <20251106133736.40e4117e@elisabeth> (raw)
In-Reply-To: <aQv090b1tTQmTTRO@zatzit>

On Thu, 6 Nov 2025 12:08:07 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> That information might supply some clues, but it's pretty likely we'll
> need debugging or packet capture output from passt to work this out.
> Unfortunately, that's a bit trickier than it should be because libvirt
> doesn't (yet) have the ability to pass the necessary options to passt.

By the way, this feature request for libvirt is currently tracked at
(public RHEL ticket, but applies to libvirt in general):

  https://issues.redhat.com/browse/RHEL-52281

Meanwhile, one thing you can do is to add a wrapper at
/usr/local/bin/passt (don't forget to chmod 755 it) with these lines:

---
#!/bin/sh

/usr/bin/passt --debug --log-file /tmp/passt.log --pcap /tmp/passt.pcap $@
---

that's the way I currently debug stuff with libvirt, at least.

Note that passt can take guest-side packet captures (you would find it
at /tmp/passt.pcap, which you can open with Wireshark / tshark later),
which is usually convenient for cases like these.

-- 
Stefano


  reply	other threads:[~2025-11-06 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPkQuZP0nhKBt28rbuM=-sj3R=mvsUeyu5yj_5ojckpTc=nzPg@mail.gmail.com>
2025-11-06  1:08 ` David Gibson
2025-11-06 12:37   ` Stefano Brivio [this message]
2025-11-10  6:16     ` David Gibson
     [not found]   ` <CAPkQuZPmO0moyRnmB2y4_DrpCnuMMJ0nTVPd-zBEaoNJ7dUvVw@mail.gmail.com>
2025-11-10  6:13     ` David Gibson

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=20251106133736.40e4117e@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=jksinton@gmail.com \
    --cc=passt-user@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.
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).