On Wednesday, February 27, 2019 at 8:30:53 PM UTC+8, unman wrote: > On Tue, Feb 26, 2019 at 06:54:15PM -0800, Sphere wrote: > > It started happening just today > > Executing sudo dnf update command on my fedora-29 template forcefully makes > > my sys-net start > > > > But thing is, I'm no longer using sys-net template as my net vm and this > > caused me to triple check my settings and my update VM is showed correctly > > as I had intended = a VM designed to securely process DNS queries that is > > attached to sys-firewall > > > > Despite this, the behavior continues, even if I kill and/or halt my > > fedora-29 template and I have no clue as to why this happens it's like > > something is forcing it to use sys-net in an attempt to get through my > > secure processing of DNS queries > > > > I also double checked that the template has no assigned net vm as intended > > according to how Qubes was designed and it's also set properly to 'none' > > > > It's absolutely persistent to the point that I ended up deleting my sys-net > > template and now the sudo dnf update command abruptly ends with "Error: > > Failed to synchronize cache for repo 'fedora-modular'" > > > > Can anyone help me with the logs to check/commands to use in diagnosing > > this problem properly? > > > > This is expected. Not a problem. > When you run dnf update , Qubes will start the update VM that you have > set. > As with any qube, if that has a netvm then it will start *that*, etc etc, > right up to sys-net. > If it didn't start a network connection, then you would get an update > error (as indeed you have).
Sorry if I wasn't clear in some way that may have caused this confusion. I should've kept it short and simple: "I'm no longer using sys-net template as my net vm" my update VM has internet connection in it, I even did a ping to google Structure is: update VM -> Firewall VM -> Net VM(not sys-net) Which means dnf update should work as expected But instead what happens is dnf update execution -> starting sys-net Making it seem like my sys-net has been set as the updateVM for my fedora-29 template I haven't tried updating my other templates yet but performing a "qubes-dom0-update" works properly as intended and is using updateVM properly -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0630b69d-04ac-449d-b318-22517dc7edd2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
