Re: [qubes-users] Re: R4.0: sys-net, sys-firewall and other network VM(s) forced to always be on
On Sat, Dec 15, 2018 at 10:21:02AM +0100, David Hobach wrote: > 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 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) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181215140906.obqq3vkys23d5utt%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: R4.0: sys-net, sys-firewall and other network VM(s) forced to always be on
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 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6162a1f5-abf2-2cef-165a-1c0674113231%40hackingthe.net. For more options, visit https://groups.google.com/d/optout. smime.p7s Description: S/MIME Cryptographic Signature
[qubes-users] Re: R4.0: sys-net, sys-firewall and other network VM(s) forced to always be on
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_dispvmD fedora28dvm default_user D user gateway D 10.137.0.5 gateway6 D include_in_backupsD True installed_by_rpm D False ipD 10.137.0.5 ip6 D kernelD 4.14.74-1 kerneloptsD nopat iommu=soft swiotlb=8192 klass D AppVM label - red mac D 00:... maxmemD 4000 memory- 400 name - sys-net netvm - None provides_network - True qid - 5 qrexec_timeoutD 60 start_timeD 1544692438.38 stubdom_mem U stubdom_xid D -1 template - fedora-28 template_for_dispvms D False updateableD False uuid - db... vcpus D 2 virt_mode - pv visible_gateway D visible_gateway6 D visible_ipD 10.137.0.5 visible_ip6 D visible_netmask D xid D 1 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/aa395344-1c7d-49fc-83d9-4f6266a72592%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: R4.0: sys-net, sys-firewall and other network VM(s) forced to always be on
On 12/12/18 9:04 PM, Nick wrote: 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: On 12/11/18 1:31 AM, mike wrote: 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 what does qvm-prefs say for the VMs ? post it here out of dom0 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/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e9268550-773b-01d6-d503-67a3af87ade8%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: R4.0: sys-net, sys-firewall and other network VM(s) forced to always be on
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: > On 12/11/18 1:31 AM, mike wrote: >> 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 >> > > what does qvm-prefs say for the VMs ? post it here out of dom0 > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5f520fc1-de4f-3db8-0bd6-51e03affc539%40web.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Re: R4.0: sys-net, sys-firewall and other network VM(s) forced to always be on
On 12/11/18 1:31 AM, mike wrote: 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 what does qvm-prefs say for the VMs ? post it here out of dom0 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b9604e0d-9440-6adb-2832-8efff039286e%40riseup.net. For more options, visit https://groups.google.com/d/optout.
