On Thursday, February 28, 2019 at 11:57:22 AM UTC+8, awokd wrote: > Sphere: > > > 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 > > > Double check targets in /etc/qubes-rpc/policy/qubes.UpdatesProxy.
Thank you very much for that I checked the file and I found: # Default rule for all TemplateVMs - direct the connection to sys-net $type:TemplateVM $default allow, target=sys-net (facepalm) Does this mean that the updateVM that I assigned was meaningless after all this time? OTL -- 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/528d7e58-9612-4ca9-966e-c361f8717905%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
