Re: [PATCH v3 09/14] qemu: Refresh the actual size of virtio-mem on monitor reconnect

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/26/21 9:52 AM, Jing Qi wrote:

> S2: From the docs, "virtio-pmem" works also.
> # cat pmem.xml
>   <memory model='virtio-pmem' access='shared'>
>       <source>
>         <path>/tmp/nvdimm</path>
>       </source>
>       <target>
>         <size unit='KiB'>131072</size>
>         <label>
>         <size unit='KiB'>128</size>
>         </label>
>          </target>
>     </memory>
> # virsh attach-device pc_test pmem.xml
> Device attached successfully
> #virsh dumpxml pc_test
> <memory unit='KiB'>1441792</memory>
>   <currentMemory unit='KiB'>1282048</currentMemory>
> 
> Question:
> But seems it don't support <node> element , and if add <node> element,
> below errors are prompted -
> error: Failed to attach device from pmem
> error: unsupported configuration: virtio-pmem does not support NUMA nodes
> Since the <node> element is supported by nvdimm & virtio-mem, can you
> help to confirm if it's as expected? @Michal Privoznik
> <mailto:mprivozn@xxxxxxxxxx> 

Yes, this is expected. virtio-pmem does not support NUMA node:

https://listman.redhat.com/archives/libvir-list/2020-December/msg00211.html

Michal




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux