On 12/11/24 5:37 AM, marcandre.lur...@redhat.com wrote:
From: Marc-André Lureau
This reverts commit bb5e26749fe5b5856a3541be2cbe147701e6e121.
swtpm-setup doesn't have "tpmstate-lock", only swtpm.
Signed-off-by: Marc-André Lureau
Reviewed-by: Stefan Berger
---
src/qemu/qemu_tpm.c
On 12/11/24 5:37 AM, marcandre.lur...@redhat.com wrote:
From: Marc-André Lureau
When the vTPM source path is specified, such as:
Do not delete the parent directory, but only the given file/dir.
Fixes: commit f1304cc566 ("qemu_tpm: handle file/block storage source")
Signed-off-by: Mar
On Wed, Dec 11, 2024 at 09:46:49 +0100, Ján Tomko wrote:
> If we do not have a persistent definition, there's no point in
> looking for it since we cannot store it.
>
> Also skip the update if the tpm device(s) in the persistent
> definition are different.
>
> This fixes the crash when starting a
On 12/11/24 3:46 AM, Ján Tomko wrote:
If we do not have a persistent definition, there's no point in
looking for it since we cannot store it.
Also skip the update if the tpm device(s) in the persistent
definition are different.
This fixes the crash when starting a transient domain.
https://
On 12/11/2024 1:10 AM, Purna Pavan Chandra Aekkaladevi wrote:
On Tue, Dec 10, 2024 at 10:28:41AM -0600, Praveen K Paladugu wrote:
On 12/2/2024 3:46 AM, Purna Pavan Chandra Aekkaladevi wrote:
Implement `chReadProcessEvents` and `chProcessEvents` to read events from
event monitor FIFO file a
On Wed, Dec 11, 2024 at 09:46:49 +0100, Ján Tomko wrote:
> If we do not have a persistent definition, there's no point in
> looking for it since we cannot store it.
>
> Also skip the update if the tpm device(s) in the persistent
> definition are different.
>
> This fixes the crash when starting a
From: Marc-André Lureau
This reverts commit bb5e26749fe5b5856a3541be2cbe147701e6e121.
swtpm-setup doesn't have "tpmstate-lock", only swtpm.
Signed-off-by: Marc-André Lureau
---
src/qemu/qemu_tpm.c | 11 ++-
src/util/virtpm.c | 1 -
src/util/virtpm.h | 1 -
tests/testutilsq
From: Marc-André Lureau
Commit bb5e26749fe5b ("qemu: explicit swtpm state locking") attempted to
lock the state, but only for swtpm-setup. The capability
"tpmstate-opt-lock" is actually only exposed by swtpm.
Signed-off-by: Marc-André Lureau
Reviewed-by: Stefan Berger
---
src/qemu/qemu_tpm.c
From: Marc-André Lureau
When the vTPM source path is specified, such as:
Do not delete the parent directory, but only the given file/dir.
Fixes: commit f1304cc566 ("qemu_tpm: handle file/block storage source")
Signed-off-by: Marc-André Lureau
---
src/qemu/qemu_tpm.c | 26
On Tue, Dec 10, 2024 at 13:28:44 -0500, Stefan Berger wrote:
>
>
> On 12/10/24 10:50 AM, Jiri Denemark wrote:
> > On Tue, Dec 10, 2024 at 15:01:16 +0100, Ján Tomko wrote:
> >> If we do not have a persistent definition, there's no point in
> >> looking for it since we cannot store it.
> >>
> >> Al
If we do not have a persistent definition, there's no point in
looking for it since we cannot store it.
Also skip the update if the tpm device(s) in the persistent
definition are different.
This fixes the crash when starting a transient domain.
https://issues.redhat.com/browse/RHEL-69774
Fixes:
Hi Team,
Can we fix all unfixed version numbers and submit new patch v7, or can we wait
till the reviews are complete?
Thanks & Regards,
Harikumar R
Add support for parsing "nestedSmmuv3" devices from the VM definition. When a
"nestedSmmuv3" IOMMU model is parsed from the VM definition, add a
"nestedSmmuv3" device to the VM definition for each host SMMU node detected from
sysfs. Specify the associated host SMMU sysfs filename as the "name" attr
Implement a sub-test in qemuxmlconftest that mocks the scanning of sysfs to
determine how many "nestedSmmuv3" devices to assign to the VM when
"nestedSmmuv3" IOMMU model is parsed from the VM definition. Add a VM
definition example with an associated qemu command line that exercises the
detection o
Hi,
This is a draft solution for supporting multiple vSMMU instances in a qemu VM.
Based on discussions/suggestions received for a previous RFC by Nicolin here[0],
the association of vSMMUs to VFIO devices in VM PCIe topology should be moved
out of qemu into libvirt. In addition, the nested SMMU
Add a pcie-expander-bus controller to the VM definition for each "nestedSmmuv3"
device that is generated when the "nestedSmmuv3" IOMMU model is parsed from the
VM definition. Assign each "nestedSmmuv3" device to one PXB controller, and
route any unmanaged "hostdev" VFIO devices with associated host
Update the PXB controller busNrs to account for devices we attached in the
previous commit, ensuring there are enough VM bus numbers to be assigned for
each device attached downstream from each PXB controller.
Signed-off-by: Nathan Chen
---
src/qemu/qemu_domain_address.c | 52 +++
Add support for specifying "nestedSmmuv3" as the IOMMU model. In the following
commits, when the "nestedSmmuv3" IOMMU model is parsed from the VM definition,
PXB controllers and "nestedSmmuv3" devices will be auto-added to the VM
definition and VFIO devices will be routed to PXB controllers based o
This patch series includes the changes needed to
support POWER11 cpu and POWER11 host on libvirt.
Patch also adds and updates the qemu caps with
the latest qemu for the caps tests to include POWER11.
Patch 0001: Add POWER11 cpu model support.
Patch 0002: Add POWER11 host model support.
Patch 0003:
This changes will add POWER11 host-model support to libvirt.
Signed-off-by: Narayana Murty N
---
src/cpu/cpu_ppc64.c | 8
tests/qemuxmlconftest.c | 4
tests/testutilshostcpus.h | 11 +++
tests/testutilsqemu.c | 4
tests/testutilsqemu.h | 1 +
5 file
Add POWER11 as a supported cpu model for ppc64.
Signed-off-by: Narayana Murty N
---
src/cpu_map/index.xml | 1 +
src/cpu_map/meson.build | 1 +
src/cpu_map/ppc64_POWER11.xml | 6 ++
3 files changed, 8 insertions(+)
create mode 100644 src/cpu_map/ppc64_POWER11.xml
diff --git a
21 matches
Mail list logo
