To allow pass-through devices receiving ACPI notifications, permit to
register ACPI notify handler (via VFIO_DEVICE_SET_IRQS) for a given
device. The handler role is to receive and propagate such ACPI
notifications to the user-space through the user provided eventfd. This
allows VMM to receive and
On Wed, May 10, 2023 at 03:08:37PM +0200, Andrea Bolognani wrote:
> It's not used as part of the build process or searched for at
> build time, and the QEMU driver detects its path at runtime,
> so one could think that the BuildRequires is unnecessary. But
> we actually need it to be present at
On Mon, May 22, 2023 at 11:55:15AM +0200, Cornelia Huck wrote:
> On Wed, May 17 2023, Andrea Bolognani wrote:
> > Migration is of course the most obvious failure scenario, but one of
> > the critical features offered by libvirt is guest ABI compatibility.
> >
> > If the user needs MTE3
Polite ping.
On 5/8/23 7:10 PM, Boris Fiuczynski wrote:
Instead of updating defined mdevs only add another update for active
devices as well to cover transient mdev devices as well.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2143158
Signed-off-by: Boris Fiuczynski
---
On Mon, May 22, 2023 at 11:53:45AM +0200, Michal Privoznik wrote:
We already check that there's no when
is set. But we are missing the opposite
check: there's when there is .
Even though the logic is inverted in here it is correct both in the
patch and in the commit messages, so for the
We are getting close to the next release of libvirt. To aim for the
release on Jun 01 I suggest entering the freeze on Friday May 26 and
tagging RC2 on Tuesday May 30.
I hope this works for everyone.
Jirka
On Wed, May 17 2023, Andrea Bolognani wrote:
> On Wed, May 17, 2023 at 11:19:17AM +0200, Cornelia Huck wrote:
>> This has been through some iterations... we (as in people working on
>> this in QEMU) need to decide on where to go with cpu features, cpu
>> models, etc. on Arm, but for now, it's a
When parsing a we also check whether the @mode
argument fulfills some requirements wrt 'restrictive' mode. This
is not the right place though. There's virDomainNumaDefValidate()
which contains other checks.
Signed-off-by: Michal Privoznik
---
src/conf/numa_conf.c | 16
1 file
We already do check that if there's
then all have to be of 'restrictive' mode too. But
what we are missing the reverse: if there is with
'restrictive' mode, then the has to be of the same mode
too.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2208946
Signed-off-by: Michal Privoznik
We already check that there's no when
is set. But we are missing the opposite
check: there's when there is .
Michal Prívozník (3):
virDomainNumatuneNodeSpecified: Fix const correctness
numa_conf: Move memnode mode validation into
virDomainNumaDefValidate()
numa_conf: Deny other
The virDomainNumatuneNodeSpecified() function does not write into
passed @numatune pointer, it just reads from it. Therefore, the
argument should be const, which allows this function to be called
from places where virDomainNuma is already const (e.g. domain
validation code).
Signed-off-by: Michal
On Mon, May 22 2023, Andrea Bolognani wrote:
> See the subthread starting at [1] for the rationale. The QEMU commit
> that (temporarily) reverted KVM support is at [2].
>
> [1] https://listman.redhat.com/archives/libvir-list/2023-May/239911.html
> [2]
>
On a Monday in 2023, Andrea Bolognani wrote:
See the subthread starting at [1] for the rationale. The QEMU commit
that (temporarily) reverted KVM support is at [2].
[1] https://listman.redhat.com/archives/libvir-list/2023-May/239911.html
[2]
The QEMU interface is still in a state of flux, and KVM support
has been pulled shortly after having been merged. Let's not
commit to a stable interface in libvirt just yet.
Reverts: 720e8f13ff71377580cd37b118cee8a1f982d1d8
Signed-off-by: Andrea Bolognani
---
docs/formatdomain.rst
The QEMU interface is still in a state of flux, and KVM support
has been pulled shortly after having been merged. Let's not
commit to a stable interface in libvirt just yet.
Reverts: 1347a19f75a23b4d92e6a7b549fcde52b23f0258
Signed-off-by: Andrea Bolognani
---
src/qemu/qemu_capabilities.c
The QEMU interface is still in a state of flux, and KVM support
has been pulled shortly after having been merged. Let's not
commit to a stable interface in libvirt just yet.
Reverts: c6c9b5d251de215ed378aa0bc31daa2e1170409e
Signed-off-by: Andrea Bolognani
---
src/qemu/qemu_validate.c | 25
See the subthread starting at [1] for the rationale. The QEMU commit
that (temporarily) reverted KVM support is at [2].
[1] https://listman.redhat.com/archives/libvir-list/2023-May/239911.html
[2]
https://gitlab.com/qemu-project/qemu/-/commit/d009607d08d22f91ca399b72828c6693855e7325
Andrea
The QEMU interface is still in a state of flux, and KVM support
has been pulled shortly after having been merged. Let's not
commit to a stable interface in libvirt just yet.
Reverts: b10bc8f7ab6f9986ccc54ba04fc5b3bad7576be6
Signed-off-by: Andrea Bolognani
---
src/qemu/qemu_command.c
18 matches
Mail list logo
