From: Li Feng <fengli@smartx.com>
To: passt-user@passt.top
Subject: Re: qemu couldn't connect the unix domain socket
Date: Fri, 29 Oct 2021 11:33:06 +0800 [thread overview]
Message-ID: <CAHckoCzVc9f3pQcOo-pCGH3v8xQ1D2MdYD90CgfXCuAxTkYXzQ@mail.gmail.com> (raw)
In-Reply-To: <20211028093037.11cd79c3@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 3176 bytes --]
Hi Stefano,
The previous test has included the fix.
This is my repo HEAD:
* 2c7431f - (HEAD -> master, origin/master, origin/HEAD) README:
Feature list, links to lists, bugs, chat (6 days ago) <Stefano Brivio>
* a77c5ef - README, perf_report: Markdown and CSS fixes (7 days ago)
<Stefano Brivio>
* 94c7c1d - slirp4netns.sh: Fix up usage, exit 0 on --help (7 days
ago) <Stefano Brivio>
* 1fc6416 - seccomp: Add newfstatat to list of allowed syscalls (7
days ago) <Stefano Brivio>
* d36e429 - netlink: Fix length of address attribute (7 days ago)
<Stefano Brivio>
My OS is Fedora 35, x64 version.
I will try to dig it when I have some time.
Thanks,
Feng Li
On Thu, Oct 28, 2021 at 3:30 PM Stefano Brivio <sbrivio(a)redhat.com> wrote:
>
> Hi Feng Li,
>
> On Thu, 28 Oct 2021 12:25:29 +0800
> Li Feng <fengli(a)smartx.com> wrote:
>
> > Add cc.
>
> Sorry, I missed your email. It looks like on Mailman3, if I'm the owner
> of a list, I'm not automatically a member receiving posts from the list
> itself -- added myself as member, too.
>
> > On Tue, Oct 26, 2021 at 1:28 PM Li Feng <fengli(a)smartx.com> wrote:
> > >
> > > Hi,
> > > I just tested the master code, the passt just exited without any error.
> > >
> > > ```
> > > $ ./passt
> > > Outbound interface: ens192
> > > ARP:
> > > address: 00:50:56:be:9d:1f
> > > DHCP:
> > > assign: 192.168.64.217
> > > mask: 255.255.240.0
> > > router: 192.168.64.1
> > > search:
> > > .
> > > UNIX domain socket bound at /tmp/passt_1.socket
> > >
> > > You can now start qrap:
> > > ./qrap 5 kvm ... -net socket,fd=5 -net nic,model=virtio
> > > or directly qemu, patched with:
> > > qemu/0001-net-Allow-also-UNIX-domain-sockets-to-be-used-as-net.patch
> > > as follows:
> > > kvm ... -net socket,connect=/tmp/passt_1.socket -net nic,model=virtio
> > > 21-10-26 13:23:43 root(a)192.168.64.217:~/passt(master✗)
>
> passt will fork into background as soon as it gets a connection. Can
> you retry running it as:
>
> ./passt -f -d
>
> so we can see if something strange is going on (-f stands for
> --foreground, -d for --debug)? Because:
>
> > > ```
> > > Another terminal:
> > > ```
> > > $ bash x.sh
> > > recv: Connection reset by peer
> > > Probe of /tmp/passt_1.socket failed
> > > connect: No such file or directory
> > > Probe of /tmp/passt_2.socket failed
> > > connect: No such file or directory
> > > Probe of /tmp/passt_3.socket failed
> > > ...
> > > ```
>
> ...well, this shouldn't happen. It's probing /tmp/passt_1.socket and
> failing to get an answer.
>
> This just happened to another user, in that case seccomp was
> terminating passt because on his system daemon() called a different set
> of syscalls compared to my system:
>
> https://passt.top/passt/commit/?id=1fc6416cf9446cbf75818fd61772610e74709065
>
> and I expect some more issues like these at the beginning, I didn't
> test it on different distributions yet.
>
> By the way, I'm working on adding tests for a few distributions right
> now, so that we can catch those early.
>
> --
> Stefano
>
next prev parent reply other threads:[~2021-10-29 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 5:28 qemu couldn't connect the unix domain socket Li Feng
2021-10-28 4:25 ` Li Feng
2021-10-28 7:30 ` Stefano Brivio
2021-10-29 3:33 ` Li Feng [this message]
2021-10-29 5:27 ` Li Feng
2021-10-29 7:44 ` Stefano Brivio
2021-10-29 8:54 ` Li Feng
2021-10-29 9:34 ` Stefano Brivio
2021-10-29 11:02 ` Li Feng
2021-10-29 11:52 ` Stefano Brivio
2021-10-29 12:20 ` Li Feng
2022-02-03 20:47 ` Stefano Brivio
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=CAHckoCzVc9f3pQcOo-pCGH3v8xQ1D2MdYD90CgfXCuAxTkYXzQ@mail.gmail.com \
--to=fengli@smartx.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).