On Thu, Sep 26, 2024 at 04:44:28PM -0400, Stefan Berger wrote:
>
>
> On 9/26/24 4:18 PM, Daniel P. Berrangé wrote:
> > On Thu, Sep 26, 2024 at 03:32:07PM -0400, Stefan Berger wrote:
> > > Add documentation for the TPM backend profile node and point the reader to
> > > further documentation about
I have just tagged v10.8.0-rc2 in the repository and pushed signed
tarballs to https://download.libvirt.org/
Please give the release candidate some testing and in case you find a
serious issue which should have a fix in the upcoming release, feel
free to reply to this thread to make sure the issue
Commit 0caacf47d7b423db9126660fb0382ed56cd077c1 recently
made it so the new path used for qemu-bridge-helper in Debian
would be allowed, but the logic used to actually figure out
the complete path for the helper was not updated accordingly.
https://bugs.debian.org/1082530
Signed-off-by: Andrea Bo
On Fri, Sep 27, 2024 at 10:22:34AM +0200, Peter Krempa wrote:
> On Fri, Sep 27, 2024 at 15:45:43 +0800, Han Han wrote:
> > It will be used for the property "intremap" of the device amd-iommu.
>
> Looking at the detected versions and the qemu code it seems that
> 'intremap' is supported for all qem
On Fri, Sep 27, 2024 at 03:45:41PM +0800, Han Han wrote:
> Here is a draft patch series for amd-iommu device. It will implement
> amd-iommu device and its attributes: intremap, device-iotlb, xtsup.
>
> However, its secret device AMDVI-PCI will occupy a PCIe slot and cause
> VM failed to start:
> D
Note that this is not a full review as I don't know how the iommu is
behaving/used so I can't comment on that.
On Fri, Sep 27, 2024 at 15:45:46 +0800, Han Han wrote:
> Fixes: https://issues.redhat.com/browse/RHEL-50560
Please describe in the commit message what/why you are doing. e.g. at
the v
On Fri, Sep 27, 2024 at 15:45:44 +0800, Han Han wrote:
> It will be used for the device-iotlb property of amd-iommu device.
Same as previous patch.
On Fri, Sep 27, 2024 at 15:45:43 +0800, Han Han wrote:
> It will be used for the property "intremap" of the device amd-iommu.
Looking at the detected versions and the qemu code it seems that
'intremap' is supported for all qemu versions and also it doesn't seem
to be able to be disabled.
Thus thi
Fixes: https://issues.redhat.com/browse/RHEL-50560
Signed-off-by: Han Han
---
docs/formatdomain.rst | 20 +-
src/conf/domain_conf.c| 16
src/conf/domain_conf.h| 2 +
src/conf/domain_validate.c
It will be used for the xtsup property of amd-iommu device.
Signed-off-by: Han Han
---
src/qemu/qemu_capabilities.c | 2 ++
src/qemu/qemu_capabilities.h | 1 +
tests/qemucapabilitiesdata/caps_9.0.0_x86_64.xml | 1 +
tests/qemucapabilitiesdata/caps_9.1.0_x8
It will be used for the device-iotlb property of amd-iommu device.
Signed-off-by: Han Han
---
src/qemu/qemu_capabilities.c | 2 ++
src/qemu/qemu_capabilities.h | 1 +
tests/qemucapabilitiesdata/caps_5.2.0_x86_64.xml | 1 +
tests/qemucapabilitie
It will be used for the property "intremap" of the device amd-iommu.
Signed-off-by: Han Han
---
src/qemu/qemu_capabilities.c | 8
src/qemu/qemu_capabilities.h | 1 +
tests/qemucapabilitiesdata/caps_5.2.0_x86_64.xml | 1 +
tests/qemucap
This qemu capability will be used for the device amd-iommu.
Signed-off-by: Han Han
---
src/qemu/qemu_capabilities.c | 4 +
src/qemu/qemu_capabilities.h | 3 +
.../caps_5.2.0_x86_64.replies | 90 +++--
.../caps_5.2.0_x86_64.xml
Here is a draft patch series for amd-iommu device. It will implement
amd-iommu device and its attributes: intremap, device-iotlb, xtsup.
However, its secret device AMDVI-PCI will occupy a PCIe slot and cause
VM failed to start:
Domain XML:
...
...
➜ ~ virsh create
When concluding a job with a 'mirror' we first unplugged the appropriate
no-longer used images from qemu and then updated the definition.
Normally this wouldn't be a problem because for any other thread this is
done under the VM lock thus atomic. Unfortunately though, the AppArmor
security backend
The 'disk->mirrorJob' and 'disk->mirrorState' fields need to be cleared
after a blockjob, but should be kept around while 'disk->mirror' is
still in place. As 'disk->mirror' is cleared only after conclusion of
the job in 'qemuBlockJobEventProcessConcluded()' we should be resetting
them only afterwa
Modify the ordering so that the VM definition stays in a state allowing
us to format a valid XML for the virt-aa-helper.
Peter Krempa (2):
qemu: blockjob: Update 'mirror' of a copy job before removing images
qemu: blockjob: Clean out disk mirror data after concluding the job
src/qemu/qemu_bl
Thomas Huth writes:
> According to https://marc.info/?l=fedora-devel-list&m=171934833215726
> the GlusterFS development effectively ended. Thus mark it as deprecated
> in QEMU, so we can remove it in a future release if the project does
> not gain momentum again.
>
> Acked-by: Niels de Vos
> Sig
18 matches
Mail list logo
