On PPC platform it is required that a NVDIMM has an UUID. If none
is provided then libvirt generates one during parsing (see
v6.2.0-rc1~96 and friends). However, the example provided in our
documentation is not valid XML.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Tested-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Tested-by: Han Han <hhan@redhat.com>
</target>
</memory>
<memory model='nvdimm'>
- <uuid>
+ <uuid>9066901e-c90a-46ad-8b55-c18868cf92ae</uuid>
<source>
<path>/tmp/nvdimm</path>
</source>
</target>
</memory>
<memory model='nvdimm' access='shared'>
- <uuid>
+ <uuid>e39080c8-7f99-4b12-9c43-d80014e977b8</uuid>
<source>
<path>/dev/dax0.0</path>
<alignsize unit='KiB'>2048</alignsize>
``uuid``
For pSeries guests, an uuid can be set to identify the nvdimm module. If
- absent, libvirt will generate an uuid. automatically. This attribute is
+ absent, libvirt will generate an uuid automatically. This attribute is
allowed only for ``model='nvdimm'`` for pSeries guests. :since:`Since 6.2.0`
``source``