libvirt users - Mar 2017 - Help needed on a gentoo system after update to libvirtd 3.1.0

(sorry, dont know how i put my posting into an reply to an other issue 
before,
  new posting to sepearte it, big sorry)




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
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 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




-- 
zbfmail - Mittendrin statt nur Datei!

OpenDKIM, SPF, DSPAM, Greylisting, POSTSCREEN, AMAVIS, Mailgateways
Mailfiltering, SMTP Service, Spam Abwehr, MX-Backup, Mailserver Backup
Redundante Mailgateways, HA Mailserver, Secure Mailserver

On 03/07/2017 11:44 AM, Marko Weber | 8000 wrote:
> 
> 
> (sorry, dont know how i put my posting into an reply to an other issue
> before,
>  new posting to sepearte it, big sorry)
> 
> 
> 
> 
> 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
> Hello list,
> 
> anyone knows this effect after update?
> do i have to change some more things?
> or is this a bug?
What is your domain configuration? What is your firewall setting? I use
gentoo too, but hasn't experienced this. On the other hand, I don't use
the same setting as you do.

Michal

Hello there.

I discovered, that since qemu 2.8 , external snapshots (very similar to: 
http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit), 
freezes block device after:

# virsh blockcommit (...)

There is no error message after completion of the command above.
I'm using gluster + ZFS fuse mount as a storage for a VM on gentoo.
libvirt debug showed nothing helpful.
With qemu <2.8 -: snapshots are working as expected.

Is this a known issue?
Is it qemu or libvirt ?

If it helps, how can i diagnose this further?

Thank You & Best regards
Piotr Rybicki

Am 2017-03-07 13:01, schrieb Michal Privoznik:
> On 03/07/2017 11:44 AM, Marko Weber | 8000 wrote:
>> 
>> 
>> (sorry, dont know how i put my posting into an reply to an other issue
>> before,
>>  new posting to sepearte it, big sorry)
>> 
>> 
>> 
>> 
>> 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
>> Hello list,
>> 
> 
> 
>> anyone knows this effect after update?
>> do i have to change some more things?
>> or is this a bug?
> 
> What is your domain configuration? What is your firewall setting? I use
> gentoo too, but hasn't experienced this. On the other hand, I don't
use
> the same setting as you do.
> 
> Michal
Hello Michal,
what do you mean with "domain config"? i can do a virsh xml dump of
the
domain.
Firewall, i dont used an nw* from libvirt, i do all via iptables & 
shorewall

i paste it here
tell me if you need more

the domain:

<domain type='kvm' id='4'>
   <name>PAC-DC</name>
   <uuid>47d0e291-ff7f-47af-98ef-ee8b8124af0d</uuid>
   <title>PAC-DC</title>
   <memory unit='KiB'>16777216</memory>
   <currentMemory unit='KiB'>16777216</currentMemory>
   <vcpu placement='static' current='2'>12</vcpu>
   <resource>
     <partition>/machine</partition>
   </resource>
   <os>
     <type arch='x86_64'
machine='pc-i440fx-2.8'>hvm</type>
     <bootmenu enable='yes'/>
   </os>
   <features>
     <acpi/>
     <apic/>
     <hyperv>
       <relaxed state='on'/>
       <vapic state='on'/>
       <spinlocks state='on' retries='8191'/>
     </hyperv>
   </features>
   <cpu mode='custom' match='exact'>
     <model fallback='forbid'>Broadwell</model>
     <vendor>Intel</vendor>
     <topology sockets='1' cores='6' threads='2'/>
     <feature policy='require' name='vme'/>
     <feature policy='require' name='ds'/>
     <feature policy='require' name='acpi'/>
     <feature policy='require' name='ss'/>
     <feature policy='require' name='ht'/>
     <feature policy='require' name='tm'/>
     <feature policy='require' name='pbe'/>
     <feature policy='require' name='dtes64'/>
     <feature policy='require' name='monitor'/>
     <feature policy='require' name='ds_cpl'/>
     <feature policy='require' name='vmx'/>
     <feature policy='require' name='smx'/>
     <feature policy='require' name='est'/>
     <feature policy='require' name='tm2'/>
     <feature policy='require' name='xtpr'/>
     <feature policy='require' name='pdcm'/>
     <feature policy='require' name='dca'/>
     <feature policy='require' name='osxsave'/>
     <feature policy='require' name='f16c'/>
     <feature policy='require' name='rdrand'/>
     <feature policy='require' name='arat'/>
     <feature policy='require' name='tsc_adjust'/>
     <feature policy='require' name='xsaveopt'/>
     <feature policy='require' name='pdpe1gb'/>
     <feature policy='require' name='abm'/>
   </cpu>
   <clock offset='localtime'>
     <timer name='rtc' tickpolicy='catchup'/>
     <timer name='pit' tickpolicy='delay'/>
     <timer name='hpet' present='no'/>
     <timer name='hypervclock' present='yes'/>
   </clock>
   <on_poweroff>destroy</on_poweroff>
   <on_reboot>restart</on_reboot>
   <on_crash>restart</on_crash>
   <pm>
     <suspend-to-mem enabled='no'/>
     <suspend-to-disk enabled='no'/>
   </pm>
   <devices>
     <emulator>/usr/bin/qemu-system-x86_64</emulator>
     <disk type='file' device='disk'>
       <driver name='qemu' type='qcow2'/>
       <source file='/vm/windows-2016-_DC.qcow2'/>
       <backingStore/>
       <target dev='vda' bus='virtio'/>
       <boot order='2'/>
       <alias name='virtio-disk0'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x06'
