Hello
Thank you for the answer
Now, with this patch, and only ESX enabled returns a different error:
--------------------------------------
Making all in daemon
make[2]: Entering directory
`/root/InstalledPackages/libvirt-0.8.3/daemon'
make all-am
make[3]: Entering directory
`/root/InstalledPackages/libvirt-0.8.3/daemon'
make[3]: *** No rule to make target `libvirtd.8', needed by `all-am'.
Stop.
make[3]: Leaving directory
`/root/InstalledPackages/libvirt-0.8.3/daemon'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/root/InstalledPackages/libvirt-0.8.3/daemon'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/InstalledPackages/libvirt-0.8.3'
make: *** [all] Error 2
--------------------------------------
It seems a libvirtd error, but libvirtd is not enabled:
"configure: Libvirtd: no"
I don't know why returns a libvirtd error. Is there another patch to
solve this?
Thanks in advance
Antoni Artigues
El jue, 27-01-2011 a las 14:06 +0100, Matthias Bolte escribió:
> If you only need the ESX part you can disable most of the parts that
> may have problems due to the old kernel version. Running configure
> like Justin suggested:
>
> ./configure --with-esx --without-libvirtd --without-network
>
> This will disable libvirtd, the network driver and probably other
> things. configure will disable other things like macvtap automatically
> when it doesn't detect support for them in your system.
>
> The compile error you see can easily by avoided by this patch:
>
>
> diff --git a/src/util/interface.c b/src/util/interface.c
> index fe58823..1463574 100644
> --- a/src/util/interface.c
> +++ b/src/util/interface.c
> @@ -348,7 +348,7 @@ ifaceGetIndex(bool reportError,
>
> #endif /* __linux__ */
>
> -#ifdef __linux__
> +#if 0
> int
> ifaceGetVlanID(const char *vlanifname, int *vlanid) {
> struct vlan_ioctl_args vlanargs = {
>
>
> As ifaceGetVlanID is only used in macvtap specific code that'll
> probably be disabled anyway because of the kernel version.
>
> Matthias
>
> 2011/1/27 antoni artigues <tartigues@xxxxxxx>:
> > Hello
> >
> > Yes. I want to run only the libvirt client. I want to connect from it to
> > manage vmware ESX servers on the cluster nodes.
> >
> > But we must hurry up. So, I think we can't wait for your solution.When
> > would be the improvement?
> >
> > Thank for the answers
> >
> > regards
> >
> > Antoni Artigues
> >
> >
> > El jue, 27-01-2011 a las 19:55 +1100, Justin Clift escribió:
> >> On 27/01/2011, at 4:27 PM, Daniel Veillard wrote:
> >> <snip>
> >> > I still wonder about the usefulness of libvirt on RHEL-4 (except maybe
> >> > for the client library part).
> >>
> >> That's a really good point. Antoni, what are you wanting to do with libvirt?
> >>
> >> If you want the libvirt server to run... that's probably never going to work.
> >>
> >> But if you're only needing the libvirt client to run, so you can connect from
> >> it to other servers, that's something we should probably think about letting
> >> work. :)
> >>
> >> Regards and best wishes,
> >>
> >> Justin Clift
> >
> >
> >
> > _______________________________________________
> > libvirt-users mailing list
> > libvirt-users@xxxxxxxxxx
> > https://www.redhat.com/mailman/listinfo/libvirt-users
