On Thu, 23 Feb 2023 10:15:15 -0800 Andrea Bolognani
<abologna(a)redhat.com> wrote:
Note the change from passt.avx2 to passt. Looking
at the process
listing, plain passt was used in both cases, so I assume that the
passt.avx2 mention is journald trying to fill in the blanks and
getting it wrong?
Yes, it's your system logger filling in the blanks, but it didn't
really get it wrong, as the process name is actually "passt.avx2" if
the AVX2-enabled build starts. Look at this, cough cough, beauty in
arch.c:
https://passt.top/passt/tree/arch.c#n21
"passt.avx2" wasn't intended in any case.
Oh, I see now that I actually have passt.avx2 running, despite the
output of ps hiding this fact:
$ ps aux | grep bin/passt
qemu 173991 [...] /usr/bin/passt [...]
$ sudo ls -l /proc/173991/exe
[...] /proc/173991/exe -> /usr/bin/passt.avx2
So it looks like everything is indeed working as intended :)
--
Andrea Bolognani / Red Hat / Virtualization