libvirt users - Mar 2017 - Re: Compile DLL for Windows

I would like to know if there is a proper documentation for compiling
libvirt for Windows.
This is in regard to the latest versions of libvirt.

Also, most answers are outdated and the scripts by Matthias Bolte on github
don't use the latest versions and patches for libvirt.



Regards,
Kartik Vaishnav

Hello list,

i updated on a gentoo system from libvirtd 2.5 to 3.1.0
Now my windows machines cant access internet.
I did a virbr1 with virt-manager and route it to the eth0, works fine on 
2.5



on install i get this:



Important: The openrc libvirtd init script is now broken up into two
separate services: libvirtd, that solely handles the daemon, and
libvirt-guests, that takes care of clients during shutdown/restart of 
the
host. In order to reenable client handling, edit 
/etc/conf.d/libvirt-guests
and enable the service and start it:

         $ rc-update add libvirt-guests
         $ service libvirt-guests start


For the basic networking support (bridged and routed networks) you don't
need any extra software. For more complex network modes including but 
not
limited to NATed network, you can enable the 'virt-network' USE flag. It
will pull in required runtime dependencies


If you are using dnsmasq on your system, you will have to configure
/etc/dnsmasq.conf to enable the following settings:

         bind-interfaces
         interface or except-interface

Otherwise you might have issues with your existing DNS server.


For openrc users:

         Please use /etc/conf.d/libvirtd to control the '--listen' 
parameter for
         libvirtd.

         Use /etc/init.d/libvirt-guests to manage clients on 
restart/shutdown of
         the host. The default configuration will suspend and resume 
running kvm
         guests with 'managedsave'. This behavior can be changed under
         /etc/conf.d/libvirt-guests


virt-manager starts fine and shows my vm´s. i dont touched /etc/dnsmasq 
cause i dont used it. so left untouched.
yes, i added libvirt-guests with rc-update

the virbr1 has 192.168.18.1 as address, and is reachable via ping from 
vm guest.
but it cant resolve hostnames and cant ping ip´s outside the 
virtualisation host.

anyone knows this effect after update?
do i have to change some more things?
or is this a bug?

any help and hints are welcome

thank you

marko weber

On Mon, Mar 06, 2017 at 12:36:08PM +0530, Kartik Vaishnav
wrote:
>I would like to know if there is a proper documentation for compiling
>libvirt for Windows.
>This is in regard to the latest versions of libvirt.
>
>Also, most answers are outdated and the scripts by Matthias Bolte on github
>don't use the latest versions and patches for libvirt.
>
For testing I use mingw, that's what the code is prepared for.  I see
some checks for MSVC there as well, so I guess it will work as well.

Anyway, I haven't tried building *on* windows machine, I'm building the
binaries normally as I build for my system as well, just with some
configure options.  Specifically what I do from clean git is:

./autogen.sh --host=i686-w64-mingw32 --without-sasl --without-avahi \
             --without-polkit --without-xen --without-qemu --without-lxc \
             --without-openvz --without-libvirtd --without-dbus \
             --without-systemd-daemon

and then just make.  If you have a tarball you should be able to just
use ./configure instead of ./autogen.sh with the same options.
>
>
>Regards,
>Kartik Vaishnav
>_______________________________________________
>libvirt-users mailing list
>libvirt-users@redhat.com
>https://www.redhat.com/mailman/listinfo/libvirt-users

On Tue, Mar 07, 2017 at 10:49:06AM +0100, Marko Weber | 8000
wrote:
>
>
>Hello list,
>
>i updated on a gentoo system from libvirtd 2.5 to 3.1.0
>Now my windows machines cant access internet.
>I did a virbr1 with virt-manager and route it to the eth0, works fine on
>2.5
>
Firstly, you replied to a message that has nothing to do with this, you
should fix your client if that wasn't just a mistake (which it could've
been, it happens).

I'm not precisely sure what you mean by just 'routing' it.  Can you
attach XMLs of the network and the domain?  Just the interface for the
domain would be enough.
>
>
>on install i get this:
>
[...]
>For the basic networking support (bridged and routed networks) you don't
>need any extra software. For more complex network modes including but
>not
>limited to NATed network, you can enable the 'virt-network' USE
flag. It
>will pull in required runtime dependencies
>
[...]
>
>virt-manager starts fine and shows my vm´s. i dont touched /etc/dnsmasq
>cause i dont used it. so left untouched.
>yes, i added libvirt-guests with rc-update
>
From all the above, only the virt-network USE flag is related.  Do you
have it enabled?
>the virbr1 has 192.168.18.1 as address, and is reachable via ping from
>vm guest.
>but it cant resolve hostnames and cant ping ip´s outside the
>virtualisation host.
>
So this is why I had a feeling it's not just routed out.  It's NATted
network, OK.  So for DNS resolution you need dnsmasq running on the host
or setup nameservers to point to outside ones if you are using just
static IPs.  For accessing outside networks there should be iptables
rules for all that to work.  Can you check if they changed during the
update?

Also, did you restart the network?  You shouldn't (need to) do that when
the domain is running.
>anyone knows this effect after update?
>do i have to change some more things?
>or is this a bug?
>
There should be no need to change anything.
>any help and hints are welcome
>
>thank you
>
>marko weber
>
>
>
>_______________________________________________
>libvirt-users mailing list
>libvirt-users@redhat.com
>https://www.redhat.com/mailman/listinfo/libvirt-users