[PATCH v3 09/14] qemu: Refresh the actual size of virtio-mem on monitor reconnect
Michal Prívozník
mprivozn at redhat.com
Mon Apr 26 08:32:48 UTC 2021
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 at redhat.com>
Yes, this is expected. virtio-pmem does not support NUMA node:
https://listman.redhat.com/archives/libvir-list/2020-December/msg00211.html
Michal
More information about the libvir-list
mailing list