Re: [PATCH] rpm: re-enable ppc64 on RHEL-8

2021-05-14 Thread Neal Gompa
On Fri, May 14, 2021 at 8:24 AM Andrea Bolognani wrote: > > On Fri, May 14, 2021 at 12:57:24PM +0100, Daniel P. Berrangé wrote: > > Historically PowerPC 64 was always supported with qemu-kvm in RHEL. > > > > In future RHEL-9 it is being discontinued and this was addressed > > in > > > > commit

Re: [PATCH] rpm: disable glusterfs on RHEL-9

2021-05-14 Thread Neal Gompa
On Fri, May 14, 2021 at 8:27 AM Andrea Bolognani wrote: > > On Fri, May 14, 2021 at 12:58:09PM +0100, Daniel P. Berrangé wrote: > > Support for glusterfs with KVM is being dropped in RHEL-9 in the > > virtualization stack. > > > > Signed-off-by: Daniel P. Berrangé > > --- > > libvirt.spec.in |

Re: [PATCH v2 3/3] qapi: deprecate drive-backup

2021-05-14 Thread John Snow
On 5/6/21 5:57 AM, Kashyap Chamarthy wrote: TODO: We also need to deprecate drive-backup transaction action.. But union members in QAPI doesn't support 'deprecated' feature. I tried to dig a bit, but failed :/ Markus, could you please help with it? At least by advice? Oho, I see. OK, I'm not

[libvirt PATCH 3/4] tests: nodedevxml2xmltest: test more mdev files

2021-05-14 Thread Jonathon Jongsma
Add the rest of the mdev xml files to the xml2xml test, and include 2 new test cases: one that explicitly specifies 'manual' start, and one that explicitly specifies 'auto' start. Signed-off-by: Jonathon Jongsma --- tests/nodedevschemadata/mdev_autostart.xml| 10 ++

[libvirt PATCH 4/4] docs: nodedev: document mdev uuid property

2021-05-14 Thread Jonathon Jongsma
Signed-off-by: Jonathon Jongsma --- docs/formatnode.html.in | 4 1 file changed, 4 insertions(+) diff --git a/docs/formatnode.html.in b/docs/formatnode.html.in index 3065570405..9a505f0fe9 100644 --- a/docs/formatnode.html.in +++ b/docs/formatnode.html.in @@ -384,6 +384,10 @@

[libvirt PATCH 2/4] nodedev: support auto-start property for mdevs

2021-05-14 Thread Jonathon Jongsma
From: Boris Fiuczynski This adds a new element to the mdev capabilities xml schema that represents the start policy for a defined mediated device. The actual auto-start functionality is handled behind the scenes by mdevctl, but it wasn't yet hooked up in libvirt. Signed-off-by: Boris Fiuczynski

[libvirt PATCH 1/4] test: move nodedev xml2xml output to a separate dir

2021-05-14 Thread Jonathon Jongsma
Currently, we're loading and parsing the xml from the input file, and then formatting it and then comparing it directly back to the input file. This works for now, but is severely limiting as it relies on the input file being fully-specified and in the exact order as the output xml format. If

[libvirt PATCH 0/4] Support autostart for mediated devices

2021-05-14 Thread Jonathon Jongsma
This is a short patch series based on an initial patch from Boris Fiuczynski that I massaged a little bit and added a few additional patches. This allows you to define mediated devices in libvirt which are started automatically at boot or parent device plugin. Boris Fiuczynski (1): nodedev:

Re: [PATCH v2 2/3] docs/interop/bitmaps: use blockdev-backup

2021-05-14 Thread John Snow
On 5/5/21 9:58 AM, Vladimir Sementsov-Ogievskiy wrote: We are going to deprecate drive-backup, so use modern interface here. In examples where target image creation is shown, show blockdev-add as well. If target creation omitted, omit blockdev-add as well. Signed-off-by: Vladimir

Re: [PATCH v2 1/3] docs/block-replication: use blockdev-backup

2021-05-14 Thread John Snow
On 5/5/21 9:58 AM, Vladimir Sementsov-Ogievskiy wrote: We are going to deprecate drive-backup, so don't mention it here. Moreover, blockdev-backup seems more correct in the context. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: John Snow --- docs/block-replication.txt | 4

Re: [libvirt PATCH v2 0/6] Refactor more XML parsing boilerplate code, part X

