I can imagine that passt actually terminates after initialisation for some
reason. Could you please re-run it in foreground:
  /usr/local/bin/passt -6 -f

and start the guest from another terminal, and see what happens to the passt
process?

(In reply to Stefano Brivio from comment #1)
> I can imagine that passt actually terminates after initialisation for some
> reason. Could you please re-run it in foreground:
>   /usr/local/bin/passt -6 -f
> 
> and start the guest from another terminal, and see what happens to the passt
> process？

Still hit the same error  

[test@dell-per440-18 ~]$ /usr/local/bin/passt -6 -f
Couldn't get any nameserver address
Outbound interface: eno1
NDP/DHCPv6:
    assign: 2620:52:0:4972:c2ea:8fbd:2a2f:a168
    router: fe80::cee1:9402:8b35:be41
    our link-local: fe80::10fc:4758:1541:ef2f
DNS search list:
    lab.eng.pek2.redhat.com
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

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


another terminal:
[test@dell-per440-18 tmp]$qrap 5 qemu-kvm -m 16059 -cpu host -smp 6 -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=./rhel900-64-virtio.qcow2 -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0 -nographic -serial stdio -nodefaults -device virtio-net-pci,netdev=hostnet0,x-txburst=16384 -netdev socket,fd=5,id=hostnet0
Probe of /tmp/passt_1.socket failed
connect: Connection refused
Probe of /tmp/passt_2.socket failed
connect: Connection refused
Probe of /tmp/passt_3.socket failed

Patch at:

    https://lists.passt.top/hyperkitty/list/passt-dev@passt.top/thread/G35AZE232AHDLJV5SLUAB3H4QCEVFDFB/

The issue still existed with passt-0.git.2022_08_04.b516d15-0.el9.x86_64

[test@dell-per440-18 ~]$ /usr/bin/passt -6
Couldn't get any nameserver address
Outbound interface (IPv6): eno1
MAC:
    host: 2c:ea:7f:71:b6:ee
NDP/DHCPv6:
    assign: 2620:52:0:4972:c2ea:8fbd:2a2f:a168
    router: fe80::cee1:9402:8b35:be41
    our link-local: fe80::10fc:4758:1541:ef2f
DNS search list:
    lab.eng.pek2.redhat.com
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

[test@dell-per440-18 tmp]$ qrap 5 qemu-kvm -m 16059 -cpu host -smp 6 -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=./rhel900-64-virtio.qcow2 -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0 -nographic -serial stdio -nodefaults -device virtio-net-pci,netdev=hostnet0,x-txburst=16384 -netdev socket,fd=5,id=hostnet0                                                                                                                                     recv: Resource temporarily unavailable
Probe of /tmp/passt_1.socket failed
connect: No such file or directory
Probe of /tmp/passt_2.socket failed
.....

Setting back to ASSIGNED as this is another issue (I can't reproduce it, but that's another topic).

There were a number of issues with initial configuration of addresses that we solved in passt-0^20230222.g4ddbcb9-1.el9 (bz2172244) -- I'm fairly sure this was a combination of some of those. Moving to MODIFIED.

Lei,

could you check (setting ITM to 26) ?

Thanks,

(In reply to Laurent Vivier from comment #9)
> Lei,
> 
> could you check (setting ITM to 26) ?
> 
> Thanks,
Hi Laurent 

It's ok for me

Thanks
Lei

==>Reproduced this bug passt-0^20221110.g4129764-1.el9.x86_64

Test Version:
passt-0^20221110.g4129764-1.el9.x86_64
qemu-kvm-7.2.0-9.el9.x86_64
kernel-5.14.0-281.el9.x86_64
libvirt-9.0.0-6.el9.x86_64
edk2-ovmf-20221207gitfff6d81270b5-6.el9.noarch

Test Steps:
1. Create passt socket
$ passt -6
Couldn't get any nameserver address
Outbound interface (IPv6): switch
MAC:
    host: ec:2a:72:30:86:32
NDP/DHCPv6:
    assign: 2620:52:0:49d4:daa3:c9ff:27c7:4e06
    router: fe80::52c7:903:543b:88e1
    our link-local: fe80::c3e8:6ed9:7dbc:ba55
DNS search list:
    lab.eng.pek2.redhat.com
UNIX domain socket bound at /tmp/passt_1.socket

You can now start qemu (>= 7.2, with commit 13c6be96618c):
    kvm ... -device virtio-net-pci,netdev=s -netdev stream,id=s,server=off,addr.type=unix,addr.path=/tmp/passt_1.socket
or qrap, for earlier qemu versions:
    ./qrap 5 kvm ... -net socket,fd=5 -net nic,model=virtio

2. Boot guest
$ qrap 5 qemu-kvm -m 16059 -smp 6 -blockdev '{"node-name": "file_ovmf_code", "driver": "file", "filename": "/usr/share/OVMF/OVMF_CODE.secboot.fd", "auto-read-only": true, "discard": "unmap"}' -blockdev '{"node-name": "drive_ovmf_code", "driver": "raw", "read-only": true, "file": "file_ovmf_code"}' -blockdev '{"node-name": "file_ovmf_vars", "driver": "file", "filename": "/home/test/avocado-vt-vm1_rhel920-64-virtio-scsi_qcow2_filesystem_VARS.fd", "auto-read-only": true, "discard": "unmap"}' -blockdev '{"node-name": "drive_ovmf_vars", "driver": "raw", "read-only": false, "file": "file_ovmf_vars"}' -machine q35,memory-backend=mem-machine_mem,pflash0=drive_ovmf_code,pflash1=drive_ovmf_vars -device '{"id": "pcie-root-port-0", "driver": "pcie-root-port", "multifunction": true, "bus": "pcie.0", "addr": "0x1", "chassis": 1}' -device '{"id": "pcie-pci-bridge-0", "driver": "pcie-pci-bridge", "addr": "0x0", "bus": "pcie-root-port-0"}' -nodefaults -device '{"driver": "VGA", "bus": "pcie.0", "addr": "0x2"}' -m 62464 -object '{"size": 65498251264, "id": "mem-machine_mem", "qom-type": "memory-backend-ram"}' -smp 28,maxcpus=28,cores=14,threads=1,dies=1,sockets=2 -cpu 'Icelake-Server',ds=on,ss=on,dtes64=on,vmx=on,pdcm=on,hypervisor=on,tsc-adjust=on,avx512ifma=on,sha-ni=on,rdpid=on,fsrm=on,md-clear=on,stibp=on,arch-capabilities=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,tsx-ctrl=on,hle=off,rtm=off,mpx=off,intel-pt=off,kvm_pv_unhalt=on  -device '{"id": "pcie-root-port-2", "port": 2, "driver": "pcie-root-port", "addr": "0x1.0x2", "bus": "pcie.0", "chassis": 3}' -device '{"id": "virtio_scsi_pci0", "driver": "virtio-scsi-pci", "bus": "pcie-root-port-2", "addr": "0x0"}' -blockdev '{"node-name": "file_image1", "driver": "file", "auto-read-only": true, "discard": "unmap", "aio": "threads", "filename": "/home/test/2.qcow2", "cache": {"direct": true, "no-flush": false}}' -blockdev '{"node-name": "drive_image1", "driver": "qcow2", "read-only": false, "cache": {"direct": true, "no-flush": false}, "file": "file_image1"}' -device '{"driver": "scsi-hd", "id": "image1", "drive": "drive_image1", "write-cache": "on"}' -device '{"id": "pcie-root-port-3", "port": 3, "driver": "pcie-root-port", "addr": "0x1.0x3", "bus": "pcie.0", "chassis": 4}' -device '{"driver": "virtio-net-pci", "id": "net0", "netdev": "hostnet0", "x-txburst": 16384, "bus": "pcie-root-port-3", "addr": "0x0"}' -netdev socket,fd=5,id=hostnet0 -boot menu=off,order=cdn,once=c,strict=off -vnc :1 -boot menu=off,order=cdn,once=c,strict=off -monitor stdio
Connected to /tmp/passt_1.socket
qemu-kvm: 5: Could not open '5': No such file or directory

==> So reproduced this problem on passt-0^20221110.g4129764-1.el9.x86_64

==> Update to the latest version: passt-0^20230222.g4ddbcb9-1.el9.x86_64

Test Version:
passt-0^20230222.g4ddbcb9-1.el9.x86_64
qemu-kvm-7.2.0-9.el9.x86_64
kernel-5.14.0-281.el9.x86_64
libvirt-9.0.0-6.el9.x86_64
edk2-ovmf-20221207gitfff6d81270b5-6.el9.noarch

Test Steps:
1. Update the passt version to the latest version: passt-0^20230222.g4ddbcb9-1.el9.x86_64
# yum -y install passt-0^20230222.g4ddbcb9-1.el9.x86_64.rpm
# reboot (on the host)

2. After the host is power on, repeat the above test steps. Guest can boot up with passt "-6" option.

Based on the Comment 11 test result, move to "VERIFIED".

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (passt bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2292