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

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.

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.

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. I also made support

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.

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: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.

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: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.

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

Hi all, I'm trying to install libvirt for xen on a brand new, minimal installation of CentOS 7.5.1804. After installing the OS, I did a 'yum update' and followed the basic how-tos at https://wiki.centos.org/HowTos/Xen/Xen4QuickStart and https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt From previous experience, I know that the above steps worked fine. However,

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

I have a Dell T430 with CentOS 7 kernel release: 3.18.41-20.el7.x86_64 and xen_version : 4.6.3-3.el7 I am doing an update of my server, but it fails:- yum update ================================================================================= Error: Package: libvirt-daemon-driver-libxl-1.3.0-1.el7.x86_64 (@centos-virt-xen) Requires: libvirt-daemon = 1.3.0-1.el7 Removing:

Anyone have an idea of what may have happened or how to fix? I'm only seeing this issue after the OS update to CentOS 7.3. Thanks PJ On Sat, Dec 24, 2016 at 10:19 AM, PJ Welsh <pjwelsh at gmail.com> wrote: > I'v also got this issue when trying to update my CentOS 7.3 systems. I did > see a new user request that mentioned beginning to help with libvrit 2.0 > and/or 2.5

PJ My server is critical to me, but not the public, fortunately. I can take it down as I suggested, but am a bit reluctant to do so until I have heard more opinions. Presumably your system update failed using your script, so it will probably fail for me if I copy it. I will keep a copy anyway. ----- Original Message ----- > From: "PJ Welsh" <pjwelsh at gmail.com> > To:

The man page for libguestfs says: export LIBGUESTFS_BACKEND_SETTINGS=force_tcg will force the direct and libvirt backends to use TCG (software emulation) instead of KVM (hardware accelerated virtualization). However, our application has many services (run by different users) which make use of libguestfs tools, and it is painful to have to set this environment variable for each script and

Dear Jean-Marc, Thank you for replying. I Installed CentOS 7 and centos-virt from the normal repos (CentOS-Xen) in December 2015 and have not had to build anything. I am running CentOS 7, not sure if it has automatically updated itself to 7.3, so I would expect the updates to come from the repo, and not need building from source. Regards Francis ----- Original Message ----- > From:

Hi all, I would like to rebuild a kmod.src.rpm package for a specific kernel. When I try to do it, this message appears: Building target platforms: i686 Building for target i686 error: Failed build dependencies: kernel-xen-devel-i686 = 2.6.18-98.el5 is needed by mymodule-kmod-0.1.5-2.i686 kernel-PAE-devel-i686 = 2.6.18-98.el5 is needed by mymodule-kmod-0.1.5-2.i686. Is

Are there any RPM wizards out there that know how to specify a different architecture for a subpackage in a spec file? I have a package that has a binary component and a non-binary component that I would like split into 2 packages one, the binary which is architecture dependant and the other 'noarch'. I haven't found a spec file that does this yet :-( Ross S. W. Walker

On 2018/02/16 12:12 pm, Daniel P. Berrangé wrote: > On Fri, Feb 16, 2018 at 11:59:42AM -0500, Andre Goree wrote: >> I'm trying to determine if it's possible to edit/attach/apply nwfilter >> rules >> at runtime? I.e., after a VM is already running, can I apply a >> nwfilter to >> the VM and have it work without rebooting the machine? Thus far, I've

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