Re: [PATCH] rpc: report error from filing to add timer

s/filing/failing/ in the summary line :-) On 7/22/24 10:56 AM, Daniel P. Berrangé wrote: Signed-off-by: Daniel P. Berrangé --- src/rpc/virnetclientstream.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/rpc/virnetclientstream.c b/src/rpc/virnetclientstream.c index 98034d737d..380b

Re: cpugroups for hyperv hypervisor

On 7/9/2024 2:43 PM, Daniel P. Berrangé wrote: On Wed, Jun 26, 2024 at 09:18:37AM -0500, Praveen K Paladugu wrote: Hey folks, My team is working on exposing `cpugroups` to Libvirt while using 'hyperv' hypervisor with cloud-hypervisor(VMM). cpugroups are relevant in a specific configuration o

[PATCH] rpc: report error from filing to add timer

Signed-off-by: Daniel P. Berrangé --- src/rpc/virnetclientstream.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/rpc/virnetclientstream.c b/src/rpc/virnetclientstream.c index 98034d737d..380b785869 100644 --- a/src/rpc/virnetclientstream.c +++ b/src/rpc/virnetclientstream.c @@ -725,6

Re: [PATCH] conf: virtiofs: add rlimit_nofile element

On Tue, Jul 16, 2024 at 11:40:36AM +0200, Adam Julis wrote: > Add an element to configure the rlimit nofile size: > > ... > > > I think this XML design is sub-optimal in a number of ways * "rlimit" is an implementation detail which is something we hide from XML generally * "nofile" is

Re: [PATCH v2 1/1] Expose available AMD SEV models in domain capabilities

On 2/20/24 07:31, Takashi Kajinami wrote: > This introduces the new "model" field in sev elements, returned by > domain capabilities API, so that client can ensure SEV-ES is available > in this hypervisor. > > Signed-off-by: Takashi Kajinami > --- > docs/formatdomaincaps.rst | 5 ++ > src/

Re: [PATCH 0/2] Add Granite Rapids cpu model

On 7/18/24 15:27, Tim Wiederhake wrote: > Also, update the sync tool with new features introduced in qemu. > > Tim Wiederhake (2): > sync_qemu_models_i386.py: Add missing features > cpu_map: Add GraniteRapids CPU model > > src/cpu_map/index.xml | 1 + > src/cpu_map/

Re: [PATCH] cpu_map: Add libcpuinfo as optional data source

On 6/21/24 15:24, Tim Wiederhake wrote: > This adds an option to use libcpuinfo [1] as data source for > libvirt's list of x86 cpu features. This is purely optional and > does not change the script's behavior if libcpuinfo is not > installed. > > libcpuinfo is a cross-vendor, cross-architecture so

[PATCH 5/5] NEWS: Document pstore device addition

Signed-off-by: Michal Privoznik --- NEWS.rst | 7 +++ 1 file changed, 7 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 2fdb52c607..d31fa15867 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -19,6 +19,13 @@ v10.6.0 (unreleased) * qemu: Add support for the 'pauth' Arm CPU feature + * Int

[PATCH 4/5] security: Set seclabels for pstore device

The acpi-erst backend for pstore device exposes a path in the host accessible to the guest and as such we must set seclabels on it to grant QEMU RW access. Signed-off-by: Michal Privoznik --- src/security/security_dac.c | 10 ++ src/security/security_selinux.c | 9 + src/sec

[PATCH 2/5] conf: Introduce pstore device

The aim of pstore device is to provide a bit of NVRAM storage for guest kernel to record oops/panic logs just before the it crashes. Typical usage includes usage in combination with a watchdog so that the logs can be inspected after the watchdog rebooted the machine. While Linux kernel (and possibl

[PATCH 3/5] qemu: Build cmd line for pstore device

Nothing special going on here. Resolves: https://issues.redhat.com/browse/RHEL-24746 Signed-off-by: Michal Privoznik --- src/qemu/qemu_alias.c | 10 src/qemu/qemu_command.c | 51 +++ .../pstore-acpi-erst.x86_64-latest.args

[PATCH 1/5] qemu_capabilities: Introduce QEMU_CAPS_DEVICE_ACPI_ERST

This capability tracks whether QEMU has acpi-erst device. Signed-off-by: Michal Privoznik --- src/qemu/qemu_capabilities.c | 2 ++ src/qemu/qemu_capabilities.h | 1 + tests/qemucapabilitiesdata/caps_7.0.0_aarch64+hvf.xml | 1 + tests/qemucapabili

[PATCH RESEND 0/5] Introduce pstore device

This is a rebased version of: https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/UAUKLOCOYOYSUBF5DCCYCCDCLAZDEQHJ/ which was a rebased version of: https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/VWR67LTU4Z5TQHDWVTPEVOGIS53FTJYK/ Let's hope no more rese

Re: [PATCH v3] qemu: add a monitor to /proc/$pid when killing times out

On Mon, Jul 22, 2024 at 10:55:05 +0200, Michal Prívozník wrote: > On 7/19/24 17:44, Boris Fiuczynski wrote: > > In cases when a QEMU process takes longer than the time sigterm and > > sigkill are issued to kill the process do not simply fail and leave the > > VM in state VIR_DOMAIN_SHUTDOWN until t

Plans for 10.6.0 release (freeze on Monday 29 Jul)

We are getting close to 10.6.0 release of libvirt. Since I'll be away from computers next week, I suggest moving the "last week in a month" freeze a bit and aim for the release on Monday 05 Aug after entering the freeze on Monday 29 Jul. There will be no RC2 this time. I hope this works for everyo

Re: [PATCH v3] qemu: add a monitor to /proc/$pid when killing times out

On 7/22/24 10:55 AM, Michal Prívozník wrote: On 7/19/24 17:44, Boris Fiuczynski wrote: In cases when a QEMU process takes longer than the time sigterm and sigkill are issued to kill the process do not simply fail and leave the VM in state VIR_DOMAIN_SHUTDOWN until the daemon stops. Instead set u

Re: [PATCH v3] qemu: add a monitor to /proc/$pid when killing times out

On 7/19/24 17:44, Boris Fiuczynski wrote: > In cases when a QEMU process takes longer than the time sigterm and > sigkill are issued to kill the process do not simply fail and leave the > VM in state VIR_DOMAIN_SHUTDOWN until the daemon stops. Instead set up > an fd on /proc/$pid and get notified w