From: "Liu, Jing2" <jing2.liu@linux.intel.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: yang.zhong@intel.com, stefanha@redhat.com
Subject: [Qemu-devel] [Consult] nfs-vsocks support
Date: Fri, 23 Mar 2018 17:54:53 +0800 [thread overview]
Message-ID: <22f7f184-c295-4e18-c186-3fd9fdcce213@linux.intel.com> (raw)
Hello,
I am currently trying to use nfs-vsocks on x86 for vitural machine
filesystem by some manuals on
https://www.spinics.net/lists/linux-nfs/msg64563.html
and https://lwn.net/Articles/647516/
It tells the quickstart steps with the following codes but I got some
problems as listed.
* Linux kernel: https://github.com/stefanha/linux.git vsock-nfs
* QEMU virtio-vsock device: https://github.com/stefanha/qemu.git vsock
* nfs-utils vsock: https://github.com/stefanha/nfs-utils.git vsock
1. I would like to ask what is the current status of these codes? If
there're some updates? :)
2. nfs-utils codes could not compile for me... I refered to the README
but failed for both ways. It seems no configure script and
autoheader/automake... So I don't know how to install this.
3. For the 5th step (Start nfsd), I'd like to know the rpc.nfsd --vsock
is enabled by which codes? Is it the CONFIG_VHOST_VSOCK kernel module in
host? Because I installed the kernel with vsock-nfs repo with the
specified config options but failed to do rpc.nfsd --vsock.
Could you give me some help and thanks in advance!
BRs,
Jing Liu
next reply other threads:[~2018-03-23 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 9:54 Liu, Jing2 [this message]
2018-03-23 16:02 ` [Qemu-devel] [Consult] nfs-vsocks support Stefan Hajnoczi
2018-03-26 10:12 ` Liu, Jing2
2018-03-28 11:25 ` Liu, Jing2
2018-04-04 9:45 ` Stefan Hajnoczi
2018-04-16 6:21 ` Liu, Jing2
-- strict thread matches above, loose matches on Subject: below --
2018-04-16 23:45 Roy, Arindam
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=22f7f184-c295-4e18-c186-3fd9fdcce213@linux.intel.com \
--to=jing2.liu@linux.intel.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=yang.zhong@intel.com \
/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).