On 9/14/20 1:40 PM, Andrea Bolognani wrote:
On Thu, 2020-09-10 at 20:53 +0200, Michal Privoznik wrote:
On 9/10/20 4:56 PM, Daniel P. Berrangé wrote:
On Thu, Sep 10, 2020 at 04:54:08PM +0200, Milan Zamazal wrote:
Daniel P. Berrangé writes:
If we're enforcing this 1 MB rounding though, we r
On Thu, 2020-09-10 at 20:53 +0200, Michal Privoznik wrote:
> On 9/10/20 4:56 PM, Daniel P. Berrangé wrote:
> > On Thu, Sep 10, 2020 at 04:54:08PM +0200, Milan Zamazal wrote:
> > > Daniel P. Berrangé writes:
> > > > > > If we're enforcing this 1 MB rounding though, we really should be
> > > > > > d
On 9/10/20 4:56 PM, Daniel P. Berrangé wrote:
On Thu, Sep 10, 2020 at 04:54:08PM +0200, Milan Zamazal wrote:
Daniel P. Berrangé writes:
On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote:
Daniel P. Berrangé writes:
On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote
On Thu, Sep 10, 2020 at 04:54:08PM +0200, Milan Zamazal wrote:
> Daniel P. Berrangé writes:
>
> > On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote:
> >> Daniel P. Berrangé writes:
> >>
> >
> >> > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote:
> >> >> Hi,
> >> >>
>
Daniel P. Berrangé writes:
> On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote:
>> Daniel P. Berrangé writes:
>>
>
>> > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote:
>> >> Hi,
>> >>
>> >
>> >> I've met two situations with NVDIMM support in libvirt where I'm not
>>
On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote:
> Daniel P. Berrangé writes:
>
> > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote:
> >> Hi,
> >>
> >
> >> I've met two situations with NVDIMM support in libvirt where I'm not
> >> sure all the parties (libvirt & I) do
Daniel P. Berrangé writes:
> On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote:
>> Hi,
>>
>
>> I've met two situations with NVDIMM support in libvirt where I'm not
>> sure all the parties (libvirt & I) do the things correctly.
>>
>> The first problem is with memory alignment and siz
On Thu, Jul 09, 2020 at 11:53:19AM +0200, Milan Zamazal wrote:
> Milan Zamazal writes:
>
> > Daniel P. Berrangé 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 S
Milan Zamazal writes:
> Daniel P. Berrangé 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
Daniel P. Berrangé writes:
> On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote:
>> Hi,
>>
>
>> I've met two situations with NVDIMM support in libvirt where I'm not
>> sure all the parties (libvirt & I) do the things correctly.
>>
>> The first problem is with memory alignment and siz
On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote:
> Hi,
>
> I've met two situations with NVDIMM support in libvirt where I'm not
> sure all the parties (libvirt & I) do the things correctly.
>
> The first problem is with memory alignment and size changes. In
> addition to the size c
Hi,
I've met two situations with NVDIMM support in libvirt where I'm not
sure all the parties (libvirt & I) do the things correctly.
The first problem is with memory alignment and size changes. In
addition to the size changes applied to NVDIMMs by QEMU, libvirt also
makes some NVDIMM size change
12 matches
Mail list logo