Tiny Core Linux

Tiny Core Extensions => TCE Corepure64 => Topic started by: core.dump on April 07, 2020, 05:27:33 AM

Title: virt-manager error on startup
Post by: core.dump on April 07, 2020, 05:27:33 AM
I tried the recently added virt-manager on a fresh TC installation.
When I try to start virt-manager for the first time, I get this error:

Code: [Select]
Unable to connect to libvirt qemu:///system.

internal error: Unable to get DBus system bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/connection.py", line 956, in _do_open
    self._backend.open(connectauth.creds_dialog, self)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtinst/connection.py", line 174, in open
    open_flags)
  File "/usr/local/lib/python3.6/site-packages/libvirt.py", line 104, in openAuth
    if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: internal error: Unable to get DBus system bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

If I try to start libvirtd from shell, I get:

Code: [Select]
tc@box:~$ sudo libvirtd
2020-04-07 14:09:23.116+0000: 13809: info : libvirt version: 1.3.5
2020-04-07 14:09:23.116+0000: 13809: info : hostname: box
2020-04-07 14:09:23.116+0000: 13809: error : dnsmasqCapsRefreshInternal:736 : Cannot check dnsmasq binary dnsmasq: No such file or directory
2020-04-07 14:09:23.119+0000: 13809: error : virDBusGetSystemBus:107 : internal error: Unable to get DBus system bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
2020-04-07 14:09:23.119+0000: 13809: warning : networkStateInitialize:698 : DBus not available, disabling firewalld support in bridge_network_driver: internal error: Unable to get DBus system bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
2020-04-07 14:09:24.047+0000: 13809: error : virFirewallValidateBackend:191 : direct firewall backend requested, but /sbin/iptables is not available: No such file or directory
2020-04-07 14:09:24.047+0000: 13809: error : virFirewallApply:938 : internal error: Failed to initialize a valid firewall backend
2020-04-07 14:09:24.053+0000: 13809: error : virSysinfoRead:1020 : internal error: Failed to find path for dmidecode binary
2020-04-07 14:09:24.096+0000: 13809: error : virNodeSuspendSupportsTarget:331 : internal error: Cannot probe for supported suspend types
2020-04-07 14:09:24.098+0000: 13809: warning : virQEMUCapsInit:1085 : Failed to get host power management capabilities
2020-04-07 14:09:24.606+0000: 13809: error : virSysinfoRead:1020 : internal error: Failed to find path for dmidecode binary
2020-04-07 14:09:24.606+0000: 13809: error : virExec:490 : Cannot find 'ip' in path: No such file or directory
2020-04-07 14:09:24.608+0000: 13809: error : virNodeSuspendSupportsTarget:331 : internal error: Cannot probe for supported suspend types
2020-04-07 14:09:24.608+0000: 13809: warning : virLXCDriverCapsInit:88 : Failed to get host power management capabilities
2020-04-07 14:09:24.610+0000: 13809: error : virNodeSuspendSupportsTarget:331 : internal error: Cannot probe for supported suspend types
2020-04-07 14:09:24.610+0000: 13809: warning : umlCapsInit:74 : Failed to get host power management capabilities
2020-04-07 14:09:24.622+0000: 13809: error : virNetDevBridgeCreateWithIoctl:413 : Unable to create bridge virbr0: Package not installed
2020-04-07 14:09:41.319+0000: 13800: error : virDBusGetSystemBus:107 : internal error: Unable to get DBus system bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
2020-04-07 14:09:41.324+0000: 13792: error : virNetSocketReadWire:1625 : End of file while reading data: Input/output error

What is missing???
Title: Re: virt-manager error on startup
Post by: Rich on April 07, 2020, 05:41:14 AM
Hi core.dump
The  .info  file states:
Quote
                ----------
                Howto:
                $ sudo modprobe kvm-intel
                $ sudo libvirtd -d
                ..then start virt-manager
                ----------

Code: [Select]
Unable to connect to libvirt qemu:///system.