function='0x0'/>
     </disk>
     <disk type='file' device='cdrom'>
       <driver name='qemu' type='raw'/>
       <backingStore/>
       <target dev='hdb' bus='ide'/>
       <readonly/>
       <boot order='1'/>
       <alias name='ide0-0-1'/>
       <address type='drive' controller='0' bus='0'
target='0' unit='1'/>
     </disk>
     <disk type='file' device='cdrom'>
       <driver name='qemu' type='raw'/>
       <source file='/store/virtio-win.iso'/>
       <backingStore/>
       <target dev='hdc' bus='ide'/>
       <readonly/>
       <alias name='ide0-1-0'/>
       <address type='drive' controller='0' bus='1'
target='0' unit='0'/>
     </disk>
     <controller type='usb' index='0'
model='ich9-ehci1'>
       <alias name='usb'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x04'
function='0x7'/>
     </controller>
     <controller type='usb' index='0'
model='ich9-uhci1'>
       <alias name='usb'/>
       <master startport='0'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x04'
function='0x0' multifunction='on'/>
     </controller>
     <controller type='usb' index='0'
model='ich9-uhci2'>
       <alias name='usb'/>
       <master startport='2'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x04'
function='0x1'/>
     </controller>
     <controller type='usb' index='0'
model='ich9-uhci3'>
       <alias name='usb'/>
       <master startport='4'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x04'
function='0x2'/>
     </controller>
     <controller type='pci' index='0'
model='pci-root'>
       <alias name='pci.0'/>
     </controller>
     <controller type='ide' index='0'>
       <alias name='ide'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x01'
function='0x1'/>
     </controller>
     <controller type='virtio-serial' index='0'>
       <alias name='virtio-serial0'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x05'
function='0x0'/>
     </controller>
     <interface type='network'>
       <mac address='52:54:00:0f:69:2b'/>
       <source network='br1' bridge='virbr1'/>
       <target dev='vnet0'/>
       <model type='virtio'/>
       <alias name='net0'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x03'
function='0x0'/>
     </interface>
     <serial type='pty'>
       <source path='/dev/pts/1'/>
       <target port='0'/>
       <alias name='serial0'/>
     </serial>
     <console type='pty' tty='/dev/pts/1'>
       <source path='/dev/pts/1'/>
       <target type='serial' port='0'/>
       <alias name='serial0'/>
     </console>
     <console type='pty'>
       <source path='/dev/pts/2'/>
       <target type='virtio' port='1'/>
       <alias name='console1'/>
     </console>
     <channel type='unix'>
       <source mode='bind' 
path='/var/lib/libvirt/qemu/channel/target/domain-4-PAC-DC/org.qemu.guest_agent.0'/>
       <target type='virtio' name='org.qemu.guest_agent.0' 
state='connected'/>
       <alias name='channel0'/>
       <address type='virtio-serial' controller='0'
bus='0' port='1'/>
     </channel>
     <input type='tablet' bus='usb'>
       <alias name='input0'/>
       <address type='usb' bus='0' port='1'/>
     </input>
     <input type='mouse' bus='ps2'>
       <alias name='input1'/>
     </input>
     <input type='keyboard' bus='ps2'>
       <alias name='input2'/>
     </input>
     <graphics type='vnc' port='5900' autoport='yes'
listen='127.0.0.1'>
       <listen type='address' address='127.0.0.1'/>
     </graphics>
     <video>
       <model type='virtio' heads='1'
primary='yes'/>
       <alias name='video0'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x02'
function='0x0'/>
     </video>
     <memballoon model='virtio'>
       <stats period='5'/>
       <alias name='balloon0'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x07'
function='0x0'/>
     </memballoon>
     <rng model='virtio'>
       <backend model='random'>/dev/random</backend>
       <alias name='rng0'/>
       <address type='pci' domain='0x0000' bus='0x00'
slot='0x08'
function='0x0'/>
     </rng>
   </devices>
   <seclabel type='none' model='none'/>
   <seclabel type='dynamic' model='dac'
relabel='yes'>
     <label>+77:+77</label>
     <imagelabel>+77:+77</imagelabel>
   </seclabel>
</domain>


networking br1 (virbr1):
and routed to existing br0

virsh # net-dumpxml br1
<network connections='2'>
   <name>br1</name>
   <uuid>990cd005-c551-4f5e-86f9-9b718f3b810b</uuid>
   <forward dev='br0' mode='route'>
     <interface dev='br0'/>
   </forward>
   <bridge name='virbr1' stp='on' delay='0'/>
   <mac address='52:54:00:75:a4:2f'/>
   <domain name='br1'/>
   <ip address='192.168.18.1' netmask='255.255.255.0'>
   </ip>
</network>


you need more info?

hmm i also had an "host-bridge" defined network to br0 on my gentoo 
machine

# ifconfig
br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
         inet 192.168.17.1  netmask 255.255.255.0  broadcast 
192.168.17.255
         ether f6:6a:1c:5a:e8:93  txqueuelen 1000  (Ethernet)
         RX packets 67984  bytes 5401548 (5.1 MiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 33143  bytes 45362855 (43.2 MiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 88.198.185.235  netmask 255.255.255.192  broadcast 
88.198.185.255
         ether 18:66:da:88:0d:37  txqueuelen 1000  (Ethernet)
         RX packets 1080633  bytes 990840130 (944.9 MiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 1735305  bytes 2045606964 (1.9 GiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
         device interrupt 18

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
         inet 127.0.0.1  netmask 255.0.0.0
         loop  txqueuelen 1000  (Local Loopback)
         RX packets 607097  bytes 1883581534 (1.7 GiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 607097  bytes 1883581534 (1.7 GiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         ether f6:6a:1c:5a:e8:93  txqueuelen 100  (Ethernet)
         RX packets 67984  bytes 6353324 (6.0 MiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 85353  bytes 48259222 (46.0 MiB)
         TX errors 0  dropped 188 overruns 0  carrier 0  collisions 0

virbr1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.18.1  netmask 255.255.255.0  broadcast 
192.168.18.255
         ether 52:54:00:75:a4:2f  txqueuelen 1000  (Ethernet)
         RX packets 178002  bytes 54585053 (52.0 MiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 241542  bytes 899962475 (858.2 MiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         ether fe:54:00:0f:69:2b  txqueuelen 1000  (Ethernet)
         RX packets 3692  bytes 3461678 (3.3 MiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 14142  bytes 1201183 (1.1 MiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         ether fe:54:00:0a:34:1e  txqueuelen 1000  (Ethernet)
         RX packets 79661  bytes 18343744 (17.4 MiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 112365  bytes 437957368 (417.6 MiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


or do i have to set via virt-manager the br1 (virbr1) routed to eth0?

thanks

Marko

Am 2017-03-07 13:01, schrieb Michal Privoznik:
> On 03/07/2017 11:44 AM, Marko Weber | 8000 wrote:
>> 
>> 
>> (sorry, dont know how i put my posting into an reply to an other issue
>> before,
>>  new posting to sepearte it, big sorry)
>> 
>> 
>> 
>> 
>> 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
>> Hello list,
>> 
> 
> 
>> anyone knows this effect after update?
>> do i have to change some more things?
>> or is this a bug?
> 
> What is your domain configuration? What is your firewall setting? I use
> gentoo too, but hasn't experienced this. On the other hand, I don't
use
> the same setting as you do.
> 
> Michal

Michal,
here is also the 'host-bridge' i defined via a short xml

virsh # net-dumpxml host-bridge
<network>
   <name>host-bridge</name>
   <uuid>51a0a2b0-a568-4e5d-bd2b-c4315bbb7cbf</uuid>
   <forward mode='bridge'/>
   <bridge name='br0'/>
</network>

idea in email before was, to route virbr1 to eth0 instead br0.
is that a better way?

marko