Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> Check what netvm is set for those VMs. I guess currently you have two of > them: sys-net and (just restored) sys-net1. Choose which one you want to > use and remove the other. > Thanks a lot Marek and Andrew for your help and patience. I now have access to all my AppVMs. -- 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/6632a035-af30-4785-833f-72ea42bc8e2c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> > Just one thing : I want to use my backed up "debian-8" TemplateVM, how can > > I replace the original "debian-8" ? I'm not able to delete it and as long > > as its there I won't be able to retore my backed up "debian-8" Template VM. > > Command line version of restore tool (qvm-backup-restore) allow you to > rename conflicting VMs (--rename-conflicting). The template will be > restored under different name (with "1" at the end), then you can switch > your VMs to that template. And after you switch all the VMs, you can > remove old template, and possibly rename the restored one back to > debian-8. I was able to restore all VMs with this command : "qvm-backup-restore -d sys-net --rename-conflicting /run/media/user/New\ Volume/qubesbackup/qubes-2016-12-21T080046" so now my (backed up) "debian-8" is "debian-81". It had been updated. some AppVMs start properly, others doesn't : with this error message : "Error starting VM: Requested operation is not valid: PCI device :00:19:.0 is in use by driver xenlight, domain sys-net" Is there something to do to access those VMs ? -- 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/d93e36e8-6726-4c52-b6b3-ec5ad8922355%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
On Tuesday, December 20, 2016 at 5:56:40 PM UTC-5, raah...@gmail.com wrote: > On Tuesday, December 20, 2016 at 9:11:58 AM UTC-5, jasonwals...@gmail.com > wrote: > > There is a typo in my last message but it was written as "journald-dev-log" > > rather than "journal-dev-log". > > > > Is there something to do with my problems with dom0 ? At the bare minimum > > I would like at least to recover my files from my VMs. > > > > Thanks > > I had similar probs. clean install is way to go in future imo. Backups > restored no problems. Only tip is if you make alot of changes to the default > templates. clone them instead and use the clone for your vms, to ensure > they get restored properly when backed up. But appvms should be no probs. Luckily, I was able to backup all my VMs from the state my computer was. I did a clean install, now Qubes work as it should. Just one thing : I want to use my backed up "debian-8" TemplateVM, how can I replace the original "debian-8" ? I'm not able to delete it and as long as its there I won't be able to retore my backed up "debian-8" Template VM. All my appVMs restored without problems. -- 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/8ebf2779-5983-4525-a53d-f47449018dde%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
There is a typo in my last message but it was written as "journald-dev-log" rather than "journal-dev-log". Is there something to do with my problems with dom0 ? At the bare minimum I would like at least to recover my files from my VMs. Thanks -- 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/351c6e8a-4a26-4abd-8d35-f6c806fe62c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> > > It isn't a command, it should be a socket. But apparently it doesn't > > > exist. Check status of systemd unit providing it: > > > > > > systemctl status systemd-journcald-dev-log.socket > > A typo here, should be systemd-journald-dev-log.socket [user@dom0 ~]$ systemctl status systemd-journal-dev-log.socket systemd-journal-dev-log.socket - Journal Socket (/dev/log) Loaded: loaded (/usr/lib/systemd/system/systemd-journal-dev-log.socket; statis; vendor preset: disabled) Active: inactive (dead) since Sat 2016-12-17 00:26:10 EST; 1min 49s ago Docs: man:systemd-journal.service(8) man:journald.conf(5) Listen: /run/systemd/journal/dev-log (Datagram) Dec 17 00:26:10 dom0 systemd[1]: Stopping Journal Socket (/dev/log). Dec 17 00:26:10 dom0 systemd[1]: systemd-journald-dev-log.socket: Socket service systemd-journald.service already active, refusing. Dec 17 00:26:10 dom0 systemd[1]: Failed to listen on Journal Socket (/dev/log). [user@dom0 ~]$ sudo rm -rf /dev/log [user@dom0 ~]$ sudo systemctl restart systemd-journald-dev-log.socket Job for systemd-journald-dev-log.socket failed. See "systemctl status systemd-journald-dev-log.socket" and "journalctl -xe" for details. [user@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/0f498763-ff97-49b1-bd33-7d035d072580%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> This looks like a problem with connecting to syslog. Do you have > /dev/log in place? It should be something like this: > > [marmarek@dom0 ~]$ ls -l /dev/log > lrwxrwxrwx 1 root root 28 Dec 13 23:57 /dev/log -> > /run/systemd/journal/dev-log [user@dom0 ~]$ ls -l /dev/log srw-rw-rw- 1 root root 0 Dec 16 07:32 /dev/log [user@dom0 ~]$/run/systemd/journal/dev-log bash: /run/systemd/journal/dev-log: Permission denied [user@dom0 ~]$ sudo /run/systemd/journal/dev-log sudo: /run/systemd/journal/dev-log: command not found -- 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/f4a3dded-122c-457e-aadd-f507614f8295%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> And what happens when you restart qubes-qmemman? this : Job for qubes-qmemman.service failed because the control process exited with error code. See "systemctl status qubes-qmemman.service" and "journalctl -xe" for details. "sudo systemctl status qubes-qmemman.service" returns the same kind of error as "sudo systemctl status qubes-qmemman" and "sudo journalctl -xe" is a bit long to copy, let me know if there is something specific to look there. -- 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/c400bfad-3f75-4955-b03c-544e85f033ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> - From this thread: > > https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion > > 'Please check "sudo systemctl status qubes-qmemman", or better "sudo > journalctl -u qubes-qmemman" for error messages. Then you can restart > the service with "sudo systemctl restart qubes-qmemman".' results for "sudo systemctl status qubes-qmemman" (I'm not able to transfer logs to another computer from dom0 at the moment so i need to write the logs ...) : Active: failed (Results: exit-code) Process: 2081 ExecStart=/usr/lib/qubes/qmemman_deamon.py (code=exited, status=1/FAILURE) Main PID: 2081 (code-exited, status=1/FAILURE) qmemman_deamon.py[2081]: self.connect_unixsocket(address) qmemman_deamon.py[2081]: File "/usr/lib64/python2.7/logging/handlers.py" line 789, in connect_unixsocket qmemman_deamon.py[2081]: self.socket.connect(address) qmemman_deamon.py[2081]: File "/usr/lib64/python2.7/socket.py", line 228, in meth qmemman_deamon.py[2081]: return getadttr(self._sock,name)(*args) qmemman_deamon.py[2081]: socket.error: [errno 111] Connection refused systemd[1]: qubes-qmemman.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start Qubes memory management deamon systemd[1]: qubes-qmemman.service: Unit entered failed state. systemd[1]: qubes-qmemman.service: Failed with result 'exit-code' it seams to be the same error for "sudo journalctl -u qubes-qmemman" In Qubes VM manager, when I right click on dom0 and then click on VM settings, nothing happens, I can infinitly click on "VM settings". This does not apply to other VMs. -- 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/af221208-9aad-4ecf-9416-5d4290e654c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> Yes, I see the problem. It sounds like your ServiceVMs are based on > debian-8. Have you tried basing them on the default Fedora template > instead? Ok, I have now assign sys-net & sys-firewall to fedora-23 TemplateVM, I still have the same qmemman error. Is it normal that when I start my computer (after decryption) that my desktop looks like this (this is also how my desktop looked like before the upgrade) : https://s23.postimg.org/tgs6vy8yj/006.jpg and now (after the upgrade) looks like this : https://s30.postimg.org/o1ot24zoh/007.jpg In the last picture you can see that only dom0 is in active state with 3934 MB as MEM. (its always at 3934 MB) -- 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/f055f65e-811e-42d1-80b1-09276596d046%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
After running this process a couple times : https://www.qubes-os.org/doc/upgrade-to-r3.2/ I think I was able to upgrade to 3.2, but with new problems Here's the results for "yum info qubes-core-dom0" : Redirecting to '/usr/bin/dnf info qubes-core-dom0' (see 'man yum2dnf') Failed to synchonize cache for repo 'updates', disabling. Failed to synchonize cache for repo 'fedora', disabling. Failed to synchonize cache for repo 'qubes-templates-itl', disabling. Failed to synchonize cache for repo 'qubes-dom0-current', disabling. Installed Packages: Name: qubes-core-dom0 Arch: x86_64 Version : 3.2.12 Release : 1.fc23 Size: 1.7 M Repo: @System Summary : The Qubes core files (Dom0-side) URL : http://www.qubes-os.org License : GPL Description : The Qubes core files for installation on Dom0. I also notice that there is no more wifi network. And when I try to start a VM i get this message : "Error starting VM 'email': Error: Failed to connect to qmemman: [errno 2] no such file or directory" Anyone can help to properly finish this upgrade to 3.2 process ? -- 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/40e9124a-4f3e-447a-9025-3d5f8b206ba2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> Is your sys-firewall based on Debian template? If so, there is > additional step in the upgrade procedure. this is what I've done : sudo qubes-dom0-update systemd-compat-libs perl-libwww-perl perl-Term-ANSIColor perl-Term-Cap gdk-pixbuf2-xlib speexdsp qubes-mgmt-salt-admin-tools lvm2 --> n sudo qubes-don0-update --clean this is the results of "yum info qubes-core-dom0" : Installed Packages Name: qubes-core-dom0 Arch: x86_64 Version : 3.1.18 Release : 1.fc20 Size: 1.7 M Repo: installed >From repo : qubes-dom0-cached Summary : The Qubes core files (Dom0-side) URL : http://www.qubes-os.org License : GPL Description : The Qubes core files for installation on Dom0. Available Packages Name: qubes-core-dom0 Arch: x86_64 Version : 3.2.12 Release : 1.fc23 Size: 328 k Repo: qubes-dom0-cached Summary : The Qubes core files (Dom0-side) URL : http://www.qubes-os.org License : GPL Description : The Qubes core files for installation on Dom0. I'm still stuck with 411 pending updates. -- 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/4d107495-a500-45fb-b081-4ba8fb528ae8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates
> If updates are already downloaded (it looks so), you can try running > "sudo dnf update" in dom0 - maybe it will be better at resolving > dependencies. [user@dom0 ~]$ sudo dnf update sudo: dnf: command not found -- 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/dcce1fa7-dbe5-4b04-9f5f-96d70c2c5e34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] help updating dom0 - no network - stuck with lots of pending updates
I'm trying to update dom0, (419 Updates Selected). After searching for infos on qubesOS website and from google, after various attempt, I'm still getting this message from dom0 : "None of the selected packages could be updated." When I click "check for new Updates", i'm getting this message : "There is no network connection available. Please check your connection settings and try again" I'm still having 419 Updates to make I just upgraded from Qubes Os 3.1 to Qubes release 3.2 (R3.2) You can find the logs from the command "sudo qubes-dom0-update --clean" here : http://pastebin.com/Em0W21YV Any help to properly update my dom0 will be very appreciated. Thanks -- 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/dd2290ef-eea8-4cf4-885e-a54a7c67ef47%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
