Displaying 4 results from an estimated 4 matches for "devdax".
Did you mean:
dev_dax
2020 Jul 09
0
NVDIMM in devdax mode and SELinux (was: Two questions about NVDIMM devices)
Milan Zamazal <mzamazal@redhat.com> writes:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
>> On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote:
>>> The second problem is that a VM fails to start with a backing NVDIMM in
>>> devdax mode due to SELinux preventing access to the /dev/dax* device (it
>>> doesn't happen with any other NVDIMM modes). Who should be responsible
>>> for handling the SELinux label appropriately in that case? libvirt, the
>>> system administrator, anybody else? Using &l...
2020 Jul 02
2
Re: Two questions about NVDIMM devices
...n libvirt is just not to waste 256 MB
unnecessarily. Still, all the size shuffling scares me and I can only
hope that I compute my target sizes for the domain XML correctly to make
everything working well...
>> The second problem is that a VM fails to start with a backing NVDIMM in
>> devdax mode due to SELinux preventing access to the /dev/dax* device (it
>> doesn't happen with any other NVDIMM modes). Who should be responsible
>> for handling the SELinux label appropriately in that case? libvirt, the
>> system administrator, anybody else? Using <seclabel&g...
2020 Jul 02
3
Two questions about NVDIMM devices
...ultimate goal
of getting the VM started and having the NVDIMM aligned properly to make
(non-NVDIMM) memory hot plug working. Is the size alignment performed
by libvirt, especially rounding up, completely correct for NVDIMMs?
The second problem is that a VM fails to start with a backing NVDIMM in
devdax mode due to SELinux preventing access to the /dev/dax* device (it
doesn't happen with any other NVDIMM modes). Who should be responsible
for handling the SELinux label appropriately in that case? libvirt, the
system administrator, anybody else? Using <seclabel> in NVDIMM's source
d...
2020 Jul 02
0
Re: Two questions about NVDIMM devices
...to pick the right rounded sizes.
If we're enforcing this 1 MB rounding though, we really should be
documenting it clearly, so that apps can pick the right backing file
size. I think we dropped the ball on docs.
> The second problem is that a VM fails to start with a backing NVDIMM in
> devdax mode due to SELinux preventing access to the /dev/dax* device (it
> doesn't happen with any other NVDIMM modes). Who should be responsible
> for handling the SELinux label appropriately in that case? libvirt, the
> system administrator, anybody else? Using <seclabel> in NVDIMM...