similar to: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.

Compared to v3 this suggests: +Suggests: qemu-block-curl +Suggests: qemu-block-gluster +Suggests: qemu-block-iscsi +Suggests: qemu-block-rbd +Suggests: qemu-block-ssh which I missed in an earlier email from danpb.

On Friday, 10 January 2020 15:59:35 CET Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.

This gets rid of the various storage drivers. I believe we do not use type=volume, *except* on secrets. Rich.

On Fri, Jan 10, 2020 at 03:10:51PM +0100, Pino Toscano wrote: > On Friday, 10 January 2020 15:05:33 CET Richard W.M. Jones wrote: > > libguestfs usually needs qemu. However it only requires an emulator > > for the same architecture, not for all architectures. > > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > > architectures, as well as a bunch of

On Fri, Jan 10, 2020 at 02:05:33PM +0000, Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.

v3 adds libvirt-daemon-driver-storage-core too as a Recommends. Dan, there is a scratch build ongoing here: https://koji.fedoraproject.org/koji/taskinfo?taskID=40377285 Rich.

On Friday, 10 January 2020 15:05:33 CET Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. --- libguestfs.spec

On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > Do you use the libvirt "secret" APIs at all (disk encryption, network > disk auth passwords) ? If so you will need "libvirt-daemon-driver-secret" > too. How about any other libvirt sub-driver APIs ? Networking ? Host > dev, etc ? The full list of APIs we use is attached, assuming I got my

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. --- libguestfs.spec

On Friday, 10 January 2020 15:39:21 CET Daniel P. Berrangé wrote: > On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > > Do you use the libvirt "secret" APIs at all (disk encryption, network > > > disk auth passwords) ? If so you will need

On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > Do you use the libvirt "secret" APIs at all (disk encryption, network > > disk auth passwords) ? If so you will need "libvirt-daemon-driver-secret" > > too. How about any other libvirt sub-driver APIs ? Networking ?

On Fri, Jan 10, 2020 at 05:21:23PM +0100, Pino Toscano wrote: > On Friday, 10 January 2020 15:39:21 CET Daniel P. Berrangé wrote: > > On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > > > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > > > Do you use the libvirt "secret" APIs at all (disk encryption, network >

Hi, I try to define an iscsi pool with virsh but I always get the following error : error :internal error: missing backend for pool type 5 (iscsi) And yet libvirt was compiled with iscsi support : configure: Storage Drivers configure: configure: Dir: yes configure: FS: yes configure: NetFS: yes configure: LVM: yes configure: iSCSI: yes configure: SCSI: yes configure:

To all, I started the process of updating some of our systems from 7.5 to 7.6. Most of the servers had no problems, but several of the desktops had some difficulties. I was required to perform several yum commands to update as much as possible in the format of yum update a* then b* etc. Then after I got everything updated that would update in this manner and after the use of "rpm -Va

rhbz#:51422 --- ovirt-node.spec.in | 149 +++++++++------------------------------------------ 1 files changed, 27 insertions(+), 122 deletions(-) diff --git a/ovirt-node.spec.in b/ovirt-node.spec.in index 3138011..b4e660d 100644 --- a/ovirt-node.spec.in +++ b/ovirt-node.spec.in @@ -43,76 +43,23 @@ Requires: nc Requires: grub Requires: /usr/sbin/crond Requires: anyterm

On Friday, 10 January 2020 17:34:27 CET Daniel P. Berrangé wrote: > > > > virStoragePoolFree ( > > > > virStoragePoolGetInfo ( > > > > virStoragePoolLookupByName ( > > > > virStorageVolFree ( > > > > virStorageVolGetInfo ( > > > > virStorageVolGetPath ( > > > > virStorageVolLookupByName ( > > > > >

Hi, i have a two-node cluster running on SLES 12 with pacemaker. The cluster refused to start the domains on one node. So i took some of the domains out of the cluster and tried to start it manually. This is what happened: virsh # define /mnt/share/vm_documents-oo.xml error: Failed to define domain from /mnt/share/vm_documents-oo.xml error: cannot open /dev/null: Operation not permitted Same

Hi, When trying to attach a created volume to an instance using the virsh utility I am running into this error :- [] $ sudo virsh attach-device instance-00000015 disk.xml error: Failed to attach device from disk.xml error: internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk21' could not be initialized For experimental purpose I