On 12/4/20 2:35 AM, Daniel P. Berrangé wrote:
On Thu, Dec 03, 2020 at 04:25:42PM -0700, Jim Fehlig wrote:
Attempting to create a lxc domain with fails
virsh --connect lxc:/// create distro_nosec.xml
error: Failed to create domain from distro_nosec.xml
error: unsupported configuration: Security
On 04.12.2020 19:46, Peter Krempa wrote:
> On Fri, Dec 04, 2020 at 19:28:55 +0300, Nikolay Shirokovskiy wrote:
>>
>>
>> On 04.12.2020 19:24, Peter Krempa wrote:
>>> On Fri, Dec 04, 2020 at 19:00:57 +0300, Nikolay Shirokovskiy wrote:
On 04.12.2020 18:52, Peter Krempa wrote:
> O
On 04.12.2020 19:24, Peter Krempa wrote:
> On Fri, Dec 04, 2020 at 19:00:57 +0300, Nikolay Shirokovskiy wrote:
>>
>>
>> On 04.12.2020 18:52, Peter Krempa wrote:
>>> On Fri, Dec 04, 2020 at 18:44:00 +0300, Nikolay Shirokovskiy wrote:
On 04.12.2020 18:11, Peter Krempa wrote:
> On Fri, Nov
On 04.12.2020 18:52, Peter Krempa wrote:
> On Fri, Dec 04, 2020 at 18:44:00 +0300, Nikolay Shirokovskiy wrote:
>> On 04.12.2020 18:11, Peter Krempa wrote:
>>> On Fri, Nov 13, 2020 at 09:53:28 +0300, Nikolay Shirokovskiy wrote:
>
> [...]
>
>> Ok. By the way what about the issue described in
>>
On 04.12.2020 18:11, Peter Krempa wrote:
> On Fri, Nov 13, 2020 at 09:53:28 +0300, Nikolay Shirokovskiy wrote:
>> This is successor to [1] but I changed the subject as in the review the patch
>> 'qemu: sync backing chain update in virDomainGetBlockJobInfo' was not
>> considered good one from des
On Fri, Sep 04, 2020 at 11:34:52AM +0800, Shi Lei wrote:
> V1 here: [https://www.redhat.com/archives/libvir-list/2020-June/msg00357.html]
>
> Differ from V1:
>
> * Move the generator into scripts/xmlgen and rename it 'xmlgen'.
>
> * Declare virXMLChildNode and virXMLChildNodeSet in libvirt_p
On Fri, Sep 04, 2020 at 11:35:34AM +0800, Shi Lei wrote:
> Signed-off-by: Shi Lei
> ---
> src/conf/domain_conf.c | 109 ---
> src/conf/domain_conf.h | 18 ++---
> src/qemu/qemu_command.c | 2 +
> src/qemu/qemu_hotplug.c | 1 +
On 12/4/20 3:15 PM, Andrea Bolognani wrote:
On Fri, 2020-12-04 at 13:50 -0300, Daniel Henrique Barboza wrote:
On 12/4/20 12:13 PM, Andrea Bolognani wrote:
I suggest you instead do a pseudo-revert, where you rename the
function (without otherwise altering its signature) and move it to
the par
On Fri, Sep 04, 2020 at 11:35:29AM +0800, Shi Lei wrote:
> Signed-off-by: Shi Lei
> ---
> src/conf/domain_conf.c | 272 ++---
> src/conf/domain_conf.h | 37 +++---
> 2 files changed, 26 insertions(+), 283 deletions(-)
>
> diff --git a/src/conf/domain_conf.c b
On Fri, 2020-12-04 at 13:50 -0300, Daniel Henrique Barboza wrote:
> On 12/4/20 12:13 PM, Andrea Bolognani wrote:
> > I suggest you instead do a pseudo-revert, where you rename the
> > function (without otherwise altering its signature) and move it to
> > the part of qemu_domain.c where you are ulti
On Fri, Sep 04, 2020 at 11:34:57AM +0800, Shi Lei wrote:
> Signed-off-by: Shi Lei
> ---
> src/libvirt_private.syms | 3 +++
> src/util/virstring.c | 57
> src/util/virstring.h | 9 +++
> 3 files changed, 69 insertions(+)
>
> diff --git a/src
On Fri, Sep 04, 2020 at 11:34:52AM +0800, Shi Lei wrote:
> V1 here: [https://www.redhat.com/archives/libvir-list/2020-June/msg00357.html]
> For those new and changed directives, illustrate them by an example:
>
> struct _virDomainGraphicsAuthDef { /* genparse, genformat:separate */
> char *
On 12/4/20 4:07 PM, Peter Krempa wrote:
This is a workaround for the issue that Nikolay tries to fix in:
https://www.redhat.com/archives/libvir-list/2020-November/msg00669.html
This one is a far more focused hack for apps which don't bother to
update to events for block job completion checking.
On 12/4/20 4:07 PM, Peter Krempa wrote:
Don't make the logic confusing by representing the 3 options using an
integer with negative values.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_driver.c | 9 +
src/qemu/qemu_monitor.h | 3 ++-
src/qemu/qemu_monitor_json.c | 8 ++--
On Fri, Sep 04, 2020 at 11:34:53AM +0800, Shi Lei wrote:
> This tool is used to generate parsexml/formatbuf functions.
> It is based on libclang and its python-binding.
> Some directives (such as genparse, xmlattr, etc.) need to be added on
> the declarations of structs to direct the tool.
In test
On Thu, Dec 03, 2020 at 09:46:20PM +0100, Michal Privoznik wrote:
If starting an container fails, the virLXCProcessStop() is
called. But since vm->def->id is not set until libvirt_lxc is
spawned (the domain's ID is PID of that process),
virLXCProcessStop() returns early as virDomainObjIsActive()
On 12/4/20 12:13 PM, Andrea Bolognani wrote:
On Fri, 2020-12-04 at 15:55 +0100, Andrea Bolognani wrote:
On Thu, 2020-12-03 at 22:05 -0300, Daniel Henrique Barboza wrote:
This reverts commit d3f3c2c97f9b92c982ff809479495f44614edb88
(domain_conf.c: auto-align pSeries NVDIMM in virDomainMemoryD
On Fri, Dec 04, 2020 at 19:28:55 +0300, Nikolay Shirokovskiy wrote:
>
>
> On 04.12.2020 19:24, Peter Krempa wrote:
> > On Fri, Dec 04, 2020 at 19:00:57 +0300, Nikolay Shirokovskiy wrote:
> >>
> >>
> >> On 04.12.2020 18:52, Peter Krempa wrote:
> >>> On Fri, Dec 04, 2020 at 18:44:00 +0300, Nikolay
On Fri, 4 Dec 2020 16:31:56 +0100
Boris Fiuczynski wrote:
> On 12/4/20 11:24 AM, Erik Skultety wrote:
> > On Thu, Dec 03, 2020 at 06:59:32PM +0100, Shalini Chellathurai Saroja
> > wrote:
> >> Add support for AP card devices, AP queues and AP matrix devices in
> >> libvirt node device driver.
>
On Fri, Dec 04, 2020 at 19:00:57 +0300, Nikolay Shirokovskiy wrote:
>
>
> On 04.12.2020 18:52, Peter Krempa wrote:
> > On Fri, Dec 04, 2020 at 18:44:00 +0300, Nikolay Shirokovskiy wrote:
> >> On 04.12.2020 18:11, Peter Krempa wrote:
> >>> On Fri, Nov 13, 2020 at 09:53:28 +0300, Nikolay Shirokovsk
On Fri, Dec 04, 2020 at 16:29:51 +0100, Michal Privoznik wrote:
> After previous cleanup the @qemuCaps argument in
> qemuDomainDefValidateMemoryHotplug() is unused and thus doesn't
> need to be passed.
>
> Signed-off-by: Michal Privoznik
> ---
> src/qemu/qemu_domain.c | 2 --
> src/qemu/qemu_d
On Fri, Dec 04, 2020 at 16:31:03 +0100, Michal Privoznik wrote:
> The AppArmorSetMemoryLabel() is a callback that is called from
> qemuSecuritySetMemoryLabel() which never passes NULL as @mem.
> Therefore, there is no need to check whether @mem is NULL. Also,
> no other driver does that and just de
On Fri, Dec 04, 2020 at 18:44:00 +0300, Nikolay Shirokovskiy wrote:
> On 04.12.2020 18:11, Peter Krempa wrote:
> > On Fri, Nov 13, 2020 at 09:53:28 +0300, Nikolay Shirokovskiy wrote:
[...]
> Ok. By the way what about the issue described in
>
> [PATCH v2 09/10] qemu: fix race on legacy block com
On 12/4/20 11:24 AM, Erik Skultety wrote:
On Thu, Dec 03, 2020 at 06:59:32PM +0100, Shalini Chellathurai Saroja wrote:
Add support for AP card devices, AP queues and AP matrix devices in
libvirt node device driver.
---
v4:
- Added virNodeDevAPAdapterParseXML function to extract the adapter
The AppArmorSetMemoryLabel() is a callback that is called from
qemuSecuritySetMemoryLabel() which never passes NULL as @mem.
Therefore, there is no need to check whether @mem is NULL. Also,
no other driver does that and just dereference it immediately.
Signed-off-by: Michal Privoznik
---
src/sec
After previous cleanup the @qemuCaps argument in
qemuDomainDefValidateMemoryHotplug() is unused and thus doesn't
need to be passed.
Signed-off-by: Michal Privoznik
---
src/qemu/qemu_domain.c | 2 --
src/qemu/qemu_domain.h | 1 -
src/qemu/qemu_hotplug.c | 2 +-
src/qemu/qemu_validate.c | 2 +
On Thu, 2020-12-03 at 22:05 -0300, Daniel Henrique Barboza wrote:
> qemuDomainAlignMemorySizes() has an operation order problem. We are
> calculating 'initialmem' without aligning the memory modules first.
> Since we're aligning the dimms afterwards this can create inconsistencies
> in the end resu
On Fri, 2020-12-04 at 15:55 +0100, Andrea Bolognani wrote:
> On Thu, 2020-12-03 at 22:05 -0300, Daniel Henrique Barboza wrote:
> > This reverts commit d3f3c2c97f9b92c982ff809479495f44614edb88
> > (domain_conf.c: auto-align pSeries NVDIMM in virDomainMemoryDefPostParse()).
> >
> > This reverts comm
On Fri, Nov 13, 2020 at 09:53:28 +0300, Nikolay Shirokovskiy wrote:
> This is successor to [1] but I changed the subject as in the review the patch
> 'qemu: sync backing chain update in virDomainGetBlockJobInfo' was not
> considered good one from design POV. However I think the basic patch is
> he
Signed-off-by: Peter Krempa
---
src/qemu/qemu_monitor.c | 29 -
src/qemu/qemu_monitor.h | 4
2 files changed, 33 deletions(-)
diff --git a/src/qemu/qemu_monitor.c b/src/qemu/qemu_monitor.c
index 551b65e778..40f2997cb6 100644
--- a/src/qemu/qemu_monitor.c
+++ b/s
Replace qemuMonitorGetBlockJobInfo by qemuMonitorGetAllBlockJobInfo and
hash table lookup. This basically open-codes qemuMonitorGetBlockJobInfo,
but it will be removed in next patch.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_driver.c | 20
1 file changed, 12 insertions(+
Don't make the logic confusing by representing the 3 options using an
integer with negative values.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_driver.c | 9 +
src/qemu/qemu_monitor.h | 3 ++-
src/qemu/qemu_monitor_json.c | 8 ++--
src/qemu/qemu_process.c | 4 ++--
This is a workaround for the issue that Nikolay tries to fix in:
https://www.redhat.com/archives/libvir-list/2020-November/msg00669.html
This one is a far more focused hack for apps which don't bother to
update to events for block job completion checking.
Peter Krempa (7):
virDomainGetBlockJob
Using ! on integers is misleading.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index 800f98e474..b82f7e249a 100644
--- a/src/qemu/qemu_driver.c
+++ b/src/qemu/qemu_drive
If the job has finished, but we didn't yet process the completion fake
that it's still incomplete so that apps which decided to poll
qemuDomainGetBlockJobInfo rather than use events can be sure that the
XML update was completed.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_driver.c | 14 +++
Add a note saying that polling virDomainGetBlockJobInfo is not a good
idea. Use events instead.
Signed-off-by: Peter Krempa
---
src/libvirt-domain.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/libvirt-domain.c b/src/libvirt-domain.c
index f5cd43ecea..5d3747fd39 100644
--- a/src/
Explicitly state that if 'end == 1' the data doesn't represent actual
progress in most cases.
Signed-off-by: Peter Krempa
---
src/libvirt-domain.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/src/libvirt-domain.c b/src/libvirt-domain.c
index 5d3747fd39.
On Thu, 2020-12-03 at 22:05 -0300, Daniel Henrique Barboza wrote:
> From: Andrea Bolognani
>
> The ppc64 tests
>
> memory-hotplug-ppc64-nonuma
> memory-hotplug-nvdimm-ppc64
>
> are not passed the same information for qemuxml2argv and
> qemuxml2xml tests; the former, in particular, doesn't s
On Thu, 2020-12-03 at 17:04 -0300, Daniel Henrique Barboza wrote:
> On 12/3/20 11:37 AM, Andrea Bolognani wrote:
> > This is where I'm a bit confused. IIUC the new value for ,
> > 1572992 KiB, is exactly 1 GiB (initial NUMA memory) + 512 MiB (NVDIMM
> > guest area size) + 128 KiB (NVDIMM label size
On Thu, 2020-12-03 at 22:05 -0300, Daniel Henrique Barboza wrote:
> This reverts commit d3f3c2c97f9b92c982ff809479495f44614edb88
> (domain_conf.c: auto-align pSeries NVDIMM in virDomainMemoryDefPostParse()).
>
> This reverts commit ace5931553c87beebb6b3cd994061742b3f88238
> (conf, qemu: move qemuD
On 12/4/20 5:12 AM, zhukeqian wrote:
Hi folks,
Kindly ping. I found that this patch is not applied.
Has reviewed by Daniel Henrique Barboza and Daniel P. Berrangé.
It has my ACK, but looking into the messages I see that Daniel was
inquiring about this being a bug fix or an enhancement (he
On Thu, Dec 03, 2020 at 13:36:30 +0100, Michal Privoznik wrote:
> Signed-off-by: Michal Privoznik
> ---
> NEWS.rst | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --git a/NEWS.rst b/NEWS.rst
> index 135c4e2fe0..adedf15d2b 100644
> --- a/NEWS.rst
> +++ b/NEWS.rst
> @@ -13,6 +13,15 @@ v7
On Thu, Dec 03, 2020 at 13:36:28 +0100, Michal Privoznik wrote:
> What code tries to achieve is that if no flags were provided to
> either 'setmem' or 'setmaxmem' commands then the old (no flags)
> API is called to be able to communicate with older daemons.
> Well, the code can be simplified a bit.
When an interface has some bandwidth limitation set (it's root
qdisc is htb in that case) but this gets cleared out via public
API call (virDomainSetInterfaceParameters() or
virDomainUpdateDeviceFlags()) then virNetDevBandwidthSet() clears
out whatever qdiscs were set on the interface and kernel pl
This fixes my previous series:
https://www.redhat.com/archives/libvir-list/2020-October/msg00636.html
Michal Prívozník (2):
qemu: Set default qdisc before setting bandwidth
qemu: Restore default root qdisc when QoS is cleared out
src/qemu/qemu_command.c | 4 ++--
src/qemu/qemu_driver.c |
While the code that's setting default qdisc is clever enough to
not overwrite any bandwidth (potentially) set by
virNetDevBandwidthSet() (and thus the root qdisc htb is not
replaced with noqueue), it does print a debug message when that's
the case. It's needless. We can set the root qdisc beforehan
On Thu, Dec 03, 2020 at 13:36:29 +0100, Michal Privoznik wrote:
> Provide an user friendly way of modifying 'requested-size' of a
> virtio-mem device. New --node and --alias arguments are
> introduced but they are needed only if it is not clear which
> virtio-mem does user mean.
>
> Signed-off-by:
On Fri, Sep 04, 2020 at 11:34:54AM +0800, Shi Lei wrote:
> Make sure python3-clang has been installed.
>
> Signed-off-by: Shi Lei
> ---
> meson.build | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/meson.build b/meson.build
> index 1eadea3..f97a03b 100644
> --- a/meson.build
> +++
On Thu, Dec 03, 2020 at 13:36:26 +0100, Michal Privoznik wrote:
> As advertised in previous commit, this event is delivered to us
> when virtio-mem module changes the allocation inside the guest.
> It comes with one attribute - size - which holds the new size of
> the virtio-mem (well, allocated si
On 12/2/20 11:13 AM, Peter Krempa wrote:
The domain definition stored with a checkpoint isn't used currently
apart from matching disks when creating a new checkpoints.
As some users of the incremental backup API want to provide backups in
offline mode under their control (obviously while comp
On 12/2/20 11:13 AM, Peter Krempa wrote:
Coniditonalize code which assumes that the domain definition stored in
s/Coniditonalize/Conditionalize
the checkpoint is present.
Signed-off-by: Peter Krempa
---
Reviewed-by: Daniel Henrique Barboza
src/conf/checkpoint_conf.c
On 12/2/20 11:13 AM, Peter Krempa wrote:
Checking the definition ABI when redefining checkpoints doesn't make
much sense for the following reasons:
* the domain definition in the checkpoint is mostly unused (a relic
adopted from the snapshot code)
* can be very easily overriden by deletin
On 12/2/20 11:13 AM, Peter Krempa wrote:
Fix the type for a variable holding flags to the usual 'unsigned int'
and change the name to be more appropriate to it's use.
s/it's/its
Reviewed-by: Daniel Henrique Barboza
Signed-off-by: Peter Krempa
---
src/conf/checkpoint_conf.c | 6 +++--
On 12/2/20 11:13 AM, Peter Krempa wrote:
We can extract './domain' directly and let the parser deal with the
type.
Signed-off-by: Peter Krempa
---
Reviewed-by: Daniel Henrique Barboza
src/conf/checkpoint_conf.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
dif
On Fri, Dec 04, 2020 at 13:17:52 +0100, Peter Krempa wrote:
> On Thu, Dec 03, 2020 at 13:36:23 +0100, Michal Privoznik wrote:
> > QEMU gained this new virtio-mem model. It's similar to pc-dimm
> > in a sense that guest uses it as memory, but in a sense very
> > different from it as it can dynamical
On Thu, Dec 03, 2020 at 13:36:25 +0100, Michal Privoznik wrote:
> As advertised in the previous commit, we want' to be able to
> change 'requested-size' attribute of virtio-mem on the fly. This
> commit does exactly that. Changing anything else is checked for
> and forbidden.
>
> Signed-off-by: Mi
On Thu, Dec 03, 2020 at 13:36:23 +0100, Michal Privoznik wrote:
> QEMU gained this new virtio-mem model. It's similar to pc-dimm
> in a sense that guest uses it as memory, but in a sense very
> different from it as it can dynamically change allocation,
> without need for hotplug. More specifically,
On Thu, Dec 03, 2020 at 13:36:22 +0100, Michal Privoznik wrote:
> Now we have everything prepared for generating the command line.
> The device alias prefix was chosen to be 'virtiopmem'.
>
> Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1735375
> Signed-off-by: Michal Privoznik
> ---
>
On Wed, Dec 02, 2020 at 11:38:22 +0100, Tim Wiederhake wrote:
> See arch/x86/include/asm/intel-family.h in the Kernel:
> #define INTEL_FAM6_ICELAKE_X0x6A
>
> Signed-off-by: Tim Wiederhake
> ---
> src/cpu_map/x86_Icelake-Server-noTSX.xml | 2 +-
> src/cpu_map/x86_Icelake-Server.
On Thu, Dec 03, 2020 at 06:59:32PM +0100, Shalini Chellathurai Saroja wrote:
> Add support for AP card devices, AP queues and AP matrix devices in
> libvirt node device driver.
> ---
> v4:
> - Added virNodeDevAPAdapterParseXML function to extract the adapter
>parsing logic.
> - Modified accor
On Thu, Dec 03, 2020 at 06:59:38PM +0100, Shalini Chellathurai Saroja wrote:
> Add support for AP matrix device in libvirt node device driver.
>
> Signed-off-by: Shalini Chellathurai Saroja
> Reviewed-by: Bjoern Walk
> Reviewed-by: Boris Fiuczynski
> ---
> docs/schemas/nodedev.rng |
On Thu, Dec 03, 2020 at 06:59:44PM +0100, Shalini Chellathurai Saroja wrote:
> Signed-off-by: Shalini Chellathurai Saroja
> ---
> NEWS.rst | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/NEWS.rst b/NEWS.rst
> index 135c4e2f..5fa9d68f 100644
> --- a/NEWS.rst
> +++ b/NEWS.rst
> @@ -
On Thu, Dec 03, 2020 at 04:25:42PM -0700, Jim Fehlig wrote:
> Attempting to create a lxc domain with fails
>
> virsh --connect lxc:/// create distro_nosec.xml
> error: Failed to create domain from distro_nosec.xml
> error: unsupported configuration: Security driver model '(null)' is not
> availa
On Thu, Dec 03, 2020 at 13:36:21 +0100, Michal Privoznik wrote:
> So far our memory modules could go only into DIMM slots. But with
> virtio model this assumption is no longer true - virtio-pmem goes
> onto PCI bus. But for formatting PCI address onto command line we
> already have a function - qem
On 12/4/20 12:25 AM, Jim Fehlig wrote:
Attempting to create a lxc domain with fails
virsh --connect lxc:/// create distro_nosec.xml
error: Failed to create domain from distro_nosec.xml
error: unsupported configuration: Security driver model '(null)' is not
available
The lxc driver does not se
On Thu, Dec 03, 2020 at 13:36:20 +0100, Michal Privoznik wrote:
> Some users might wanto have virtio-pmem backed by a block device
> in which case we have to create the device in domain namespace.
>
> Signed-off-by: Michal Privoznik
> ---
> src/qemu/qemu_namespace.c | 19 +--
> 1
On Thu, Dec 03, 2020 at 13:36:19 +0100, Michal Privoznik wrote:
> Some users might wanto have virtio-pmem backed by a block device
> in which case we have to allow the device in CGroups.
>
> Signed-off-by: Michal Privoznik
> ---
> src/qemu/qemu_cgroup.c | 43 -
On Thu, Dec 03, 2020 at 13:36:18 +0100, Michal Privoznik wrote:
> Signed-off-by: Michal Privoznik
> ---
> src/security/security_apparmor.c | 26
> src/security/security_dac.c | 42 +---
> src/security/security_selinux.c | 42 +
Hi folks,
Kindly ping. I found that this patch is not applied.
Has reviewed by Daniel Henrique Barboza and Daniel P. Berrangé.
Cheers,
Keqian
On 2020/7/15 14:18, Keqian Zhu wrote:
> For that Qemu supports returning incoming migration info since its commit
> 65ace0604551 (migration: add postcopy
On Thu, Dec 03, 2020 at 13:36:16 +0100, Michal Privoznik wrote:
> In this commit two new capabilities are introduced that reflect
> device support by give qemu:
>
> QEMU_CAPS_DEVICE_VIRTIO_MEM_PCI, /* -device virtio-mem-pci */
> QEMU_CAPS_DEVICE_VIRTIO_PMEM_PCI, /* -device virtio-pmem-pci */
>
>
On 12/3/20 6:31 PM, Andrea Bolognani wrote:
On Thu, 2020-12-03 at 17:39 +0100, Michal Privoznik wrote:
On 10/26/20 10:21 AM, Nikolay Shirokovskiy wrote:
-cp %{_datadir}/libvirt/nwfilter/*.xml %{_sysconfdir}/libvirt/nwfilter/
+# keep existing filters uuid on update
+for dfile in %{_datadir}/libv
On Thu, Dec 03, 2020 at 13:36:15 +0100, Michal Privoznik wrote:
> The virtio-pmem is a virtio variant of NVDIMM and just like
> NVDIMM virtio-pmem also allows accessing host pages bypassing
> guest page cache. The difference is that if a regular file is
> used to back guest's NVDIMM (model='nvdimm'
72 matches
Mail list logo
