similar to: Two questions about NVDIMM devices

Daniel P. Berrangé <berrange@redhat.com> 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 size changes. In

Daniel P. Berrangé <berrange@redhat.com> 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 size changes. In

Daniel P. Berrangé <berrange@redhat.com> writes: > On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: >> Daniel P. Berrangé <berrange@redhat.com> writes: >> > >> > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> >> Hi, >> >> >> > >> >> I've met two situations with NVDIMM support

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é <berrange@redhat.com> writes: >> >>> On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: >>>> Daniel P. Berrangé <berrange@redhat.com> writes: >>>> >>> >>>>> On Thu, Jul

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 changes applied to NVDIMMs by QEMU, libvirt also > makes some

Hi, I've found out that NVDIMM size and label size matter for regular (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the guest OS will not accept the hot plugged memory and will complain with messages such as Block size [0x8000000] unaligned hotplug range: start 0x225000000, size 0x10000000 The start address above is also reported within <memory> element of the hot

Peter Krempa <pkrempa@redhat.com> writes: > On Tue, Jun 16, 2020 at 12:54:29 +0200, Milan Zamazal wrote: >> Hi, >> > >> I've found out that NVDIMM size and label size matter for regular >> (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the >> guest OS will not accept the hot plugged memory and will complain with >> messages

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

On Thu, Sep 10, 2020 at 04:54:08PM +0200, Milan Zamazal wrote: > Daniel P. Berrangé <berrange@redhat.com> writes: > > > On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: > >> Daniel P. Berrangé <berrange@redhat.com> writes: > >> > > > >> > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: > >> >>

On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: > Daniel P. Berrangé <berrange@redhat.com> 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

Michal Prívozník <mprivozn@redhat.com> writes: > On 09/19/2018 12:39 PM, Milan Zamazal wrote: >> Hi, I'm playing with dynamic ownership and not all objects have their >> owners changed. > >> >> Is dynamic_ownership and its scope documented somewhere, besides the >> comment in qemu.conf? >> >> And what kinds of objects are handled by

On Tue, Jun 16, 2020 at 12:54:29 +0200, Milan Zamazal wrote: > Hi, > > I've found out that NVDIMM size and label size matter for regular > (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the > guest OS will not accept the hot plugged memory and will complain with > messages such as > > Block size [0x8000000] unaligned hotplug range: start

On Tue, Jun 16, 2020 at 12:54:29PM +0200, Milan Zamazal wrote: > Hi, > > I've found out that NVDIMM size and label size matter for regular > (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the > guest OS will not accept the hot plugged memory and will complain with > messages such as > > Block size [0x8000000] unaligned hotplug range: start

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é <berrange@redhat.com> writes: > > > > > > If we're enforcing this 1 MB rounding though, we really should be > > > > > > documenting it

On Thu, Jul 09, 2020 at 14:14:32 +0200, Milan Zamazal wrote: > Milan Zamazal <mzamazal@redhat.com> writes: > > > Hi, > > > > I would like to clarify how to make snapshots of running VMs with > > emulated TPM devices. As far as I understand QEMU documentation, it's > > possible to make snapshots of running VMs with TPM, but it's important >

"Daniel P. Berrange" <dan@berrange.com> writes: > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: >> Hi, >> > >> we have a problem in oVirt that highly available VMs don't restart after >> host poweroff because Vdsm identifies the case as a user initiated >> shutdown (https://bugzilla.redhat.com/1800966). >> >>

"Daniel P. Berrange" <berrange@redhat.com> writes: > On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote: >> Hi, we experienced a strange, non-reproducible error after a successful >> migration to another host. When we called virDomainDestroyFlags with >> VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host, >> we got

Jiri Denemark <jdenemar@redhat.com> writes: > On Fri, Feb 17, 2017 at 12:38:24 +0100, Milan Zamazal wrote: >> Jiri Denemark <jdenemar@redhat.com> writes: >> >> > On Fri, Feb 10, 2017 at 21:50:19 +0100, Milan Zamazal wrote: >> >> Hi, is there a reliable way to find out to what kind of job does the >> >> information returned from

Daniel P. Berrangé <berrange@redhat.com> writes: > On Wed, Sep 18, 2019 at 12:18:32PM +0200, Milan Zamazal wrote: >> Daniel P. Berrangé <berrange@redhat.com> writes: >> > >> > On Wed, Sep 04, 2019 at 03:38:25PM +0200, Milan Zamazal wrote: >> >> Hi, I'm trying to add TLS migrations to oVirt, but I've hit a problem >> >> with

On Thu, Jul 09, 2020 at 17:54:23 +0200, Milan Zamazal wrote: > Peter Krempa <pkrempa@redhat.com> writes: > > > On Thu, Jul 09, 2020 at 14:14:32 +0200, Milan Zamazal wrote: > >> Milan Zamazal <mzamazal@redhat.com> writes: > >> > > > >> > Hi, > >> > > >> > I would like to clarify how to make snapshots of running