libvirt users - Mar 2013 - Libvirt remote-client compilation for RHEL4

Hi,
   We are trying to compile Libvirt 1.02 from source for an RHEL4 target.

Our virtualization hosts are running the fedora 17/ RHEL6 with the latest
standard libvirt binaries.
This is where VMs will be created.

But our user/development machines are RHEL4 and we would like users to be able
to use virsh/libvirt/python to control the Vms running on RHEL6/fedora17
remotely from the their RHEL4 machines.

We are trying to compile a minimalist libvirt necessary on RHEL4 that would make
remote control of VMs   possible.

Has anyone tried this?
Any suggestions on what options to pass to ./configure to minimize what needs to
be compiled for this purpose? Or on RHEL 4?

Thx,
Sarvi


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20130306/0109fd23/attachment.htm>

I am using the following configure to minimize dependencies and avoid anything
unrelated to getting a libvirt remote client going. Turned on ?with-remote=yes,
--with-python=yes ?with-rhel5-api=yes

./configure --with-python --with-apparmor=no --with-apparmor-mount=no
--with-attr=no --with-audit=no --with-avahi=no --with-blkid=no --with-capng=no
--with-curl=no --with-dbus=no --with-fuse=no --with-hal=no --with-netcf=no
--with-numactl=no --with-openwsman=no --with-pciaccess=no --with-sanlock=no
--with-sasl=no --with-selinux=no --with-selinux-mount=no --with-ssh2=no
--with-udev=no --with-yajl=no --with-xen=no --with-xen-inotify=no --with-qemu=no
--with-uml=no --with-openvz=no --with-vmware=no --with-phyp=no --with-xenapi=no
--with-libxl=no --with-vbox=no --with-lxc=no --with-esx=no --with-hyperv=no
--with-parallels=no --with-test=no --with-remote=yes --with-libvirtd=no
--with-rhel5-api=yes --with-gnutls=no --with-polkit=no --with-firewalld=no
--with-secdriver-selinux=no --with-secdriver-apparmor=no --with-dtrace=no
--with-numad=no --with-network=no --with-secrets=no --with-storage-dir=no
--with-storage-fs=no --with-storage-lvm=no --with-storage-iscsi=no
--with-storage-scsi=no --with-storage-mpath=no --with-storage-disk=no
--with-storage-rbd=no --with-storage-sheepdog=no --with-python=yes
--with-interface=no --with-qemu-user=no --with-qemu-group=no --with-macvtap=no
--with-virtualport=no

I am getting the following error/warnings.
  CC     libvirt_util_la-virfile.lo
In file included from util/virfile.c:36:
/usr/include/linux/loop.h:31:2: #error "Wrong dev_t in loop.h"
In file included from util/virfile.c:42:
util/viralloc.h:67: warning: declaration of 'remove' shadows a global
declaration
/usr/include/stdio.h:154: warning: shadowed declaration is here
make-3.79.1-p7[3]: *** [libvirt_util_la-virfile.lo] Error 1

I also found this thread relating to compiling clients for RHEL4 from 2011
https://www.redhat.com/archives/libvirt-users/2011-January/msg00108.html

But it doesn't talk about this error.

Sarvi

From: Cisco Employee <sarvi at cisco.com<mailto:sarvi at cisco.com>>
Date: Wed, 6 Mar 2013 23:41:46 +0000
To: "libvirt-users at redhat.com<mailto:libvirt-users at
redhat.com>" <libvirt-users at redhat.com<mailto:libvirt-users at
redhat.com>>
Subject: [libvirt-users] Libvirt remote-client compilation for RHEL4



Hi,
   We are trying to compile Libvirt 1.02 from source for an RHEL4 target.

Our virtualization hosts are running the fedora 17/ RHEL6 with the latest
standard libvirt binaries.
This is where VMs will be created.

But our user/development machines are RHEL4 and we would like users to be able
to use virsh/libvirt/python to control the Vms running on RHEL6/fedora17
remotely from the their RHEL4 machines.

We are trying to compile a minimalist libvirt necessary on RHEL4 that would make
remote control of VMs   possible.

Has anyone tried this?
Any suggestions on what options to pass to ./configure to minimize what needs to
be compiled for this purpose? Or on RHEL 4?

Thx,
Sarvi


_______________________________________________ libvirt-users mailing list
libvirt-users at redhat.com<mailto:libvirt-users at redhat.com>
https://www.redhat.com/mailman/listinfo/libvirt-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20130307/f590ca9f/attachment.htm>

On 03/06/2013 04:41 PM, Saravanan Shanmugham (sarvi)
wrote:
> 
> 
> Hi,
>    We are trying to compile Libvirt 1.02 from source for an RHEL4 target.
Good luck.  Unfortunately, upstream libvirt does not target RHEL4 (we
have only tested that upstream libvirt can build on RHEL5), so there are
probably lots of gotchas, and you will have to do lots of legwork yourself.

Feel free to submit patches on what you changed to get things to work.
> We are trying to compile a minimalist libvirt necessary on RHEL4 that would
make remote control of VMs   possible.
So all you need is the libvirt.so with RPC support, and then the python
bindings.  Use of --without-libvirtd will force a client-only configure,
which should help.  Any further compile issues are probably related to
really old portability problems in your system headers.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 621 bytes
Desc: OpenPGP digital signature
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20130307/1abcc962/attachment.sig>