public inbox for passt-user@passt.top
 help / color / mirror / Atom feed
From: Li Feng <fengli@smartx.com>
To: passt-user@passt.top
Subject: qemu couldn't connect the unix domain socket
Date: Tue, 26 Oct 2021 13:28:27 +0800	[thread overview]
Message-ID: <CAHckoCxM2SE8ZVa4uH8QkTQ9K+rHzNDcXqssRarn9NiGpKUJSA@mail.gmail.com> (raw)

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

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✗)
```
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
...
```

```
$ cat x.sh
./qrap 5 /root/qemu-master/build/qemu-system-x86_64 -uuid
1869b108-42b3-42a7-852e-70261d73f6a9 -name
guest=1869b108-42b3-42a7-852e-70261d73f6a9 -cpu host -enable-kvm -smp
4 -device pci-bridge,chassis_nr=1,id=pci.0 -device
pci-bridge,chassis_nr=1,id=pci.1 -device
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x10 -fsdev
local,security_model=mapped,id=fsdev-fs0,path=/root -device
virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=fs0 -device
intel-iommu,device-iotlb=on,intremap=on -M
q35,accel=kvm,kernel-irqchip=split -serial mon:stdio -nographic -m
size=2048M,maxmem=32G,slots=128 -device virtio-balloon -drive
file=/root/fedora34.qcow2,format=qcow2,cache=none,aio=native,if=none,id=drive-virtio-disk1,file.locking=off
-device virtio-blk-pci,scsi=off,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=1
-vnc 0.0.0.0:101 -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-222-29ec19c9-d330-4949-b/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -qmp
tcp:0.0.0.0:2235,server,nowait -device
virtio-serial-pci,id=virtio-serial0,max_ports=16 -net socket,fd=5 -net
nic,model=virtio
```

Thanks,
Feng Li

             reply	other threads:[~2021-10-26  5:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  5:28 Li Feng [this message]
2021-10-28  4:25 ` qemu couldn't connect the unix domain socket Li Feng
2021-10-28  7:30   ` Stefano Brivio
2021-10-29  3:33     ` Li Feng
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=CAHckoCxM2SE8ZVa4uH8QkTQ9K+rHzNDcXqssRarn9NiGpKUJSA@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).