R4.0: sys-net, sys-firewall and other network VM(s) forced to always be on

[mike]

Hi All,

I cannot stop sys-net, sys-firewall and my other network VM.
Even though I unset "Start qube automatically on boot", they all start during boot.
Also, when I shutdown any of them, it immediately boots up again after shutdown.
This is happening with no other VM running.

This is on R4.0.

Could you please help?

Thanks,
Mike

[reby]

what does qvm-prefs say for the VMs ? post it here out of dom0

[Nick]

Hello,
I'm experiencing the same issue ... sometimes. I am most of the time
able to shutdown my sys-net vm. Sometimes I have to try multiple times.

Thanks,
Niav

reby:

[reby]

IIRC sys-net sometimes can be stubborn if one is not patient enough so
use qvm-kill if in a hurry ..... personally I don't see a downside of it
autostarting, though I guess one might have reasons to not want that,
any way


remember to NOT top post. ...... and provide qvm-prefs sys-net
information IMO



https://www.qubes-os.org/doc/copy-from-dom0/

[mike]

On Thursday, December 13, 2018 at 2:52:06 AM UTC+2, reby wrote:

> IIRC sys-net sometimes can be stubborn if one is not patient enough so
> use qvm-kill if in a hurry ..... personally I don't see a downside of it
> autostarting, though I guess one might have reasons to not want that,
> any way

My sys-net starts when I log in to Qubes (not during boot as it would if it was configured to start on boot). It also starts immediately after being shut down. Same is for sys-firewall.
Maybe I wouldn't even have noticed that, because normally I want it to always be on, but I currently have a particular reason I would like to shut it down and can't. :)

# qvm-prefs sys-net
autostart - False
backup_timestamp - 1543343438
debug D False
default_dispvm D fedora28dvm
default_user D user
gateway D 10.137.0.5
gateway6 D
include_in_backups D True
installed_by_rpm D False
ip D 10.137.0.5
ip6 D
kernel D 4.14.74-1
kernelopts D nopat iommu=soft swiotlb=8192
klass D AppVM
label - red
mac D 00:...
maxmem D 4000
memory - 400
name - sys-net
netvm - None
provides_network - True
qid - 5
qrexec_timeout D 60
start_time D 1544692438.38
stubdom_mem U
stubdom_xid D -1
template - fedora-28
template_for_dispvms D False
updateable D False
uuid - db...
vcpus D 2
virt_mode - pv
visible_gateway D
visible_gateway6 D
visible_ip D 10.137.0.5
visible_ip6 D
visible_netmask D
xid D 1

[David Hobach]

On 12/13/18 8:10 PM, mike wrote:
> On Thursday, December 13, 2018 at 2:52:06 AM UTC+2, reby wrote:
>
>> IIRC sys-net sometimes can be stubborn if one is not patient enough so
>> use qvm-kill if in a hurry ..... personally I don't see a downside of it
>> autostarting, though I guess one might have reasons to not want that,
>> any way
>
> My sys-net starts when I log in to Qubes (not during boot as it would if it was configured to start on boot). It also starts immediately after being shut down. Same is for sys-firewall.
> Maybe I wouldn't even have noticed that, because normally I want it to always be on, but I currently have a particular reason I would like to shut it down and can't. :)
>

Any VM used by another for networking will be started as dependency
whenever you start the other.

Moreover I guess the update checks might cause a network VM start.

If you have a lot of qvm-run calls pending in the background (e.g. if
you're doing dom0 scripting), it'll also cause the target VM to
constantly restart unless you used the -n option (which is not the default).

qvm-pause could be an option without these issues.

KR
David

[unman]

Also remember time service as well as update checks, can trigger this.
I run Qubes with nothing except sys-usb starting on boot.

If you want to shutdown sys-net, change netvm for sys-firewall to none
and then shut it down. See if that solves the restart problem.(If you
have other qubes using it as netvm change them also)