From: Johannes Berg <johannes@sipsolutions.net>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: ido@wizery.com, linux-um@lists.infradead.org,
qemu-devel <qemu-devel@nongnu.org>,
Linux Virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [Qemu-devel] custom virt-io support (in user-mode-linux)
Date: Fri, 24 May 2019 11:54:26 +0200 [thread overview]
Message-ID: <aa9490ff07c587b3bca01ec5eb33d59ea440b645.camel@sipsolutions.net> (raw)
In-Reply-To: <CAJSP0QWSZXT3OJAc=abagD40xZ7DWWrcP_+AwVBuqQyQNgaOEg@mail.gmail.com> (sfid-20190523_164131_760945_C45BA0A2)
On Thu, 2019-05-23 at 15:41 +0100, Stefan Hajnoczi wrote:
> > Also, not sure I understand how the client is started?
>
> The vhost-user device backend can be launched before QEMU. QEMU is
> started with the UNIX domain socket path so it can connect.
Hmm. I guess I'm confusing the terminology then - I thought qemu was the
server and the backend was the client that connects to it. If it's the
other way around, yeah, that makes things easier and certainly makes
sense (you could have a daemon that implements something).
> QEMU itself doesn't fork+exec the vhost-user device backend. It's
> expected that the user or the management stack has already launched
> the vhost-user device backend.
Right.
> > Do you know if there's a sample client/server somewhere?
>
> See contrib/libvhost-user in the QEMU source tree as well as the
> vhost-user-blk and vhost-user-scsi examples in the contrib/ directory.
Awesome, thanks!
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2019-05-24 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 13:02 custom virt-io support (in user-mode-linux) Johannes Berg
2019-05-22 13:28 ` Anton Ivanov
2019-05-22 13:46 ` Johannes Berg
2019-05-22 14:00 ` Anton Ivanov
2019-05-23 11:59 ` [Qemu-devel] " Stefan Hajnoczi
2019-05-23 14:25 ` Johannes Berg
2019-05-23 14:41 ` Stefan Hajnoczi
2019-05-24 9:54 ` Johannes Berg [this message]
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=aa9490ff07c587b3bca01ec5eb33d59ea440b645.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ido@wizery.com \
--cc=linux-um@lists.infradead.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=virtualization@lists.linux-foundation.org \
/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 NNTP newsgroup(s).