Changes v1 -> v2:
* v1 series subject was:
"qmp: Report supported device types on 'query-machines'"
* Now we return additional bus information: bus ID, bus type,
and the list of accepted device types on each bus
* Now hotplug can be covered because accepted-device-types can
be set by
The new field will return a list MachineBusInfo structs,
containing information about the buses that are always created by
the machine (even if -nodefaults is used).
Note that some machine options may enable or disable some bus
types and affect the set of available buses. Introspection of
those
On 2016-11-24 18:18, Daniel P. Berrange wrote:
This is better sent to the QEMU mailing list, rather than libvirt,
since
the former is where the QEMU audio experts are...
Regards,
Daniel
OK done. Good call, thanks Dan.
--
libvir-list mailing list
libvir-list@redhat.com
On 25.11.2016 18:33, Roman Mohr wrote:
> On Fri, Nov 25, 2016 at 6:04 PM, Michal Privoznik
> wrote:
>
>> On 25.11.2016 17:54, Roman Mohr wrote:
>>> On Fri, Nov 25, 2016 at 4:34 PM, Michal Privoznik
>>> wrote:
>>>
On 25.11.2016 14:38, Roman Mohr
On Thu, Nov 24, 2016 at 19:10:18 +0100, Pavel Hrdina wrote:
> On Mon, Nov 21, 2016 at 12:21:09AM +0100, Jiri Denemark wrote:
> > CPU models (and especially some additional details which we will start
> > probing for later) differ depending on the accelerator. Thus we need to
> > call
On Fri, Nov 25, 2016 at 19:56:23 +0100, Jiri Denemark wrote:
> The code that runs a new QEMU process to be used for probing
> capabilities is separated into four reusable functions so that any code
> that wants to probe a QEMU process may just follow a few simple steps:
>
> cmd =
The code that runs a new QEMU process to be used for probing
capabilities is separated into four reusable functions so that any code
that wants to probe a QEMU process may just follow a few simple steps:
cmd = virQEMUCapsInitQMPCommandNew(...);
mon = virQEMUCapsInitQMPCommandRun(cmd,
On Thu, Nov 24, 2016 at 14:54:48 +0100, Pavel Hrdina wrote:
> On Mon, Nov 21, 2016 at 12:20:57AM +0100, Jiri Denemark wrote:
> > The code that runs a new QEMU process to be used for probing
> > capabilities is separated into four reusable functions so that any code
> > that wants to probe a QEMU
On Fri, Nov 25, 2016 at 17:14:48 +0100, Peter Krempa wrote:
> Thanks to the complex capability caching code virQEMUCapsProbeQMP was
> never called when we were starting a new qemu VM. On the other hand,
> when we are reconnecting to the qemu process we reload the capability
> list from the status
On Fri, Nov 25, 2016 at 6:04 PM, Michal Privoznik
wrote:
> On 25.11.2016 17:54, Roman Mohr wrote:
> > On Fri, Nov 25, 2016 at 4:34 PM, Michal Privoznik
> > wrote:
> >
> >> On 25.11.2016 14:38, Roman Mohr wrote:
> >>> Hi,
> >>>
> >>> I recently started
And I didn't test this carefully, my apologies :-( Whether gpg-agent
can prompt the password depends on the pinentry program in use, but for
pinentry-curses this also requires to pass TERM. Patch modified
accordingly.
From: Guilhem Moulin
Subject: [PATCH] Pass GPG_TTY
On 25.11.2016 17:54, Roman Mohr wrote:
> On Fri, Nov 25, 2016 at 4:34 PM, Michal Privoznik
> wrote:
>
>> On 25.11.2016 14:38, Roman Mohr wrote:
>>> Hi,
>>>
>>> I recently started to use the libvirt domain events. With them I increase
>>> the responsiveness of my VM state
On Fri, Nov 25, 2016 at 4:34 PM, Michal Privoznik
wrote:
> On 25.11.2016 14:38, Roman Mohr wrote:
> > Hi,
> >
> > I recently started to use the libvirt domain events. With them I increase
> > the responsiveness of my VM state wachers.
> > In general it works pretty well. I
Thanks to the complex capability caching code virQEMUCapsProbeQMP was
never called when we were starting a new qemu VM. On the other hand,
when we are reconnecting to the qemu process we reload the capability
list from the status XML file. This means that the flag preventing the
function being
On Fri, Nov 25, 2016 at 05:12:41PM +0100, Martin Kletzander wrote:
> On Fri, Nov 25, 2016 at 03:39:17PM +, Daniel P. Berrange wrote:
> > On Fri, Nov 25, 2016 at 04:35:14PM +0100, Martin Kletzander wrote:
> > > On Fri, Nov 25, 2016 at 03:19:54PM +0100, Viktor Mihajlovski wrote:
> > > > On
On Fri, Nov 25, 2016 at 03:39:17PM +, Daniel P. Berrange wrote:
On Fri, Nov 25, 2016 at 04:35:14PM +0100, Martin Kletzander wrote:
On Fri, Nov 25, 2016 at 03:19:54PM +0100, Viktor Mihajlovski wrote:
> On 18.11.2016 17:44, Viktor Mihajlovski wrote:
> > With kernel 3.18 (since commit
22-Nov-16 15:05, Nikolay Shirokovskiy пишет:
ACK
Pushed now. Thanx.
Maxim
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On Mon, Nov 21, 2016 at 06:35:50PM -0500, John Ferlan wrote:
> Rather than have multiple bool values, create a single enum with bits
> representing what can be set.
>
> Signed-off-by: John Ferlan
> ---
> src/qemu/qemu_driver.c | 113
>
On Fri, Nov 25, 2016 at 04:35:14PM +0100, Martin Kletzander wrote:
> On Fri, Nov 25, 2016 at 03:19:54PM +0100, Viktor Mihajlovski wrote:
> > On 18.11.2016 17:44, Viktor Mihajlovski wrote:
> > > With kernel 3.18 (since commit 3e32cb2e0a12b6915056ff04601cf1bb9b44f967)
> > > the
> > > "unlimited"
On Fri, Nov 25, 2016 at 03:19:54PM +0100, Viktor Mihajlovski wrote:
On 18.11.2016 17:44, Viktor Mihajlovski wrote:
With kernel 3.18 (since commit 3e32cb2e0a12b6915056ff04601cf1bb9b44f967) the
"unlimited" value for cgroup memory limits has changed once again as its byte
value is now computed
On 25.11.2016 14:38, Roman Mohr wrote:
> Hi,
>
> I recently started to use the libvirt domain events. With them I increase
> the responsiveness of my VM state wachers.
> In general it works pretty well. I just listen to the events and do a
> periodic resync to cope with missed events.
>
> While
On Mon, Nov 21, 2016 at 06:35:48PM -0500, John Ferlan wrote:
> Rather than using negative logic and setting the maxparams to a lesser
> value based on which capabilities exist, alter the logic to modify the
> maxparams based on a base value plus the found capabilities. Reduces the
> chance that
On Mon, Nov 14, 2016 at 11:13:22AM +0100, Guilhem Moulin wrote:
Hi Daniel,
On Mon, 14 Nov 2016 at 10:02:55 +, Daniel P. Berrange wrote:
On Sat, Nov 12, 2016 at 02:19:37PM +0100, Guido Günther wrote:
This came in via the Debian BTS:
http://bugs.debian.org/43863
This seems to be the
On Tue, Nov 01, 2016 at 12:11:16PM +, Jaroslav Safka wrote:
Add html documentation for memoryBacking element.
We usually merge documentation with the conf changes.
---
docs/formatdomain.html.in | 10 ++
1 file changed, 10 insertions(+)
diff --git a/docs/formatdomain.html.in
On Tue, Nov 01, 2016 at 12:11:15PM +, Jaroslav Safka wrote:
This second change introduces support for preallocated
shared file descriptor based memory backing.
It allows vhost-user to be used without hugepages.
Also token memAccess in numa cell is used (if not present, default value
from
On Fri, Nov 25, 2016 at 14:25:33 +0100, Boris Fiuczynski wrote:
> On 11/25/2016 10:07 AM, Peter Krempa wrote:
> > On Fri, Nov 25, 2016 at 10:03:38 +0100, Peter Krempa wrote:
> > > On Fri, Nov 25, 2016 at 09:19:18 +0100, Boris Fiuczynski wrote:
> >
> > [...]
>
> Peter,
> looking at your commit
Eduardo Habkost writes:
> Instead of using custom feature name lookup code for
> plus_features/minus_features, save the property names used in
> "[+-]feature" and use object_property_set_bool() to set them.
>
> We don't need a feat2prop() call because we now have alias
>
On Tue, Nov 01, 2016 at 12:11:14PM +, Jaroslav Safka wrote:
This first change introduces xml parsing support for preallocated
shared file descriptor based memory backing.
It allows vhost-user to be used without hugepages.
New xml elements:
---
docs/schemas/domaincommon.rng
Hi Daniel,
On Mon, Nov 14, 2016 at 10:02:55AM +, Daniel P. Berrange wrote:
> On Sat, Nov 12, 2016 at 02:19:37PM +0100, Guido Günther wrote:
> > This came in via the Debian BTS:
> >
> > http://bugs.debian.org/43863
>
> This seems to be the wrong bug number.
I've updated the commit message
On Wed, 2016-11-23 at 16:02 +1100, David Gibson wrote:
> > > The change from OHCI to XHCI only affected the *default* USB
> > > controller, which libvirt tries its best not to use anyway:
> > > instead, it will prefer to use '-M ...,usb=off' along with
> > > '-device ...' and set both the
On Fri, Oct 28, 2016 at 12:33:28PM -0700, Prerna Saxena wrote:
An errno=ECONNRESET received on a monitor socket reflects that the
guest may have closed the socket.
How would they close it? Does that happen when the process is dying?
Today, we just mark it as a 'hangup' and do not trigger
On 18.11.2016 17:44, Viktor Mihajlovski wrote:
> With kernel 3.18 (since commit 3e32cb2e0a12b6915056ff04601cf1bb9b44f967) the
> "unlimited" value for cgroup memory limits has changed once again as its byte
> value is now computed from a page counter.
> The new "unlimited" value reported by the
The functions to retrieve online and present host CPU information
are only supported on Linux for the time being.
This leads to runtime errors if these function are used on other
platforms. To avoid that, code in higher levels using the functions
must replicate the conditional compilation in
This is a rework of the original patch allowing to use all host
CPUs if the cpuset controller is not configured by libvirt.
The major enhancement is that we won't try to retrieve the online
host CPU map on platforms where this is not supported and just
fall back to the old behavior.
V3:
- Added
If the cpuset cgroup controller is disabled in /etc/libvirt/qemu.conf
QEMU virtual machines can in principle use all host CPUs, even if they
are hot plugged, if they have no explicit CPU affinity defined.
However, there's libvirt code supposed to handle the situation where
the libvirt daemon
On Wed, 2016-11-23 at 16:00 +1100, David Gibson wrote:
> > Existing libvirt versions assume that pseries guests have
> > a legacy PCI root bus, and will base their PCI address
> > allocation / PCI topology decisions on that fact: they
> > will, for example, use legacy PCI bridges.
>
> Um.. yeah..
Hi,
I recently started to use the libvirt domain events. With them I increase
the responsiveness of my VM state wachers.
In general it works pretty well. I just listen to the events and do a
periodic resync to cope with missed events.
While watching the events I ran into a few interesting
On 11/25/2016 10:07 AM, Peter Krempa wrote:
On Fri, Nov 25, 2016 at 10:03:38 +0100, Peter Krempa wrote:
On Fri, Nov 25, 2016 at 09:19:18 +0100, Boris Fiuczynski wrote:
[...]
src/qemu/qemu_process.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
On Wed, Oct 19, 2016 at 02:39:46PM +0300, Konstantin Neumoin wrote:
The option for removing vcpu pinning information from config was added
in:
'7ea9778 vcpupin: add vcpupin resetting feature to qemu driver'
By the way, this hash is ambiguous, 7ea9778c is better, but I rather use
7ea9778c8a3d
Enable libvirt users to query logging output settings.
Signed-off-by: Erik Skultety
---
daemon/admin.c | 37 +
include/libvirt/libvirt-admin.h | 4
src/admin/admin_protocol.x | 16 +++-
v1 here https://www.redhat.com/archives/libvir-list/2016-November/msg9.html
since v1:
- incorporated notes raised during review
- allowed passing of NULL via the public APIs
* behaves the same way as an empty string, but lead to even more code
reduction in 'daemonSetupLogging' for
Enable libvirt users to modify logging filters of a daemon from outside.
Signed-off-by: Erik Skultety
---
daemon/admin.c | 10 ++
include/libvirt/libvirt-admin.h | 4
src/admin/admin_protocol.x | 12 +++-
Along with an empty string, it should also be possible for users to pass NULL
to the public APIs which in turn would trigger a routine (future work)
responsible for defining an appropriate default logging output given the current
circumstances.
Signed-off-by: Erik Skultety
Signed-off-by: Erik Skultety
---
docs/news.html.in | 4
1 file changed, 4 insertions(+)
diff --git a/docs/news.html.in b/docs/news.html.in
index 59bf20d..f2a65f5 100644
--- a/docs/news.html.in
+++ b/docs/news.html.in
@@ -31,6 +31,10 @@
Add the capability to
Provide a simple C example demonstrating the use of both query APIs as well as
setter APIs.
Signed-off-by: Erik Skultety
---
.gitignore | 1 +
examples/Makefile.am | 3 +-
examples/admin/logging.c | 102 +++
These helpers will manage the log destination defaults (fetch/set). The reason
for this is to stay consistent with the current daemon's behaviour with respect
to /etc/libvirt/.conf file, since both assignment of an empty string
or not setting the log output variable at all trigger the daemon's
Enable libvirt users to modify daemon's logging output settings from outside.
If either an empty string or NULL is passed, a default logging output will be
used the same way as it would be in case writing an empty string to the
libvirtd.conf
Signed-off-by: Erik Skultety
---
Enable libvirt users to query logging filter settings.
Signed-off-by: Erik Skultety
---
daemon/admin.c | 47 +
include/libvirt/libvirt-admin.h | 4
src/admin/admin_protocol.x | 16 +-
Finally, now that all APIs have been introduced, wire them up to virt-admin
and introduce daemon-log-outputs and daemon-log-filters commands.
Signed-off-by: Erik Skultety
---
tools/virt-admin.c | 120 +++
Now that virLog{Get,Set}DefaultOutput routines are introduced we can wire them
up to the daemon's logging initialization code. Also, change the order of
operations a bit so that we still strictly honor our precedence of settings:
cmdline > env > config now that outputs and filters are not appended
On Fri, 2016-11-25 at 13:44 +0100, Peter Krempa wrote:
> > You'll also need to close the element properly, or
> > building the documentation will fail.
>
> Right. The format of the file, where we wrap the text back to the column
> where the tag starts rather than wrapping it to the column where
On Fri, 2016-11-25 at 07:30 -0500, John Ferlan wrote:
> > > This patch series provides a libvirt implementation of the vhost-scsi
> > > interface in QEMU.
> >
> > Can you please provide a release notes entry briefly
> > describing this change? You can look at existing entries
> > in
On Fri, Nov 25, 2016 at 13:36:01 +0100, Andrea Bolognani wrote:
> On Fri, 2016-11-25 at 12:14 +0100, Peter Krempa wrote:
> > ---
> > docs/news.html.in | 4
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/docs/news.html.in b/docs/news.html.in
> > index 0a4b767..2ba25f5 100644
> >
On Fri, 2016-11-25 at 12:14 +0100, Peter Krempa wrote:
> ---
> docs/news.html.in | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/docs/news.html.in b/docs/news.html.in
> index 0a4b767..2ba25f5 100644
> --- a/docs/news.html.in
> +++ b/docs/news.html.in
> @@ -34,6 +34,10 @@
>
On Fri, 2016-11-25 at 12:14 +0100, Peter Krempa wrote:
> ---
> docs/news.html.in | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/docs/news.html.in b/docs/news.html.in
> index 54eb8ad..0a4b767 100644
> --- a/docs/news.html.in
> +++ b/docs/news.html.in
> @@ -31,6 +31,9 @@
>
On 11/25/2016 05:50 AM, Andrea Bolognani wrote:
> On Mon, 2016-11-21 at 22:58 -0500, Eric Farman wrote:
>> This patch series provides a libvirt implementation of the vhost-scsi
>> interface in QEMU.
>
> Can you please provide a release notes entry briefly
> describing this change? You can look
On Fri, Nov 25, 2016 at 11:53 AM, Jiri Denemark wrote:
>> How do you want to handle this, would you like me to open an issue in
>> bugzilla?
>
> Yes please. Unless you want to provide the patches :-)
I'd love to, but it is a bit outside of my area of expertise.
I opened
Peter Krempa (2):
docs: NEWS: Mention 'gluster_debug_level' qemu.conf option in the news
docs: news: Mention changes in memory slot number allocation
docs/news.html.in | 7 +++
1 file changed, 7 insertions(+)
--
2.10.2
--
libvir-list mailing list
libvir-list@redhat.com
---
docs/news.html.in | 4
1 file changed, 4 insertions(+)
diff --git a/docs/news.html.in b/docs/news.html.in
index 0a4b767..2ba25f5 100644
--- a/docs/news.html.in
+++ b/docs/news.html.in
@@ -34,6 +34,10 @@
qemu: Users can now enable debug logging for native gluster
---
docs/news.html.in | 3 +++
1 file changed, 3 insertions(+)
diff --git a/docs/news.html.in b/docs/news.html.in
index 54eb8ad..0a4b767 100644
--- a/docs/news.html.in
+++ b/docs/news.html.in
@@ -31,6 +31,9 @@
Add the capability to pass through a scsi_host HBA and the
On Fri, 2016-11-25 at 09:28 +0100, Michal Privoznik wrote:
> We have couple of functions that operate over NULL terminated
> lits of strings. However, our naming sucks:
>
> virStringJoin
> virStringFreeList
> virStringFreeListCount
> virStringArrayHasString
> virStringGetFirstWithPrefix
>
> We
On Fri, Nov 25, 2016 at 11:38:36 +0100, Ruben Kerkhof wrote:
> Hi Jiri,
>
> On Fri, Nov 25, 2016 at 9:26 AM, Jiri Denemark wrote:
> > I guess it should be possible to also check the progress of all running
> > block jobs so that we can report statistics about ongoing storage
Signed-off-by: Jiri Denemark
---
docs/news.html.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/news.html.in b/docs/news.html.in
index 59bf20da3..3a0fea65e 100644
--- a/docs/news.html.in
+++ b/docs/news.html.in
@@ -35,6 +35,8 @@
Improvements
Only the latest APIs are fully documented and the documentation of the
older variants (which are just limited versions of the new APIs anyway)
points to the newest APIs.
Signed-off-by: Jiri Denemark
---
src/libvirt-domain.c | 348
We have 6 public APIs for migration: virDomainMigrate,
virDomainMigrate2, virDomainMigrate3, virDomainMigrateToURI,
virDomainMigrateToURI2, and virDomainMigrateToURI3. Each of them was
documented separately, but the documentation was not consistent. Some
APIs documented individual flags, some
The enhanced documentation of VIR_MIGRATE_RDMA_PIN_ALL fixes
https://bugzilla.redhat.com/show_bug.cgi?id=1373783
Signed-off-by: Jiri Denemark
---
include/libvirt/libvirt-domain.h | 153 +--
1 file changed, 132 insertions(+), 21
On Mon, 2016-11-21 at 22:58 -0500, Eric Farman wrote:
> This patch series provides a libvirt implementation of the vhost-scsi
> interface in QEMU.
Can you please provide a release notes entry briefly
describing this change? You can look at existing entries
in docs/news.html.in to see how it
Hi Jiri,
On Fri, Nov 25, 2016 at 9:26 AM, Jiri Denemark wrote:
> On Thu, Nov 24, 2016 at 22:54:10 +0100, Ruben Kerkhof wrote:
>> Hi all,
>>
>> Running virsh domjobinfo on my CentOS 6 systems during a migration
>> with --copy-storage-all, the output used to look like this:
>>
On Mon, 2016-11-21 at 00:01 -0500, Laine Stump wrote:
> Patches 1 and 4 were originally added to the end of the "more PCIe
> less legacy PCI" patchset in its final incarnation, but all the other
> patches were ACKed and pushed, while this needed a bit more work,
> resulting in this "faux V2" -
Catch up with changes that have been pushed but didn't include
updates to the NEWS file themselves.
---
Pushed under the "this NEWS file thing will need some time
to catch on" rule.
docs/news.html.in | 7 +++
1 file changed, 7 insertions(+)
diff --git a/docs/news.html.in b/docs/news.html.in
On Fri, Nov 25, 2016 at 04:20:18PM +0800, Zhang Zhuoyu wrote:
> CPU sockets calculation is inconsistent with physical sockets when
> Host machine has more than one node. It only calculate the maximum
> socket number of all CPU nodes instead of summing up.
>
> For example:
>
> Architecture:
Currently when the vcpu placement is static
and cpuset is not specified, CPU Affinity
under virsh vcpupin shows 0..CPUMAX. This
patchset will result in display of only
online CPU's under CPU Affinity on linux.
Signed-off-by: Nitesh Konkar
---
src/conf/domain_conf.c
Currently when the vcpu placement is static and
cpuset is not specified, CPU Affinity shows 0..
CPUMAX. This patchset will result in display of
only online CPU's under CPU Affinity on linux.
Fixes the following Bug:
virsh dumpxml Fedora
Fedora
aecf3e5e-6f9a-42a3-9d6a-223a75569a66
3145728
Currently when the vcpu placement is static
and cpuset is not specified, CPU Affinity
under virsh emulatorpin shows 0..CPUMAX. This
patchset will result in display of only
online CPU's under CPU Affinity on linux.
Signed-off-by: Nitesh Konkar
---
On Fri, Nov 25, 2016 at 10:03:38 +0100, Peter Krempa wrote:
> On Fri, Nov 25, 2016 at 09:19:18 +0100, Boris Fiuczynski wrote:
[...]
> > src/qemu/qemu_process.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c
> >
On Fri, Nov 25, 2016 at 09:19:18 +0100, Boris Fiuczynski wrote:
> (Re-)Starting libvirt on a system with running qemu domains which earlier
> had been successfully started by libvirt results in the error
>
> internal error: unable to execute QEMU command 'query-hotpluggable-cpus':
> The feature
qemu commit: f74eefe0
https://lwn.net/Articles/667156/
Signed-off-by: Lin Ma
---
src/cpu/cpu_map.xml | 7 +++
1 file changed, 7 insertions(+)
diff --git a/src/cpu/cpu_map.xml b/src/cpu/cpu_map.xml
index 6da8321..dca5720 100644
--- a/src/cpu/cpu_map.xml
+++
On Thu, Nov 24, 2016 at 01:28:00PM +0100, Boris Fiuczynski wrote:
If libvirt is compiled without NUMACTL support starting libvirtd
reports a libvirt internal error "NUMA isn't available on this host"
without checking if NUMA support is compiled into the libvirt binaries.
This patch adds the
On Tue, Nov 22, 2016 at 01:45:42PM +0100, Michal Privoznik wrote:
If you've ever tried running a huge page backed guest under
different user than root, you probably failed. Problem is even
Surely you mean different than the default user from qemu.conf.
though we have corresponding APIs in
We have couple of functions that operate over NULL terminated
lits of strings. However, our naming sucks:
virStringJoin
virStringFreeList
virStringFreeListCount
virStringArrayHasString
virStringGetFirstWithPrefix
We can do better:
virStringListJoin
virStringListFree
virStringListFreeCount
On Thu, Nov 24, 2016 at 22:54:10 +0100, Ruben Kerkhof wrote:
> Hi all,
>
> Running virsh domjobinfo on my CentOS 6 systems during a migration
> with --copy-storage-all, the output used to look like this:
>
> Job type: Unbounded
> Time elapsed: 1830632 ms
> Data processed:
(Re-)Starting libvirt on a system with running qemu domains which earlier
had been successfully started by libvirt results in the error
internal error: unable to execute QEMU command 'query-hotpluggable-cpus':
The feature 'query-hotpluggable-cpus' is not enabled
if the qemu binary does not
On Tue, Nov 22, 2016 at 01:45:43PM +0100, Michal Privoznik wrote:
Since its introduction in 2012 this internal API did nothing. Now
it's finally the right time to put it into a good use. It's
implementation is fairly simple and exactly the same as
virSecurityDomainSetPathLabel.
Then why do
Marcel Apfelbaum writes:
> On 11/24/2016 05:41 PM, Markus Armbruster wrote:
>> Marcel Apfelbaum writes:
>>
>>> On 11/24/2016 03:34 PM, Markus Armbruster wrote:
Eduardo Habkost writes:
> On Wed, Nov 23, 2016 at 06:43:16PM
84 matches
Mail list logo