From: Hyman Huang(黄勇)
Implement qemuMonitorQueryVcpuDirtyLimit which query vcpu
dirty limit info by calling qmp 'query-vcpu-dirty-limit'.
Signed-off-by: Hyman Huang(黄勇)
---
src/qemu/qemu_monitor.c | 12 +++
src/qemu/qemu_monitor.h | 17 ++
src/qemu/qemu_monitor_json.c | 6
From: Hyman Huang(黄勇)
Implement qemuDomainSetVcpuDirtyLimit, which can be used to
set or cancel the upper limit of the dirty page rate for
virtual CPUs.
Signed-off-by: Hyman Huang(黄勇)
---
src/qemu/qemu_driver.c | 131 +++
src/qemu/qemu_monitor.c | 13
From: Hyman Huang(黄勇)
Extend dirtylimit statistics for domGetStats to display the
information of the upper limit of dirty page rate for
virtual CPUs.
Signed-off-by: Hyman Huang(黄勇)
---
include/libvirt/libvirt-domain.h | 1 +
src/libvirt-domain.c | 9 ++
src/qemu/qemu_driver.c
From: Hyman Huang(黄勇)
Introduce limit-dirty-page-rate virsh api to set or cancel
dirty page rate upper limit for virtual CPUs.
Usage is below:
$ virsh limit-dirty-page-rate --rate \
[--vcpu ] [--config] [--live] [--current]
Set the dirty page rate upper limit for the given vcpu
specified by
From: Hyman Huang(黄勇)
Introduce command 'virsh domstats --dirtylimit' for reporting dirty
page rate upper limit (megabyte/s) infomation. The info is listed as
follows:
Domain: 'vm'
dirtylimit.vcpu.0.limit=10
dirtylimit.vcpu.0.current=16
dirtylimit.vcpu.1.limit=10
dirtylimit.vcpu.1.curren
From: Hyman Huang(黄勇)
Export virDomainDefHasDirtyLimitStartupVcpus as a util function,
which could be used in qemu_process.c file for the next commit.
Signed-off-by: Hyman Huang(黄勇)
---
src/conf/domain_validate.c | 2 +-
src/conf/domain_validate.h | 2 ++
src/libvirt_private.syms | 1 +
3 fi
From: Hyman Huang(黄勇)
Introduce virDomainSetVcpuDirtyLimit API to set or cancel the
dirty page rate upper limit.
The API will throttle the virtual CPU as needed to keep their dirty
page rate within the limit. Since it just throttles the virtual CPU,
which dirties memory, read processes in the gu
From: Hyman Huang(黄勇)
The dirty_limit attribute in XML requires setting up the
upper limit of dirty page rate once after launching the
VM, so add the implementation.
Signed-off-by: Hyman Huang(黄勇)
---
src/qemu/qemu_process.c | 44 +
1 file changed, 44 in
From: Hyman Huang(黄勇)
The upper limit (megabyte/s) of the dirty page rate configured
by the user can be tracked by the XML. To allow this, add the
following XML:
...
3
...
The "dirty_limit" attribute in "vcpu" sub-element within "vcpus"
element allows to set an upper limi
From: Hyman Huang(黄勇)
set-vcpu-dirty-limit/cancel-vcpu-dirty-limit/query-vcpu-dirty-limit
were introduced since qemu >=7.1.0. Introduce corresponding
capability.
Signed-off-by: Hyman Huang(黄勇)
---
src/qemu/qemu_capabilities.c | 2 ++
src/qemu/qemu_capabilities.h
Hi, This is the latest version for the series, please review.
Thanks,
Yong
v3:
- rebase on master and fix conflicts
- refactor the comments and update the version tag
v2:
The patch set introduce a new API virDomainSetVcpuDirtyLimit to
allow upper Apps to set upper limits of dirty page rate for v
Refactor the version processing logic in ch driver to support versions
from non-release cloud-hypervisor binaries. This version also supports
versions with branch prefixes in them.
Signed-off-by: Praveen K Paladugu
---
src/ch/ch_conf.c | 39 ---
1 file changed
On a Tuesday in 2023, Peter Krempa wrote:
This series converts all outstanding test cases to use real
capabilities.
In the process few cases of pointless tests or features which are
supported by every version of qemu were identified and addressed.
To simplify the bulk of the conversion I've opt
s/node/note/ in the commit summary
On a Tuesday in 2023, Peter Krempa wrote:
'virQEMUCapsAddCPUDefinitions' is used solely to populate fake cpu
models for the fake-caps tests. Note that and also populate the 'type'
field so that default cpu type can be propagated properly.
Signed-off-by: Peter
On a Tuesday in 2023, Peter Krempa wrote:
Use the modern infrastructure to populate capabilities cache with real
capabilities instead of the faked one which will be soon removed.
Signed-off-by: Peter Krempa
---
tests/securityselinuxlabeltest.c | 11 +--
1 file changed, 5 insertions(+), 6
Use the modern infrastructure to populate capabilities cache with real
capabilities instead of the faked one which will be soon removed.
Signed-off-by: Peter Krempa
---
tests/securityselinuxlabeltest.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/tests/security
On Tue, Sep 05, 2023 at 16:23:27 +0200, Peter Krempa wrote:
> This series converts all outstanding test cases to use real
> capabilities.
>
> In the process few cases of pointless tests or features which are
> supported by every version of qemu were identified and addressed.
>
> To simplify the b
Move the 'smp-dies' test case into 'cpu-topology4' and remove
unnecessary cruft.
Remove cpu definition from 'cpu-topology2' as it's not relevant to the
test case.
Remove 'smp' case as it's covered by the rest.
Use real capabilities for all of them.
Signed-off-by: Peter Krempa
---
args =>
Signed-off-by: Peter Krempa
---
tests/testutilsqemu.c | 2 +-
tests/testutilsqemu.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/tests/testutilsqemu.c b/tests/testutilsqemu.c
index 05b28699c8..bb3e1b52c5 100644
--- a/tests/testutilsqemu.c
+++ b/tests/testutilsqemu.c
@@ -10
It's no longer needed in tests as we are no longer adding fake machines.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 2 +-
src/qemu/qemu_capspriv.h | 14 --
2 files changed, 1 insertion(+), 15 deletions(-)
diff --git a/src/qemu/qemu_capabilities.c b/src/qemu/
To minimize further churn when coverting to real capabilities, assume
that all fake-caps machines support the piix3 USB controller.
Since we already have solid testing of USB controllers, this will have
effect only in cases when it's not relevant to the test itself.
Signed-off-by: Peter Krempa
-
The function was used only to fill the cpu models into fake
capabilities, whic no longer exists.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 40
src/qemu/qemu_capabilities.h | 5 -
2 files changed, 45 deletions(-)
diff --git a/src/qem
Use proper version for negative case of 'hugepages-memaccess3'
QEMU allowed to configure a memory backend for default ram since
qemu-5.2. Fix the test to use real capability data.
Signed-off-by: Peter Krempa
---
...rr => hugepages-default-1G-nodeset-2M.x86_64-latest.err} | 0
...id.err => hugep
Now that all tests were converted to use real capabilities we can drop
x86_64 from the tooling to create fake capabilities.
Signed-off-by: Peter Krempa
---
tests/testutilsqemu.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/tests/testutilsqemu.c b/tests/testutilsqemu
In order to minimize further churn, make all fake-caps test assume that
the seccomp sandbox is supported.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvdata/acpi-table.args | 1 +
tests/qemuxml2argvdata/autoindex.args | 1 +
tests/qemuxml2ar
The status XML doesn't require any capabilities to be parsed and
formatted back. Remove all qemuCaps related code.
Signed-off-by: Peter Krempa
---
tests/qemustatusxml2xmltest.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/tests/qemustatusxml2xmltest.c b/
Modernize test cases using 'host-mode' cpu type, where the actual CPU
doesn't isn't important.
As using the host cpu from the 'latest' capabilities data would cause
test churn in case the host cpu changes in the future, convert them
using the overriden Haswell cpu.
Signed-off-by: Peter Krempa
--
Now that all fake-caps testing was removed we can also remove the
filling of the fake caps by cpu models.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 49
1 file changed, 49 deletions(-)
diff --git a/tests/qemuxml2argvtest.c b/tests/qemuxml
Few tests were invoked multiple times either with identical or
equivalent config. Remove those invocations.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/tests/qemuxml2argvtest.c b/tests/qemuxml2argvtest.c
index 92ff7e4b1c..8709028
'virQEMUCapsAddCPUDefinitions' is used solely to populate fake cpu
models for the fake-caps tests. Note that and also populate the 'type'
field so that default cpu type can be propagated properly.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 4
1 file changed, 4 insertions
Assume the two features modern qemus have to bring the test data closer
to the 'latest' real-caps versions.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvdata/controller-order.args | 2 +-
tests/qemuxml2argvdata/pcie-expander-bus.args| 2 ++
tests/qemuxml2argvdata/pci
Use real capabilities, but select the fake 'Haswell' host CPU for test
stability.
Signed-off-by: Peter Krempa
---
.../{cpu-minimum1.args => cpu-minimum1.x86_64-latest.args}| 2 +-
.../{cpu-minimum2.args => cpu-minimum2.x86_64-latest.args}| 2 +-
tests/qemuxml2argvtest.c
Use the fake Haswell processor definition and augment the list of
features to make the test pass.
Signed-off-by: Peter Krempa
---
...u-strict1.args => cpu-strict1.x86_64-latest.args} | 2 +-
tests/qemuxml2argvdata/cpu-strict1.xml | 12 +++-
tests/qemuxml2argvtest.c
Improve testing of an explicitly requested USB controller without a
model being provided.
For this purpose the 'usb-controller' case is renamed to
'usb-controller-default-i440fx'; 'usb-controller-default-q35' is moved
up to form a group. In both cases tests are covnerted to use
DO_TEST_CAPS_LATEST
Use real capabilities, but select the fake 'Haswell' host CPU for test
stability.
Signed-off-by: Peter Krempa
---
.../{cpu-exact1.args => cpu-exact1.x86_64-latest.args}| 0
...back.args => cpu-exact2-nofallback.x86_64-latest.args} | 0
.../{cpu-exact2.args => cpu-exact2.x86_64-latest.args}
The 'numatune-memory' case is completely dropped as it's sufficiently
covered by 'numatune-memnode'.
The positive fake-caps version of 'numatune-memnode' is dropped as it's
covered by the two existing real caps invocations.
'numatune-memory-invalid-nodeset', 'numatune-memnode-invalid-mode',
'numa
Modernize all test cases which set 'Haswell' as the host cpu model.
Signed-off-by: Peter Krempa
---
...X.args => cpu-Haswell-noTSX.x86_64-latest.args} | 0
...Haswell.args => cpu-Haswell.x86_64-latest.args} | 0
...swell2.args => cpu-Haswell2.x86_64-latest.args} | 0
...swell3.args => cpu-Has
Assume the features modern qemus have to bring the test data closer
to the 'latest' real-caps versions.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvdata/graphics-sdl.args| 2 +-
tests/qemuxml2argvdata/pcie-root-port.args | 2 +-
tests/qemuxml2argvdata/pcie-swit
Remove all the code for adding fake machines into the testing capability
cache as we no longer have any machines in it.
Signed-off-by: Peter Krempa
---
tests/testutilsqemu.c | 144 +++---
1 file changed, 9 insertions(+), 135 deletions(-)
diff --git a/tests/te
Assume the support for the 'pcie-root-port' all modern qemus have to
bring the test data closer to the 'latest' real-caps versions.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvdata/autoindex.args| 2 +-
tests/qemuxml2argvdata/pcie-expander-bus.args| 2 +-
te
There are per-machine type variations on which usb controller will be
picked on an x86_64 machine. Add test cases where a USB controller is
completely missing to cover all 3 cases ('isapc', 'pc', 'q35') when an
USB controller is not explicitly requested by the user.
Signed-off-by: Peter Krempa
--
Since qemu-8.0 a new way to disable 'hpet' via -machine was added.
Properly test both branches with real capabilities.
Signed-off-by: Peter Krempa
---
.../clock-hpet-off.x86_64-7.2.0.args | 39 +++
...args => clock-hpet-off.x86_64-latest.args} | 4 +-
tests/qemuxml2argv
Previously without modern capabilities the test was relying on a CPU
model which was not entered into a fake list of supported cpus.
With real capabilities we have to pick a CPU model which is supported by
libvirt but in some version is not supported by qemu. I've picked
EPYC-Milan, which was intr
As these were using DO_TEST_FULL the churn-reducing patches didn't
influence these.
Signed-off-by: Peter Krempa
---
...migrate-numa-unaligned.x86_64-latest.args} | 13 +++
...igrate.args => migrate.x86_64-latest.args} | 9 ++---
args => restore-v2-fd.x86_64-latest.args} | 11 +++---
...
The rest of the test cases has no change in the output now that we've
assumed some flags.
Remove the fake-caps test macros after conversion.
Signed-off-by: Peter Krempa
---
...fx-ide-address-conflict.x86_64-latest.err} | 0
...err => 440fx-wrong-root.x86_64-latest.err} | 0
...ble.args => a
Rename the 'usb-controller-explicit-(unavailable-)q35' test case to
'usb-controller-nec-xhci'. Since this also covers what
'usb-controller-xhci' was testing the latter is removed.
Other 'usb-xhci' test cases which were using the NEC controller are also
renamed to contain the name.
In case of 'usb
Remove the notion of legacy cpus as there are no test cases using it any
more.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 27 +--
tests/testutilsqemu.h| 5 ++---
2 files changed, 7 insertions(+), 25 deletions(-)
diff --git a/tests/qemuxml2argvtest.c
Move all controller related tests together and consolidate naming of the
test cases.
Signed-off-by: Peter Krempa
---
...gs => usb-controller-ich9-autoassign.args} | 0
...xml => usb-controller-ich9-autoassign.xml} | 0
...rgs => usb-controller-ich9-companion.args} | 0
xml => usb-controll
All tests have already a real capability variant.
Signed-off-by: Peter Krempa
---
.../qemuxml2argvdata/console-compat-auto.args | 36 ---
.../console-compat-chardev.args | 36 ---
tests/qemuxml2argvdata/console-compat.args| 35 --
.../paralle
Assume the two features modern qemus have to bring the test data closer
to the 'latest' real-caps versions.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvdata/cpu-cache-disable.args | 2 +-
tests/qemuxml2argvdata/cpu-cache-emulate-l3.args | 2 +-
tests/qemuxml2ar
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 3 +--
src/qemu/qemu_capabilities.h | 2 +-
tests/qemucapabilitiesdata/caps_4.2.0_aarch64.xml | 1 -
tests/qemucapabilitiesdata/caps_4.2.0_ppc64.xml | 1 -
tests/qemucapabili
Drop tests which already are tested with real caps, thus the fake caps
version doesn't bring much value.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvdata/cpu-host-model.args| 40 ---
.../graphics-egl-headless.args| 33 ---
tests/qemuxml2argvt
Similarly to 'cpu-host-model' add a real capability invocation for each
version we support and remove the old fake caps invocation.
Signed-off-by: Peter Krempa
---
...cpu-host-model-fallback.x86_64-4.2.0.args} | 7 ++--
.../cpu-host-model-fallback.x86_64-5.0.0.args | 33 ++
.../
Change DO_TEST_GIC so that it accepts the version and switch it to use
DO_TEST_CAPS_ARCH_VER_FULL internally which will ensure that the output
filenames conform to the format we use for real capabilities.
This also allows us to convert a few of versioned tests to use this
improved macro.
Signed-o
The 'display' option for the 'vfio-pci' device was added in qemu-2.12
and can't be compiled out. Assume support for the flag.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_domain.c | 11 ---
src/qemu/qemu_validate.c| 6 --
tes
All supported qemu versions have this feature and it can't be compiled
out. The logic is a bit more complex in this instance as the flag is
asserted if:
if (ARCH_IS_X86(qemuCaps->arch) &&
virQEMUCapsGet(qemuCaps, QEMU_CAPS_QUERY_CPU_MODEL_EXPANSION)) {
virQEMUCapsSet(qemuCaps,
Similarly to 'cpu-host-model' add a real capability invocation for each
version we support and remove the old fake caps invocation.
Signed-off-by: Peter Krempa
---
.../cpu-host-model-nofallback.err | 1 -
...pu-host-model-nofallback.x86_64-4.2.0.args | 33 ++
...pu-h
The feature is supported since qemu-5.1. Use real qemu-5.0 caps for the
test.
Signed-off-by: Peter Krempa
---
...rtio-options-memballoon-freepage-reporting.x86_64-5.0.0.err} | 0
tests/qemuxml2argvtest.c| 2 +-
2 files changed, 1 insertion(+), 1 deletion(-
QMP monitor is the only thing we support at this point, thus all other
tests test the same thing.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvdata/monitor-json.args | 34
tests/qemuxml2argvdata/monitor-json.xml | 25 -
tests/qemuxml2argvtest.c
At this point only x86_64 is using fake machines, and for real machines
we don't populate the fake cpu models. Thus we can remove everything
non-x86_64.
Signed-off-by: Peter Krempa
---
tests/qemuxml2argvtest.c | 30 --
1 file changed, 30 deletions(-)
diff --git a/tes
We've forgot to add test invocations with real caps for qemu versions
starting with 6.2.
Signed-off-by: Peter Krempa
---
.../cpu-host-model.x86_64-6.2.0.args | 39 +++
.../cpu-host-model.x86_64-7.0.0.args | 39 +++
.../cpu-host-model.x86_64-7.1.0
If a test uses ARG_CAPS_HOST_CPU_MODEL feature we override the global
host cpu model to the selected CPU but don't clear it afterwards. This
can trip up fake caps tests following a test which uses this feature.
This does not happen with real caps, because unless overriden, the host
cpu from capabi
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 7 +--
src/qemu/qemu_capabilities.h | 2 +-
tests/qemucapabilitiesdata/caps_4.2.0_x86_64.xml | 1 -
tests/qemucapabilitiesdata/caps_5.0.0_x86_64.xml | 1 -
tests/qemucapabili
Internally the preferred machine which is 'pc' for x86_64 must be kept
in the first place in the array of machines. This was not the case when
stripping the machine aliases for use in tests (so that test output
stays stable) where we've created a new entry for the alias. This means
that the origina
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 12
src/qemu/qemu_capabilities.h | 8
tests/qemucapabilitiesdata/caps_4.2.0_x86_64.xml | 4
tests/qemucapabilitiesdata/caps_5.0.0_x86_64.xml | 4 ---
The support for PIIX power management was added in qemu commit
v1.0-3094-g459ae5ea5a and the suport for ICH9 power management was added
in qemu commit v2.2.0-542-g6ac0d8d44c and both can't be compiled out.
This means we can always assume support for these features. Remove the
validation and imposs
This series converts all outstanding test cases to use real
capabilities.
In the process few cases of pointless tests or features which are
supported by every version of qemu were identified and addressed.
To simplify the bulk of the conversion I've opted to simply set the most
common capabilitie
On a Tuesday in 2023, Michal Privoznik wrote:
The sole purpose of getDeviceType() is to parse a file that
contains one integer (and a newline character). Well, we already
have a function for that: virFileReadValueInt(). Use the latter
and drop the former.
Signed-off-by: Michal Privoznik
---
src
The sole purpose of getDeviceType() is to parse a file that
contains one integer (and a newline character). Well, we already
have a function for that: virFileReadValueInt(). Use the latter
and drop the former.
Signed-off-by: Michal Privoznik
---
src/storage/storage_util.c | 75 --
On a Tuesday in 2023, Michal Privoznik wrote:
*** BLURB HERE ***
Michal Prívozník (3):
ch: Use uint for @maxvcpus in virCHDomainRefreshThreadInfo()
ch: Use int for @niothreads in virCHMonitorGetIOThreads()
ch: Use proper format directive for @i in virCHProcessSetupIOThreads()
src/ch/ch_domai
The @i variable inside of virCHProcessSetupIOThreads() is a
typical loop counter - it's declared as size_t. But when passed
to VIR_DEBUG an invalid format directive is used (%ld). Fix that.
Signed-off-by: Michal Privoznik
---
src/ch/ch_process.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
The @maxvcpus variable inside of virCHDomainRefreshThreadInfo()
holds retval of virDomainDefGetVcpusMax() which returns an
unsigned int. Also, the variable is then passed to VIR_WARN()
with incorrect format directive (%ld). Switch variable to uint
and fix the format directive.
Signed-off-by: Micha
The @niothreads inside of virCHMonitorGetIOThreads() is declared
as of size_t type. This would work, except the variable is then
passed to VIR_DEBUG with incorrect format directive (%ld) and
returned. But the function returns an int not size_t. Fix the
variable declaration and format directive.
S
*** BLURB HERE ***
Michal Prívozník (3):
ch: Use uint for @maxvcpus in virCHDomainRefreshThreadInfo()
ch: Use int for @niothreads in virCHMonitorGetIOThreads()
ch: Use proper format directive for @i in virCHProcessSetupIOThreads()
src/ch/ch_domain.c | 4 ++--
src/ch/ch_monitor.c | 4 ++--
On Mon, Sep 04, 2023 at 02:44:48PM +0300, Dmitry Frolov wrote:
Reviewing the sources, I noticed that, argumets order in
virCgroupGetMemoryStat() function call does not correspond
to the function declaration:
-instead of *activeAnon, &meminfo->inactive_anon is passed;
-instead of *inactiveAnon,
On Tue, Sep 5, 2023 at 6:22 PM Martin Kletzander
wrote:
> Sorry for not looking into this earlier, but it's been quite a while and
> I, personally, received only patches 2, 6, 5, 9, and 10 from this
> series. I, however, see the rest in the archive, so the issue is
> probably somewhere on my par
Sorry for not looking into this earlier, but it's been quite a while and
I, personally, received only patches 2, 6, 5, 9, and 10 from this
series. I, however, see the rest in the archive, so the issue is
probably somewhere on my part.
Would you mind resending the second version again, ideally re
On Tue, Sep 05, 2023 at 11:05:17 +0200, Michal Prívozník wrote:
> On 9/5/23 09:43, Peter Krempa wrote:
> > On Mon, Sep 04, 2023 at 16:09:00 +0200, Michal Prívozník wrote:
> >> On 8/30/23 13:59, Peter Krempa wrote:
> >>> After recent cleanups we can now restrict the maximum stack frame size
> >>> to
On 9/5/23 09:43, Peter Krempa wrote:
> On Mon, Sep 04, 2023 at 16:09:00 +0200, Michal Prívozník wrote:
>> On 8/30/23 13:59, Peter Krempa wrote:
>>> After recent cleanups we can now restrict the maximum stack frame size
>>> to 2k.
>>>
>>> Signed-off-by: Peter Krempa
>>> ---
>>> meson.build | 2 +-
Reviewing the sources, I noticed that, argumets order in
virCgroupGetMemoryStat() function call does not correspond
to the function declaration:
-instead of *activeAnon, &meminfo->inactive_anon is passed;
-instead of *inactiveAnon, &meminfo->active_anon is passed;
-instead of *activeFile, &me
On Tue, Sep 05, 2023 at 09:43:47AM +0200, Peter Krempa wrote:
> On Mon, Sep 04, 2023 at 16:09:00 +0200, Michal Prívozník wrote:
> > On 8/30/23 13:59, Peter Krempa wrote:
> > > After recent cleanups we can now restrict the maximum stack frame size
> > > to 2k.
> > >
> > > Signed-off-by: Peter Kremp
On Thu, Aug 31, 2023 at 16:40:06 -0500, Jonathon Jongsma wrote:
> Change the return value for qemuNbdkitProcessRestart() and
> qemuNbdkitStorageSourceManageProcess() to return an error status. The
> main effect of this change is that when libvirt starts up and reconnects
> to an already-running dom
On Thu, Aug 31, 2023 at 16:40:05 -0500, Jonathon Jongsma wrote:
> Adds the ability to monitor the nbdkit process so that we can take
> action in case the child exits unexpectedly.
>
> When the nbdkit process exits, we pause the vm, restart nbdkit, and then
> resume the vm. This allows the vm to co
On Thu, Aug 31, 2023 at 16:40:04 -0500, Jonathon Jongsma wrote:
> Since the restart handler will trigger at an arbitrary time (when the
> nbdkit process crashes, for instance), it's difficult to provide
> feedback to the user if the restart is unsuccessful. Rather than just
> relying on a warning i
On Tue, Sep 05, 2023 at 09:00:45 +0200, Philipp Hahn wrote:
> Hello,
>
> "pip install libvirt-python" does not work in several cases as that requires
> the low-level C library, compilers, tools, and Python header files to be
> installed. This prevents the use of "libvirt" in scenarios, where "root
On Mon, Sep 04, 2023 at 16:09:00 +0200, Michal Prívozník wrote:
> On 8/30/23 13:59, Peter Krempa wrote:
> > After recent cleanups we can now restrict the maximum stack frame size
> > to 2k.
> >
> > Signed-off-by: Peter Krempa
> > ---
> > meson.build | 2 +-
> > 1 file changed, 1 insertion(+), 1
Hello,
"pip install libvirt-python" does not work in several cases as that
requires the low-level C library, compilers, tools, and Python header
files to be installed. This prevents the use of "libvirt" in scenarios,
where "root" privileges are not available to install these dependencies,
e.g
87 matches
Mail list logo
