On 12/13/21 15:29, Jiri Denemark wrote:
> So far we were enabling specific migration capabilities when a
> corresponding API flag is set. We need to generalize our code to be able
> to enable some migration capabilities unless a particular API flag is
> used.
>
> Signed-off-by: Jiri Denemark
>
On 12/13/21 15:29, Jiri Denemark wrote:
> See 2/2 for more details about the capability.
>
> Jiri Denemark (2):
> qemu: Support enabling migration caps unless a flag is used
> qemu: Add support for return-path migration capability
>
> src/qemu/qemu_migration_params.c | 39
From: Lin Yang
Two unit test files were added to verify qemu command generated
with SGX EPC enabled with 6.2.0 qemu capability.
Signed-off-by: Lin Yang
---
.../sgx-epc.x86_64-6.2.0.args | 37 +++
tests/qemuxml2argvdata/sgx-epc.xml| 36
From: Lin Yang
According to the result parsing from xml, add the argument of
SGX EPC memory backend into QEMU command line:
#qemu-system-x86_64 \
.. \
-object memory-backend-epc,id=mem1,size=64M,prealloc=on \
-object memory-backend-epc,id=mem2,size=28M \
From: Lin Yang
...
512
...
Signed-off-by: Lin Yang
---
docs/schemas/domaincommon.rng| 1 +
src/conf/domain_conf.c | 6 ++
src/conf/domain_conf.h | 1 +
src/conf/domain_validate.c | 1 +
src/qemu/qemu_alias.c| 3 +++
Convert qemu sgx capabilities:
{"sgx": true, "section-size": 0, "flc": false}
to XML format:
no
1
Signed-off-by: Haibin Huang
---
docs/schemas/domaincaps.rng | 22 ++-
src/conf/domain_capabilities.c| 19
The Qemu QMP provide the command "query-sgx-capabilities"
libvirt call the command to get sgx capabilities
{"execute":"query-sgx-capabilities"}
{"return":
{"sgx": true, "sgx1": true, "sgx2": false, "section-size": 0, \
"flc": false}}
Signed-off-by: Haibin Huang
---
This patch series provides support for enabling Intel's Software Guard
Extensions (SGX) feature in guest VM.
Giving the SGX support in QEMU be accepted and will be merged in two
days Intel SGX is a set of instructions that increases the security
of application code and data, giving them more
On 12/14/21 2:09 PM, Ján Tomko wrote:
This bumps the minimum dnsmasq version to the point where we do not need
capability probing, reducing it to a version check (which I will be
happy to remove on request).
Unless I missed something, this also means we no longer need to spawn
radvd manually.
On 12/14/21 2:09 PM, Ján Tomko wrote:
Introduced by:
"Introduced by dnsmasq commit:"
commit c4cd95df68b573b63d234ecdb675228657d65353
Author: Simon Kelley
CommitDate: 2013-10-10 20:58:11 +0100
Add --ra-param and remove --force-fast-ra
git describe: v2.67rc3-3-gc4cd95d contains:
On 12/14/21 2:09 PM, Ján Tomko wrote:
All the capabilities should be supported in 2.67.
Make this the minimum version, since even the oldest
distros we support have moved on:
Debian 8: 2.72
CentOS 7: 2.76
Ubuntu 18.04: 2.79
Signed-off-by: Ján Tomko
---
src/util/virdnsmasq.c | 13
On 12/14/21 2:09 PM, Ján Tomko wrote:
Signed-off-by: Ján Tomko
---
src/util/virdnsmasq.c | 22 ++
src/util/virdnsmasq.h | 4
2 files changed, 2 insertions(+), 24 deletions(-)
diff --git a/src/util/virdnsmasq.c b/src/util/virdnsmasq.c
index efe65174f8..016d9d64a8
It has no callers anymore.
Signed-off-by: Ján Tomko
---
src/libvirt_private.syms | 1 -
src/util/virdnsmasq.c| 9 -
src/util/virdnsmasq.h| 1 -
3 files changed, 11 deletions(-)
diff --git a/src/libvirt_private.syms b/src/libvirt_private.syms
index 36f826e2ed..8ed50d1c45 100644
Now that we only check whether the dnsmasq version is new enough,
there is no need for the caps field.
Signed-off-by: Ján Tomko
---
src/libvirt_private.syms | 1 -
src/util/virdnsmasq.c| 17 -
src/util/virdnsmasq.h| 5 -
3 files changed, 23 deletions(-)
diff --git
Signed-off-by: Ján Tomko
---
libvirt.spec.in | 2 --
1 file changed, 2 deletions(-)
diff --git a/libvirt.spec.in b/libvirt.spec.in
index 32b4243d0a..b37c6e17f3 100644
--- a/libvirt.spec.in
+++ b/libvirt.spec.in
@@ -283,7 +283,6 @@ BuildRequires: libnl3-devel
BuildRequires: libselinux-devel
Signed-off-by: Ján Tomko
---
src/network/bridge_driver.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/src/network/bridge_driver.c b/src/network/bridge_driver.c
index 39f6ed14e1..23d9ed4226 100644
--- a/src/network/bridge_driver.c
+++ b/src/network/bridge_driver.c
@@
Signed-off-by: Ján Tomko
---
meson.build | 1 -
1 file changed, 1 deletion(-)
diff --git a/meson.build b/meson.build
index cea8bbfa0c..0b7a2a69c1 100644
--- a/meson.build
+++ b/meson.build
@@ -860,7 +860,6 @@ optional_programs = [
'modprobe',
'ovs-vsctl',
'pdwtags',
- 'radvd',
Since dnsmasq supports --ra-param for a long time, this code is now
unused.
Signed-off-by: Ján Tomko
---
src/network/bridge_driver.c | 248 +---
1 file changed, 6 insertions(+), 242 deletions(-)
diff --git a/src/network/bridge_driver.c
Signed-off-by: Ján Tomko
---
src/conf/virnetworkobj.c | 16
src/conf/virnetworkobj.h | 7 ---
src/libvirt_private.syms | 2 --
3 files changed, 25 deletions(-)
diff --git a/src/conf/virnetworkobj.c b/src/conf/virnetworkobj.c
index 41c7dcba5c..f18eb35ae2 100644
---
Signed-off-by: Ján Tomko
---
src/network/bridge_driver_platform.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/src/network/bridge_driver_platform.h
b/src/network/bridge_driver_platform.h
index 884fa82831..de7cbc1195 100644
--- a/src/network/bridge_driver_platform.h
+++
Signed-off-by: Ján Tomko
---
src/util/virdnsmasq.c | 22 ++
src/util/virdnsmasq.h | 4
2 files changed, 2 insertions(+), 24 deletions(-)
diff --git a/src/util/virdnsmasq.c b/src/util/virdnsmasq.c
index efe65174f8..016d9d64a8 100644
--- a/src/util/virdnsmasq.c
+++
Introduced by:
commit c4cd95df68b573b63d234ecdb675228657d65353
Author: Simon Kelley
CommitDate: 2013-10-10 20:58:11 +0100
Add --ra-param and remove --force-fast-ra
git describe: v2.67rc3-3-gc4cd95d contains: v2.67rc4~12
Signed-off-by: Ján Tomko
---
src/network/bridge_driver.c | 6
Introduced by dnsmasq commit:
commit 54dd393f3938fc0c19088fbd319b95e37d81a2b0
CommitDate: 2012-06-20 11:23:38 +0100
Add --bind-dynamic
git describe: v2.63test1 contains: v2.63test1^0
Signed-off-by: Ján Tomko
---
src/network/bridge_driver.c | 68 ++---
1
Now that the macro is unused, delete it.
Signed-off-by: Ján Tomko
---
src/util/virdnsmasq.h | 8
1 file changed, 8 deletions(-)
diff --git a/src/util/virdnsmasq.h b/src/util/virdnsmasq.h
index 92c5d4129d..9b8aeef226 100644
--- a/src/util/virdnsmasq.h
+++ b/src/util/virdnsmasq.h
@@
Delete the code that is only run without the capability.
Signed-off-by: Ján Tomko
---
src/network/bridge_driver.c | 134 +---
1 file changed, 19 insertions(+), 115 deletions(-)
diff --git a/src/network/bridge_driver.c b/src/network/bridge_driver.c
index
Remove the (now unreachable) error message and the macro.
Signed-off-by: Ján Tomko
---
src/network/bridge_driver.c | 14 --
src/util/virdnsmasq.h | 6 --
2 files changed, 20 deletions(-)
diff --git a/src/network/bridge_driver.c b/src/network/bridge_driver.c
index
Prepare to retire older versions by droping older tests.
Signed-off-by: Ján Tomko
---
.../networkxml2confdata/isolated-network.conf | 5 +--
.../nat-network-dns-srv-record-minimal.conf | 10 +++---
.../nat-network-dns-srv-record.conf | 2 ++
.../nat-network-dns-txt-record.conf
All the capabilities should be supported in 2.67.
Make this the minimum version, since even the oldest
distros we support have moved on:
Debian 8: 2.72
CentOS 7: 2.76
Ubuntu 18.04: 2.79
Signed-off-by: Ján Tomko
---
src/util/virdnsmasq.c | 13 +
1 file changed, 13 insertions(+)
Rename 'fail' to 'error' to match the prevalent usage.
Signed-off-by: Ján Tomko
---
src/util/virdnsmasq.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/util/virdnsmasq.c b/src/util/virdnsmasq.c
index b62e353ceb..90a1ea35b6 100644
--- a/src/util/virdnsmasq.c
+++
This bumps the minimum dnsmasq version to the point where we do not need
capability probing, reducing it to a version check (which I will be
happy to remove on request).
Unless I missed something, this also means we no longer need to spawn
radvd manually.
Note that DNSMASQ_CAPS_BINDTODEVICE was
On a Tuesday in 2021, Daniel P. Berrangé wrote:
These daemons do not have any support for unprivileged readonly
access, so we must not reference -ro.socket units in scripts.
Signed-off-by: Daniel P. Berrangé
---
libvirt.spec.in | 18 +++---
1 file changed, 11 insertions(+), 7
Previous patch neglected the possibility of different modes for hyperv
(e.g. "custom" and "passthrough").
Fixes: 6e83fafe331dd0b4fb19aa384c3dd36b3af62933
Signed-off-by: Tim Wiederhake
---
src/conf/domain_conf.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/src/conf/domain_conf.c
Signed-off-by: Tim Wiederhake
---
docs/formatdomain.rst | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index 0c5e33c78f..2e9c450606 100644
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -1929,7 +1929,14 @@
Spotted by Daniel. Patches were already merged though, hence this addendum.
Tim Wiederhake (2):
docs: domain: Clarify on the dangers of migrating with
hyperv-passthrough enabled
virDomainFeaturesHyperVDefParse: Compare hyperv mode
docs/formatdomain.rst | 9 -
These daemons do not have any support for unprivileged readonly
access, so we must not reference -ro.socket units in scripts.
Signed-off-by: Daniel P. Berrangé
---
libvirt.spec.in | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/libvirt.spec.in
And its callers. The parameter is no longer used since virDomainObjSave
was replaced with qemuDomainSaveStatus wrapper.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_domain.c | 3 +--
src/qemu/qemu_domain.h | 3 +--
src/qemu/qemu_driver.c | 14 +++---
src/qemu/qemu_process.c | 13
It is a nice wrapper around virDomainObjSave which logs a warning, but
otherwise ignores the error. Let's use it where appropriate.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_domain.c| 11 ++---
src/qemu/qemu_migration.c | 9 +
src/qemu/qemu_process.c | 85
Jiri Denemark (2):
qemu: Use qemuDomainSaveStatus
qemu: Drop driver parameter from qemuDomainSetFakeReboot
src/qemu/qemu_domain.c| 12 ++---
src/qemu/qemu_domain.h| 3 +-
src/qemu/qemu_driver.c| 14 +++---
src/qemu/qemu_migration.c | 9 +---
src/qemu/qemu_process.c | 98
On Tue, Dec 14, 2021 at 16:17:32 +, Daniel P. Berrangé wrote:
> Signed-off-by: Daniel P. Berrangé
> ---
> libvirt.spec.in | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libvirt.spec.in b/libvirt.spec.in
> index 32b4243d0a..97030be407 100644
> ---
Signed-off-by: Daniel P. Berrangé
---
libvirt.spec.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libvirt.spec.in b/libvirt.spec.in
index 32b4243d0a..97030be407 100644
--- a/libvirt.spec.in
+++ b/libvirt.spec.in
@@ -1297,7 +1297,7 @@ exit 0
%post daemon
This sev-guest object property indicates whether QEMU should
expose the kernel, ramdisk, cmdline hashes to the firmware
for measurement.
The 6.2.0 capabilities are selectively refreshed to pull in
the kernel-hashes parameter to the schema.
Signed-off-by: Daniel P. Berrangé
---
Set the kernel-hashes property on the sev-guest object if the config
asked for it explicitly. While QEMU machine types currently default to
having this setting off, it is not guaranteed to remain this way.
We can't assume that the QEMU capabilities were generated on an AMD host
with SEV, so we
Normally the SEV measurement only covers the firmware
loader contents. When doing a direct kernel boot, however,
with new enough OVMF it is possible to ask for the
measurement to cover the kernel, ramdisk and command line.
It can't be done automatically as that would break existing
guests using
This is the left over pieces from the rest fo the previous SEV
series. In this version I've changed the way we probe for
capabilities and also changed the way we set the capabilities
in the test suite so we don't rely on them being generated on
an AMD SEV host.
Daniel P. Berrangé (3):
conf: add
On Fri, Nov 26, 2021 at 03:34:56PM +0100, Tim Wiederhake wrote:
> Currently, this attribute may either have a value of "custom", or be absent
> (which defaults to "custom"), for backwards compatibility.
>
> Signed-off-by: Tim Wiederhake
> ---
> src/conf/domain_conf.c | 11 +--
>
On Fri, Nov 26, 2021 at 03:35:02PM +0100, Tim Wiederhake wrote:
> Signed-off-by: Tim Wiederhake
> ---
> docs/formatdomain.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
> index 95ef2e0d05..ec944f89db 100644
> ---
rebased to 359e9f5cf4526eff630d803f68df9733abaef419
Olaf Hering (3):
libvirt.spec: relocate pre script of daemon-driver-qemu
remove sysconfig files
NEWS: mention removal of sysconfig
NEWS.rst| 10 +++
docs/daemons.rst| 20 +
Signed-off-by: Olaf Hering
---
NEWS.rst | 10 ++
1 file changed, 10 insertions(+)
diff --git a/NEWS.rst b/NEWS.rst
index 4d1a1501ef..ce324afb8a 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -36,6 +36,16 @@ v8.0.0 (unreleased)
* **Improvements**
+ * packaging: sysconfig files no longer
Reduce the delta in an upcoming change.
No change in behavior intended.
Signed-off-by: Olaf Hering
---
libvirt.spec.in | 32 +++-
1 file changed, 15 insertions(+), 17 deletions(-)
diff --git a/libvirt.spec.in b/libvirt.spec.in
index 32b4243d0a..66eff7c7e8 100644
---
sysconfig files are owned by the admin of the host. They have the
liberty to put anything they want into these files. This makes it
difficult to provide different built-in defaults.
Remove the sysconfig file and place the current desired default into
the service file.
Local customizations can
Signed-off-by: Tim Wiederhake
---
docs/manpages/virsh.rst | 2 +-
src/qemu/qemu_domain.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/manpages/virsh.rst b/docs/manpages/virsh.rst
index 275f416090..265725d214 100644
--- a/docs/manpages/virsh.rst
+++
On 12/13/21 1:58 PM, Ján Tomko wrote:
Use two variables with automatic cleanup instead of reusing one.
Remove the pointless cleanup label.
Signed-off-by: Ján Tomko
---
src/util/virdnsmasq.c | 37 -
1 file changed, 16 insertions(+), 21 deletions(-)
diff
I've noticed these while reviewing a patch that touched this part of
code.
Michal Prívozník (2):
qemuxml2xmloutdata: Turn kvm-features.xml and kvm-features-off.xml
into symlinks
domain_conf: Use virXMLFormatElement*() more in
virDomainDefFormatFeatures()
src/conf/domain_conf.c
There's no real difference between input and output XMLs for
kvm-features and kvm-features-off test cases. Do what we usually
do in such case - turn the output file into a symlink of the
input file.
Signed-off-by: Michal Privoznik
---
tests/qemuxml2argvdata/kvm-features-off.xml | 7 +++-
There are few places in virDomainDefFormatFeatures() which can
use virXMLFormatElement() or virXMLFormatElementEmpty() instead
of writing directly into the output buffer.
After this, there are still a lot of places left, but that is
much bigger task.
Signed-off-by: Michal Privoznik
---
On Tue, Dec 14, 2021 at 11:44:00AM +0100, Peter Krempa wrote:
> On Fri, Dec 10, 2021 at 16:47:10 +, Daniel P. Berrangé wrote:
> > Different CPU generations have different limits on the number
> > of SEV/SEV-ES guests that can be run. Since both limits come
> > from the same overall set, there
On 12/14/21 20:21, Michal Prívozník wrote:
On 12/14/21 10:22, Michal Prívozník wrote:
On 11/23/21 15:36, huang...@chinatelecom.cn wrote:
From: Hyman Huang(黄勇)
Dirty ring feature was introduced in qemu-6.1.0, this patch
add the corresponding feature named 'dirty-ring', which enable
dirty
Ok, I will fix it.
Thank you!
> -Original Message-
> From: Ani Sinha
> Sent: Tuesday, December 14, 2021 2:54 PM
> To: Huang, Haibin
> Cc: libvir-list@redhat.com; Ding, Jian-feng ; Yang,
> Lin A ; Lu, Lianhao ; Zhong,
> Yang
> Subject: Re: [libvirt][PATCH v8 3/5] conf: Introduce SGX EPC
On 12/14/21 10:22, Michal Prívozník wrote:
> On 11/23/21 15:36, huang...@chinatelecom.cn wrote:
>> From: Hyman Huang(黄勇)
>>
>> Dirty ring feature was introduced in qemu-6.1.0, this patch
>> add the corresponding feature named 'dirty-ring', which enable
>> dirty ring feature when starting vm.
>>
On 12/13/21 19:58, Ján Tomko wrote:
> Fear not, the end is near.
>
> Ján Tomko (5):
> docs: use g_auto in virCommand example
> util: dnsmasq: refactor CapsRefresh
> util: iscsi: use two vars in CreateIfaceIQN
> util: refactor virNodeSuspendSetNodeWakeup
> util: use g_auto in
On 12/13/21 19:42, Ján Tomko wrote:
> TBD: docs/ and src/util
>
> Ján Tomko (20):
> openvz: refactor openvzExtractVersionInfo
> openvz: refactor openvzLoadDomains
> openvz: refactor openvzGetVEID
> openvz: refactor openvzDomainDefineCmd
> openvz: refactor openvzSetInitialConfig
>
On a Tuesday in 2021, Michal Privoznik wrote:
In future commits we will need to store not just an array of
VIR_TRISTATE_SWITCH_* but also an additional integer. Follow the
example of TCG and introduce a structure where both the array an
integer can live.
Signed-off-by: Michal Privoznik
---
On 12/14/21 12:20, Hyman Huang wrote:
>
> Ok, i'll rebase the master once the changes get merged and test if the
> dirty ring still works.
>
You can find all the patches applied in my branch:
https://gitlab.com/MichalPrivoznik/libvirt/-/commits/review/
Michal
On 12/14/21 17:22, Michal Prívozník wrote:
On 11/23/21 15:36, huang...@chinatelecom.cn wrote:
From: Hyman Huang(黄勇)
Dirty ring feature was introduced in qemu-6.1.0, this patch
add the corresponding feature named 'dirty-ring', which enable
dirty ring feature when starting vm.
To implement
https://gitlab.com/libvirt/libvirt/-/issues/255
Reported-by: Jeremy Alcim
Signed-off-by: Ján Tomko
---
Pushed as trivial.
examples/c/misc/hellolibvirt.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/examples/c/misc/hellolibvirt.c b/examples/c/misc/hellolibvirt.c
On Tue, Dec 14, 2021 at 12:08:37PM +0100, Peter Krempa wrote:
> On Fri, Dec 10, 2021 at 16:47:13 +, Daniel P. Berrangé wrote:
> > Set the kernel-hashes property on the sev-guest object if
> > the config asked for it explicitly. While QEMU machine
> > types currently default to having this
On Tue, Dec 14, 2021 at 12:04:17PM +0100, Peter Krempa wrote:
> On Fri, Dec 10, 2021 at 16:47:12 +, Daniel P. Berrangé wrote:
> > This sev-guest object property indicates whether QEMU should
> > expose the kernel, ramdisk, cmdline hashes to the firmware
> > for measurement.
> >
> > The 6.2.0
On Fri, Dec 10, 2021 at 16:47:13 +, Daniel P. Berrangé wrote:
> Set the kernel-hashes property on the sev-guest object if
> the config asked for it explicitly. While QEMU machine
> types currently default to having this setting off, it
> is not guaranteed to remain this way.
>
>
On Fri, Dec 10, 2021 at 16:47:12 +, Daniel P. Berrangé wrote:
> This sev-guest object property indicates whether QEMU should
> expose the kernel, ramdisk, cmdline hashes to the firmware
> for measurement.
>
> The 6.2.0 capabilities are hacked to look as if they were
> generated with sev-guest
On Fri, Dec 10, 2021 at 16:47:10 +, Daniel P. Berrangé wrote:
> Different CPU generations have different limits on the number
> of SEV/SEV-ES guests that can be run. Since both limits come
> from the same overall set, there is typically also BIOS config
> to set the tradeoff betweeen SEV and
On Fri, Dec 10, 2021 at 16:47:12 +, Daniel P. Berrangé wrote:
> This sev-guest object property indicates whether QEMU should
> expose the kernel, ramdisk, cmdline hashes to the firmware
> for measurement.
>
> The 6.2.0 capabilities are hacked to look as if they were
> generated with sev-guest
In future commits we will need to store not just an array of
VIR_TRISTATE_SWITCH_* but also an additional integer. Follow the
example of TCG and introduce a structure where both the array an
integer can live.
Signed-off-by: Michal Privoznik
---
src/conf/domain_conf.c | 20 +---
On 11/23/21 15:36, huang...@chinatelecom.cn wrote:
> From: Hyman Huang(黄勇)
>
> Dirty ring feature was introduced in qemu-6.1.0, this patch
> add the corresponding feature named 'dirty-ring', which enable
> dirty ring feature when starting vm.
>
> To implement the dirty-ring feature,
On Fri, Dec 10, 2021 at 16:47:09 +, Daniel P. Berrangé wrote:
> This will be needed directly in the QEMU driver in a later patch.
>
> Signed-off-by: Daniel P. Berrangé
> ---
> src/cpu/cpu_x86.c| 34 +--
> src/libvirt_private.syms | 1 +
> src/util/virhostcpu.c
On Tue, Dec 14, 2021 at 09:14:38 +, Daniel P. Berrangé wrote:
> On Tue, Dec 14, 2021 at 10:05:26AM +0100, Peter Krempa wrote:
> > On Mon, Dec 13, 2021 at 17:35:36 -0700, Jim Fehlig wrote:
> > > Since commit 46783e6307a, the 'virsh dominfo' command calls
> > > virDomainGetMessages to report any
On Tue, Dec 14, 2021 at 10:05:26AM +0100, Peter Krempa wrote:
> On Mon, Dec 13, 2021 at 17:35:36 -0700, Jim Fehlig wrote:
> > Since commit 46783e6307a, the 'virsh dominfo' command calls
> > virDomainGetMessages to report any messages from the domain.
> > Hypervisors not implementing the API now
On Tue, Dec 14, 2021 at 10:05:51 +0100, Peter Krempa wrote:
> On Mon, Dec 13, 2021 at 17:35:36 -0700, Jim Fehlig wrote:
> > Since commit 46783e6307a, the 'virsh dominfo' command calls
> > virDomainGetMessages to report any messages from the domain.
> > Hypervisors not implementing the API now get
On Mon, Dec 13, 2021 at 17:35:36 -0700, Jim Fehlig wrote:
> Since commit 46783e6307a, the 'virsh dominfo' command calls
> virDomainGetMessages to report any messages from the domain.
> Hypervisors not implementing the API now get the following
> log message when clients invoke 'virsh dominfo'
>
>
On 12/14/21 01:35, Jim Fehlig wrote:
> Since commit 46783e6307a, the 'virsh dominfo' command calls
> virDomainGetMessages to report any messages from the domain.
> Hypervisors not implementing the API now get the following
> log message when clients invoke 'virsh dominfo'
>
> this function is not
79 matches
Mail list logo
