Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!
Am Montag, 31. Juli 2017 22:12:06 UTC+2 schrieb PR: > Hello, > > > > Am 31.07.2017 9:42 nachm. schrieb : > > > I was able to restore all of my VMs via CLI but after restoring I couldn't > start any VM. > > Will downgrade to 3.2 and will wait for final release of 4.0 and I hope that > this will then be fixed. > > > Of course you can go straight back to 3.2 but as this is release candidate > feedback could be helpful. > What happens when you start one of the AppVMs from the CLI? > Output/Error messages? > > > Have you tried to launch a template VM also, not only the AppVMs? > > > - PhR I can't start any VM (AppVM & Template VM) even the Template VM that was created freshly with 4.0 installation can't start. -- 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/9da17f19-455a-4f2c-9ef7-25b5a56fcc02%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: cannot install kernel 4.9.35 from …-current-testing
On Tuesday, August 1, 2017 at 7:21:10 AM UTC+2, Holger Levsen wrote: > On Mon, Jul 31, 2017 at 10:11:56PM -0700, Foppe de Haan wrote: > > and if you add --best --allowerasing to the command? > > commandline error, no such option :( > > > -- > cheers, > Holger 'sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing --best --allowerasing' shouldn't error like that. -- 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/f4017858-4bcb-4898-a319-a9b37a09eab8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: cannot install kernel 4.9.35 from …-current-testing
On Mon, Jul 31, 2017 at 10:11:56PM -0700, Foppe de Haan wrote: > and if you add --best --allowerasing to the command? commandline error, no such option :( -- cheers, Holger -- 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/20170801052105.GB2703%40layer-acht.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
On Mon, Jul 31, 2017 at 09:17:43PM +, Holger Levsen wrote: > Now I get another error OTOH, but I'll try a fresh reinstallation of 4.0rc1 > first, before > reporting that exact error… whoohooo - that fresh installation on an x260 for the first time showed reliable suspend+resumes, I've done 42 suspends of the machine (which, granted, was not doing anything) and it successfully resumed 42 times \o/ which to me is quite very amazing, running qubes 3.2 I'd estimate the success rate rather to be 60% or so, maybe 70%… (while the same machine running Debian 8 also had 99.x% successful resumes…) so far so very good. i'm curious whether this will also be the case with qubes 3.2.1 and a 4.9 kernel (so far only tried with the older 4.8 one from the qubes repos…) (but then, see the other mail on this list about my problems installing the 4.9 kernel on qubes 3.2…) OTOH, wireless didnt work after a few resumes (qubes 4.0rc1), i assume this can be fixed by unloading+reloading the module, but… I'm happy as long as resume works. -- cheers, Holger, who really did those 42 suspends and resumes… -- 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/20170801051910.GA2703%40layer-acht.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
[qubes-users] Re: cannot install kernel 4.9.35 from …-current-testing
On Tuesday, August 1, 2017 at 12:42:45 AM UTC+2, Holger Levsen wrote: > On Mon, Jul 31, 2017 at 02:38:32PM -0700, Foppe de Haan wrote: > > Try manually installing perl-Math-BigInt first? > > hah, I only tried installing the kernel and qubes-kernel-vm but not that > package. Installing perl-Math-BigInt succeeded but then I still get this: > > > [user@dom0 ~]$ LANG=C sudo qubes-dom0-update > --enablerepo=qubes-dom0-current-testing kernel > Using sys-firewall as UpdateVM to download updates for Dom0; this may take > some time... > Running command on VM: 'sys-firewall'... > Running command on VM: 'sys-firewall'... > fedora/metalink | 12 kB 00:00 > > qubes-dom0-current | 2.9 kB 00:00 > > qubes-dom0-current-testing | 2.9 kB 00:00 > > qubes-templates-itl | 2.9 kB 00:00 > > updates/metalink| 11 kB 00:00 > > --> Running transaction check > ---> Package kernel.x86_64 1000:4.9.35-19.pvops.qubes will be installed > --> Finished Dependency Resolution > /var/lib/qubes/dom0-updates/packages/kernel-4.9.35-19.pvops.qubes.x86_64.rpm > already exists and appears to be complete > find: '/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory > Redirecting to '/usr/bin/dnf > --exclude=qubes-template-whonix-gw,qubes-template-fedora-24,qubes-template-fedora-25-minimal,qubes-template-fedora-23,qubes-template-debian-8,qubes-template-whonix-ws, > install kernel' (see 'man yum2dnf') > > Qubes OS Repository for Dom0 > > 66 MB/s | 189 kB 00:00 > Package kernel-1000:4.4.14-11.pvops.qubes.x86_64 is already installed, > skipping. > Package kernel-1000:4.4.38-11.pvops.qubes.x86_64 is already installed, > skipping. > Package kernel-1000:4.8.12-12.pvops.qubes.x86_64 is already installed, > skipping. > Dependencies resolved. > > Package Arch >Version > RepositorySize > > Skipping packages with conflicts: > (add '--best --allowerasing' to command line to force their upgrade): > kernelx86_64 >1000:4.9.35-19.pvops.qubes > qubes-dom0-cached 40 M > > Transaction Summary > > Skip 1 Package > > Nothing to do. > Complete! > [user@dom0 ~]$ LANG=C sudo qubes-dom0-update > --enablerepo=qubes-dom0-current-testing kernel-qubes-vm > Using sys-firewall as UpdateVM to download updates for Dom0; this may take > some time... > Running command on VM: 'sys-firewall'... > Running command on VM: 'sys-firewall'... > fedora/metalink | 12 kB 00:00 > > qubes-dom0-current | 2.9 kB 00:00 > > qubes-dom0-current-testing | 2.9 kB 00:00 > > qubes-templates-itl | 2.9 kB 00:00 > > updates/metalink| 11 kB 00:00 > > --> Running transaction check > ---> Package kernel-qubes-vm.x86_64 1000:4.9.35-19.pvops.qubes will be > installed > --> Finished Dependency Resolution > /var/lib/qubes/dom0-updates/packages/kernel-qubes-vm-4.9.35-19.pvops.qubes.x86_64.rpm > already exists and appears to be complete > find: '/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory > Redirecting to '/usr/bin/dnf > --exclude=qubes-template-whonix-gw,qubes-template-fedora-24,qubes-template-fedora-25-minimal,qubes-template-fedora-23,qubes-template-debian-8,qubes-template-whonix-ws, > install kernel-qubes-vm' (see 'man yum2dnf') > > Qubes OS Repository for Dom0 > >
[qubes-users] Re: Announcement: Recommended Fedora 25 TemplateVM Upgrade for Qubes 3.2
So, I went through the docs, and successfully have F25 working. So.why would I want to run the command below? and/or should I be doing that at this stage? - We also provide fresh Fedora 25 TemplateVM packages through the official Qubes repositories, which you can get with the following commands (in dom0). Standard Fedora 25 TemplateVM: $ sudo qubes-dom0-update qubes-template-fedora-25 -- 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/21c331fe-997b-72c2-c4be-d9f7ff4a8ede%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Announcement: Recommended Fedora 25 TemplateVM Upgrade for Qubes 3.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-07-30 20:53, wannabeiron...@gmail.com wrote: > On Saturday, July 29, 2017 at 10:25:12 PM UTC-4, Andrew David Wong > wrote: Dear Qubes Users, > > Fedora 24, one of the supported TemplateVM versions in Qubes 3.2, > is scheduled to reach EOL (end of life) approximately one month > after the release of Fedora 26, which was on 2017-07-11. This > places the expected EOL date for Fedora 24 somewhere in the second > week of August. > > Options for migrating to Fedora 25 are now available for Qubes 3.2. > If you're currently using Fedora 24 (or older) TemplateVMs or > StandaloneVMs, we strongly recommend upgrading them to Fedora 25 > before then. We provide step-by-step instructions for upgrading > your existing TemplateVMs and StandaloneVMs in-place here: > > https://www.qubes-os.org/doc/template/fedora/upgrade-24-to-25/ > > We also provide fresh Fedora 25 TemplateVM packages through the > official Qubes repositories, which you can get with the following > commands (in dom0). > > Standard Fedora 25 TemplateVM: > > $ sudo qubes-dom0-update qubes-template-fedora-25 > > Minimal Fedora 25 TemplateVM: > > $ sudo qubes-dom0-update qubes-template-fedora-25-minimal > > After upgrading to a Fedora 25 TemplateVM, please remember to set > all qubes that were using the old template to use the new one. This > can be done in dom0 either with the Qubes VM Manager or with the > `qvm-prefs` command-line tool. > > Please note that no user action is required regarding the OS > version in dom0. If you're using Qubes 3.2, there is no dom0 OS > upgrade available, since none is currently required. For details, > please see here: > > https://www.qubes-os.org/doc/supported-versions/#dom0 > > If you're using an older version of Qubes, we strongly recommend > that you upgrade to 3.2, as older versions are no longer > supported. > > > Axon, > > Will an iso with Fed25 TemplateVMs be released soon? I have a > network driver issue with a Kaby Lake NUC that could be solved by > Fed25. Just wanted to ask before I started jumping through hoops. > Thank you. > Qubes 3.2.1 will probably have fedora-25 as a default template on the ISO, and it will probably be out Soon (TM). I'm afraid we don't yet know enough to be any more specific than that. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJZf+UWAAoJENtN07w5UDAwLfYQAMx2UGcUAK2GH+CCcsNp5U6x O/EBE4Zm42hdMJvO3qQietdIeTFSCuRJmrK8CIlTMsDBIwwcv7vghP7JtQm/zu4T oD/XZ63/MTjLJUFkA3dbSw6AnaxF3LNiylCkRw/tc9WHI6Znf/qGi15IjF47YdUm jIe7J5qvV6N/qMgiZR4VLP2o/QWBYFITWqaLOWLAfVkaiKVeETrLVSfiFfC3hzMa T8swxN9vc1FlABM1Nsnvy5QQZZbXhgtCJWTDwfaTkzUHP1u1LTTji7PvuIPaN7mS 03fAnqOu1/kYKlvN1LmyRKE3HvRiEQtWTnOk+6O++uCd7Zo2Hy5uOTj05qOLz2xd eWoHVc6gTPhuyBs9r5XrMfi/eu/7tcbXJBKiFyUOkEtsUReEpgqRVRUjfJttjF22 142AM2P6De75k+clbRmLDmqh0Nwb5nIjFo3cLagW40DieInZfScJUdxDHiIxpu1P p3ytL8j2sFodOUs5Ckhs0o1mpegOvF0nSlA9UiH/QTu8D1xnKhQDq1oFj182+zr3 jc/y/PjW6OsNTO1GySEcErD/6d+d27pQ88IkUBFsG35iq+8KwQ0mxRVFns4G24lv B3RJ1miEenIGUxpjYUdSwXSM/iXGcmwcqavy9xNeMjKY4zgirjYc8utQ4bbqhnAg C8Zp0z6sXpcb2n7hgjuU =SnhM -END PGP SIGNATURE- -- 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/538e7ca6-7639-8256-8f3e-2f3263de917e%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Not able to connect with 2 firewall-proxy/vpns at same time
On 07/31/2017 07:54 PM, 'Essax' via qubes-users wrote: AUTH: Received control message: AUTH_FAILED This sounds like an issue with the provider. If they ask for more detail you can set '--verb 5' for more verbosity from openvpn. -- Chris Laprise, tas...@openmailbox.org https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/36f1ac3c-c800-2f56-57a4-aee985e11d75%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Not able to connect with 2 firewall-proxy/vpns at same time
I have multiple firewall-proxy/vpns setup as per the qubes docs. I have always been able to use more than one at the same time with out any problems connecting to my vpn providers servers. Starting a few day ago I am no longer able to connect with more than one firewall-proxy/vpn at a time. I start and connect with vpn1 . I start vpn2 and it fails to connect. Then I start vpn2 from the CLI and this is the output I get everytime. ( I just posted the important part at the end ) Mon Jul 31 17:20:43 2017 us=x Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-client' Mon Jul 31 17:20:43 2017 us=870023 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1602,tun-mtu 1500,proto UDPv4,comp-lzo,cipher AES-256-CBC,auth SHA512,keysize 256,key-method 2,tls-server' Mon Jul 31 17:20:43 2017 us=x TCP/UDP: Preserving recently used remote address: [AF_INET]xxx Mon Jul 31 17:20:43 2017 us=870070 Socket Buffers: R=[212992->212992] S=[212992->212992] Mon Jul 31 17:20:43 2017 us=870086 UDP link local: (not bound) Mon Jul 31 17:20:43 2017 us=870101 UDP link remote: [AF_INET] Mon Jul 31 17:20:43 2017 us=951538 TLS: Initial packet from [AF_INET]Server ip xxx, sid=x Mon Jul 31 17:20:43 2017 us=951664 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Mon Jul 31 17:20:44 2017 us=42751 VERIFY OK: nsCertType=SERVER Mon Jul 31 17:20:44 2017 us=938100 NOTE: --mute triggered... Mon Jul 31 17:20:44 2017 us=938181 1 variation(s) on previous 3 message(s) suppressed by --mute Mon Jul 31 17:20:44 2017 us=938321 [server] Peer Connection Initiated with [AF_INET] Mon Jul 31 17:20:45 2017 us=987500 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) Mon Jul 31 17:20:46 2017 us=66601 AUTH: Received control message: AUTH_FAILED Mon Jul 31 17:20:46 2017 us=66649 SIGTERM received, sending exit notification to peer Mon Jul 31 17:20:49 2017 us=214365 TCP/UDP: Closing socket Mon Jul 31 17:20:49 2017 us=214441 SIGTERM[soft,exit-with-notification] received, process exiting If I were to shutdown vpn1, I would have no problems connecting with vpn2. My vpn service provider also has a limited vpn service that is free of charge. I configured a firewall-proxy/vpn with those configuration files and I could use that and one of my other proxy/vpns at the same time. Taking into consideration the vpn logs and the fact that I can connect with the free service I'm leaning towards the problem being with my vpn provider. I'm going to start a support ticket with my provider but I wanted to hear if anyone else thought as I do or if there could be another problem I'm not seeing in the logs. Thanks in advance Essax Sent with [ProtonMail](https://protonmail.com) Secure Email. -- 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/_Q5bZgOCN1vyKKhaegjrUG63zw7ymbUGzi1giV6_PWqG8mV3Gb7xYyyaerrDjFlsTRuQhOv3JQHuzwbw3V1ijMwCopsFszOozwGuyKo-HxQ%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: cannot install kernel 4.9.35 from …-current-testing
On Mon, Jul 31, 2017 at 02:38:32PM -0700, Foppe de Haan wrote: > Try manually installing perl-Math-BigInt first? hah, I only tried installing the kernel and qubes-kernel-vm but not that package. Installing perl-Math-BigInt succeeded but then I still get this: [user@dom0 ~]$ LANG=C sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Running command on VM: 'sys-firewall'... Running command on VM: 'sys-firewall'... fedora/metalink | 12 kB 00:00 qubes-dom0-current | 2.9 kB 00:00 qubes-dom0-current-testing | 2.9 kB 00:00 qubes-templates-itl | 2.9 kB 00:00 updates/metalink| 11 kB 00:00 --> Running transaction check ---> Package kernel.x86_64 1000:4.9.35-19.pvops.qubes will be installed --> Finished Dependency Resolution /var/lib/qubes/dom0-updates/packages/kernel-4.9.35-19.pvops.qubes.x86_64.rpm already exists and appears to be complete find: '/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory Redirecting to '/usr/bin/dnf --exclude=qubes-template-whonix-gw,qubes-template-fedora-24,qubes-template-fedora-25-minimal,qubes-template-fedora-23,qubes-template-debian-8,qubes-template-whonix-ws, install kernel' (see 'man yum2dnf') Qubes OS Repository for Dom0 66 MB/s | 189 kB 00:00 Package kernel-1000:4.4.14-11.pvops.qubes.x86_64 is already installed, skipping. Package kernel-1000:4.4.38-11.pvops.qubes.x86_64 is already installed, skipping. Package kernel-1000:4.8.12-12.pvops.qubes.x86_64 is already installed, skipping. Dependencies resolved. Package Arch Version RepositorySize Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): kernelx86_64 1000:4.9.35-19.pvops.qubes qubes-dom0-cached 40 M Transaction Summary Skip 1 Package Nothing to do. Complete! [user@dom0 ~]$ LANG=C sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel-qubes-vm Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Running command on VM: 'sys-firewall'... Running command on VM: 'sys-firewall'... fedora/metalink | 12 kB 00:00 qubes-dom0-current | 2.9 kB 00:00 qubes-dom0-current-testing | 2.9 kB 00:00 qubes-templates-itl | 2.9 kB 00:00 updates/metalink| 11 kB 00:00 --> Running transaction check ---> Package kernel-qubes-vm.x86_64 1000:4.9.35-19.pvops.qubes will be installed --> Finished Dependency Resolution /var/lib/qubes/dom0-updates/packages/kernel-qubes-vm-4.9.35-19.pvops.qubes.x86_64.rpm already exists and appears to be complete find: '/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory Redirecting to '/usr/bin/dnf --exclude=qubes-template-whonix-gw,qubes-template-fedora-24,qubes-template-fedora-25-minimal,qubes-template-fedora-23,qubes-template-debian-8,qubes-template-whonix-ws, install kernel-qubes-vm' (see 'man yum2dnf') Qubes OS Repository for Dom0 66 MB/s | 189 kB 00:00 Package kernel-qubes-vm-1000:4.4.14-11.pvops.qubes.x86_64 is already installed, skipping. Package kernel-qubes-vm-1000:4.4.38-11.pvops.qubes.x86_64 is already installed, skipping. Package kernel-qubes-vm-1000
Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Micah Lee: > I just installed Qubes 4.0-rc1 on a Lenovo ThinkPad T440 which runs > Qubes 3.2 without a problem. After installing it, when I boot up, grub > works, but then as soon as Qubes starts to boot the computer reboots, > and I end up back in grub. I ran into the same behavior on a T420. Removing iommu=no-igfx from the Xen command line fixed it. [1] If that doesn't help, _adding_ console=vga should let you see what's going on. Rusty 1. https://github.com/QubesOS/qubes-issues/issues/2841#issuecomment-318172669 -BEGIN PGP SIGNATURE- iQJ8BAEBCgBmBQJZf62qXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0 NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfGk4P/A0pdDRjuAVchC6oy4XF4cqB pYRckVY4hET5yvMY3bqU2NIILbfwkK0XGztAvoKEuF9eqT6sfeq8ZwKdtL02gXD0 O14Nig4oXXg3+uRhBaDA12wMKu6wuPRZ0fUjtPZk/KyP6/v24sGIxHTicSDJUpve 8u+yqJYOzqZSw8907YdMwe6vEZoDAeqXbb0nA7ngdmzSdIX3z5T2iG5SOEnRjZ64 U/1uS5OdEir7tbks+L/Xh+NSWmfk4pnMKFmF8rV1+3/bVToMmOWOQAcbgQIoMElL tK+3aWqPOHX1+66qk07xIC8Uq+ORQOsHRRA0c2wUX03EY/23RNW1OzYlRlmBIWyb xfJOdw5U8R2wSheO1wUyMO1hQ52W3fx8e927UjTaTAGzJ7t1UJ8wN1e5ZyurKLuI iwVCaCq0o4AHsQbHsOdoRNNuIrzy12N3ZHPMaDQrw3UAX840/fDPAeg8aCi0Sr/6 CAKcu/wJUXTb24/6mRYBlDIRGtMd8f8UAAq37ikUBxOZB2EdYdYZHoedoTyqzSP6 SfponcAUSUG9KIOPLJDWG5OJSCuVJisMA0ScdnByRCdULvDaFcMlDWwee/7f8bbQ JJ6IxF1BgyJdJ/8OoQViSx2055Glj8tYPivm7I0XDfTs0Cx6zGhlAWNv7ro30xYT Pt+Wa4/IsIzuLB8HhlnL =IbPe -END PGP SIGNATURE- -- 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/2017073134.GA9976%40mutt. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: cannot install kernel 4.9.35 from …-current-testing
On Monday, July 31, 2017 at 10:56:15 PM UTC+2, Holger Levsen wrote: > Hi, > > I fail to install kernel 4.9.35 on Qubes 3.2, any hints how I can accomplish > this? > > [user@dom0 ~]$ LANG=C sudo qubes-dom0-update > --enablerepo=qubes-dom0-current-testing kernel kernel-qubes-vm > Using sys-firewall as UpdateVM to download updates for Dom0; this may take > some time... > Running command on VM: 'sys-firewall'... > Running command on VM: 'sys-firewall'... > fedora/metalink | 11 kB 00:00 > > qubes-dom0-current | 2.9 kB 00:00 > > qubes-dom0-current-testing | 2.9 kB 00:00 > > qubes-templates-itl | 2.9 kB 00:00 > > updates/metalink| 11 kB 00:00 > > --> Running transaction check > ---> Package kernel.x86_64 1000:4.9.35-19.pvops.qubes will be installed > ---> Package kernel-qubes-vm.x86_64 1000:4.9.35-19.pvops.qubes will be > installed > --> Processing Dependency: perl(Math::BigInt) for package: > 1000:kernel-qubes-vm-4.9.35-19.pvops.qubes.x86_64 > --> Running transaction check > ---> Package perl-Math-BigInt.noarch 0:1.9997-355.fc23 will be installed > --> Finished Dependency Resolution > /var/lib/qubes/dom0-updates/packages/kernel-4.9.35-19.pvops.qubes.x86_64.rpm > already exists and appears to be complete > /var/lib/qubes/dom0-updates/packages/kernel-qubes-vm-4.9.35-19.pvops.qubes.x86_64.rpm > already exists and appears to be complete > /var/lib/qubes/dom0-updates/packages/perl-Math-BigInt-1.9997-355.fc23.noarch.rpm > already exists and appears to be complete > find: '/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory > Redirecting to '/usr/bin/dnf > --exclude=qubes-template-whonix-gw,qubes-template-fedora-24,qubes-template-fedora-25-minimal,qubes-template-fedora-23,qubes-template-debian-8,qubes-template-whonix-ws, > install kernel kernel-qubes-vm' (see 'man yum2dnf') > > Qubes OS Repository for Dom0 > 44 MB/s | 189 kB 00:00 > Package kernel-1000:4.4.14-11.pvops.qubes.x86_64 is already installed, > skipping. > Package kernel-1000:4.4.38-11.pvops.qubes.x86_64 is already installed, > skipping. > Package kernel-1000:4.8.12-12.pvops.qubes.x86_64 is already installed, > skipping. > Package kernel-qubes-vm-1000:4.4.14-11.pvops.qubes.x86_64 is already > installed, skipping. > Package kernel-qubes-vm-1000:4.4.38-11.pvops.qubes.x86_64 is already > installed, skipping. > Package kernel-qubes-vm-1000:4.8.12-12.pvops.qubes.x86_64 is already > installed, skipping. > Dependencies resolved. > = > Package Arch Version > Repository Size > = > Skipping packages with conflicts: > (add '--best --allowerasing' to command line to force their upgrade): > kernel x86_64 1000:4.9.35-19.pvops.qubes > qubes-dom0-cached 40 M > kernel-qubes-vm x86_64 1000:4.9.35-19.pvops.qubes > qubes-dom0-cached 56 M > perl-Math-BigInt noarch 1.9997-355.fc23 > qubes-dom0-cached 188 k > > Transaction Summary > = > Skip 3 Packages > > Nothing to do. > Complete! > [user@dom0 ~]$ > > > -- > cheers, > Holger Try manually installing perl-Math-BigInt first? -- 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/1ce545f2-2d41-45d0-a1c6-bc895a4342d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
On Monday, July 31, 2017 at 11:23:20 PM UTC+2, Micah Lee wrote: > On 07/31/2017 04:43 AM, Marek Marczykowski-Górecki wrote: > > Hello, > > > > We have just released Qubes 4.0-rc1: > > > > https://www.qubes-os.org/news/2017/07/31/qubes-40-rc1/ > > I just installed Qubes 4.0-rc1 on a Lenovo ThinkPad T440 which runs > Qubes 3.2 without a problem. After installing it, when I boot up, grub > works, but then as soon as Qubes starts to boot the computer reboots, > and I end up back in grub. > > Any ideas on how to start troubleshooting? start by pressing esc to switch to text boot. Maybe get a camera so you can capture the error msg before reboot. If that doesn't provide enough info, you can try enabling debugging in the boot options by adding the relevant parameter. -- 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/bab9b7da-ef20-4a04-8495-dbc198a06768%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
On 07/31/2017 04:43 AM, Marek Marczykowski-Górecki wrote: > Hello, > > We have just released Qubes 4.0-rc1: > > https://www.qubes-os.org/news/2017/07/31/qubes-40-rc1/ I just installed Qubes 4.0-rc1 on a Lenovo ThinkPad T440 which runs Qubes 3.2 without a problem. After installing it, when I boot up, grub works, but then as soon as Qubes starts to boot the computer reboots, and I end up back in grub. Any ideas on how to start troubleshooting? -- 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/37f90321-b62b-a74c-1f01-a6590a7f75a6%40micahflee.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
On Mon, Jul 31, 2017 at 10:46:19PM +0200, Marek Marczykowski-Górecki wrote: > Do you have VT-x enabled in BIOS? doh, indeed it was disabled. (Which slightly puzzles me as I had running Qubes 3.2 running on this machine before…) Now I get another error OTOH, but I'll try a fresh reinstallation of 4.0rc1 first, before reporting that exact error… Thanks! -- cheers, Holger -- 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/20170731211743.GB1014%40layer-acht.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [qubes-users] dispvm savefile creation fails when .qubes-dispvm-customized
On Mon, Jul 31, 2017 at 09:22:23AM -0400, Steve Coleman wrote: > On 07/29/2017 08:59 AM, Connor Page wrote: > > qvm-create-default-dvm fedora-25 > > > > Try that to check if it fails. If not then starting dvms won't be a problem > > anymore. If it does then there's something wrong with your template. > > I use a heavily customized F25 template for dvms and it never fails, but I > > always run qvm-create-default-dvm after any changes to its private image. > > I have run this command many times, to recreate the dvm, so running it again > simply does not help. > > The dvm works fine as long as Qubes does not try to process the > "customization" of the DVM prior to launching it. I have no way presently to > see what portion of the customization process that gets hung. > > What I need is to find out how to run that customization code (script?) > under trace or debugger control so I can identify the actual problem. The > question is where is this customization script, dom0 or in the template? The > only script I have found so far (still looking) is dom0 "startup-dvm.sh", > but all it does is create symbolic links and set permissions for the > savefile. It never even tests for the existence of > ".qubes-dispvm-customized". > > When this has come up in the past on the list the answer has been to delete the saved dvm file and to recreate it, add customization, and then run qvm-create-default-template again. If you want to check the script operations, look at /usr/lib/qubes/init/mount-dirs.sh and /usr/lib/qubes/init/setup-dvm-home.sh They are simple scripts, so it shouldnt take much debugging. unman -- 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/20170731210941.7enjqet7ufy3q564%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] cannot install kernel 4.9.35 from …-current-testing
Hi, I fail to install kernel 4.9.35 on Qubes 3.2, any hints how I can accomplish this? [user@dom0 ~]$ LANG=C sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel kernel-qubes-vm Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Running command on VM: 'sys-firewall'... Running command on VM: 'sys-firewall'... fedora/metalink | 11 kB 00:00 qubes-dom0-current | 2.9 kB 00:00 qubes-dom0-current-testing | 2.9 kB 00:00 qubes-templates-itl | 2.9 kB 00:00 updates/metalink| 11 kB 00:00 --> Running transaction check ---> Package kernel.x86_64 1000:4.9.35-19.pvops.qubes will be installed ---> Package kernel-qubes-vm.x86_64 1000:4.9.35-19.pvops.qubes will be installed --> Processing Dependency: perl(Math::BigInt) for package: 1000:kernel-qubes-vm-4.9.35-19.pvops.qubes.x86_64 --> Running transaction check ---> Package perl-Math-BigInt.noarch 0:1.9997-355.fc23 will be installed --> Finished Dependency Resolution /var/lib/qubes/dom0-updates/packages/kernel-4.9.35-19.pvops.qubes.x86_64.rpm already exists and appears to be complete /var/lib/qubes/dom0-updates/packages/kernel-qubes-vm-4.9.35-19.pvops.qubes.x86_64.rpm already exists and appears to be complete /var/lib/qubes/dom0-updates/packages/perl-Math-BigInt-1.9997-355.fc23.noarch.rpm already exists and appears to be complete find: '/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory Redirecting to '/usr/bin/dnf --exclude=qubes-template-whonix-gw,qubes-template-fedora-24,qubes-template-fedora-25-minimal,qubes-template-fedora-23,qubes-template-debian-8,qubes-template-whonix-ws, install kernel kernel-qubes-vm' (see 'man yum2dnf') Qubes OS Repository for Dom0 44 MB/s | 189 kB 00:00 Package kernel-1000:4.4.14-11.pvops.qubes.x86_64 is already installed, skipping. Package kernel-1000:4.4.38-11.pvops.qubes.x86_64 is already installed, skipping. Package kernel-1000:4.8.12-12.pvops.qubes.x86_64 is already installed, skipping. Package kernel-qubes-vm-1000:4.4.14-11.pvops.qubes.x86_64 is already installed, skipping. Package kernel-qubes-vm-1000:4.4.38-11.pvops.qubes.x86_64 is already installed, skipping. Package kernel-qubes-vm-1000:4.8.12-12.pvops.qubes.x86_64 is already installed, skipping. Dependencies resolved. = Package Arch Version Repository Size = Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): kernel x86_64 1000:4.9.35-19.pvops.qubes qubes-dom0-cached 40 M kernel-qubes-vm x86_64 1000:4.9.35-19.pvops.qubes qubes-dom0-cached 56 M perl-Math-BigInt noarch 1.9997-355.fc23 qubes-dom0-cached 188 k Transaction Summary = Skip 3 Packages Nothing to do. Complete! [user@dom0 ~]$ -- cheers, Holger -- 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/20170731205607.GA1014%40layer-acht.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Jul 31, 2017 at 08:42:51PM +, Holger Levsen wrote: > On Mon, Jul 31, 2017 at 01:43:20PM +0200, Marek Marczykowski-Górecki wrote: > > We have just released Qubes 4.0-rc1: > > awesome! > > I've installed it on a lenovo x260 and upon the end of the installation I had > some > error concerning sys-firewall stating "could not find capabilities for > arch=x86_64", > despite that the installation seemed successful. But then when I logged into > the > installed system and ran "qvm-run personal xterm" I got the same: > > $ qvm-run personal xterm > Running 'xterm' on personal > personal: Start failed: invalid argument: could not find capabilities for > arch=x86_64 > > IOW: this doesnt work for me at all. Happy to test+debug further though if > someone > has an idea what to do… Do you have VT-x enabled in BIOS? - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJZf5ccAAoJENuP0xzK19csMK0IAIYI/zVfwmAj7Zn8Ywja8oRQ +s4EjLS+okL5bGDt+l86BOuVrtFi0W/9ugKWQgwab+MUEzfot4Y1IMUcIQG57Ee0 UPXXSFxY9TG93wgtgq1qPLp3j6rU7gD14DYiE8hoSkAa7XmqT5eMA/u4kKD7Mp0Q cvGtcj+2qNiN2Klt+rSqAZhnQU/SbPNJncRTsI3QeU0Jvny2RT2/M5re261wa3cO JlNv0vLojgQQ0TIaL/ObeZLN4RfQScCldNTlkecjgjASEFiiNokfLRFC1wAtvlOe CGcY09DV0AXGKexmTxxE2rj6ayDloYGzhG7CWXHxCB9N3yHuCF2dHyPgA+F9Ff4= =OXeO -END PGP SIGNATURE- -- 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/20170731204619.GC13907%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
On Mon, Jul 31, 2017 at 01:43:20PM +0200, Marek Marczykowski-Górecki wrote: > We have just released Qubes 4.0-rc1: awesome! I've installed it on a lenovo x260 and upon the end of the installation I had some error concerning sys-firewall stating "could not find capabilities for arch=x86_64", despite that the installation seemed successful. But then when I logged into the installed system and ran "qvm-run personal xterm" I got the same: $ qvm-run personal xterm Running 'xterm' on personal personal: Start failed: invalid argument: could not find capabilities for arch=x86_64 IOW: this doesnt work for me at all. Happy to test+debug further though if someone has an idea what to do… -- cheers, Holger -- 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/20170731204251.GA30080%40layer-acht.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!
Hello, Am 31.07.2017 9:42 nachm. schrieb : I was able to restore all of my VMs via CLI but after restoring I couldn't start any VM. Will downgrade to 3.2 and will wait for final release of 4.0 and I hope that this will then be fixed. Of course you can go straight back to 3.2 but as this is release candidate feedback could be helpful. What happens when you start one of the AppVMs from the CLI? Output/Error messages? Have you tried to launch a template VM also, not only the AppVMs? - PhR -- 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/CAM8xnvJNd%2BDL9j5WK_Qqk_BT67LywqpM99nJhTcDp0kZ8OE5%3Dg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!
Hi, HVM Standalone option is greyed out. Also the --cdrom option no longer exists with the qvm-start command. Does anyone know if this is related to some Stubdom changes/problems and will be supported again in the final release? -- 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/53647138-4cfa-4091-a878-8350795c6c64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!
Am Montag, 31. Juli 2017 20:37:14 UTC+2 schrieb PR: > Hello, > > > > Am 31.07.2017 8:09 nachm. schrieb : > > I don't like that Qubes Manager was removed. > > > > I can understand that this might feel strange, but after getting used to it > you can do anything (even more than with Qubes Manager) from the command > line/CLI. > > > As far as I have understand, the option is there that someone can program a > Qubes GUI, but this is not in scope of the Qubes Core Team, which seem ro be > focussed more on the "real"/difficult Qubes stuff. > I think this is a good decision, but having something like a "legacy" Qubes > Manager for Newbies might be helpful for beginners. > > > > > > I am also looking for an icon for Backup/Restore. > > > You can do backup and restores from the CLI (at least on Qubes 3.2) and I am > sure that this can also be done in Qubes 4 RC1. > In dom0: > qubes-backup-restore --help > ... will tell you exactly what you need to do. > > > > > As long as I can't find this option I can't restore my VMs and this release > is useless for me. > > > Have you tried to do a restore via CLI? > If you run into problems, just tell us where exactly the problem is and we'll > figure it out. > > > I'll download RC1 this evening and will also restore my Qubes 3.2 VMs. > I can then update this post with a short how-to. > > > - PhR I was able to restore all of my VMs via CLI but after restoring I couldn't start any VM. Will downgrade to 3.2 and will wait for final release of 4.0 and I hope that this will then be fixed. -- 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/2ae18dfd-1366-464c-a261-c20793176790%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Very good news, thanks :) On 07/31/2017 02:43 PM, Marek Marczykowski-Górecki wrote: > Hello, > > We have just released Qubes 4.0-rc1: > > https://www.qubes-os.org/news/2017/07/31/qubes-40-rc1/ > > - -- Regards -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJZf4FCAAoJEGSin3PC/C0A/ZMQALsV5RzgmGmCu0JoDUROzG5u a2nkQjtlh2uIeDOtd1xkYdOjtpoOv6Jllpjef/PJF01txwgz5paNRyvu+cW2hc2C LNVeff6alf7rhDlZX11ZY6WI17ld/P/yQv/rlW6gQjW6Is5prMb6DKIhzx+1XoGS W4SQmHThkT8ZGZ/fiuqxLHXKgSh/JWxG/De1KpSf0CByU6ugh2CGbOKV4RPHwa4X Z6WMfvECr+KCvl7vqYmwQaBwKD2gNag5bKuy0DNpXKIyHf33CGFHVvfT6uPoTg40 RtRUSp/uw+mZAjKIzCzOn82gt4aeLVvczF3jvE2Prk0Td8CThQCwUxPXw4IcUZ8m RSuxYspYYKz11WLZtM7pCDl+CkfrlM/ZUU88RJJ6waeVRPa2m0oM0d4dFn210usk Uc5UOC0/sKqh15ZH3rlaHK0+CfKyMYyNEMYN6vGME1bzLkOZ3g/ZLmL5EzUuL7mn NwlS1JkCX5yXUfZ+Xa0SnI4ZIWDxqzvyjY4VORAZxTua72R3iOYOKb/xU/N7CX91 vhZ9yamW3F3mnbiUYrP38tiVhH6XKhsfxzdotBVq5CuIccKlK1BrkEfKXZJDQuze 55MdXmbTaIDpivA5zfWjA7CDPHy82az3Aa7+XwaieD3jmX+jPYNXbXWBnRnLTCUz oBTFff76TAPKfQt8kouU =KJGq -END PGP SIGNATURE- -- 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/bc002212-70a1-8e7c-0505-2b4a9d72d2b4%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] fedora 25 template on 3.2 very long boot
Hello, Very long boot of new fedora-25 template on Q3.2 vs previous fedora-24 template. With fedora 24 template appVm start almost the same like whonix template. Now, it take 2-3 mins to launch. Anybody know how to fix? And why "run in debug" mode does not work for AppVM? -- Regards -- 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/2cbcc5c2-8d3e-27ae-fa98-7ce1e5e0dd89%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!
Tiny bug with 4rc1 (clean install): qvm-copy-to-vm doesn't exit once done transferring data. -- 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/688f99ae-d794-482c-bd10-33cf1b36e2ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Seeking moderators for unofficial Qubes IRC channels on Freenode and OFTC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 07:27 PM, Andrew David Wong wrote: > Dear Qubes Community, > > We're looking for well-known, trustworthy volunteers from the > community who would like to be moderators in the unofficial Qubes > IRC channels on Freenode and OFTC (#qubes on both). We'd like to > have at least two unrelated moderators who can oversee both > channels. If you're interested, please let us know. > > Best, Andrew > > I'm always lurking in the Freenode #qubes, I'd be happy to be a moderato r. - -- kulinacs -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEPL+ie5e8l/3OecVUuXLc0JPgMlYFAll/fr8ACgkQuXLc0JPg MlYXLw//QtqB0NyvPLScIus5pZf7/93HiOkt7PJhnaqg0ENInvXkeXhJQg0bAJEA KxjdpggoxhwwsChxh4T1aq5f/YkeP5XDZhKAEeY4W/GElzTjFWgM7GSdlPb9bejS R7AOlwmtD+z0epdOHxQUb9ZWFyM0yJ9uEN/HP4tlDAqh0TrGxrWQQvoKYVagCXos bHCWcr0ynGYcRnAB//ABhRAcitGwBpyCfWgJc4fyR2sppmu6qVf5/drKC2eeJ605 H8c/RQThDuymj3W9vssYz5eLHsYYqugOJWwhCxjBIQ0bmwAmoQAH4EoVo0OoHV+T yZojBFtTnuNB+/Tf3NlOnYs8sNXmcTVoCLDt7mHYM+8mpLc2+6xCTK+K30wNjXla eveHEVjE81sxgqUhQGuh2C5jojrEReEGtPS5VAYPYVGh5kCbHarrK/XyuI9oGY98 y36H1+ViFBUdvWo5zvmA/qd/YwmRvFDULC+dFijzp6BXjEnMe9RP2D3taSHN34fB RADfhcM16GLwem14ROw9oRk8FhR8BECXYMwRmr0fqP8rH6bkGLQXswioeXKGPQdZ cJA73oyNvgiKByA7SaZdkKFJtUoPMzBGPw//kVpOWJavfkvYwZJsaG/SbvSq03ZI NBHn0qeveaMYB9Qg26HnEKcMGgFxdY2RNTnVMpGFSqrXTMmMFV4= =Alcw -END PGP SIGNATURE- -- 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/7bebf087-cb13-8113-a35c-d3ec4edba2f4%40kulinacs.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!
Hello, Am 31.07.2017 8:09 nachm. schrieb : I don't like that Qubes Manager was removed. I can understand that this might feel strange, but after getting used to it you can do anything (even more than with Qubes Manager) from the command line/CLI. As far as I have understand, the option is there that someone can program a Qubes GUI, but this is not in scope of the Qubes Core Team, which seem ro be focussed more on the "real"/difficult Qubes stuff. I think this is a good decision, but having something like a "legacy" Qubes Manager for Newbies might be helpful for beginners. I am also looking for an icon for Backup/Restore. You can do backup and restores from the CLI (at least on Qubes 3.2) and I am sure that this can also be done in Qubes 4 RC1. In dom0: qubes-backup-restore --help ... will tell you exactly what you need to do. As long as I can't find this option I can't restore my VMs and this release is useless for me. Have you tried to do a restore via CLI? If you run into problems, just tell us where exactly the problem is and we'll figure it out. I'll download RC1 this evening and will also restore my Qubes 3.2 VMs. I can then update this post with a short how-to. - PhR -- 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/CAM8xnvLEh3JZ7pt%3DVjSOa7AM8wBJLkg2qymtoyUW9sqDRb9d2w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!
Am Montag, 31. Juli 2017 13:43:28 UTC+2 schrieb Marek Marczykowski-Górecki: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello, > > We have just released Qubes 4.0-rc1: > > https://www.qubes-os.org/news/2017/07/31/qubes-40-rc1/ > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJZfxfZAAoJENuP0xzK19cswOMH/0k+rDX8EuoGXduK+q7zltmT > nZ06yFh5nzUIA0x8gi6XyFAL/Ph68d0WARKIB2r7X+e2IChG9WbXnBZAzLmnpwRP > G0PwkYSMQNeVxv7dT9cTyOXtFScZlfhTJtJAhd40LuuLB1tMbfA+wEQVYT4eR7r3 > q7wftZRz5L6AAYZ2ofeDAkraIYF2i0PBC7NZeDnKKR6vT09S4a590HzqJukDz+Ob > HbOB3PhumFbCpISNjIhtPNgUitXbUreC1Wfc3hFF35UgzMatWzskP/lXeIZxztUI > TO+X7FsO3QO7LXJXidD7IZrPH6FWLfIL1Dhms8sj2MVuA1Ug5bayuYwJ/G4ci3Y= > =SV8T > -END PGP SIGNATURE- I don't like that Qubes Manager was removed. I am also looking for an icon for Backup/Restore. As long as I can't find this option I can't restore my VMs and this release is useless for me. -- 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/84867909-49fe-4a54-ade0-5fa407b350ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Impact of the Intel hyper-threading bug [Skylake & Kaby Lake]?
Thanks Unman. 26.07.2017, 17:21, "Unman" : > On Tue, Jul 25, 2017 at 05:14:45PM +0300, private user82 wrote: >> I am concerned about the recent bug affecting Skylake and Kaby Lake gen >> Intel processors - >> https://lists.debian.org/debian-devel/2017/06/msg00308.html >> >> As BIOS updates aren't yet available from many mobo manufacturers, how can >> we Qubes users best defend ourselves against an exploit? In this post I am >> hoping to reach out to someone who may be able to comment on how we can best >> configure our platforms until a fix is available. >> >> Following the advice in the linked Debian advisory, I have disabled >> hyper-threading in the BIOS settings. My questions are as follows: >> >> 1) When I check /proc/cpuinfo in dom0, 'ht' remains listed as a flag >> (capability). Running $ lscpu in dom0 indicates that 'Threads per core: 1' >> so I assume the BIOS has in fact disabled hyper-threading. Is this correct, >> or should the flag also disappear when functionality is disabled in BIOS >> settings? >> >> 2) Is it safe to run multiple VCPUs (up to the number of physical cores) >> for each Guest VM. Or, in light of this bug, should we only be using a >> single VCPU for each guest? >> >> Many thanks in advance. > > I seem to recall that Xen used to advise disabling hyperthreading, and > VMWare counsel against its use when provisioning vcpus. > In general there's no advantage in assigning more than physical cores to any > VM. > > On the specifics, I *think* that cpuinfo reports capabilities even if > they have been diabled, so that isnt an issue. > > I dont see any issue in assigning multiple vcpus up to the number of > physical cores. I dont think that bug is relevant to the decision. -- 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/315281501502066%40web9o.yandex.ru. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] dispvm savefile creation fails when .qubes-dispvm-customized
On 07/29/2017 08:59 AM, Connor Page wrote: qvm-create-default-dvm fedora-25 Try that to check if it fails. If not then starting dvms won't be a problem anymore. If it does then there's something wrong with your template. I use a heavily customized F25 template for dvms and it never fails, but I always run qvm-create-default-dvm after any changes to its private image. I have run this command many times, to recreate the dvm, so running it again simply does not help. The dvm works fine as long as Qubes does not try to process the "customization" of the DVM prior to launching it. I have no way presently to see what portion of the customization process that gets hung. What I need is to find out how to run that customization code (script?) under trace or debugger control so I can identify the actual problem. The question is where is this customization script, dom0 or in the template? The only script I have found so far (still looking) is dom0 "startup-dvm.sh", but all it does is create symbolic links and set permissions for the savefile. It never even tests for the existence of ".qubes-dispvm-customized". -- 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/44a122d9-6907-63ce-b01b-894148a8091d%40jhuapl.edu. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Keyboard AltGr bug
In Qubes 3.2 with i3, in any qube, regardless of which template I use, and regardless of which physical keyboard I use, the right Alt key is useless when mapped as AltGr, because it generates spurious Alt_L events. With a standard American keyboard (or Polish one; they're equivalent except for the markings) and American localization, start a new qube, run xev, press and release right Alt, and notice you get KeyPress and KeyRelease events for keycode 108 (keysym Alt_R). Now, do this: xmodmap -e 'remove mod1 = Alt_R' xmodmap -e 'keycode 108 = Mode_switch' Then run xev again, and notice when you press right Alt, you get a KeyPress event for keycode 108 (keysym Mode_switch), as expected. However, when you release right Alt, you get two events: a spurious KeyPress event for keycode 64 (keysym Alt_L), followed by a KeyRelease event for keycode 108 (keysym Mode_switch). You should only get the latter. Why does that happen? On another system running plain Debian instead of Qubes, using the same keyboards, I don't get the spurious KeyPress for keycode 64. -- 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/IxfIgxhVFiQfrypF6duH5I5VqsylWsAYC0IKwUkDLwY%40local. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, We have just released Qubes 4.0-rc1: https://www.qubes-os.org/news/2017/07/31/qubes-40-rc1/ - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJZfxfZAAoJENuP0xzK19cswOMH/0k+rDX8EuoGXduK+q7zltmT nZ06yFh5nzUIA0x8gi6XyFAL/Ph68d0WARKIB2r7X+e2IChG9WbXnBZAzLmnpwRP G0PwkYSMQNeVxv7dT9cTyOXtFScZlfhTJtJAhd40LuuLB1tMbfA+wEQVYT4eR7r3 q7wftZRz5L6AAYZ2ofeDAkraIYF2i0PBC7NZeDnKKR6vT09S4a590HzqJukDz+Ob HbOB3PhumFbCpISNjIhtPNgUitXbUreC1Wfc3hFF35UgzMatWzskP/lXeIZxztUI TO+X7FsO3QO7LXJXidD7IZrPH6FWLfIL1Dhms8sj2MVuA1Ug5bayuYwJ/G4ci3Y= =SV8T -END PGP SIGNATURE- -- 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/20170731114320.GY13907%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Problems with Qubes OS launch
Hello, successfully installed Qubes OS on internal HDD of my Lenovo ThinkPad, but can't see the Qubes OS between the BOOT options. -- 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/603871ea-66c3-409d-a2ac-3c16b6389c83%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
