From: Thomas Huth <thuth@redhat.com>
To: "Zhao, Shirley" <shirley.zhao@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: virtio-fs@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu] how to use viriofs in qemu without NUMA
Date: Tue, 5 Jul 2022 09:48:32 +0200 [thread overview]
Message-ID: <3b6c8e16-3712-3402-3ab2-17bf53ec64a8@redhat.com> (raw)
In-Reply-To: <BY5PR11MB42911D5BF55D9FAF501F64F68D819@BY5PR11MB4291.namprd11.prod.outlook.com>
On 05/07/2022 03.02, Zhao, Shirley wrote:
> Hi, all,
>
> I want to use virtiofs to share folder between host and guest.
>
> From the guide, it must set the NUMA node.
> https://virtio-fs.gitlab.io/howto-qemu.html
>
> But my guest doesn’t support NUMA.
>
> Is there any guide to use qemu + virtiofs without NUMA?
>
> Or does qemu have any plan to support it?
Hi!
At least on s390x, you can also specify the memory backend via the -machine
option instead of using the -numa option, e.g.:
qemu-system-s390x -machine memory-backend=mem \
-object memory-backend-file,id=mem,...
Not sure whether that works on other architectures, too, though. Stefan,
David, do you know?
Thomas
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Huth <thuth@redhat.com>
To: "Zhao, Shirley" <shirley.zhao@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: virtio-fs@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Virtio-fs] [Qemu] how to use viriofs in qemu without NUMA
Date: Tue, 5 Jul 2022 09:48:32 +0200 [thread overview]
Message-ID: <3b6c8e16-3712-3402-3ab2-17bf53ec64a8@redhat.com> (raw)
In-Reply-To: <BY5PR11MB42911D5BF55D9FAF501F64F68D819@BY5PR11MB4291.namprd11.prod.outlook.com>
On 05/07/2022 03.02, Zhao, Shirley wrote:
> Hi, all,
>
> I want to use virtiofs to share folder between host and guest.
>
> From the guide, it must set the NUMA node.
> https://virtio-fs.gitlab.io/howto-qemu.html
>
> But my guest doesn’t support NUMA.
>
> Is there any guide to use qemu + virtiofs without NUMA?
>
> Or does qemu have any plan to support it?
Hi!
At least on s390x, you can also specify the memory backend via the -machine
option instead of using the -numa option, e.g.:
qemu-system-s390x -machine memory-backend=mem \
-object memory-backend-file,id=mem,...
Not sure whether that works on other architectures, too, though. Stefan,
David, do you know?
Thomas
next prev parent reply other threads:[~2022-07-05 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 1:02 [Qemu] how to use viriofs in qemu without NUMA Zhao, Shirley
2022-07-05 7:48 ` Thomas Huth [this message]
2022-07-05 7:48 ` [Virtio-fs] " Thomas Huth
2022-07-05 8:03 ` Dr. David Alan Gilbert
2022-07-05 8:03 ` [Virtio-fs] " Dr. David Alan Gilbert
2022-07-05 9:01 ` Zhao, Shirley
2022-07-05 9:01 ` [Virtio-fs] " Zhao, Shirley
2022-07-05 9:36 ` Dr. David Alan Gilbert
2022-07-05 9:36 ` [Virtio-fs] " Dr. David Alan Gilbert
2022-07-08 0:40 ` Zhao, Shirley
2022-07-08 0:40 ` [Virtio-fs] " Zhao, Shirley
2022-07-12 7:06 ` Zhao, Shirley
2022-07-12 7:06 ` [Virtio-fs] " Zhao, Shirley
2022-07-12 12:33 ` Vivek Goyal
2022-07-13 5:43 ` Zhao, Shirley
2022-07-13 5:43 ` Zhao, Shirley
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=3b6c8e16-3712-3402-3ab2-17bf53ec64a8@redhat.com \
--to=thuth@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shirley.zhao@intel.com \
--cc=stefanha@redhat.com \
--cc=virtio-fs@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.