internal error: Unable to get DBus system bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
You may need to start  dbus  first, maybe something like:
Code: [Select]
sudo /usr/local/etc/init.d/dbus start
Quote
Code: [Select]
2020-04-07 14:09:23.116+0000: 13809: error : dnsmasqCapsRefreshInternal:736 : Cannot check dnsmasq binary dnsmasq: No such file or directory
See if installing  dnsmasq.tcz  fixes that.
Title: Re: virt-manager error on startup
Post by: Juanito on April 07, 2020, 05:41:49 AM
It works for me using gnome-session - maybe it needs to be started with dbus (I can check tomorrow)?
Title: Re: virt-manager error on startup
Post by: core.dump on April 07, 2020, 07:52:41 AM
Hi all,
thanks for your suggestions, I added to /opt/bootlocal.sh the commands to start libvirtd and dbus, and now virt-manager seems to open correctly. Starting virt-manager as a regular user returns this error:

Code: [Select]
Unable to connect to libvirt qemu:///system.

error from service: CheckAuthorization: The name org.freedesktop.PolicyKit1 was not provided by any .service files

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/connection.py", line 956, in _do_open
    self._backend.open(connectauth.creds_dialog, self)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtinst/connection.py", line 174, in open
    open_flags)
  File "/usr/local/lib/python3.6/site-packages/libvirt.py", line 104, in openAuth
    if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: error from service: CheckAuthorization: The name org.freedesktop.PolicyKit1 was not provided by any .service files

This doesn't happen if I start virt-manager as root. The solution was to install a package called polkit.tcz providing some dbus-related stuff, this enables normal users to run virt-manager.

Now virt-manager starts and connects to the qemu backend correctly, but when I try to create a new virtual machine (either by pressing the toolbar button or thru the File menu) nothing happens. The problem is I don't get any errors. Do I have to install some other components?

EDIT: running virt-manager --debug allows to redirect errors and warning to stdout, this is what I obtained:

Code: [Select]
[Tue, 07 Apr 2020 16:54:38 virt-manager 9777] DEBUG (cli:200) Uncaught exception:
Traceback (most recent call last):
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/xmleditor.py", line 11, in <module>
    gi.require_version("GtkSource", "4")
  File "/usr/local/lib/python3.6/site-packages/gi/__init__.py", line 129, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GtkSource not available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/manager.py", line 456, in new_vm
    from .createvm import vmmCreateVM
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/createvm.py", line 31, in <module>
    from .storagebrowse import vmmStorageBrowser
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/storagebrowse.py", line 11, in <module>
    from .hoststorage import vmmHostStorage
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/hoststorage.py", line 16, in <module>
    from .createpool import vmmCreatePool
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/createpool.py", line 19, in <module>
    from .xmleditor import vmmXMLEditor
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/xmleditor.py", line 14, in <module>
    gi.require_version("GtkSource", "3.0")
  File "/usr/local/lib/python3.6/site-packages/gi/__init__.py", line 129, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GtkSource not available

I will do a search to understand what it means...
Title: Re: virt-manager error on startup
Post by: core.dump on April 07, 2020, 08:32:00 AM
It looks like I found a solution. These packages must be installed in order to get a correctly running virt-manager:

virt-manager.tcz
polkit.tcz
gtksourceview.tcz
gtksourceview-gir.tcz
libsoup.tcz

Probably they should be considered as dependencies since they're mandatory to run virt-manager without errors.
Title: Re: virt-manager error on startup
Post by: core.dump on April 07, 2020, 12:06:50 PM
Update

Sorry, I don't want to bother, but when I create a new guest in virt-manager and try to run it, I'm not able to start the network:

Code: [Select]
Could not start virtual network 'default': internal error: Failed to initialize a valid firewall backend

Traceback (most recent call last):
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/device/netlist.py", line 310, in _check_network_is_running
    netobj.start()
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
    ret = fn(self, *args, **kwargs)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/object/network.py", line 75, in start
    self._backend.create()
  File "/usr/local/lib/python3.6/site-packages/libvirt.py", line 3073, in create
    if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirt.libvirtError: internal error: Failed to initialize a valid firewall backend

Code: [Select]
Error starting domain: Requested operation is not valid: network 'default' is not active

