[qubes-users] Re: Q4.0 Fedora-26 -> Fedora-28 python3.6 errors
I had issues too going to fedora 27. I tried to do it off my clone didn't work. couldn't. find where to install it from testing repos either. but installing fedora 26 default vm and cloning and updating that worked fine. also green arrow wouldn't go away for me since i'm using google chrome and use whonix to update the vm and would get failed to synchronize cache errors. had to change fedora repos to use https. then realized have to do same thing for google chrome repo. -- 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/7ef10913-c6ac-4750-8803-0e5fa9dd98a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] whonixdvm isn't using updated torbrowser
even though I'm updating the template. I have to keep choosing the option to restart the browser to update. Anyone else experience this? I think maybe I should just delete it an recreate it. -- 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/ee5ac9c8-3732-4ce5-b2ec-b4b64a3bba7f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: why Whonix and not Tails or the anon-vm?
On Monday, May 21, 2018 at 12:43:19 AM UTC-4, cooloutac wrote: > On Sunday, May 20, 2018 at 9:16:09 PM UTC-4, john wrote: > > On 05/20/18 12:26, Name wrote: > > > On 05/19/18 22:07, awokd wrote: > > >> On Sat, May 19, 2018 12:45 pm, > > >> qubes-fan-q7wo9g+UVklWk0Htik3J/w...@public.gmane.org wrote: > > >> > > >>> Qubes is not amnesic, and therefore not suitable for running amnesic > > >>> Tails. Therefore the decission for non- amnesic Whonix, running > > >>> itself by > > >>> default, in a virtual environment loved by Qubes. > > >> > > >> Disposable VMs (including whonix-ws-dvm) are at least partly amnesic. > > >> Once > > >> you shut it down, you aren't going to recover the contents easily. Tails > > >> running directly on hardware is more amnesic. Tails running in an HVM is > > >> somewhere in between. See > > >> https://github.com/QubesOS/qubes-issues/issues/2024 and links in there. > > >> > > > > > > well, it's not really my question, but I did notice that in these > > > semi-permanent fedora-27-dvm and whonix-dvm that if I make bookmarks > > > in firefox they persist which surprises me, as I thought the whole point > > > was that with dvm's nothing persisted, I'm not sure I really > > > understand why I even have these domains listed fedora-27-dvm etc, > > > IIRC, in Q3.2 when you went to make a DVM it started and initially > > > took a while, and then told you next time it would be faster, but when > > > you closed whatever was using the DVM no domain persisted in the qvm-ls > > > / VM manager, etc ; much less things like browser bookmarks ... > > > > > > I expect with whonix-appqubes that bookmarks would persist, but not > > > whonix-dvm's > > > > > > > * actually they persist in fedora-dvm but not in whonix-dvm fwiw :) > > I've been wondering why my whonixdvm for me right now keeps asking me to > update. even though i'm updating the template. the torbrowser I meant. -- 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/88dc39b4-bc72-4ef6-91a6-4aaca625bf7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: why Whonix and not Tails or the anon-vm?
On Sunday, May 20, 2018 at 9:16:09 PM UTC-4, john wrote: > On 05/20/18 12:26, Name wrote: > > On 05/19/18 22:07, awokd wrote: > >> On Sat, May 19, 2018 12:45 pm, > >> qubes-fan-q7wo9g+UVklWk0Htik3J/w...@public.gmane.org wrote: > >> > >>> Qubes is not amnesic, and therefore not suitable for running amnesic > >>> Tails. Therefore the decission for non- amnesic Whonix, running > >>> itself by > >>> default, in a virtual environment loved by Qubes. > >> > >> Disposable VMs (including whonix-ws-dvm) are at least partly amnesic. > >> Once > >> you shut it down, you aren't going to recover the contents easily. Tails > >> running directly on hardware is more amnesic. Tails running in an HVM is > >> somewhere in between. See > >> https://github.com/QubesOS/qubes-issues/issues/2024 and links in there. > >> > > > > well, it's not really my question, but I did notice that in these > > semi-permanent fedora-27-dvm and whonix-dvm that if I make bookmarks > > in firefox they persist which surprises me, as I thought the whole point > > was that with dvm's nothing persisted, I'm not sure I really > > understand why I even have these domains listed fedora-27-dvm etc, > > IIRC, in Q3.2 when you went to make a DVM it started and initially > > took a while, and then told you next time it would be faster, but when > > you closed whatever was using the DVM no domain persisted in the qvm-ls > > / VM manager, etc ; much less things like browser bookmarks ... > > > > I expect with whonix-appqubes that bookmarks would persist, but not > > whonix-dvm's > > > > * actually they persist in fedora-dvm but not in whonix-dvm fwiw :) I've been wondering why my whonixdvm for me right now keeps asking me to update. even though i'm updating the template. -- 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/1592b3fa-8df3-43da-bd38-101c8c4a3304%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: why Whonix and not Tails or the anon-vm?
On 05/20/18 12:26, Name wrote: On 05/19/18 22:07, awokd wrote: On Sat, May 19, 2018 12:45 pm, qubes-fan-q7wo9g+UVklWk0Htik3J/w...@public.gmane.org wrote: Qubes is not amnesic, and therefore not suitable for running amnesic Tails. Therefore the decission for non- amnesic Whonix, running itself by default, in a virtual environment loved by Qubes. Disposable VMs (including whonix-ws-dvm) are at least partly amnesic. Once you shut it down, you aren't going to recover the contents easily. Tails running directly on hardware is more amnesic. Tails running in an HVM is somewhere in between. See https://github.com/QubesOS/qubes-issues/issues/2024 and links in there. well, it's not really my question, but I did notice that in these semi-permanent fedora-27-dvm and whonix-dvm that if I make bookmarks in firefox they persist which surprises me, as I thought the whole point was that with dvm's nothing persisted, I'm not sure I really understand why I even have these domains listed fedora-27-dvm etc, IIRC, in Q3.2 when you went to make a DVM it started and initially took a while, and then told you next time it would be faster, but when you closed whatever was using the DVM no domain persisted in the qvm-ls / VM manager, etc ; much less things like browser bookmarks ... I expect with whonix-appqubes that bookmarks would persist, but not whonix-dvm's * actually they persist in fedora-dvm but not in whonix-dvm fwiw :) -- 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/327d28e3-7ddd-4965-b9ad-50b4741caeb6%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Default 'revisions_to_keep'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/20/18 17:41, awokd wrote:> I think it replaces the snapshot with a new one at VM start, not shutdown. > So if you delete a file, shutdown the VM, then revert immediately, > you'll be OK. Oh yes! I've tested and worked fine. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlsB/bMACgkQFBMQ2OPt CKWq/g/9G2cD4XXF7yqk8UDx7fyOYcg3sOYFwn/eLSmRJHwbOoIEGLq6dfEG3Q8L v7q68ms5YEPgBg1N48yaZASzmju77MyxH0uKAk5UvVrhvSg+Dhu3nNcw1doiX+2K vKIja+N7AgjpoV1KINwyRarGuDflDsKv3VtfQu552HSFUqSkOGpgTLpnWCGNRdte GAnDSNH7ZWVU7hY0IqbXQmdXpH1POtT3AUptvlNzG9W65Tj0hbyBesmkQnUcQ4LI IGCK54vnEQSWlXpV3Rlj2U1/elv+B4dbp63xWn8uCDe6cIkXaorEIeWNI2x+tdb1 UWq7mNxiqEheobocHzDYIEv2+xj/BI58x4veCaqxKSCTtOxajoyOieDhjPtoMewW mJJ9CwxmYQzq+xdhtd4nmglRRitdKdwRMp75+OfUT2hV/wtmuggRdk9uIOJ1m+Kz 9vAcbbkgkoeD/RWc56dfLcvZlI7ep4QwTasKYihj2WpkwPtiZIJ6vkQG65HczDhO +cqBQEX6hmosY9UQx4Yufr4raXFncNbKggOlqt/VVdtnT3c8fcr5FEhbbs/B7ifL IEm+ixaphZ+kefzI9yimQi08ddDEbO38x0/T3fie0EzKnR5Xs3GhmMHNgj+2H6B7 jK8sYtyIxoYXJiaDWUOLcU7JBVp8cUgbNFEVNaAltpdikKIsidc= =p84L -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/e663e399-6122-1099-6b1b-e4cbe498b58f%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Q4.0 Fedora-26 -> Fedora-28 python3.6 errors
On 05/20/18 08:00, jhsdxsddw-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: On Thursday, May 17, 2018 at 8:52:20 AM UTC+3, john wrote: On 05/16/18 10:45, john wrote: On 05/16/18 04:16, Blaumeer wrote: Similar situation, different error. Did upgrade to 28 with the python exclusions: [user@fedora-28 ~]$ sudo dnf --releasever=28 --setopt=cachedir=/mnt/removable --best --allowerasing distro-sync -x python2-xcffib -x qubes-gui-vm -x qubes-gui-agent Then: [user@fedora-28 ~]$ sudo dnf swap python-xcffib python2-xcffib Error: Failed to synchronize cache for repo 'updates' interestingly, I just qvm-remove fedora-28 and started over and the 2nd time I got the xcffib error and then redid the install with -x xcffib or so ...and got one error Error: Transaction check error: file /etc/dconf/profile/user from install of dconf-0.28.0-1.fc28.x86_64 conflicts with file from package qubes-core-agent-4.0.24-1.fc26.x86_64 AND then: Error Summary - [user@fedora-28 ~]$ sudo dnf swap python-xcffib python2-xcffib Last metadata expiration check: 0:51:25 ago on Wed May 16 09:52:22 2018. No match for argument: python2-xcffib Error: Unable to find a match but, again no idea how to fix it or if it matters ..qvm-remove fedora-28 ; and again start from scratch, no errors, maybe there really is something to the 3rd time "being the charm" lol... that, or maybe I was a bit early in the release of the Fed28 templates .. mission complete How you did it? I have similar problem. sudo dnf --releasever=28 --setopt=cachedir=/mnt/removable--best --allowerasing distro-sync -x python2-xcffib -x qubes-gui-vm -x qubes-gui-agent Error: Transaction check error: file /etc/dconf/profile/user from install of dconf-0.28.0-1.fc28.x86_64 conflicts with file from package qubes-core-agent-4.0.24-1.fc26.x86_64 $ sudo dnf --releasever=28 distro-sync --best --allowerasing --enablerepo=qubes-vm*current-testing -x python2-xcffib -x qubes-gui-vm -x qubes-gui-agent then the sudo dnf swap python-xcffib python2-xcffib I guess my starting template was a clone of Fedora-27; if your clone is Fedora-26 ..YMMV as they say ( my initial post was with a Fed26 clone - 28 -- 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/cdebdee7-72cd-85e1-6ad6-21238ad6d532%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: why Whonix and not Tails or the anon-vm?
On 05/19/18 22:07, awokd wrote: On Sat, May 19, 2018 12:45 pm, qubes-...@tutanota.com wrote: Qubes is not amnesic, and therefore not suitable for running amnesic Tails. Therefore the decission for non- amnesic Whonix, running itself by default, in a virtual environment loved by Qubes. Disposable VMs (including whonix-ws-dvm) are at least partly amnesic. Once you shut it down, you aren't going to recover the contents easily. Tails running directly on hardware is more amnesic. Tails running in an HVM is somewhere in between. See https://github.com/QubesOS/qubes-issues/issues/2024 and links in there. well, it's not really my question, but I did notice that in these semi-permanent fedora-27-dvm and whonix-dvm that if I make bookmarks in firefox they persist which surprises me, as I thought the whole point was that with dvm's nothing persisted, I'm not sure I really understand why I even have these domains listed fedora-27-dvm etc, IIRC, in Q3.2 when you went to make a DVM it started and initially took a while, and then told you next time it would be faster, but when you closed whatever was using the DVM no domain persisted in the qvm-ls / VM manager, etc ; much less things like browser bookmarks ... I expect with whonix-appqubes that bookmarks would persist, but not whonix-dvm's -- 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/349d5576-6648-3c65-26e7-d33232c81905%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Corsair Strafe Keyboard stops working when booting into qubes.
I got a new keyboard (Corsair Strafe RGB), when booting into qubes it stops working. I cannot decrypt qubes to boot with this keyboard, but the mouse works fine. My old keyboard also works fine, but I'd prefer to use the corsair keyboard as switching back and forth is annoying. -- 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/5ddb51d2-e840-4932-ad54-ee3b59dc010f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HCL - Dell Latitude E6530
On 5 May 2015 15:22:26 BST, Zrubi wrote: >On 04/30/15 20:06, IX4 SVS wrote: > >> Unfortunately when docked, the built-in VGA port of the laptop seems >to >> be disabled - which means one can only have one external monitor. The >> single-external-monitor configuration works well, but I'm trying to >get >> to having two external monitors. > >As far as I know the intel GPU supports only 2 monitors. > >This means without the nVidia you are not able to use 2 external >monitors in addition to the internal LCD display. ...and indeed now with Qubes 4.0 this works out of the box. With Optimus enabled, I have three functioning monitors (built-in and two external), but their positioning is unreliable and sometimes a monitor stops receiving signal. With Optimus disabled in the BIOS, I seem to have two reliable external monitors only, which is absolutely fine with me. Alex -- 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/BF429913-10FB-4EFC-872E-4CCFE53E87D3%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] MacBookPro10,1 & R4 install
I've been running R3.2 on a MacBook pro for quite some time. I thought I'd give R4 a chance, but don't even get the installer to start. When booting the installer, it attempts to start the dracut-initqueue, but then complains about running into some timeout after a while. Any ideas? -- 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/628a598d-10cc-4d54-a272-4908f6163f1f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-usb needs more than default RAM to mount LUKS encrypted backup volume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bernhard: > > You shouldn't mount encrypted drives on sys-usb. Use qvm-block to attach > > the partition to a different VM, then mount it there. > > > This is a good question, I think. Since we distrust sys-usb I agree that we > should not do the cryptsetup operations in sys-usb. But if you distrust the > attached device as well (might be safer, right?), one might attach the > luks-partition (resp. file) first to an intermediate (even temp !) VM, > luksOpen it in there and re-attach the generated /dev/mapper volumes to the > destination VM. That way sys-usb is blind to cryptsetup and the > destination-vm is maximally protected from usb-based attacks. Overkill? That's basically what Split dm-crypt automates (with even more overkill): https://github.com/rustybird/qubes-split-dm-crypt Rusty -BEGIN PGP SIGNATURE- iQJ7BAEBCgBmBQJbAdM6XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0 NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfO78P+MOUh1UqQeXrpHcwOcj4M/mX z9+5pAXGgCa2t+MinDZTGE8Wvfeb62U/gc8A8Uwqzqs5g1NkGOQER2Z+azMS+Xnt y9XukE3PE8MRA4XgfSZzreh6xOt8AZX8QRTNzlsPet+QjteKGW3B5tk2wBtzeTIU Y+teN5cIKIWWXPy4AZPYbCDK9aXVYd0Za0/Dj6+Tcn1tuoGbOt4Gr1rLigql6Pi9 3Z1cpkK8VecoXIvOixxycYEBNAr6n7pMW35OjBCpbyB0uGHMXcZFqkoBFca2kOOb HQbZwRLMlOQnI6DGF9O0jx5unabsnOli5OUXMWHdn1Xo/PMiNSWez02tNJkCFB/4 byhLi7b6p94DnWGyg4WJCi9XkMQ3nkEtNG0a2obvvjDF6bam0X9dRFwfbT7CiNLV PleQFQjvoLFZJK/tVicnQyQVcTt2KeLD0nzzhqHe+At6XTPeiyBhf8mDERL8pIYr FVws8oRGmKs2UHeRuFT16CmUN59xjrUuZv2Lf2q/I7Zlncv7pnBfQ5V/h+xT/gim 6K3l8xOBrspV4PRO20XAAQZ1i2NaDzZ8HBig+1q3hfhvMlFfzOT6EmrNk/oSTsSh W4XO8R0L8wz5cZjHnJJU99UAooyUWj9jBiLbDd/1UT7RG8apHCXHriUpgMaFnAPo nNT9XnACZNM4zkeA0NI= =Lh2Z -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/20180520195746.GA1257%40mutt. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Librem 13v2: Qubes 4.0 stuck at loading the desktop
Le dimanche 20 mai 2018 17:59:48 UTC+2, awokd a écrit : > On Sun, May 20, 2018 11:00 am, Thib wrote: > Yes, this approach should work but you'll have to use mount commands (and > possibly LVM) directly. Look in /dev/mapper/ to see if your -private > volumes are listed. If so, you should be able to do something like "mount > /dev/mapper/guest-private /mnt" (do a "mkdir mnt" first), then copy the > files out. "umount /mnt" when done and repeat for the next volume. I can see my -private volumes like: <> So, you suggest to copy my files within the VMs on my external drives, not an entire VM-backup just like the backup-tool in the Qubes VM Manager, right? So, if I want to copy a document named "EN.docx" from the VM "vmWin7" to my external drive named "SAMSUNG", how could I proceed? Please show me the required command lines only if you do it willingly, and if it's like a game for you. It can really make my life easier but a 2nd solution could be to recreate all the lost documents. -- 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/9e290dd5-c515-4f1e-b566-c844f4c49cf8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Q4.0 Fedora-26 -> Fedora-28 python3.6 errors
Em domingo, 20 de maio de 2018 15:00:12 UTC-3, jhsd...@gmail.com escreveu: > On Thursday, May 17, 2018 at 8:52:20 AM UTC+3, john wrote: > > On 05/16/18 10:45, john wrote: > > > On 05/16/18 04:16, Blaumeer wrote: > > >> Similar situation, different error. Did upgrade to 28 with the python > > >> exclusions: > > >> > > >> [user@fedora-28 ~]$ sudo dnf --releasever=28 > > >> --setopt=cachedir=/mnt/removable --best --allowerasing distro-sync -x > > >> python2-xcffib -x qubes-gui-vm -x qubes-gui-agent > > >> > > >> Then: > > >> > > >> [user@fedora-28 ~]$ sudo dnf swap python-xcffib python2-xcffib > > >> Error: Failed to synchronize cache for repo 'updates' > > >> > > > > > > interestingly, I just qvm-remove fedora-28 and started over and the > > > 2nd time I got the xcffib error and then redid the install > > > with -x xcffib or so ...and got one error > > > > > > Error: Transaction check error: > > > file /etc/dconf/profile/user from install of > > > dconf-0.28.0-1.fc28.x86_64 conflicts with file from package > > > qubes-core-agent-4.0.24-1.fc26.x86_64 > > > > > > > > > AND then: > > > > > > Error Summary > > > - > > > > > > [user@fedora-28 ~]$ sudo dnf swap python-xcffib python2-xcffib > > > Last metadata expiration check: 0:51:25 ago on Wed May 16 09:52:22 2018. > > > No match for argument: python2-xcffib > > > Error: Unable to find a match > > > > > > > > > > > > > > > but, again no idea how to fix it or if it matters > > > > > > > ..qvm-remove fedora-28 ; and again start from scratch, no errors, > > maybe there really is something to the 3rd time "being the charm" lol... > > > > that, or maybe I was a bit early in the release of the Fed28 templates .. > > > > > > mission complete > > How you did it? I have similar problem. > > sudo dnf --releasever=28 --setopt=cachedir=/mnt/removable--best > --allowerasing distro-sync -x python2-xcffib -x qubes-gui-vm -x > qubes-gui-agent > > > > Error: Transaction check error: > file /etc/dconf/profile/user from install of dconf-0.28.0-1.fc28.x86_64 > conflicts with file from package qubes-core-agent-4.0.24-1.fc26.x86_64 I did in fedora-27 terminal template: sudo dnf clean all; sudo dnf --releasever=28 --allowerasing --best -x python2-xcffib -x qubes-gui-vm -x qubes-gui-agent -x dconf; sudo dnf swap python-xcffib python2-xcffib; sudo dnf update --allowerasing --best enablerepo=qubes-vm*-current-testing; No errors! -- 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/a3442542-979c-4461-8c80-76fd1f9a6376%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-firewall domain start failed
On Sun, May 20, 2018 4:54 pm, apuebl...@gmail.com wrote: > > It works! My BIOS automatically chooses UEFI for the thumb drive chosen to > install. However, it has an option to directly boot any detected device. I > chose the thumb drive with the direct boot option, without UEFI in its > prefix. > > This results in Automatic Partitioning creating a /boot partition for the > bootloader, whereas when choosing to boot the thumb drive with UEFI > prefixed, the installer creates /boot/efi. > > The direct boot allows the installer to finish cleanly. The UEFI boot > results in a failure to create sys-firewall domain for some reason. No more PV mode? Great! Nice catch on the /boot/efi appearing and disappearing. -- 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/e8bb6c492233a05382315937670d9f33%40elude.in. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Q4.0 Fedora-26 -> Fedora-28 python3.6 errors
On Thursday, May 17, 2018 at 8:52:20 AM UTC+3, john wrote: > On 05/16/18 10:45, john wrote: > > On 05/16/18 04:16, Blaumeer wrote: > >> Similar situation, different error. Did upgrade to 28 with the python > >> exclusions: > >> > >> [user@fedora-28 ~]$ sudo dnf --releasever=28 > >> --setopt=cachedir=/mnt/removable --best --allowerasing distro-sync -x > >> python2-xcffib -x qubes-gui-vm -x qubes-gui-agent > >> > >> Then: > >> > >> [user@fedora-28 ~]$ sudo dnf swap python-xcffib python2-xcffib > >> Error: Failed to synchronize cache for repo 'updates' > >> > > > > interestingly, I just qvm-remove fedora-28 and started over and the > > 2nd time I got the xcffib error and then redid the install > > with -x xcffib or so ...and got one error > > > > Error: Transaction check error: > > file /etc/dconf/profile/user from install of > > dconf-0.28.0-1.fc28.x86_64 conflicts with file from package > > qubes-core-agent-4.0.24-1.fc26.x86_64 > > > > > > AND then: > > > > Error Summary > > - > > > > [user@fedora-28 ~]$ sudo dnf swap python-xcffib python2-xcffib > > Last metadata expiration check: 0:51:25 ago on Wed May 16 09:52:22 2018. > > No match for argument: python2-xcffib > > Error: Unable to find a match > > > > > > > > > > but, again no idea how to fix it or if it matters > > > > ..qvm-remove fedora-28 ; and again start from scratch, no errors, > maybe there really is something to the 3rd time "being the charm" lol... > > that, or maybe I was a bit early in the release of the Fed28 templates .. > > > mission complete How you did it? I have similar problem. sudo dnf --releasever=28 --setopt=cachedir=/mnt/removable--best --allowerasing distro-sync -x python2-xcffib -x qubes-gui-vm -x qubes-gui-agent Error: Transaction check error: file /etc/dconf/profile/user from install of dconf-0.28.0-1.fc28.x86_64 conflicts with file from package qubes-core-agent-4.0.24-1.fc26.x86_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/8184b5bf-f029-4b2e-b8ae-834c16b85657%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-firewall domain start failed
On Sunday, May 20, 2018 at 12:04:51 PM UTC-4, awokd wrote: > On Sun, May 20, 2018 3:15 pm, apuebl...@gmail.com wrote: > > On Sunday, May 20, 2018 at 9:36:36 AM UTC-4, apue...@gmail.com wrote: > >> On Sunday, May 20, 2018 at 9:34:39 AM UTC-4, apue...@gmail.com wrote: > > >> > Thanks for replying! Makes sense. But sys-net still won't start unless > >> in PV mode, like all other VMs. NICs attached or detached is > >> irrelevant. I've even tried not allowing the installer to create them, > >> as in making sys-VMs from scratch with the same result. > >> > > >> > Debian/Fedora templates make no difference. > >> > Attach options make no difference. Sys-net attempts to start, pop-up > >> notification states it has started, but never goes pass the yellow > >> state. Refresh qube list reveals it goes back into off state. > >> > > >> > Nothing starts without PV mode. :( > >> > >> It seems that firewall being unable to start during the installation's > >> final configuration makes Qubes believe there is some kind of > >> incompatibility? > > > > > > What are the default partitions created because I'm seeing a discrepancy > > now. At times I see /boot/efi - 200MB. At others, it is only /boot at > > 1024MB... ? Could this be the problem? > > If you're booting in UEFI mode, you should always see /boot/efi. Is it > possible some other bootloader is running before Qubes'?. I've heard of > viruses that act that way too, but maybe it's just a bug in your UEFI. > Assuming there is nothing else on your hard drive you need to keep, try to > reinstall Qubes, select "I want to make space available", tell it to erase > everything, and let it auto partition. It works! My BIOS automatically chooses UEFI for the thumb drive chosen to install. However, it has an option to directly boot any detected device. I chose the thumb drive with the direct boot option, without UEFI in its prefix. This results in Automatic Partitioning creating a /boot partition for the bootloader, whereas when choosing to boot the thumb drive with UEFI prefixed, the installer creates /boot/efi. The direct boot allows the installer to finish cleanly. The UEFI boot results in a failure to create sys-firewall domain for some reason. -- 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/3d437a65-393e-48c3-aeec-f8aec379f3a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-firewall domain start failed
On Sun, May 20, 2018 3:15 pm, apuebl...@gmail.com wrote: > On Sunday, May 20, 2018 at 9:36:36 AM UTC-4, apue...@gmail.com wrote: >> On Sunday, May 20, 2018 at 9:34:39 AM UTC-4, apue...@gmail.com wrote: >> > Thanks for replying! Makes sense. But sys-net still won't start unless >> in PV mode, like all other VMs. NICs attached or detached is >> irrelevant. I've even tried not allowing the installer to create them, >> as in making sys-VMs from scratch with the same result. >> > >> > Debian/Fedora templates make no difference. >> > Attach options make no difference. Sys-net attempts to start, pop-up >> notification states it has started, but never goes pass the yellow >> state. Refresh qube list reveals it goes back into off state. >> > >> > Nothing starts without PV mode. :( >> >> It seems that firewall being unable to start during the installation's >> final configuration makes Qubes believe there is some kind of >> incompatibility? > > > What are the default partitions created because I'm seeing a discrepancy > now. At times I see /boot/efi - 200MB. At others, it is only /boot at > 1024MB... ? Could this be the problem? If you're booting in UEFI mode, you should always see /boot/efi. Is it possible some other bootloader is running before Qubes'?. I've heard of viruses that act that way too, but maybe it's just a bug in your UEFI. Assuming there is nothing else on your hard drive you need to keep, try to reinstall Qubes, select "I want to make space available", tell it to erase everything, and let it auto partition. -- 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/f7116c8f916e4d974a5c10a69e905ea6%40elude.in. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Librem 13v2: Qubes 4.0 stuck at loading the desktop
On Sun, May 20, 2018 11:00 am, Thib wrote: > << > Qubes, with Xen 4.8.3 and Linux 4.14.18-1.pvops.qubes.x86_64 >>> > Then I press Enter but at the end it still stuck at user-password after > the following message: https://share.riseup.net/#j_PGs-isYm9Hot3AW2aSdQ This rules out the recent kernel update then- 4.14.18-1 is the older one. > I'm open for more advice :) My goal is to recover the documents from some > VMs (accounting, vmWin7, vault, untrusted, personal, work, archives). So > perhaps it's possible to create a backup of my VMs on my external drive by > entering commands in "Rescue a Qubes system" and then reinstall Qubes 4.0? > What do you think about it? Yes, this approach should work but you'll have to use mount commands (and possibly LVM) directly. Look in /dev/mapper/ to see if your -private volumes are listed. If so, you should be able to do something like "mount /dev/mapper/guest-private /mnt" (do a "mkdir mnt" first), then copy the files out. "umount /mnt" when done and repeat for the next volume. If you don't see the /dev/mapper/ entries, look into LVM commands like vgscan and kpartx. -- 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/a16ac5ff87a9201e037355d114193cea%40elude.in. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Default 'revisions_to_keep'
On Sun, May 20, 2018 9:27 am, donoban wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 05/20/18 03:58, Marek Marczykowski-Górecki wrote: >> Actually, revisions_to_keep is about previous revisions. So "1" >> means you have one snapshot you can revert to (the state before >> you've started the VM). >> > > But was (and will be) this snapshot saved when you shutdown the VM? > > Imagine you accidentally delete an important file, how can you use the > snapshot for recover it? Doing revert with the VM running? If you > shutdown the VM the snapshot with the important file will be lost. I think it replaces the snapshot with a new one at VM start, not shutdown. So if you delete a file, shutdown the VM, then revert immediately, you'll be OK. -- 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/3ec68f4f55003f632bffba92b6dc3aa9%40elude.in. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-firewall domain start failed
On Sunday, May 20, 2018 at 9:36:36 AM UTC-4, apue...@gmail.com wrote: > On Sunday, May 20, 2018 at 9:34:39 AM UTC-4, apue...@gmail.com wrote: > > > > 2016-07-26 00:01:02.935+: libxl: > > > > libxl_device.c:1081:device_backend_callback: unable to add device with > > > > path /local/domain/5/backend/vif/7/0 > > > > 2016-07-26 00:01:02.935+: libxl: > > > > libxl_create.c:1512:domcreate_attach_devices: unable to add nic devices > > > > > > I think the above is saying it can't start sys-firewall because sys-net is > > > down (and your date also seems pretty far off). Is sys-net running? If > > > not, note what devices are attached to sys-net, remove them, then see if > > > it starts. If it does, shut it back down, add your NIC back in, and again > > > see if it starts. If not, troubleshoot by trying the Debian template > > > instead of Fedora as well as the attach options described here > > > https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues. > > > > Thanks for replying! Makes sense. But sys-net still won't start unless in > > PV mode, like all other VMs. NICs attached or detached is irrelevant. I've > > even tried not allowing the installer to create them, as in making sys-VMs > > from scratch with the same result. > > > > Debian/Fedora templates make no difference. > > Attach options make no difference. Sys-net attempts to start, pop-up > > notification states it has started, but never goes pass the yellow state. > > Refresh qube list reveals it goes back into off state. > > > > Nothing starts without PV mode. :( > > It seems that firewall being unable to start during the installation's final > configuration makes Qubes believe there is some kind of incompatibility? What are the default partitions created because I'm seeing a discrepancy now. At times I see /boot/efi - 200MB. At others, it is only /boot at 1024MB... ? Could this be the problem? -- 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/e5608288-c16a-4a50-a5e6-38fc27a4214a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-firewall domain start failed
On Sunday, May 20, 2018 at 9:34:39 AM UTC-4, apue...@gmail.com wrote: > > > 2016-07-26 00:01:02.935+: libxl: > > > libxl_device.c:1081:device_backend_callback: unable to add device with > > > path /local/domain/5/backend/vif/7/0 > > > 2016-07-26 00:01:02.935+: libxl: > > > libxl_create.c:1512:domcreate_attach_devices: unable to add nic devices > > > > I think the above is saying it can't start sys-firewall because sys-net is > > down (and your date also seems pretty far off). Is sys-net running? If > > not, note what devices are attached to sys-net, remove them, then see if > > it starts. If it does, shut it back down, add your NIC back in, and again > > see if it starts. If not, troubleshoot by trying the Debian template > > instead of Fedora as well as the attach options described here > > https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues. > > Thanks for replying! Makes sense. But sys-net still won't start unless in PV > mode, like all other VMs. NICs attached or detached is irrelevant. I've even > tried not allowing the installer to create them, as in making sys-VMs from > scratch with the same result. > > Debian/Fedora templates make no difference. > Attach options make no difference. Sys-net attempts to start, pop-up > notification states it has started, but never goes pass the yellow state. > Refresh qube list reveals it goes back into off state. > > Nothing starts without PV mode. :( It seems that firewall being unable to start during the installation's final configuration makes Qubes believe there is some kind of incompatibility? -- 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/2fbdecbe-361d-445d-8198-4f88e1b211a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-firewall domain start failed
> > 2016-07-26 00:01:02.935+: libxl: > > libxl_device.c:1081:device_backend_callback: unable to add device with > > path /local/domain/5/backend/vif/7/0 > > 2016-07-26 00:01:02.935+: libxl: > > libxl_create.c:1512:domcreate_attach_devices: unable to add nic devices > > I think the above is saying it can't start sys-firewall because sys-net is > down (and your date also seems pretty far off). Is sys-net running? If > not, note what devices are attached to sys-net, remove them, then see if > it starts. If it does, shut it back down, add your NIC back in, and again > see if it starts. If not, troubleshoot by trying the Debian template > instead of Fedora as well as the attach options described here > https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues. Thanks for replying! Makes sense. But sys-net still won't start unless in PV mode, like all other VMs. NICs attached or detached is irrelevant. I've even tried not allowing the installer to create them, as in making sys-VMs from scratch with the same result. Debian/Fedora templates make no difference. Attach options make no difference. Sys-net attempts to start, pop-up notification states it has started, but never goes pass the yellow state. Refresh qube list reveals it goes back into off state. Nothing starts without PV mode. :( -- 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/9beab712-4d73-43a9-9e4a-6e98c9ddb9af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Librem 13v2: Qubes 4.0 stuck at loading the desktop
Le jeudi 17 mai 2018 15:11:21 UTC+2, platschi a écrit : > https://share.riseup.net/#9tAE4-t7G8clcYXQxGQQVA > > sys-net not working properly with older kernel though :/ @awokd @platschi I'm grateful for your information. I tried what you said, but it still doesn't work: When I select "Advanced options for Qubes" I have 3 alternatives: << 1. Xen hypervisor, version 4.8.3 2. Xen hypervisor, version 4.8.3.config 3. Xen hypervisor, version 4.8 >> When I select the 1st alternative, I have: << Qubes, with Xen 4.8.3 and Linux 4.14.18-1.pvops.qubes.x86_64 >> Then I press Enter but at the end it still stuck at user-password after the following message: https://share.riseup.net/#j_PGs-isYm9Hot3AW2aSdQ When I select the 2nd, I have: << Loading Xen 4.8.3.config ... error: no multiboot header found. Loading Linux 4.14.18-1.pvops.qubes.x86_64 ... error: you need to load the kernel first. Loading initial ramdisk ... error: you need to load the kernel first. Press any key to continue... >> Here nothing happens. When I select the 3rd, I have: << Qubes, with Xen 4.8 and Linux 4.14.18-1.pvops.qubes.x86_64 >> Then I press Enter but at the end it still stuck at user-password after the following message: https://share.riseup.net/#VogDUuIl4FHqx2_EetnhXA I'm open for more advice :) My goal is to recover the documents from some VMs (accounting, vmWin7, vault, untrusted, personal, work, archives). So perhaps it's possible to create a backup of my VMs on my external drive by entering commands in "Rescue a Qubes system" and then reinstall Qubes 4.0? What do you think about it? -- 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/58edffda-162a-4a62-814b-bd4c24adf3b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Default 'revisions_to_keep'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/20/18 03:58, Marek Marczykowski-Górecki wrote: > Actually, revisions_to_keep is about previous revisions. So "1" > means you have one snapshot you can revert to (the state before > you've started the VM). > But was (and will be) this snapshot saved when you shutdown the VM? Imagine you accidentally delete an important file, how can you use the snapshot for recover it? Doing revert with the VM running? If you shutdown the VM the snapshot with the important file will be lost. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlsBP5kACgkQFBMQ2OPt CKW94A/9FZiSXPyXJyLLxz28NwoQ7YL4EpKFJqzDfQ630uqzq1YyFytn3cgsiEBR ZyUY//1KwWqsH4NkCzCT7hEv6lg5FDRyBDErzdsGleKBQ/scrN9XP852ff3uFoDp noLekYo8f8+aJbeY06M42PGJj/xYh2GNc16e1I4douvbK+R+QVl6gYowBjB+V4aL +ZGobJrCtQ3/MXNIw18Ggi/Cpznuva2YhepUPd0OouD+S8th10AbweZ97YaLrkIO hn8h88IT7ggtpF+CB7TpyLrr7gC8A3MluvcRXQLPW2dhTmIMzuJDeVlhDL0bREw0 2+CroALSLm0D03yZH+6PdzHykbA2Or+PqoUoFpQCtkATM3TtuQZ+NH+uCTr1SJDa JZfRdA91V1glxDlI0rWjo78qV4thQLWAES/okK+BEIFzk+JQGd70DHKQXtKEkNM/ B9O86wHwu5bCx1WPlY9j3s6sf85TMzc8e6aK2Q0gaJRBLF62qr2JisIiodCH0Ui4 T9s7JXu6tOlpd8kyCNJnINAPZtuw26y2AYAuuuiqFEvnONVNqfsb5dg3NKvI3YzL KKw4IwsrmFF1zPq7xEyQ//UjPs1ob0FCCO3Z7BpO53X2bPNlVthEWwyyvvaUKXSB zuLmlDZjZrWAekhjRcg88dyg+oMyLBcR/ovoW3O6gNTnNLdchQA= =Q8CA -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/e7ba5f43-a408-41aa-ba0e-c5c66e152bed%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 - Intel 9260 Firmware not found.
On Sun, May 20, 2018 7:46 am, Alchemist wrote: > Has anyone been able to get an Intel 9260 working in 3.2? I just installed > one in my laptop the other day and Qubes can't seem to load it. > > Dmesg return a firmware not found, when I go to download the firmware and > move it into /usr/lib/firmware sys-net fails to start. It sounds like you're manually installing the firmware? Install the firmware package with dnf (or apt on Debian) into the template underlying sys-net instead. > I've tested using a Fedora 23 and 26 NetVM neither seem to work, any > advice would be appreciated. Try the Debian template instead too. -- 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/e5b800a3826132b254c8f438fd83af61%40elude.in. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-firewall domain start failed
On Sun, May 20, 2018 2:54 am, apuebl...@gmail.com wrote: > 2016-07-26 00:01:02.935+: libxl: > libxl_device.c:1081:device_backend_callback: unable to add device with > path /local/domain/5/backend/vif/7/0 > 2016-07-26 00:01:02.935+: libxl: > libxl_create.c:1512:domcreate_attach_devices: unable to add nic devices I think the above is saying it can't start sys-firewall because sys-net is down (and your date also seems pretty far off). Is sys-net running? If not, note what devices are attached to sys-net, remove them, then see if it starts. If it does, shut it back down, add your NIC back in, and again see if it starts. If not, troubleshoot by trying the Debian template instead of Fedora as well as the attach options described here https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues. -- 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/dba765d663451e5ca22e73d6f41d1a8e%40elude.in. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sys-usb needs more than default RAM to mount LUKS encrypted backup volume
On Sat, May 19, 2018 10:12 pm, Alex wrote: >>You shouldn't mount encrypted drives on sys-usb. Use qvm-block to >>attach >>the partition to a different VM, then mount it there. > > Can you elaborate? > > 1. What's the security benefit? Sys-usb, like sys-net, exist to protect the rest of your system from potentially compromised hardware devices and low level attacks. Say you plugged in a USB drive you happened to find laying on your front doorstep, and it managed to compromise sys-usb but not your other VMs. If you then passed through a second drive with qvm-block, the bad sys-usb still wouldn't have access to the decrypted contents, but would if it's mounted directly in sys-usb. > 2. What are the steps to correctly restore by Qubes backups from a USB > disk? Mounting it directly in sys-usb is "correct" in that it works, but suggest something like https://www.mail-archive.com/qubes-users@googlegroups.com/msg17265.html. > 3. Is there anything in the backup tool UI that guides users towards the > workflow you describe? No. Closest might be the introduction to the https://www.qubes-os.org/doc/usb/#creating-and-using-a-usb-qube section, but I can't remember any more exactly where I learned this. Would it help if it were in the FAQ section and/or backup/restore guide? -- 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/19ba74141f4be5f14042314e092a38b0%40elude.in. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: why Whonix and not Tails or the anon-vm?
On Sat, May 19, 2018 12:45 pm, qubes-...@tutanota.com wrote: > Qubes is not amnesic, and therefore not suitable for running amnesic > Tails. Therefore the decission for non- amnesic Whonix, running itself by > default, in a virtual environment loved by Qubes. Disposable VMs (including whonix-ws-dvm) are at least partly amnesic. Once you shut it down, you aren't going to recover the contents easily. Tails running directly on hardware is more amnesic. Tails running in an HVM is somewhere in between. See https://github.com/QubesOS/qubes-issues/issues/2024 and links in 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/2923e90300da37a0a64654aa9711a132%40elude.in. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 - Intel 9260 Firmware not found.
Has anyone been able to get an Intel 9260 working in 3.2? I just installed one in my laptop the other day and Qubes can't seem to load it. Dmesg return a firmware not found, when I go to download the firmware and move it into /usr/lib/firmware sys-net fails to start. I've tested using a Fedora 23 and 26 NetVM neither seem to work, any advice would be appreciated. -- 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/79e6a26c-c6db-4022-937e-f423ac099e43%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
