similar to: Do I need these?

Laine, you are right, some packages mixed: [root@openstack3 ~]# rpm -qa | grep '\(libvirt\|netcf\|libnl\)' | sort libnl-1.1.4-3.el7.x86_64 libnl3-3.2.21-7.el6.x86_64 libnl3-cli-3.2.21-7.el6.x86_64 libnl3-debuginfo-3.2.21-7.el6.x86_64 libnl-debuginfo-1.1.4-3.el7.x86_64 libnl-devel-1.1.4-3.el7.x86_64 libvirt-client-1.1.1-29.el7_0.3.x86_64 libvirt-daemon-1.1.1-29.el7_0.3.x86_64

Hi all, I looked at patching oVirt Server to work with the latest Matahari schema, from Matahari's 'next' branch, version 0.4.0. ovirt-server depends on matahari version 0.0.5, which is currently latest in Fedora, and it is used during Node registration, to enumerate hardware information. Usage extracted from src/host-browser/host-register.rb is as follows: host_list =

On 03/11/15 19:32, Ned Slider wrote: > > > On 11/03/15 23:24, Mark LaPierre wrote: >> Hey Y'all, >> >> I'm looking at ZCad: >> http://sourceforge.net/projects/zcad/?source=directory >> >> It looks like the kind of 3D CAD package that I've been looking for. It >> says that it works on Linux but it's zipped with 7-Zip which

Hey all, I've installed MuseScore on my C6.6 machine. MuseScore is able to generate a midi sounding playback through the speakers of the active score. I want to capture that sound directly to a file without using a microphone. I want to send individual sound files to each of the members of my quartet with their part only. Does anyone know how I can capture sound directly to a file? Is

Hi All, I have one netcf question, please help me to resolve it, thanks. I can set a IFF_RUNNING flag to a bridge device which are no interface device attached. What status of a flag on a bridge device in current kernel?(w/o interface), is this a new change in kernel or other component? In netcf, but there is a patch to fix that flag issue, I can't understand it. fix wrong status of

Hi All, I have a usage question about netcf. Why netcf can not rename a existing physical interface dynamically by itself? If you have any other method, please share to me, or can we add support for it in netcf? You can see the following steps for details. Version: netcf-0.2.4-1.el6.x86_64 kernel-2.6.32-431.el6.x86_64 1. Select a existing NIC from host, for example eth1. [root@rhel6 ~]# ncftool

Hey all, I'm trying to install the fedora-packager group so that I can build Fedora source packages into RPMs that I can install. I'm getting this error: Error: Package: fedora-packager-0.6.0.1-1.el6.noarch (epel) Requires: python-yubico <SNIP> [root at peach ~]# yum install python-yubico <SNIP> No package python-yubico available. Do you suppose that maybe this

Hi Martin: Actually, I have installed all the debuginfo for this coredump file. But the netcf debuginfo report "mismatch" as below: warning: the debug information found in "/usr/lib/debug/usr/lib64/libnetcf.so.1.4.0.debug" does not match "/lib64/libnetcf.so.1" (CRC mismatch). So I ignore this warning before. You can check what I did on the attachment

On 01/10/17 13:12, Tony Schreiner wrote: > On Tue, Jan 10, 2017 at 11:12 AM, Mark LaPierre <marklapier at gmail.com> > wrote: > >> Hey all, I'm trying to install the fedora-packager group so that I can >> build Fedora source packages into RPMs that I can install. I'm getting >> this error: >> >> Error: Package:

On 28.05.2014 15:27, Laine Stump wrote: > On 05/27/2014 09:07 AM, Jianwei Hu wrote: >> Hi All, >> >> I have one netcf question, please help me to resolve it, thanks. >> >> I can set a IFF_RUNNING flag to a bridge device which are no interface device attached. What status of a flag on a bridge device in current kernel?(w/o interface), is this a new change in kernel

On 05/23/2014 04:56 PM, Laine Stump wrote: > On 05/23/2014 06:46 AM, Jianwei Hu wrote: >> Hi All, >> >> I have a usage question about netcf. Why netcf can not rename a existing physical interface dynamically by itself? > The name of a physical interface is determined by lower levels of the > operating system, and can't be modified by netcf. the configuration that

Hi, I have a working fc14 install with a few virtual interfaces set up, and just noticed the following in messages: Apr 18 13:07:43 fc14 libvirtd: 13:07:43.155: error : interfaceGetXMLDesc:355 : internal error could not get interface XML description (netcf: NETLINK socket operation failed - couldn't find ifindex for interface `br0:0`) Apr 18 13:07:43 fc14 libvirtd: 13:07:43.165: error :

On 03/26/2015 05:31 AM, 梅磊 wrote: > Hi Martin: > Actually, I have installed all the debuginfo for this coredump file. But the netcf debuginfo report "mismatch" as below: > warning: the debug information found in "/usr/lib/debug/usr/lib64/libnetcf.so.1.4.0.debug" does not match "/lib64/libnetcf.so.1" (CRC mismatch). > > So I ignore this warning before.

Hello Facing below error while trying to access the iface-list. # virsh iface-list *error: Failed to list active interfaces error: this function is not supported by the connection driver: virConnectNumOfInterfaces* root at kvm-1:/usr/local/src/libvirt# virsh list Id Name State ---------------------------------------------------- 1 vm1

On 10 February 2015 at 10:08, Kahlil Hodgson <kahlil.hodgson at dealmax.com.au> wrote: > I think you can simply submit a bug report under fedora documentation. Via bugzilla: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Documentation

On my CenOS7 system with stunnel from base stunnel-4.56-4.el7.x86_64 there's a systemd service file /etc/systemd/system/stunnel.service try sudo systemctl enable stunnel.service Hope this helps, K ?al?

Actually, I know what the MAC is for the builtin Port1 and 2. Those are listed in the BIOS. But ultimately I don't want to rely on them as I want the same kickstart file to work for other machines, so hardcoding those in the kickstart file wouldn't quite work, unless I start writing multiple kickstart files, one per machine. Anyway, lspci reports this: 00:19.0 Ethernet controller: Intel

On 10 February 2015 at 10:15, PatrickD Garvey <patrickdgarveyt at gmail.com> wrote: > Please allow me to make sure I am perceiving this correctly, > reports of errors found in RedHat documentation are to be reported > against the Fedora Documentation product type in the RedHat bugzilla? > and > reports of errors found in Fedora documentation are, also, to be > reported

Right, I understand that part. However I believe I'm now in the realm of making this specific to this machine as I have no guarantee that another identical machine will pop up with those same bus IDs. Maybe for the internal ports, but I don't know if the same will happen for the PCIe bus. Would that be correct? On Thu, May 14, 2015 at 6:21 PM, Kahlil Hodgson < kahlil.hodgson at

Hi, I'm trying to install the newest version of libvirt and libvirt-client from the rpms at ftp://libvirt.org/libvirt/ on a Fedora 14 machine. The naming of the rpms as "libvirt-0.9.4-1.fc14.x86_64.rpm" suggests that this is exactly the system this was made for, however, installation still does not go smoothly. When I try to install these packages with yum install