Den tir. 13. nov. 2018 kl. 14.50 skrev unman <un...@thirdeyesecurity.org>:
> On Tue, Nov 13, 2018 at 02:22:49PM +0100, 'Ahmed Al Aqtash' via > qubes-users wrote: > > Den tir. 13. nov. 2018 kl. 14.12 skrev unman <un...@thirdeyesecurity.org > >: > > > > > On Tue, Nov 13, 2018 at 01:46:39PM +0100, 'Ahmed Al Aqtash' via > > > qubes-users wrote: > > > > Den tir. 13. nov. 2018 kl. 13.38 skrev unman < > un...@thirdeyesecurity.org > > > > I am running Qubes OS 4.0.0, only vanilla repos, only stable. > > > > > > > > Nothing happens when I run qvm-start --verbose sys-net. It just > starts as > > > > if nothing is wrong. No feedback in the terminal. > > > > If I run it again, while sys-net is running, is simply outputs that > > > sys-net > > > > is already running. > > > > > > > > > > That's good. > > > Can you confirm you're using sys-firewall as updateVM? > > > qubes-prefs in dom0 - look at value for updatevm > > > > > > > > sys-firewall is set as updateVM yes > > > > > > > If so, when you start sys-firewall, and try again, do you get the same > > > response? > > > > > > > > Yes, the exact same response. > > It starts up as normal, then gives the message stating that it is already > > running. > > > > What is the output when you attempt the install? > > > > > > Well, I know that I am not connected to anything right now, since there > is > > no wifi near me that I have connected to before. > > I tried beaming from my phone, and it didn't say that anything was > > connected. > > The output when I run: > > sudo qubes-dom0-update qubes-gui-dom0 > > > > Is: > > Using sys-firewall as UpdateVM to download updates for Dom0; this may > take > > some time... > > Failed to synchronize cache for repo 'updates', disabling. > > Failed to synchronize cache for repo 'fedora', disabling. > > Failed to synchronize cache for repo 'qubes-dom0-current', disabling. > > Failed to synchronize cache for repo 'qubes-templates-itl', disabling. > > No match for argument: qubes-gui-dom0 > > Error: Unable to find a match > > > > It takes a while for it to bail out. > > Well obviously we need to pick this up again when you're able to > connect. Let me know when that is. > You can get a terminal in sys-net by running in dom0: > sudo xl console sys-net > Log in as root > You can then check network status using ip tools. > I wanted to check if I could get the console up at least, but that doesn't seem to work. When running sudo xl console sys-net I get xenconsole: Could not read tty from store: No such file or directory Hmm.. -- 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/CA%2B3%2BOviOhPxA1kFYoZqAWXfmVx-uJN91NcRFuEPe5YQch9p5ig%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
