"Liu, Jingqi" writes:
> Hi Milan,
>
> On 4/30/2021 8:18 PM, Milan Zamazal wrote:
>> Hi,
>>
>> I work on NVDIMM support in oVirt/RHV, I think other virtualization
>> management software built on top of QEMU may have similar concerns.
>>
>> When a virtual NVDIMM device size is specified, it's not n
Hi Milan,
On 4/30/2021 8:18 PM, Milan Zamazal wrote:
Hi,
I work on NVDIMM support in oVirt/RHV, I think other virtualization
management software built on top of QEMU may have similar concerns.
When a virtual NVDIMM device size is specified, it's not necessarily the
eventual NVDIMM device size
Igor Mammedov writes:
> On Fri, 30 Apr 2021 14:18:30 +0200
> Milan Zamazal wrote:
>
>> Hi,
>>
>> I work on NVDIMM support in oVirt/RHV, I think other virtualization
>> management software built on top of QEMU may have similar concerns.
>>
>> When a virtual NVDIMM device size is specified, it's
On Fri, 30 Apr 2021 14:18:30 +0200
Milan Zamazal wrote:
> Hi,
>
> I work on NVDIMM support in oVirt/RHV, I think other virtualization
> management software built on top of QEMU may have similar concerns.
>
> When a virtual NVDIMM device size is specified, it's not necessarily the
> eventual NVD
Hi,
I work on NVDIMM support in oVirt/RHV, I think other virtualization
management software built on top of QEMU may have similar concerns.
When a virtual NVDIMM device size is specified, it's not necessarily the
eventual NVDIMM device size visible to the guest OS. As seen in
https://github.com/