search for: qemudomainupdatememorydeviceinfo

..._64). >> >> I'd like to clarify, how libvirt makes the DIMM address above. How is > > If the address isn't provided in the device XML of the attached device, > libvirt attaches the device without any address at all and then > refreshes the address from qemu in 'qemuDomainUpdateMemoryDeviceInfo'. OK, I can look into the QEMU source code, but I'd still like to have some official confirmation, especially regarding possible pitfalls or future changes. We can't risk data loss. >> the NVDIMM memory range determined? According to my experiments, it >> seems the NVDIM...

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

...ignment > (128 MB on x86_64). > > I'd like to clarify, how libvirt makes the DIMM address above. How is If the address isn't provided in the device XML of the attached device, libvirt attaches the device without any address at all and then refreshes the address from qemu in 'qemuDomainUpdateMemoryDeviceInfo'. > the NVDIMM memory range determined? According to my experiments, it > seems the NVDIMM specified <size> is taken, NVDIMM <label> size is > subtracted from it and the resulting value is reduced to the nearest > multiple of NVDIMM <alignsize>. Is this observat...