2021-05-14 Thread Laine Stump
On 5/13/21 11:31 AM, Tim Wiederhake wrote: For background, see https://listman.redhat.com/archives/libvir-list/2021-April/msg00668.html Changes since V1: * Split up VIR_FREE'd and reused ´g_autofree xmlNodePtr *´ variables. Tim Wiederhake (6): virNodeDeviceDefParseXML: Use g_auto*

Re: How to hot plugin a new vhost-user-blk-pci device to running VM?

2021-05-14 Thread Michal Prívozník
On 5/14/21 8:33 AM, Liang Chaojun wrote: > > > Thanks,I have tried qemu monitor as below. I used chardev_add to add a > chardev and used device_add it to running vm. But i often hit a issue and > cause the vm crash. qemu-system-x86_64: ../hw/virtio/vhost.c:1566: > vhost_dev_get_config:

Re: [PATCH] rpm: disable glusterfs on RHEL-9

2021-05-14 Thread Andrea Bolognani
On Fri, May 14, 2021 at 12:58:09PM +0100, Daniel P. Berrangé wrote: > Support for glusterfs with KVM is being dropped in RHEL-9 in the > virtualization stack. > > Signed-off-by: Daniel P. Berrangé > --- > libvirt.spec.in | 11 --- > 1 file changed, 8 insertions(+), 3 deletions(-) > >

Re: [PATCH] rpm: re-enable ppc64 on RHEL-8

2021-05-14 Thread Andrea Bolognani
On Fri, May 14, 2021 at 12:57:24PM +0100, Daniel P. Berrangé wrote: > Historically PowerPC 64 was always supported with qemu-kvm in RHEL. > > In future RHEL-9 it is being discontinued and this was addressed > in > > commit 03cc3c9064322ac4028a2213105cd230fe28c013 > Author: Jiri Denemark >

[PATCH] rpm: disable glusterfs on RHEL-9

2021-05-14 Thread Daniel P . Berrangé
Support for glusterfs with KVM is being dropped in RHEL-9 in the virtualization stack. Signed-off-by: Daniel P. Berrangé --- libvirt.spec.in | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/libvirt.spec.in b/libvirt.spec.in index 8ac324be0a..c52f607bd1 100644 ---

[PATCH] rpm: re-enable ppc64 on RHEL-8

2021-05-14 Thread Daniel P . Berrangé
Historically PowerPC 64 was always supported with qemu-kvm in RHEL. In future RHEL-9 it is being discontinued and this was addressed in commit 03cc3c9064322ac4028a2213105cd230fe28c013 Author: Jiri Denemark Date: Wed Apr 21 14:55:03 2021 +0200 spec: Do not build qemu driver for

[libvirt PATCH] meson: Add yajl kludge

2021-05-14 Thread Andrea Bolognani
If this looks familiar, that's because it's literally *the same code* that we used to work around *the same issue* in readline before 1635dca26f61def3fbf56c70fbbfe514f2b50987 :) Note that the issue only really affects people building from source on Apple Silicon: on Intel, Homebrew installs

Re: How to hot plugin a new vhost-user-blk-pci device to running VM?

2021-05-14 Thread Liang Chaojun
Thanks,I have tried qemu monitor as below. I used chardev_add to add a chardev and used device_add it to running vm. But i often hit a issue and cause the vm crash. qemu-system-x86_64: ../hw/virtio/vhost.c:1566: vhost_dev_get_config: Assertion `hdev->vhost_ops' failed. virsh

Re: How to hot plugin a new vhost-user-blk-pci device to running VM?

2021-05-14 Thread Peter Krempa
On Fri, May 14, 2021 at 14:33:37 +0800, Liang Chaojun wrote: > > > Thanks,I have tried qemu monitor as below. I used chardev_add to add a > chardev and used device_add it to running vm. But i often hit a issue and > cause the vm crash. qemu-system-x86_64: ../hw/virtio/vhost.c:1566: >

Re: How to hot plugin a new vhost-user-blk-pci device to running VM?

2021-05-14 Thread Liang Chaojun
Thanks,I have tried qemu monitor as below. I used chardev_add to add a chardev and used device_add it to running vm. But i often hit a issue and cause the vm crash. qemu-system-x86_64: ../hw/virtio/vhost.c:1566: vhost_dev_get_config: Assertion `hdev->vhost_ops' failed. virsh