From: "Zhao, Shirley" <shirley.zhao@intel.com> To: "Dr. David Alan Gilbert" <dgilbert@redhat.com> Cc: Thomas Huth <thuth@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "virtio-fs@redhat.com" <virtio-fs@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com> Subject: RE: [Qemu] how to use viriofs in qemu without NUMA Date: Fri, 8 Jul 2022 00:40:06 +0000 [thread overview] Message-ID: <BY5PR11MB4291BCA40054FB484003D4278D829@BY5PR11MB4291.namprd11.prod.outlook.com> (raw) In-Reply-To: <YsQGNk5hLv8b6DJS@work-vm> Yes, the qemu version is too old. My previous qemu version is 4.2, and I upgraded it into 6.0, and it worked now. Thanks a lot. - Shirley -----Original Message----- From: Dr. David Alan Gilbert <dgilbert@redhat.com> Sent: Tuesday, July 5, 2022 5:37 PM To: Zhao, Shirley <shirley.zhao@intel.com> Cc: Thomas Huth <thuth@redhat.com>; qemu-devel@nongnu.org; virtio-fs@redhat.com; Stefan Hajnoczi <stefanha@redhat.com> Subject: Re: [Qemu] how to use viriofs in qemu without NUMA * Zhao, Shirley (shirley.zhao@intel.com) wrote: > Thanks for the information. > Yes, I also found the memory backend options on s390x, and also copy the command to x86, but failed. > > The following is the command used to start qemu + virtiofs + ubuntu 20.04. > One is worked well using NUMA, another one is failed without NUMA. > Is there anything wrong? > > The worked one with NUMA options: > > qemu-system-x86_64 -M pc -cpu host --enable-kvm -smp 2 -m 4G -object > memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on -numa > node,memdev=mem -chardev socket,id=char0,path=/tmp/vfsd.sock -device > vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs -chardev > stdio,mux=on,id=mon -mon chardev=mon,mode=readline -device > virtio-serial-pci -device virtconsole,chardev=mon -vga none -display > none -drive if=virtio,file=ubuntu.img > > The failed one without NUMA options: > > qemu-system-x86_64 -M pc -cpu host --enable-kvm -smp 2 -m 4G -object > memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on -machine > q35,memory-backend=mem -chardev socket,id=char0,path=/tmp/vfsd.sock > -device vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs > -chardev stdio,mux=on,id=mon -mon chardev=mon,mode=readline -device > virtio-serial-pci -device virtconsole,chardev=mon -vga none -display > none -drive if=virtio,file=ubuntu.img What error did it give? 20.04 is quite old, what qemu version is it? I'd have to check when the memdev= went in. Dave > > Thanks. > - Shirley > > -----Original Message----- > From: Dr. David Alan Gilbert <dgilbert@redhat.com> > Sent: Tuesday, July 5, 2022 4:04 PM > To: Thomas Huth <thuth@redhat.com> > Cc: Zhao, Shirley <shirley.zhao@intel.com>; qemu-devel@nongnu.org; > virtio-fs@redhat.com; Stefan Hajnoczi <stefanha@redhat.com> > Subject: Re: [Qemu] how to use viriofs in qemu without NUMA > > * Thomas Huth (thuth@redhat.com) wrote: > > 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? > > Right, that's the way I do it on x86. > We wrote virtiofs before the memory-backend option existed, which is why the old docs talk about using the NUMA stuff. > > Dave > > > Thomas > > > -- > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
WARNING: multiple messages have this Message-ID (diff)
From: "Zhao, Shirley" <shirley.zhao@intel.com> To: "Dr. David Alan Gilbert" <dgilbert@redhat.com> Cc: Thomas Huth <thuth@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "virtio-fs@redhat.com" <virtio-fs@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com> Subject: Re: [Virtio-fs] [Qemu] how to use viriofs in qemu without NUMA Date: Fri, 8 Jul 2022 00:40:06 +0000 [thread overview] Message-ID: <BY5PR11MB4291BCA40054FB484003D4278D829@BY5PR11MB4291.namprd11.prod.outlook.com> (raw) In-Reply-To: <YsQGNk5hLv8b6DJS@work-vm> Yes, the qemu version is too old. My previous qemu version is 4.2, and I upgraded it into 6.0, and it worked now. Thanks a lot. - Shirley -----Original Message----- From: Dr. David Alan Gilbert <dgilbert@redhat.com> Sent: Tuesday, July 5, 2022 5:37 PM To: Zhao, Shirley <shirley.zhao@intel.com> Cc: Thomas Huth <thuth@redhat.com>; qemu-devel@nongnu.org; virtio-fs@redhat.com; Stefan Hajnoczi <stefanha@redhat.com> Subject: Re: [Qemu] how to use viriofs in qemu without NUMA * Zhao, Shirley (shirley.zhao@intel.com) wrote: > Thanks for the information. > Yes, I also found the memory backend options on s390x, and also copy the command to x86, but failed. > > The following is the command used to start qemu + virtiofs + ubuntu 20.04. > One is worked well using NUMA, another one is failed without NUMA. > Is there anything wrong? > > The worked one with NUMA options: > > qemu-system-x86_64 -M pc -cpu host --enable-kvm -smp 2 -m 4G -object > memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on -numa > node,memdev=mem -chardev socket,id=char0,path=/tmp/vfsd.sock -device > vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs -chardev > stdio,mux=on,id=mon -mon chardev=mon,mode=readline -device > virtio-serial-pci -device virtconsole,chardev=mon -vga none -display > none -drive if=virtio,file=ubuntu.img > > The failed one without NUMA options: > > qemu-system-x86_64 -M pc -cpu host --enable-kvm -smp 2 -m 4G -object > memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on -machine > q35,memory-backend=mem -chardev socket,id=char0,path=/tmp/vfsd.sock > -device vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs > -chardev stdio,mux=on,id=mon -mon chardev=mon,mode=readline -device > virtio-serial-pci -device virtconsole,chardev=mon -vga none -display > none -drive if=virtio,file=ubuntu.img What error did it give? 20.04 is quite old, what qemu version is it? I'd have to check when the memdev= went in. Dave > > Thanks. > - Shirley > > -----Original Message----- > From: Dr. David Alan Gilbert <dgilbert@redhat.com> > Sent: Tuesday, July 5, 2022 4:04 PM > To: Thomas Huth <thuth@redhat.com> > Cc: Zhao, Shirley <shirley.zhao@intel.com>; qemu-devel@nongnu.org; > virtio-fs@redhat.com; Stefan Hajnoczi <stefanha@redhat.com> > Subject: Re: [Qemu] how to use viriofs in qemu without NUMA > > * Thomas Huth (thuth@redhat.com) wrote: > > 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? > > Right, that's the way I do it on x86. > We wrote virtiofs before the memory-backend option existed, which is why the old docs talk about using the NUMA stuff. > > Dave > > > Thomas > > > -- > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2022-07-08 0:41 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 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 [this message] 2022-07-08 0:40 ` 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=BY5PR11MB4291BCA40054FB484003D4278D829@BY5PR11MB4291.namprd11.prod.outlook.com \ --to=shirley.zhao@intel.com \ --cc=dgilbert@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=stefanha@redhat.com \ --cc=thuth@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: linkBe 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.