similar to: New push candidate with feedback from apevec...

This patch goes with the node patch just sent, and is ready for pushing upstream. I'll be doing the blacklisting in a later patch once this is upstream.

The purpose of this patch is to add the matahari qmf agent package (http://git.et.redhat.com/?p=matahari.git;a=summary) to the node image. Matahari is a qmf agent that publishes hardware information to an amqp broker, replacing functionality from ovirt-identify-node. However, since the capability is not ovirt specific, the agent is maintained as a separate project (see link above). Dependencies

The following patches introduce support for multipath and cciss devices to the ovirt-node and node-image. Comments are appreciated. These patches assume that the 3 patches (2 node, 1 node-image) from Joey are all incorporated. Mike

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Removed ks files, now in ovirt-node-recipe, which is subpackage of ovirt-node. Removed tools, these are now in ovirt-node-recipe which is subpackage of ovirt-node.

Unable to boot using qemu-kvm and gPXE from virt-preview repository https://bugzilla.redhat.com/show_bug.cgi?id=512358 Signed-off-by: Alan Pevec <apevec at redhat.com> --- common-blacklist.ks | 9 +++++++++ common-pkgs.ks | 3 +++ 2 files changed, 12 insertions(+), 0 deletions(-) diff --git a/common-blacklist.ks b/common-blacklist.ks index 7c19aa4..2f8842f 100644 ---

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Moves tools and kickstart files form ovirt-node-image to subpackage ovirt-node-recipe. Removes old sub packages form ovirt-node, stateless, logos, selinux. Modifies init scripts to meet Fedora packaging guidelines: added status, reload, and lockfile, rhbz: 514221 Added License file.

Hi, Two doubts. 1. What I've to replace in "NEEDED"? or I need to just run the whole command you given 2. You mean this one, rpm -qa | grep libguestfs* On Mon, Mar 16, 2015 at 5:35 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sat, Mar 14, 2015 at 11:14:55PM +0530, Thirumalai Nambi wrote: > > Thanks for your update, > > > > I got the

Move all the dependencies with the same name in all the distributions to a single list at the end. There should be no change to the package list used to build the p2v ISO. --- p2v/dependencies.m4 | 72 ++++++++++++++++------------------------------------- 1 file changed, 21 insertions(+), 51 deletions(-) diff --git a/p2v/dependencies.m4 b/p2v/dependencies.m4 index 21541b4..e590f57 100644 ---

Hi, > BTW: is there a tool (or pciutils patch) which can decode the virtio > capabilities? Searched for a patch today, and all google found me was this mail asking for one :-o So I went ahead and coded one up. Attached. While hacking it up I've noticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ...

Hi, > BTW: is there a tool (or pciutils patch) which can decode the virtio > capabilities? Searched for a patch today, and all google found me was this mail asking for one :-o So I went ahead and coded one up. Attached. While hacking it up I've noticed spec doesn't match reality. The "Virtio Structure PCI Capabilities" section here ...

Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure out what I am doing wrong. This is the script I wrote that I am running on a brand new install from ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 59

virtio uses vendor-specific capabilities to specify the location of the virtio register ranges. The specification can be found here: http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 This patch adds support for decoding these capabilities to lspci. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- Makefile | 2 +- ls-caps-vendor.c | 59

Hi, So the 'modules.pcimap' file, needed by Hardware Detection Tool to display kernel modules, is now missing. pciutils/kmod deprecated usage of this file adn depmod lost its -m option. So here are may questions: 1- How to generate a "modules.pcimap" or an equivalent file nowadays? 2- Is it still needed by HDT ? 3- What if it is missing, is HDT semi-broken? Thanks.

On Thu, Jan 15, 2015 at 10:18:18PM +0100, Gerd Hoffmann wrote: > Hi, > > > QEMU side is still undergoing polishing, but is already testable. > > Looked art the qemu side for now, commenting here due to qemu patches > not being posted to the list yet (guess that is at least partly already > on your todo list): Absolutely. > * Both legacy and modern should be

On Thu, Jan 15, 2015 at 10:18:18PM +0100, Gerd Hoffmann wrote: > Hi, > > > QEMU side is still undergoing polishing, but is already testable. > > Looked art the qemu side for now, commenting here due to qemu patches > not being posted to the list yet (guess that is at least partly already > on your todo list): Absolutely. > * Both legacy and modern should be

Hello! > virtio uses vendor-specific capabilities to specify the location of > the virtio register ranges. The specification can be found here: > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > This patch adds support for decoding these capabilities to lspci. I like the patch, except for a couple of details: (1) Please follow the

Hello! > virtio uses vendor-specific capabilities to specify the location of > the virtio register ranges. The specification can be found here: > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > This patch adds support for decoding these capabilities to lspci. I like the patch, except for a couple of details: (1) Please follow the

Hi all, Who can tell me how to install xen4.0.1 from source on centos5.4? I cannot find the yum repositories for the version of 4.0.1. Best Wishes Qiang Ma _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

libtool-2.2.6-15.5.el6.x86_64 upstart-0.6.5-13.el6_5.3.x86_64 atmel-firmware-1.3-7.el6.noarch redhat-rpm-config-9.0.3-42.el6.centos.noarch plymouth-scripts-0.8.3-27.el6.centos.1.x86_64 patchutils-0.3.1-3.1.el6.x86_64 bc-1.06.95-1.el6.x86_64 cscope-15.6-6.el6.x86_64 coreutils-8.4-37.el6.x86_64 ncurses-devel-5.7-3.20090208.el6.x86_64 libselinux-utils-2.0.94-5.8.el6.x86_64