okay I was missing the firewall rules of Qubes.
So, surely, I can trigger exceptions for the HVM OMV I have installed and that will works, if i find the right ports needed
but, theses exceptions will be for static IP and the full purpose of installing OMV is to bring it everywhere.
and then, I don't want have to setup news statics IP rules each time I move.
So, I was thinking : I did it wrong.
Let's create a new template for an altenate sys-net,
so I cloned my debian template, and try to install OMV packages,
then :
Code
invoke-rc.d: initscript nmbd, action "start" failed.
● nmbd.service - Samba NMB Daemon
Loaded: loaded (/lib/systemd/system/nmbd.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2019-01-08 03:10:16 MSK; 11ms ago
Docs: man:nmbd(8)
man:samba(7)
man:smb.conf(5)
Process: 2368 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=killed, signal=TERM)
Main PID: 2368 (code=killed, signal=TERM)
Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."
Jan 08 03:08:46 debian-9-clone-1 systemd[1]: Starting Samba NMB Daemon...
Jan 08 03:10:16 debian-9-clone-1 systemd[1]: nmbd.service: Start operation timed out. Terminating.
Jan 08 03:10:16 debian-9-clone-1 systemd[1]: Failed to start Samba NMB Daemon.
Jan 08 03:10:16 debian-9-clone-1 systemd[1]: nmbd.service: Unit entered failed state.
Jan 08 03:10:16 debian-9-clone-1 systemd[1]: nmbd.service: Failed with result 'timeout'.
Alles anzeigen
meh.
the template solely disposes of a lo IP, and the different ways i see to do something are full of behaviors ...