Traceback (most recent call last):
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
    callback(*args, **kwargs)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
    ret = fn(self, *args, **kwargs)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/object/domain.py", line 1279, in startup
    self._backend.create()
  File "/usr/local/lib/python3.6/site-packages/libvirt.py", line 1059, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: Requested operation is not valid: network 'default' is not active

I'm not sure what these messages are referring to... ?
Title: Re: virt-manager error on startup
Post by: Rich on April 07, 2020, 12:32:36 PM
Hi core.dump
See if this solution fixes the first error message:
https://superuser.com/questions/1063240/libvirt-failed-to-initialize-a-valid-firewall-backend

Then report any remaining errors.
Title: Re: virt-manager error on startup
Post by: core.dump on April 07, 2020, 01:02:53 PM
Hi Rich,

I tried that solution, installed ebtables, started ebtablesd and dnsmasq, then restarted libvirtd. When I try to start the network in virt-manager, I still get the "libvirt.libvirtError: internal error: Failed to initialize a valid firewall backend" error message.

I don't understand, isn't ebtables a firewall?
Title: Re: virt-manager error on startup
Post by: Rich on April 07, 2020, 01:18:31 PM
Hi core.dump
... I don't understand, isn't ebtables a firewall?
In the  .info  file:
http://tinycorelinux.net/11.x/x86_64/tcz/ebtables.tcz.info

It states:
Quote
filtering tool for bridging firewalls

Based on that description, I would say no. Based on the  .list  file:

/usr/local/etc/ethertypes
/usr/local/lib/libebtc.so
/usr/local/lib/libebtc.so.0
/usr/local/lib/libebtc.so.0.0.0
/usr/local/sbin/ebtables
/usr/local/sbin/ebtables-restore
/usr/local/sbin/ebtables-save

/usr/local/sbin/ebtablesd
/usr/local/sbin/ebtablesu


It appears to have some configuration options. Possibly it requires some setup.

Iptables comes with a basic firewall, but I don't know if that helps you.
Title: Re: virt-manager error on startup
Post by: core.dump on April 07, 2020, 02:03:07 PM
Iptables comes with a basic firewall, but I don't know if that helps you.

No, in fact I tried installing iptables, but nothing changes:

Code: [Select]
Error starting network 'default': internal error: Failed to initialize a valid firewall backend

Traceback (most recent call last):
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
    callback(*args, **kwargs)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
    ret = fn(self, *args, **kwargs)
  File "/tmp/tcloop/virt-manager/usr/local/share/virt-manager/virtManager/object/network.py", line 75, in start
    self._backend.create()
  File "/usr/local/lib/python3.6/site-packages/libvirt.py", line 3073, in create
    if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirt.libvirtError: internal error: Failed to initialize a valid firewall backend

ebtablesd, iptables dnsmasq and libvirtd are all running but the error is still there. I have searched the web for a solution, but nothing seems to work...

Moreover, there's another thing I don't understand: after installing iptables, I noticed it hasn't anything to "run" the firewall: no servers (it doesn't exist, e.g., an "iptablesd"), no command line flags ("iptables -d" or such), no kernel modules (I didn't find any "iptables.ko" or similar). So my question is: how can it work if there isn't an "active" component?
Title: Re: virt-manager error on startup
Post by: Rich on April 07, 2020, 05:23:11 PM
Hi core.dump
... Moreover, there's another thing I don't understand: after installing iptables, I noticed it hasn't anything to "run" the firewall: no servers (it doesn't exist, e.g., an "iptablesd"), no command line flags ("iptables -d" or such), no kernel modules (I didn't find any "iptables.ko" or similar). So my question is: how can it work if there isn't an "active" component?

From:
http://tinycorelinux.net/11.x/x86/tcz/iptables.tcz.info

It appears the x86 version includes includes a basic firewall script not included in x86_64:
Code: [Select]
Comments:       Iptables is the userspace tool to control
the linux kernel firewall. A simple script
included, suitable for home users.
-
From a terminal:
sudo /usr/local/sbin/basic-firewall
-
From bootlocal.sh (to start on every boot):
/usr/local/sbin/basic-firewall noprompt

Title: Re: virt-manager error on startup
Post by: GNUser on April 07, 2020, 08:09:11 PM
No, in fact I tried installing iptables, but nothing changes:

Code: [Select]
Error starting network 'default': internal error: Failed to initialize a valid firewall backend
In TCL, kernel functionality required for firewall is in the  ipv6-netfilter-KERNEL.tcz  extension (which is a dependency of iptables.tcz). It should have been automatically installed when you installed iptables.tcz, but please check to make sure. When you run this command, does it say the extension is already installed?
Code: [Select]
$ tce-load -wi ipv6-netfilter-KERNEL
Title: Re: virt-manager error on startup
Post by: GNUser on April 07, 2020, 08:21:31 PM
Moreover, there's another thing I don't understand: after installing iptables, I noticed it hasn't anything to "run" the firewall: no servers (it doesn't exist, e.g., an "iptablesd"), no command line flags ("iptables -d" or such), no kernel modules (I didn't find any "iptables.ko" or similar). So my question is: how can it work if there isn't an "active" component?
If  iptables.tcz  and  ipv6-netfilter-KERNEL.tcz  extensions are installed, then your system has the capability of creating a firewall. However, no firewall is created until you configure one (either manually or using some helper script/application).

I have both of the above packages installed on my TC11 64bit laptop but didn't configure a firewall, so no firewall is running. Run this command:
Code: [Select]
$ sudo iptables -nvL
Chain INPUT (policy ACCEPT 12688 packets, 10M bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 9551 packets, 7421K bytes)
 pkts bytes target     prot opt in     out     source               destination       

If your output is similar to mine (i.e., if there are no rules listed for any of the chains) then it means no firewall is running.
Title: Re: virt-manager error on startup
Post by: Juanito on April 08, 2020, 12:38:13 AM
It looks like I found a solution. These packages must be installed in order to get a correctly running virt-manager:

virt-manager.tcz
polkit.tcz
gtksourceview.tcz
gtksourceview-gir.tcz
libsoup.tcz

Probably they should be considered as dependencies since they're mandatory to run virt-manager without errors.

gnome-boxes seems much easier to use to me...

I have not found the need to load polkit, gtksourceview or libsoup - virt-manager does however need gtk-vnc-gir and spice-gtk-gir to connect to a running vm, although it still gives an error message.

I've adjusted the dep and info files and reposted.
Title: Re: virt-manager error on startup
Post by: core.dump on April 08, 2020, 01:56:33 AM
gnome-boxes seems much easier to use to me...

I have not found the need to load polkit, gtksourceview or libsoup - virt-manager does however need gtk-vnc-gir and
spice-gtk-gir to connect to a running vm, although it still gives an error message.

Yes, but it has tons of other dependencies slowing down the bootup... :(

Hi core.dump
From:
http://tinycorelinux.net/11.x/x86/tcz/iptables.tcz.info

It appears the x86 version includes includes a basic firewall script not included in x86_64:
Code: [Select]
Comments:       Iptables is the userspace tool to control
the linux kernel firewall. A simple script
included, suitable for home users.
-
From a terminal:
sudo /usr/local/sbin/basic-firewall
-
From bootlocal.sh (to start on every boot):
/usr/local/sbin/basic-firewall noprompt

Could you please post that script? Probably with that I will be able to start a firewall. I suppose it is valid for x86_64 too, even though I don't know why it has not been included...
Title: Re: virt-manager error on startup
Post by: Juanito on April 08, 2020, 03:07:11 AM
You can download the 32-bit iptables extension and mount it to get access to the script.
Title: Re: virt-manager error on startup
Post by: core.dump on April 08, 2020, 04:48:28 AM
OK, got the script, tried to launch it. Even with iptables activated the error persists. The same error is thrown when using virsh in a shell.

Could it be a libvirt bug?
Title: Re: virt-manager error on startup
Post by: Juanito on April 08, 2020, 05:28:26 AM
...virt-manager does however need gtk-vnc-gir and spice-gtk-gir to connect to a running vm, although it still gives an error message.

spice-gtk-gir was missing a dep - corrected now
Title: Re: virt-manager error on startup
Post by: core.dump on April 14, 2020, 05:47:40 AM
Hi,
by reading this article (https://libvirt.org/firewall.html) it seems that libvirt (thus virt-manager) requires firewalld. Could firewalld be included in TC extensions?
Title: Re: virt-manager error on startup
Post by: Juanito on April 14, 2020, 07:11:16 AM
Maybe you could try installing filewalld with pip3.6 first to see if it’s really needed?
Title: Re: virt-manager error on startup
Post by: Rich on April 14, 2020, 07:24:35 AM
Hi Juanito
Maybe you could try installing filewalld with pip3.6 first to see if it’s really needed?
Don't type so fast. You misspelled  firewalld. :o
Title: Re: virt-manager error on startup
Post by: core.dump on April 14, 2020, 07:28:11 AM
Maybe you could try installing filewalld with pip3.6 first to see if it’s really needed?

firewalld is not included in pip3.6 packages:

Code: [Select]
tc@box:~$ pip3.6 search firewall
dns-firewall (0.0.4)                        - Local DNS Firewall
cloudshell-firewall-core (1.0.8)            - QualiSystems Firewall Python package
cloudshell-firewall-a10 (1.0.1)             - QualiSystems firewall A10 specific package
cloudshell-firewall-fortinet (1.1.1)        - QualiSystems firewall FortiNet specific package
firewall (0.2.0)                            - Punch a hole into an AWS EC2 security group temporarily
cloudshell-firewall-panos (1.0.0)           - QualiSystems firewall Palo Alto PanOS specific Package
cloudshell-shell-firewall-standard (3.0.2)  - QualiSystems Shells Firewall Standard Package
cloudshell-firewall-juniper-junos (1.0.3)   - QualiSystems firewall Juniper JunOS specific Package
cloudshell-firewall-cisco-asa (3.0.5)       - QualiSystems firewall Cisco ASA specific Package
cloudshell-firewall (3.0.3)                 - QualiSystems Python package
tornado-http-firewall (0.0.3)               - Validation and Hosting daemon for scatter.online.
pyfluffy (0.0.12)                           - Fluffy - A Firewall as a Service
firelet (0.5.0a3)                           - Distributed firewall management
trackerfw (0.0.4)                           - TrackerFw - firewall for trackers
fwmacro (0.9.6)                             - Firewall macro compiler
orangengine (0.0.1)                         - Firewall Policy Automation Engine
django-firefence (0.1.0)                    - A firewall for your Django views.
fwunit (1.2.0)                              - Unit tests for firewall rules
nagato (0.6.0)                              - Bypass korean firewall(warning.or.kr)
hotcidr (0.1.0)                             - Firewall rule management and automation tools
teamvault (0.8.4)                           - Keep your passwords behind the firewall
djaodjin-rules (0.2.4)                      - HTTP proxy firewall Django App
iptdump (1b1.3)                             - describes firewall rules and dump it out
mcsf (0.0.6)                                - Port modification wrapper for ConfigServer Security&Firewall
mignis (0.9.5.post1)                        - Mignis is a semantic based tool for firewall configuration
DAXFi (1.1)                                 - configure different kinds of firewalls in a consistent way.
zmqfirewall (0.1dev)                        - Object-based ZeroMQ message repeater/firewall
servicewall (0.4.2)                         - the desktop firewall that adapts to different network connections
wafw00f (2.1.0)                             - The Web Application Firewall Detection and Fingerprinting Toolkit.
waf-brain (1.0.0)                           - WAF-brain: the clever and efficient Firewall for the Web
shadowd (2.0.0)                             - Python connector for the Shadow Daemon web application firewall
rfw (0.2.2)                                 - Remote firewall as a web service. REST API for iptables.
pyrewall (0.9.1.post1)                      - A Python tool / service for managing iptables firewalls with ease
MinistryOfPackages (0.9.5)                  - A minimal PyPI implementation meant for use behind a firewall.
saruman (0.3.0)                             - A firewall that leverage AMQP workqueue ! Build by iresam for iresam !
find2deny (0.2.10)                          - find Bot IPs in log file to firewall them
behvpn (2.3.2)                              - A fast tunnel proxy that help you get through firewalls
nbsocks (2.9.1)                             - A fast tunnel proxy that help you get through firewalls
shadowsocks-cui (3.0.0)                     - A fast tunnel proxy that help you get through firewalls
fwgen (0.19.0)                              - A simple management framework for ip(6)tables based firewalls
relay (0.0.8)                               - Meta-magical SSH tunnels for remote developers behind firewalls.
snmpfwd (0.4.4)                             - SNMP Proxy Forwarder can act as an application-level firewall
shadowsocks (2.8.2)                         - A fast tunnel proxy that help you get through firewalls
shadowsocks-valoroso (3.0.7)                - A fast tunnel proxy that help you get through firewalls
wlister (0.1.0)                             - Web application firewall designed to whitelist and/or blacklist HTTP requests.
myremotedump (0.1.0)                        - Dumps a firewalled MySQL database via a ssh tunnel to the remote system
acl-stats (0.1.3)                           - Quickly gather access-lists stats from Cisco ASA Firewalls
firval (1.2.1)                              - a netfilter firewall rules generator designed designed to be easy to read, write and maintain
enuma-elish (0.0.4)                         - A fast tunnel proxy  extension from ss ,which help you get through firewalls
blocklistsaggregator (0.5.1)                - A Python tool that downloads IP block lists from various sources and builds configurations for network
                                              equipments and firewalls.
check_paloalto (0.3.2)                      - check_paloalto is a Nagios/Icinga plugin for Palo Alto Next Generation Firewalls. It is written in Python and
                                              based on the PA REST API.
openSeSSHIAMe (0.1.0)                       - openSeSSHIAMe allows SSH access to an instance behind the great AWS firewall (security group for the instance)
                                              for authorized IAM users from their current location.
shadowsocks-py (2.9.1)                      - A fast tunnel proxy that help you get through firewalls, the original pypi source is not maintained since
                                              version 2.8.2, this is a newly maintained pypi source by SilverLining.
portube (0.0.1)                             - Software-implemented port forwarding, transparent proxy, which can bypass firewalls in specific cases where the
                                              host restricts the inbound rules but does not restrict the outbound rules

If you (or anyone else) don't want to create a firewalld.tcz package it is ok for me, but please be patient, I need to get virt-manager working and I'm trying to solve as many problems as I can by myself, BUT I'm not a technician, so my skills are a bit limited...
Title: Re: virt-manager error on startup
Post by: Juanito on April 19, 2020, 04:31:36 AM
firewalld posted, but not fully tested.

There risk to be several hard-coded locations and/or obscure python run-time deps I didn't find.
Title: Re: virt-manager error on startup
Post by: core.dump on May 07, 2020, 02:26:08 AM
It's been a while... first of all, thank you Juanito for posting firewalld.tcz, it seems to work just fine.

Now when I start virt-manager it detects the firewall correctly, but there is another issue:

Code: [Select]
libvirt.libvirtError: Cannot check dnsmasq binary dnsmasq: No such file or directory
By searching around for this error, I found that the solution would be to recompile virt-manager with the "--with-dnsmasq-path" option

I'm not sure how to recompile it :-/
Title: Re: virt-manager error on startup
Post by: Juanito on May 07, 2020, 02:36:02 AM
Did you load the dnsmasq extension? If so, maybe a symlink /usr/sbin/dnsmasq -> /usr/local/sbin/dnsmasq might help?

See here for compilation notes:

http://tinycorelinux.net/11.x/x86_64/tcz/src/virt-manager/
Title: Re: virt-manager error on startup
Post by: core.dump on May 07, 2020, 08:43:38 AM
Ummm, tried to symlink /usr/local/sbin/dnsmasq to /usr/sbin, /usr/bin and even /bin (one at a time), it didn't help...

BTW, I'm sorry, in my latest post I wrote "recompile virt-manager with the "--with-dnsmasq-path" option" but I was wrong, it was referring to libvirt, not virt-manager... my fault  :-\

I took a look at http://tinycorelinux.net/11.x/x86_64/tcz/src/libvirt/compile_libvirt (http://tinycorelinux.net/11.x/x86_64/tcz/src/libvirt/compile_libvirt), but it is too complicated for my skill levels... and, of course, it is not guardanteed that it will work