On Thu, Dec 10, 2020 at 04:48:57PM +, Liam Merwick wrote:
> On 16/09/2020 10:51, Stefan Hajnoczi wrote:
> > v2:
> > * s/the the/the/ in documentation [Philippe]
> > * Assign nvdimm->unarmed earlier [Philippe]
> >
> > There is currently no way to back an NVDIMM with a read-only file so it c
On 16/09/2020 10:51, Stefan Hajnoczi wrote:
v2:
* s/the the/the/ in documentation [Philippe]
* Assign nvdimm->unarmed earlier [Philippe]
There is currently no way to back an NVDIMM with a read-only file so it can be
safely shared between untrusted guests.
Introduce an -object memory-backend
On Wed, Sep 16, 2020 at 10:51:47AM +0100, Stefan Hajnoczi wrote:
> v2:
> * s/the the/the/ in documentation [Philippe]
> * Assign nvdimm->unarmed earlier [Philippe]
Ping
> There is currently no way to back an NVDIMM with a read-only file so it can be
> safely shared between untrusted guests.
>
v2:
* s/the the/the/ in documentation [Philippe]
* Assign nvdimm->unarmed earlier [Philippe]
There is currently no way to back an NVDIMM with a read-only file so it can be
safely shared between untrusted guests.
Introduce an -object memory-backend-file,readonly=on|off option.
Julio Montes sent