You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2021. It is now read-only.
Enable libpmem to support PMEM when running under Kubernetes.
see kata-containers/runtime#2262
According to QEMU's nvdimm documentation: When 'pmem' is 'on' and QEMU is
built with libpmem support, QEMU will take necessary operations to guarantee
the persistence of its own writes to the vNVDIMM backend.
fixeskata-containers#958
Signed-off-by: Julio Montes <julio.montes@intel.com>
Enable libpmem to support PMEM when running under Kubernetes.
see kata-containers/runtime#2262
According to QEMU's nvdimm documentation: When 'pmem' is 'on' and QEMU is
built with libpmem support, QEMU will take necessary operations to guarantee
the persistence of its own writes to the vNVDIMM backend.
fixeskata-containers#958
Signed-off-by: Julio Montes <julio.montes@intel.com>
devimc
pushed a commit
to devimc/kata-packaging
that referenced
this issue
Mar 2, 2020
Enable libpmem to support PMEM when running under Kubernetes.
see kata-containers/runtime#2262
According to QEMU's nvdimm documentation: When 'pmem' is 'on' and QEMU is
built with libpmem support, QEMU will take necessary operations to guarantee
the persistence of its own writes to the vNVDIMM backend.
fixeskata-containers#958
Signed-off-by: Julio Montes <julio.montes@intel.com>
enable libpmem to guarantee the persistence of qemu's writes to the vNVDIMM backend.
see kata-containers/runtime#2262
The text was updated successfully, but these errors were encountered: