So today I updated my system (Fedora 25) and it pulled the following virt
related updates:
> libvirt.x86_64
 libvirt-client
 libvirt-daemon
 " "-config-network
 " "-nxfilter
 " "-driver-interface
 " " "=libxl
 " " "-lxc
 " " "-network
 " " "-nodedev
 " " "-nwfilter
 " " "-qemu
 " " "-secret
 " " "-storage
 " " "-uml
 " " "-vbox
 " " "-xen
 "-glib
 "-libs
>

Once these updates were complete I believe the install process restart
libvirt because my open VM guest was closed and virt-manager was no longer
connected to QEMU.
So I right click, tell it to connect and it just sits there.
Checking journalctl the only thing I find that's from today is:

>Jun 22 10:57:51 Vostok libvirtd[14333]: libvirt version: 2.2.1, package:
2.fc25 (Fedora Project, 2017-05-30-23:29:39,
buildvm-17.phx2.fedoraproject.org)
Jun 22 10:57:51 Vostok libvirtd[14333]: hostname: Vostok
Jun 22 10:57:51 Vostok libvirtd[14333]: Libvirt doesn't support VirtualBox
API version 5001016
Jun 22 10:57:51 Vostok audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=libvirtd comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 10:57:52 Vostok libvirtd[14333]: COMMAND_FAILED: '/usr/sbin/iptables
-w2 -w --table filter --insert FORWARD --destination 192.168.100.0/24
--out-interface virbr0 --match conntrack --ctstate >ESTABLISHED,RELATED
--jump ACCEPT' failed:


Now the line about LIbvirt not supporting VirtualBox API version 5001016
has been happening for months.  But this Iptables entry is new.  Checking
iptables I have:

>$ sudo iptables-save
# Generated by iptables-save v1.6.0 on Thu Jun 22 10:59:47 2017
*security
:INPUT ACCEPT [480297:662444293]
:FORWARD ACCEPT [3406:273312]
:OUTPUT ACCEPT [401307:361870089]
COMMIT
# Completed on Thu Jun 22 10:59:47 2017
# Generated by iptables-save v1.6.0 on Thu Jun 22 10:59:47 2017
*mangle
:PREROUTING ACCEPT [591835:807244244]
:INPUT ACCEPT [480297:662444293]
:FORWARD ACCEPT [3406:273312]
:OUTPUT ACCEPT [401307:361870089]
:POSTROUTING ACCEPT [405762:362240145]
COMMIT
# Completed on Thu Jun 22 10:59:47 2017
# Generated by iptables-save v1.6.0 on Thu Jun 22 10:59:47 2017
*raw
:PREROUTING ACCEPT [591835:807244244]
:OUTPUT ACCEPT [401307:361870089]
COMMIT
# Completed on Thu Jun 22 10:59:47 2017
# Generated by iptables-save v1.6.0 on Thu Jun 22 10:59:47 2017
*filter
:INPUT ACCEPT [4416:6686704]
:FORWARD ACCEPT [59:4713]
:OUTPUT ACCEPT [3303:1718179]
-A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
COMMIT
># Completed on Thu Jun 22 10:59:47 2017


I cannot manually run that Insert either.. says the chain/target/match by
that name.  I'm assuming FORWARD but IDK for sure.

Anyone else ran into something like this?
Thanks!

***p.s. I know the Fedora community doesn't write/maintain libvirt, Im just
hoping a fellow user has seen this.***
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Reply via email to