Re: [qubes-users] Please help with 8th Generation Intel i5
On Fri, January 19, 2018 11:32 am, Krišjānis Gross wrote: > On Thursday, 18 January 2018 20:56:10 UTC, donoban wrote: >> >> (EE) VESA(0): V_BIOS address 0xaa7a0 out of range >>> A side question- how can I copy the logs in /tmp to a flash drive or >>> something in order to post those here? Can you get sys-usb started? If so, use qvm-copy-to-vm in dom0 to copy the logs to a VM, then to the flash drive. Otherwise, you could boot with a live image of some type, mount the hard drive and copy out the logs. > Thank You for the suggestion! Will check that out. > I tried to install Debian 9 on this hardware and all went fine. Only thing > that I noticed when installation was finished was that there was a > notification that system is running a " software emulated graphics" and > therefore CPU usage might be considerably higher. Not sure whether that > is relevant though. Both seem unhappy with your video card. What's in that laptop? Please post Debian's boot log (redact hardware serial numbers & MAC addresses), and Qubes' xl dmesg log if you can get 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/b519c85a88c014b796bfd0fea7a4eb50.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote: > Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk: > >> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: >> >>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote: >>> >>> Try turning off memory-management and give the sys-net an initial >>> amount of something like 800MB. Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory balancing" and increase initial memory to 800. See if there are any other errors in dom0 with "sudo journalctl -b" when you start the VM. -- 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/53335dad85efbad2d215fb489dd7d4e1.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Using fedora-26-minimal sys-vms
Hello, I want to use fedora-26-minimal based sys-vms and followed the documentation (https://www.qubes-os.org/doc/templates/fedora-minimal ) I have updated the default fedora-26-minimal template and installed all packages mentioned in the docs (Qubes 4.0 part of the above documentation link) plus all firmware packages. What do I need to install to get the network manager icon working? NetworkManager is installed in the template and I have verified in the sys-net VM that it is running: systemctl status NetworkManager Says: active (running) I tried to start NetworkManager from command line, but got the message: You must be root to run NetworkManager. I then started a xterm from dom0 as the Root user: qvm-start -u root sys-net NetworkManager but nothing happened. I also try to do this from a xterm session (qvm-start -u root sys-net xterm). Any ideas how to get a sys-net which has a working network manager? [799] -- 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/BbBUvPEuJO1mn1_nuijkn0vBxPn5xAorFclHFOsQUwXeKtaNWwMhl8VHFATTVmmwWbXI2Nd8SGeKn6YPoIJ7n5XvDKzRXgdfSCt4PGZkxU8%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote: > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd: > >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote: >> >>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev >>> a...@it-minds.dk: >>> >>> >>>> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: >>>> >>>> >>>>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users >>>>> wrote: >>>>> >>>>> >> >>>>> Try turning off memory-management and give the sys-net an initial >>>>> amount of something like 800MB. >> >> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory >> balancing" and increase initial memory to 800. >> >> See if there are any other errors in dom0 with "sudo journalctl -b" >> when you start the VM. > > Can I disable it through qvm-prefs? Because my qubes manager (the GUI is > back again now) is broken.. Yes, type qvm-prefs sys-net to see a list of settings. qubes-vm-settings sys-net should also give you the gui. -- 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/e4a8eb7ce62c2569bc5cdf9338b1b4c3.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd: > On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote: > > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd: > > > >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote: > >> > >>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev > >>> a...@it-minds.dk: > >>> > >>> > >>>> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: > >>>> > >>>> > >>>>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users > >>>>> wrote: > >>>>> > >>>>> > >> > >>>>> Try turning off memory-management and give the sys-net an initial > >>>>> amount of something like 800MB. > >> > >> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory > >> balancing" and increase initial memory to 800. > >> > >> See if there are any other errors in dom0 with "sudo journalctl -b" > >> when you start the VM. > > > > Can I disable it through qvm-prefs? Because my qubes manager (the GUI is > > back again now) is broken.. > > Yes, type qvm-prefs sys-net to see a list of settings. qubes-vm-settings > sys-net should also give you the gui. Sorry. Which setting exactly disables dynamic memory allocation, because I can't seem to figure it out. If I set maxmem to 0, will it disable it? The GUI is broken. It comes up with an error if I try to start it, no matter how I try to start it. It complains about a bug, but that isn't really important right now. -- 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/71be7916-6e82-4265-8844-ca25d5c1106b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skrev a...@it-minds.dk: > Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd: > > On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote: > > > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd: > > > > > >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote: > > >> > > >>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev > > >>> a...@it-minds.dk: > > >>> > > >>> > > >>>> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander: > > >>>> > > >>>> > > >>>>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users > > >>>>> wrote: > > >>>>> > > >>>>> > > >> > > >>>>> Try turning off memory-management and give the sys-net an initial > > >>>>> amount of something like 800MB. > > >> > > >> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory > > >> balancing" and increase initial memory to 800. > > >> > > >> See if there are any other errors in dom0 with "sudo journalctl -b" > > >> when you start the VM. > > > > > > Can I disable it through qvm-prefs? Because my qubes manager (the GUI is > > > back again now) is broken.. > > > > Yes, type qvm-prefs sys-net to see a list of settings. qubes-vm-settings > > sys-net should also give you the gui. > > Sorry. > > Which setting exactly disables dynamic memory allocation, because I can't > seem to figure it out. If I set maxmem to 0, will it disable it? > > The GUI is broken. It comes up with an error if I try to start it, no matter > how I try to start it. It complains about a bug, but that isn't really > important right now. Okay! I set the maxmem to 1 (cannot set it to 0) and initial mem to 800. sys-net starts now. I am updating my system now, hopefully this will disappear on its own. Any deeper insight as to the 'why'? I am kind of confused.. Without your guys' suggestions I would have been lost.. Thanks a bunch! -- 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/59912f3c-476f-494d-9bc8-5a77a8f379f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
On Fri, January 19, 2018 2:53 pm, aaq via qubes-users wrote: > > I set the maxmem to 1 (cannot set it to 0) and initial mem to 800. > sys-net starts now. Good! In theory it should work too if you leave maxmem at 4000. > I am updating my system now, hopefully this will disappear on its own. > > > Any deeper insight as to the 'why'? > I am kind of confused.. Zander? -- 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/1cda744977ce902ad165299c0f13b189.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
AW: Re: [qubes-users] Another "Best Hardware" 4 VMs setup question.
Davidson wrote: > I am running 3.2, have 16gb mem, and a > Samsung ssd drive and it still takes 10 sec > (timed it) to put up a terminal in a new vm I am also interested in comparing App(VM) start times, to compare the performance. I have run the following test after boot and with only sys-firewall and sys-net running: Test on my Lenovo x230 Intel Core i5-3320M @ 2.60Ghz 16 GB RAM 500 GB SanDisk SSD Qubes 4.0rc3 Coreboot'able startup/boot till xterm window = 17sec (normal AppVM) startup/boot till xterm window = 21sec (Disposable AppVM) Test on my Lenovo W540 Intel Core i7-4900MQ @ 2.8 Ghz 16 GB RAM 480 GB Samsung SSD Qubes 4.0rc3 Not Coreboot'able startup/boot till xterm window = 15sec (normal AppVM) startup/boot till xterm window = 16sec (Disposable AppVM) If the AppVM is already running launching new applications is done within in 1 or 2 sec. Your question regarding hardware recommendation: I would look at the Coreboot HCL/Compatibility List and choose a model which fits your preferred display size and resolution. https://www.coreboot.org/Supported_Motherboards Using Coreboot you can also remove large parts of Intel ME. Then as a 2nd test check the Qubes HCL https://www.qubes-os.org/hcl/ [799] -- 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/ZZb07xj5Bxb2MPWCOFsK9ggitygqGD_gIUiIs59RUxbFXiTR7ldGL9wqatBqd0Xynbp09egpUOUwCXSTwZHO_fZ8eWHB-y_FjGB_6PXo_Dw%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
AW: Re: [qubes-users] Using fedora-26-minimal sys-vms
Hello, Unman wrote: > You DO have a working network manager - > see the response from systemctl. > I assume what you want is a nice gui > interface this is nm-applet. If it is installed, > start it and you will get the nice tray icon - if > not installed, install it. I was able to get Network Manager running and instead of using the default "fat" fedora-templates, I am now running the sys-VMs with fedora-26-minimal templates. I was always wondering why Qubes doesn't come with a dedicated sys-template, so that the sys VMs (sys-net | sys-firewall | sys-usb) are running with a smaller/maybe even hardened template. For the Google Archive a short how-to, how I have built the template for the sys-VMs: --- --- --- 8# Install default minimal template in dom0 sudo qubes-dom0-update qubes-template-fedora-26-minimal # Clone template to keep the original template qvm-clone fedora-26-minimal t-sys # Launch xterm in the new template as root qvm-run -u root t-sys xterm # Install basic applications in the template VM sudo dnf -y install gnome-terminal terminus-fonts less vim-minimal nano dejavu-sans-fonts # install basic tools dnf -y install sudo pciutils psmisc gnome-keyring # Install missing packages für Sys-VMs dnf -y install qubes-core-agent-qrexec qubes-core-agent-systemd qubes-core-agent-passwordless-root qubes-core-agent-nautilus qubes-core-agent-networking qubes-core-agent-network-manager qubes-core-agent-dom0-updates pulseaudio-qubes usbutils # Install missing drivers (to support the network devices) dnf -y install linux-firmware iwl7260-firmware # install additional packages to get network manager working dnf install -y NetworkManager NetworkManager-wifi network-manager-applet wireless-tools # shutdown template shutdown -h now # Change Templates for sys-VMs in dom0 qvm-prefs --set sys-net template t-sys qvm-prefs --set sys-firewall template t-sys qvm-prefs --set sys-usb template t-sys --- --- --- 8 [799] -- 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/-BuSXf2YMvlH0cwfdLE7WPqqYBMjDeV3JAj5CIthJ0Ri61D74wyUpvaGiO_NZ2AVV8WxzXzdrH8Rwimf-IFACspMTgWegOvXXhb-8N4iYsw%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to get to command line for dom0?
On Sat, January 20, 2018 8:46 pm, Kyle Breneman wrote: > I am trying to follow these steps > <https://www.qubes-os.org/doc/template/fedora/upgrade-23-to-24/> to > upgrade from Fedora 23 to Fedora 24 (and then from 24 to 26), but I got > stuck right away because I cannot figure out how to get to a command line > window for dom0. Can someone please tell me, or point to documentation > which explains? I've done several web searches without finding an answer. Click the Q button, then Terminal Emulator. Recommend not trying to upgrade though, rather you "sudo qubes-dom0-update qubes-template-fedora-26". This will start you off with a fresh 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/4fa7fbf62099ac88401f46c11bd964f3.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
AW: Re: AW: [qubes-users] Alt-Tab not passed through
Hello, [799] wrote: >> Is there anything I can do, so that Alt+Tab is >> not (!) working in dom0 but in the AppVM >> window / in the virtual desktop connection? mossy-nw answered: > I'm not sure you want to do this, e.g. if your > virtual desktop ever ends up in full-screen > mode, there are security reasons why you > want alt-tab as a sanity check to be sure > you're in direct communication with dom0. > Could you assign a different shortcut > (SHIFT-CTRL tab?) within the VM? I haven't thought about the Alt+Tab behaviour as a (security) feature - thank you for the interesting view. I have chosen to come up with a workarround as solution to switch my Apps in my virtual desktop window: 1) Download Autohotkey in the virtual desktop 2) Create a my-autohotkey.ahk configuration file with the following entries: LAlt & w::AltTab LAlt & q::ShiftAltTab 3) run Autohotkey with the above configuration I am now able to switch windows back & forward using Alt + Q and Alt + W, which is good enough. [799] -- 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/aaGK4T9a58873cage7VERtwbNHqFKUGtknfEIWJUWTKcN0250jE8xx0f0FHdPOraCNRnjyk5lE6g6d8fI4JuObqrk-A3f91kEse50T0-SgE%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
AW: Re: [qubes-users] Created new fedora-26 dvm, how to delete old dvm
> I tried to remove the default DVM, but it didn't > work. What do I need to > do, to get rid of the > old (Fedora 25 based) DVM which comes with > the default Qubes 4rc3 > isntallation ? After some trial and error I found out what was causing the problem, deleting the default fedora-25-dvm and the fedora-25 template. I had not only to migrate all AppVMs to the new fedora-26 template, I also had to edit /var/lib/qubes/qubes.xml and change the entries default_template and default_dispvm from fedora-25 to fedora_26. After that I was able to qvm-remove the fedora-25-dvm and also the fedora-25 template via sudo dnf remove qubes-template-fedora-25 [799] -- 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/_wbkzGY79kVeiPvZCdx5yvLLWLA_Xz4df_VLCSAZOPZs7eGsnulKxvtRWenKCQCLn9eJxAJpR6IfKiJrScjcFdj7JxDxwc4yEu49g8GVOeI%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] No network (HELP)
Qubes 4 RC3 So, I updated using current testing yesterday, and there was an update to qubes core dom0 and other changes.. Network worked fine before I shutdown my machine, but now when I try to start sys-net I get an error saying "Not enough memory to start domain 'sys-net'" I have tried rebooting, and I have tried upscaling and downscaling the initial memory to sys-net with qvm-prefs sys-net memory XX I can start my templateVM's with no issue (eg fedora-26 which is my template for sys-net/sys-firewall, and I have tried starting my debian 9 template). What can I do :S Needless to say it is pretty fatal for me that I have no network. Thanks in advance. -- 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/34fa87a3-eedc-4c6a-982e-16c61257e769%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] No network (HELP)
Den fredag den 19. januar 2018 kl. 16.39.31 UTC+1 skrev Marek Marczykowski-Górecki: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Fri, Jan 19, 2018 at 06:53:55AM -0800, aaq via qubes-users wrote: > > Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skrev a...@it-minds.dk: > > > Which setting exactly disables dynamic memory allocation, because I can't > > > seem to figure it out. If I set maxmem to 0, will it disable it? > > > > > > The GUI is broken. It comes up with an error if I try to start it, no > > > matter how I try to start it. It complains about a bug, but that isn't > > > really important right now. > > It's a bit obscure, see qvm-service. "meminfo-writer" service is > responsible for memory balancing. But it should be already in "off" > state for sys-net. > > > I set the maxmem to 1 (cannot set it to 0) and initial mem to 800. > > This is maximum memory size in MB. Setting it to 1 doesn't sounds like a > good idea, but... for VMs with PCI devices it is ignored and "memory" > property is used instead (because of Xen limitation, namely > populate-on-demand being incompatible with PCI-passthrough). > > 400MB should be enough for sys-net, in some cases even lower number > should suffice. > > > sys-net starts now. > > > > I am updating my system now, hopefully this will disappear on its own. > > There were a bunch of fixes yesterday (late) evening, including one for > qmemman, and GUI stuff. Make sure you have: > > qubes-core-dom0 4.0.18 > qubes-core-admin-client 4.0.13 > qubes-manager 4.0.11 > qubes-dbus 1.0.4 > > Specifically qmemman was broken in qubes-core-dom0 in 4.0.16 and 4.0.17. > > - -- > 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- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpiEQ4ACgkQ24/THMrX > 1ywPywf/Tl8SsGq0NQ5zQC2uiMIWrkEipbRj0hMkeeqIIQQpgzn101bDlLgoud+w > JzbBUfRqA1tO2KUWhOG0XRcuUiRQszOhR95p13hMsoEm4Nnxu0chFietPe7aOQZx > sMQqr3BjHkJxtYh780F6reke9Ec0fvkxANnKC4J53YocEQSIGtqX7GSUuxdEYM0K > T02DpNJJseocFO6s2G8aTqQpTiorl+mWVvdL8PjzlJ7XOduLVtHna3sZL5LrbP18 > 3SsTWZQ5bhRfk/3Elt0t26UYe+Aeyeyxric/HCbe7nmWqxrNqqnZkjpNXkFZi+9F > oDHvHUm5N834oxlidhG2gGwr0u2bCw== > =w6SK > -END PGP SIGNATURE- Thanks again! -- 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/82a29f20-68c9-4ee8-b942-f0c1ecc1fd0f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: [qubes-devel] Qubes Controller as the new Qubes-Manager
Den lørdag den 6. januar 2018 kl. 12.27.18 UTC+1 skrev Tom Zander: > On Saturday, 6 January 2018 00:11:43 GMT Franz wrote: > > I would add some way to make some order in the > > applVM list, so that a standard view may show only the most commonly used > > VMs, while rarely used VMs are hidden and shown only clicking a button. To > > do that, there should be a flag to differentiate the visibility of VMs. > > I made a start with this based on my own usage; See the attached > screenshots. > Going from screenshot1 (showing all my qubes) to 5 by removing ones based > on; > * being templates for disposable VMs. (you likely never want to start them > after initial configuration). > * being a "network" VM. > * Being a template. > * Being halted. > > Naturally you can combine those settings in any way you want to show the > subsection of qubes you use. > I expect that I''l end up using the settings as "snapshot4" shows it most of > the time. > > > This may be helpful also in a corporate environment when an administrator > > can decide which VMs should be shown and which should be hidden. > > This is a great idea, I recall that root added tags in 4.0. I have not tried > them yet, but it sounds like a good fit. > > Thanks for the ideas! > > -- > Tom Zander > Blog: https://zander.github.io > Vlog: https://vimeo.com/channels/tomscryptochannel This is amazing though, good job Tom! -- 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/3945ab58-c37a-47ec-afb5-066137bccca6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
AW: [qubes-users] help, trying to make custom launchers
pixel fairy wrote: >> qubes 4.0rc3 Id like to make custom >> launchers for two purposes [...] Hello pixel fairy, My suggestion is: don't spend time playing around tweaking custom . desktop files. I have installed menulibre in dom0 and I am now able to tweak my menu through a comfortable GUI. https://bluesabre.org/projects/menulibre/ As an additional benefit it is also very easy to hide menu items you don't need and you can reorder the menu. qubes-dom0-update menulibre If you want this additional comfort through installing additionall packages in dom0 is up to you - most users don't like to go this road. You can also install menulibre by downloading the package manually. Suggestion: Having a default installation of menulibre in dom0 (through the Qubes Team) Regards [799] -- 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/PGMymgXLyYUSJebI-TWJ_PAgN1eBgntDq1t7Q_yL7ER3vGYeJFA_yVN8DR2ob4_w4LV0ENHfpzo106SJaDOpuNOaMXg_kmXWXDivVryNXrs%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Recovery questions
On Mon, January 22, 2018 4:54 pm, Brian LoBue wrote: > Error starting VM work: VM root image doesn't exist > /var/lib/qubes/vm-templates/fedora-23/root.img > Is there a way to reinstall fedora-23 and get sys-net and my app vms to > work again? I'm not aware of a way to reinstall just the fedora-23 template from the install image. > If not and I need to reinstall that's fine. I just need a few files from > some app vms. > > I found this method to copy from vms to dom0 so I could backup files > > > https://www.qubes-os.org/doc/copy-from-dom0/ Unfortunately, you'd need to be able to start the appvms to use this method. > Where are the app vm files stored? Are the files available from dom0 with > the VM not running? If possible, suggest you run a backup of the VMs with the GUI interface instead of trying to access the files directly. You'd need to attach another drive accessible to dom0 temporarily to backup to. If you go this route, make sure to disconnect it prior to the reinstall so the installer doesn't mess with it, then reconnect when done and restore. The actual VM .img files are under /var/lib/qubes/appvms. You could copy out those appvms' .img files directly to your backup drive, then mount them from within a VM after a reinstall but again, make sure to disconnect your backup drive for the install. Might not be a bad idea to copy these over directly in addition to the backup, in case the backup/restore process gets confused by missing templates. -- 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/74761911a80dff5705f064f561ea75e5.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] how to install new template and appvm?
On Mon, January 22, 2018 5:17 pm, jerr...@disroot.org wrote: > what is the command to install whonix-ws and anon-whonix? the full > specific command "sudo qubes-dom0-update qubes-template-whonix-ws" for the ws template. Not sure there's a documented process for creating anon-whonix under 4.0 but check their website. You'd want to create a disposable VM based on the whonix-ws 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/92cfc0849f45403ab12d64d352cccec3.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Please help with 8th Generation Intel i5
On Thu, January 25, 2018 7:19 pm, Krišjānis Gross wrote: > > here it is (attached). Hope that helps! >From the journal: Jan 25 20:53:15 localhost.localdomain kernel: [drm] The driver support for your hardware in this kernel version is alpha quality See CONFIG_DRM_I915_ALPHA_SUPPORT or i915.alpha_support module parameter to enable support in this kernel version, or check for kernel updates. This is enabled by default on Qubes 4.0, but I'm not sure if that's the case for 3.2. That could be why video was so slow on 3.2. (On a side note, why is this Linux driver still alpha after it's been around for years?) Everything else looks fine. I see DMAR gets set up so hardware virtualization should work. Didn't notice any obvious problems in the Xorg logs. Look for the "i915.preliminary_hw_support=1" entries in https://pastebin.com/u8z6nWV5 for an example of where you should add them to 3.2 if they aren't there. I agree with the other suggestion made earlier, wait for rc4 then try 4.0 again 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/effedb1fb5a5eca4867fac9287bf44ee.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0 Documentation
On Fri, January 26, 2018 3:36 am, Andrew David Wong wrote: > On 2018-01-25 12:28, awokd wrote: >> 1. Should I open an issue for tracking and move the discussion >> over there? Move to qubes-devel? Keep here? > > Please open an issue in qubes-issues. https://github.com/QubesOS/qubes-issues/issues/3495 > I agree that the tool man pages should not be shared between 3.2 and > 4.0 (but they probably wouldn't be anyway, due to the nature of the > system just described). What will be the naming convention for direct links? I can see sometimes we'd want to link to the latest version of qvm-whatever, and other times when we want to link to a specific major version. > I > think it makes sense to handle these cases specifically, by creating a > page that collects all the versions of each one. I'll do this now. Thank you. > In general, it's worth thinking about whether we even want to keep > severely outdated category 2 documentation around. Does it have any value > anymore, or will it just produce misleading search results? (Note that it > will all remain permanently archived in the git revision history, so it's > mainly a question of visibility on the website.) My vote is to axe 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/835aa4381a02b34be8f3162224d965f0.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0 Documentation
On Fri, January 26, 2018 9:22 am, Alex Dubois wrote: > On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong wrote: > Happy to contribute. maybe we can have a direct conversation so that we > can discuss what is needed and where I feel comfortable... Speaking only on my own behalf of course, thank you. Editing the docs is pretty straight-forward (https://www.qubes-os.org/doc/doc-guidelines/), so I'd suggest jumping in and editing whatever you are comfortable with. I'm coming across documents where someone else has already gone in and called out or updated with R4.0 content, so thanks to those contributors as well! -- 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/012f06ff57be8fd2c1405d791ae01424.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: i3 under Qubes 4 RC3
Den torsdag den 25. januar 2018 kl. 20.17.48 UTC+1 skrev Kevin Martinsen: > i3 has been working fine for me. > > Did you follow the installation instructions on > https://www.qubes-os.org/doc/i3/? Specifically: > $ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > i3-settings-qubes Yesh, I have followed those steps (but please also note that the documentation is related to 3.2, and as such it might be that i3 has actually been bumped to the stable repos, but I don't know :) > What do you mean you cannot start any programs from vms? How are you trying > to start programs? For me I have mod4+d to use dmenu. And do you mean to say > that qvm-run works correctly? My dmenu is broken, for starters. Dmenu only shows dom0 applications, so I cannot start anything that way. When I run qvm-run to start something, I can see that my VM is started (with qvm-ls) and I can hear my CPU responding (as in it starts fanning), but nothing visually happens. Nothing is ever started. -- 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/4f15ee67-f291-41e4-b9bf-1b24df5fa915%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qubes 4 windows installation
On Fri, January 26, 2018 6:05 pm, Yuraeitha wrote: > On Friday, January 26, 2018 at 6:47:14 PM UTC+1, goo...@itrichter.de > wrote: > >> Am Samstag, 6. Januar 2018 20:28:21 UTC+1 schrieb goo...@itrichter.de: >> >> Addition: In order to get a stable Windows 7, I had to disable memory >> balancing AND set the min and max memory to the same value. Otherwise, >> the VM would crash each time the memory balancing occured. > > Yes, I can second this issue, I experience it too and had to turn off > dynamic memory. Although I did not confirm if it was the case the last > 1-2 months or so. I also had to be put on minimum Memory at 4GB, since > 3GB or 3.5GB RAM sometimes made Win7 crash. 4GB+ made it stable on my > system. Thirded, except I'm stable with 2GB min/max and have the Win7 swapfile fixed at 1GB. It didn't seem to like resizing the swap file. My Win7 gets very light use, however. > > For some > weird out reason I can't use my legal license key to download the medium > on the MS-website for a legal clean Win7 copy... seems like it isn't > uncommon either for others? Must be their way to encourage you to switch completely to Linux! > I can't see any windows-tools in the repository in Qubes 4, was it > integrated into Qubes from the beginning, done in a different way, or > maybe its not been done yet? There might be a GSoC suggestion to update them but like you found, I don't think they have an active maintainer. -- 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/4be3443a79386c69cb5e8335a567d2c6.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Troubleshooting IOMMU compatibility
On Wed, January 17, 2018 12:58 am, jspiegelm...@airmail.cc wrote: > > Any refuse to work when connected to an HVM. IOMMU is not working at > all, so I'm wondering how to troubleshoot it and see if it's just an > improper configuration by the motherboard manufacturers that can be fixed > in some way. Add iommu=debug loglvl=all to your Xen boot options, then display the results with xl dmesg. -- 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/b9dc1a6d083a3eb0266682bec8319cdd.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Multiple usability issues Qubes 4RC3
Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash: > Hello all! > > > I apologise for the vague subject, but I have been trying all kinds of > things, and I simply can't understand half of the issues, and the other half > I can't seem to find a solution to. > > > First of all I have all the respect in the world for the entire Qubes team, > and I sincerely believe that you are making the world a better place. > > > The machine: ThinkPad X270 (full specs: > https://www.uk.insight.com/en-gb/productinfo/portatili-e-notebook/0007017591). > It has 8 GB RAM. > > > So.. to the issues.. > 1) A more general gripe with not having enough documentation to actually get > through a setup process. I used Qubes 3.2 before, and I simply went about > Qubes 4 the same way. I know that there have been multiple changes, and I > honestly believe the changes are for the better. > > > But issues like moving a templates home directory to /etc/skel (meaning that > appvm's inherit /etc/skel as home dir from the template) left me baffled with > my first install.. I setup my template exactly as I wanted, created an appvm, > and nothing was initialised. I had no idea what was going on, and the only > way I could get some information was through a GitHub issue. Even after > moving everything over to /etc/skel, I still have issues.. not everything is > being carried over, not everything is being read correctly, and /etc/skel is > not being synchronised either. If I add something new to /etc/skel AFTER > creating a appvm, the appvm's homedir won't be updated. > > > I like the idea with moving all the GUI functionality to the shell. I prefer > using the shell anyway. But for instance, in 3.2, you could allow access to > through the firewall for a templatevm. Now it has to be done through > qvm-prefs. This is not documented anywhere, and this was also an infuriating > issue for me. > > > 2) I have reinstalled qubes multiple times over the weekend (friday through > sunday) to get my install at a state that I am actually satisfied with. > > > Most griping issues: sys-net and sys-firewall do not start on boot. > Journalctl claims that there isn't enough memory to start sys-net on boot (I > don't have anything more descriptive for sys-firewall). > I can easily start them after boot and login. If I need more memory, then I > will happily upgrade. I intended to do so anyway, but I cannot understand why > it worked fine in 3.2 with 8 GB RAM. > > > 3) The issue mentioned under documentation with setting up a template exactly > the way I want it. > To understand the issue in depth, I think it's in place to describe my setup: > Having 2 base templates (based on the debian 9 template): > > > * One I call 'trusted' which is based on debian sid (unstable) that I > install everything I use for daily usage (firefox, libreoffice, mpv, emacs, > other open source tools). Primarily AppVM's will be based out of this > template. > > > * One I call 'untrusted' that is going to be a clone of 'trusted', and that I > install proprietary software in, that I also use on a daily basis (e.g. > spotify). Also AppVM's out of this, but probably only 1 to start with. > > > * I will probably create a standalone VM based off of 'trusted' that I use > for development. So I will install stuff like docker, golang, and all other > stuff I would otherwise use for developing. > > > I have not been able to create my 'trusted' template in a proper manner, > since I can't get /etc/skel to work properly. > > > NOTE: I use zsh with oh my zsh and spacemacs. Both of which are git repos > that are cloned to the homedir of the user (meaning they are git repos cloned > to /etc/skel) > If this is improper usage, then please guide me to how I should go about > doing this instead, as I have no idea what the smartest solution would > otherwise be. > > > Sorry for the long email, and thanks in advance for clarifying answers. > > > Best regards and all the best. UPDATE: So, I decided to go on with an install and with the knowledge of my previous misinstalls and guidance from here this is the result: 1) I decided to go on with the install and scheme that I already wrote about. I looked into bind-dirs, and it is definitely something I am going to use at some point, but the effort right now on a 'per-application basis' is simply too much (I just need a running system). 2) I still have an issue with sys-net/sys-firewall not being started on boot, but this problem isn't really a dealbreaker for me. It's just an annoyance. 3) Sound doesn't seem to be working in debian (unstable). None of the fixes seem to work either.
[qubes-users] Re: Multiple usability issues Qubes 4RC3
Den fredag den 12. januar 2018 kl. 10.45.02 UTC+1 skrev a...@it-minds.dk: > Den mandag den 8. januar 2018 kl. 14.29.06 UTC+1 skrev Ahmed Al Aqtash: > > Hello all! > > > > > > I apologise for the vague subject, but I have been trying all kinds of > > things, and I simply can't understand half of the issues, and the other > > half I can't seem to find a solution to. > > > > > > First of all I have all the respect in the world for the entire Qubes team, > > and I sincerely believe that you are making the world a better place. > > > > > > The machine: ThinkPad X270 (full specs: > > https://www.uk.insight.com/en-gb/productinfo/portatili-e-notebook/0007017591). > > It has 8 GB RAM. > > > > > > So.. to the issues.. > > 1) A more general gripe with not having enough documentation to actually > > get through a setup process. I used Qubes 3.2 before, and I simply went > > about Qubes 4 the same way. I know that there have been multiple changes, > > and I honestly believe the changes are for the better. > > > > > > But issues like moving a templates home directory to /etc/skel (meaning > > that appvm's inherit /etc/skel as home dir from the template) left me > > baffled with my first install.. I setup my template exactly as I wanted, > > created an appvm, and nothing was initialised. I had no idea what was going > > on, and the only way I could get some information was through a GitHub > > issue. Even after moving everything over to /etc/skel, I still have > > issues.. not everything is being carried over, not everything is being read > > correctly, and /etc/skel is not being synchronised either. If I add > > something new to /etc/skel AFTER creating a appvm, the appvm's homedir > > won't be updated. > > > > > > I like the idea with moving all the GUI functionality to the shell. I > > prefer using the shell anyway. But for instance, in 3.2, you could allow > > access to through the firewall for a templatevm. Now it has to be done > > through qvm-prefs. This is not documented anywhere, and this was also an > > infuriating issue for me. > > > > > > 2) I have reinstalled qubes multiple times over the weekend (friday through > > sunday) to get my install at a state that I am actually satisfied with. > > > > > > Most griping issues: sys-net and sys-firewall do not start on boot. > > Journalctl claims that there isn't enough memory to start sys-net on boot > > (I don't have anything more descriptive for sys-firewall). > > I can easily start them after boot and login. If I need more memory, then I > > will happily upgrade. I intended to do so anyway, but I cannot understand > > why it worked fine in 3.2 with 8 GB RAM. > > > > > > 3) The issue mentioned under documentation with setting up a template > > exactly the way I want it. > > To understand the issue in depth, I think it's in place to describe my > > setup: > > Having 2 base templates (based on the debian 9 template): > > > > > > * One I call 'trusted' which is based on debian sid (unstable) that I > > install everything I use for daily usage (firefox, libreoffice, mpv, emacs, > > other open source tools). Primarily AppVM's will be based out of this > > template. > > > > > > * One I call 'untrusted' that is going to be a clone of 'trusted', and that > > I install proprietary software in, that I also use on a daily basis (e.g. > > spotify). Also AppVM's out of this, but probably only 1 to start with. > > > > > > * I will probably create a standalone VM based off of 'trusted' that I use > > for development. So I will install stuff like docker, golang, and all other > > stuff I would otherwise use for developing. > > > > > > I have not been able to create my 'trusted' template in a proper manner, > > since I can't get /etc/skel to work properly. > > > > > > NOTE: I use zsh with oh my zsh and spacemacs. Both of which are git repos > > that are cloned to the homedir of the user (meaning they are git repos > > cloned to /etc/skel) > > If this is improper usage, then please guide me to how I should go about > > doing this instead, as I have no idea what the smartest solution would > > otherwise be. > > > > > > Sorry for the long email, and thanks in advance for clarifying answers. > > > > > > Best regards and all the best. > > UPDATE: > > So, I decided to go on with an install and with the knowledge of my previous > misinstal
Re: [qubes-users] HCL - G505s (HD 8650G + R5 M230 dual graphics)
On Sun, January 14, 2018 7:07 pm, 'Emil Novik' via qubes-users wrote: > I did, no idea why HVM still doesn't work. > > > --- > Emil Novik > > > Original Message > On Jan 14, 2018, 19:48, taii...@gmx.com wrote: > > >> On 01/14/2018 06:05 AM, 'Emil Novik' via qubes-users wrote: >> >> >>> Mostly works fine, but has some issues : >>> - Can't use any HVM(crashes the computer every time). >>> >> Have you applied awokd's patch? >> Thought I had HVM on 3.2 working but once the Xen updates for Meltdown/Spectre ship I'll go back and reinstall and confirm. Have been running HVM in 4.0 with no trouble. -- 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/08b414db7ed9c3d3f28fbbe6756d8a12.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
RE: [qubes-users] validate IOMMU support
On Fri, January 12, 2018 8:23 am, Wim Vervoorn wrote: > Hello, > > > Thanks. I tried this. Now I am running into problems with the PCI devices > I am using. Qubes can't reset those. For some reason they are not > exposing the FLR capability. I am trying to find out why because they > should according to the datasheet. I'm personally interested in this because I have the same issue with a Corebooted laptop so please let me know if you figure it out, but there are probably going to be more subject matter experts over on the Coreboot mailing list! For purposes of validating IOMMU support though, as long as you can get one PCI device passed through I think that would be all that matters? -- 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/e7eece61bf481dec30d8113178aad1fb.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Multiple usability issues Qubes 4RC3
Den fredag den 12. januar 2018 kl. 12.38.20 UTC+1 skrev awokd: > On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote: > > > 6) Resizing a urxvt window in my debian unstable to a certain dimension > > (or fullscreen hotkey) crashes the terminal. If I have another window > > running the VM, and that window already 'broke' the dimensions in > > question, then urxvt has no issues taking on any dimensions. If urxvt is > > the only window running in the appvm, it will however keep crashing when > > it reaches a specific size. > > That sounds like this issue: > https://github.com/QubesOS/qubes-issues/issues/2617. Try starting from a > fresh Qubes Stretch template and upgrading it to unstable. If that's what > you did, it might be a regression. Can anything be done to fix this? I can't seem to find a solution in that issue, other than core components being updated. It's fine with me if there aren't any workarounds btw. Just wondering :) -- 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/2d2c8071-359d-44fa-af9f-8004a52a62fb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Multiple usability issues Qubes 4RC3
On Fri, January 12, 2018 12:28 pm, aaq via qubes-users wrote: > Den fredag den 12. januar 2018 kl. 12.38.20 UTC+1 skrev awokd: > >> On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote: >> >> >>> 6) Resizing a urxvt window in my debian unstable to a certain >>> dimension (or fullscreen hotkey) crashes the terminal. If I have >>> another window running the VM, and that window already 'broke' the >>> dimensions in question, then urxvt has no issues taking on any >>> dimensions. If urxvt is the only window running in the appvm, it will >>> however keep crashing when it reaches a specific size. >> >> That sounds like this issue: >> https://github.com/QubesOS/qubes-issues/issues/2617. Try starting from a >> fresh Qubes Stretch template and upgrading it to unstable. If that's >> what you did, it might be a regression. > > Can anything be done to fix this? > I can't seem to find a solution in that issue, other than core components > being updated. > > It's fine with me if there aren't any workarounds btw. Just wondering :) You're right, it's fixed (or should be!) if you are running the stable Qubes templates but all bets are off if you decide to go and upgrade them to unstable. :) -- 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/11be549d0310cd1ab3550503ac9e14c2.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0-rc3
On Fri, January 12, 2018 4:20 am, Andrew David Wong wrote: > It shouldn't require much effort. In most cases, all you have to add > is `## Qubes 3.2` above the existing documentation, shift the rest of the > headers down one by adding a `#` in front of each one, then add `## Qubes > 4.0` above the 4.0 content you want to add. It might be > slightly trickier if the current headings use the underlining syntax. This > requires basic familiarity with Markdown, but that's already required for > most doc contributions. Only one person has to do this for each document, > and many documents will not even require this because the content applies > to both 3.2 and 4.0. Would it be of value if I went through the published Docs and added these version headers? Should newer versions be added at the top (so 4.0 before 3.2 content)? 4.0 might just be "TBD". -- 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/89c7fa47e95e74b13e9c21e1d721a636.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes in a corporate network behind HTTP proxy
On Fri, January 12, 2018 8:03 am, pr0xy wrote: > > > SUCCESS! > > > Changing the /etc/apt/apt.conf.d in Debian and the /etc/dnf/dnf.conf in > Fedora, AND allowing the proxy IP on the firewall of EACH TemplateVM > finally allows me to update them via the sys-firewall. That's a huge speed > improvement over sys-whonix. > > Now I'm wondering if my failure to set firewall rules was the reason I > couldn't use your earlier IPtables examples. I might revisit that, but for > now this solution allows me to use Qubes somewhat normally behind this > corporate proxy. Glad to hear it! Sorry I couldn't help more. Would you mind providing a detailed list of steps you had to do to get this set up behind a corporate proxy? I know I'm a bit lost and it might help others in the future. -- 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/b0bdd7093b4d7986f90b2434d589269c.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Multiple usability issues Qubes 4RC3
On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote: > 6) Resizing a urxvt window in my debian unstable to a certain dimension > (or fullscreen hotkey) crashes the terminal. If I have another window > running the VM, and that window already 'broke' the dimensions in > question, then urxvt has no issues taking on any dimensions. If urxvt is > the only window running in the appvm, it will however keep crashing when > it reaches a specific size. That sounds like this issue: https://github.com/QubesOS/qubes-issues/issues/2617. Try starting from a fresh Qubes Stretch template and upgrading it to unstable. If that's what you did, it might be a regression. -- 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/1209585faf59c9328bb5ba67b0d015fc.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Running Windows from Qubes VM ?
On Fri, January 12, 2018 6:48 am, ThierryIT wrote: > Hello, > > > I have a laptop with two internal Hard Drives. > One HD with Windows 7 the second Hard Drive with Qubes on it. > Is it possible to run Windows 7 from a VM's Qubes instead of building a > Win dows's VM ? You might be able to create a Win 7 HVM inside Qubes, then use qvm-start win7 --drive /dev/sdb5 (or wherever your Win7 bootable partition is located) to start it. Never tried it though. -- 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/d8c97927644ca4f7c3af066bea0d5bf0.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: porting to ARM
On Fri, January 12, 2018 8:59 am, Ph.T wrote: > . my initial motivation for ARM was that > intel seemed more prone to #spectre than ARM; > https://developer.arm.com/support/security-update > "majority of Arm processors are not impacted > by any variation of this side-channel speculation mechanism." AMD is less prone than Intel too. :) > and is ARM saddled with ME or SMM? ...not sure. It has https://www.arm.com/products/security-on-arm/trustzone, but I don't know if owner controlled implementations are available or not. -- 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/417826305e26fd58084dffbb988a1cda.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)
On Mon, January 15, 2018 1:15 am, Nik H wrote: > On Monday, January 15, 2018 at 12:20:48 AM UTC+7, Vít Šesták wrote: > >> As far as I understand it, microcode update cannot fix it. It just >> brings some new instructions that can be used for Spectre fix. (But >> they don't help on their own.) >> >> You can try to update your BIOS if it is well supported by your vendor. >> Mine is. >> >> >> Alternatively, you can try to update microcode via Xen. (In fact, the >> new microcode is loaded on every boot, because CPU has no persistent >> storage for that. It should be loaded in early stage of boot.*) Xen has >> some documentation, it would be probably enough to use some Linux >> package and add something like “ucode=scan” to Xen parameters: >> https://wiki.xenproject.org/wiki/XenParavirtOps/microcode_update > > Thanks, this is good info. I found instructions to update microcode in > linux - seems very simple. Xen instructions seem simple as well but where > do I enter this? In the Dom0 terminal? I am a bit unclear as to how Dom0 > and Xen interact. If you're referring to the "ucode=scan" addition to the bootloader; yes, you'd enter those from dom0. > As a side-note, spectre does compromise the entire qubes architecture. I > know, nobody was thinking about these things, so no shame in that. But > one of the main premises in qubes is that VMs are isolated from each > other, and that is no longer the case as long as spectre is out there. > Good that meltdown is not an issue, yes, but doesn't really matter, > weakest link and all that. It matters a bit because Spectre is harder to exploit than Meltdown. IIUR, Qubes' design allowed it to constrict Meltdown to a single VM versus other OS designs where that would give access to the entire system. I'm still somewhat unclear on how Spectre operates under hardware virtualization but you're right, it needs to 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/79d8c47ca62d358458e6850a36a74686.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4.0 Documentation
Resuming working my way through splitting up the documentation now that
the 3.2 vs. 3.3 question has been mostly settled. Some general questions:
1. Should I open an issue for tracking and move the discussion over there?
Move to qubes-devel? Keep here?
2. The command line tools in particular
(https://www.qubes-os.org/doc/vm-tools/ and
https://www.qubes-os.org/doc/dom0-tools/) seem Wrong to try to share the
same pages for 3.2 and 4.0. Not only is the selection of commands slightly
different between versions, but many have slightly different options ("-a"
vs. "a"). I'm thinking of copying all the existing pages, appending "4" so
they can be linked to directly, and putting in their own section.
Thoughts?
3. Some of these documents are pretty outdated. Should we have an Archive
link and move stuff like
https://www.qubes-os.org/doc/template/fedora/upgrade-18-to-20/ to it so it
doesn't clutter up the main Docs page?
--
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/d53c8644bc985ae4263f1f5ec25a7622.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: [qubes-announce] [UPDATE] QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)
On Thu, January 25, 2018 10:51 pm, yreb...@riseup.net wrote: > *by this if I ran sudo qubes-dom0-update > --enablerepo=qubes-dom0-security-testing*once, I take it , that > I am still on the Stable Track "repo" so somehow magically I > have the current testing Xen version (I checked and do), but when the > security Xen goes to Stable , they will just be integrated . so > currently I have a combination of 1 time security Xen and the rest is > "current" (Not testing) ? Exactly! -- 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/07ea481657628bfab2ee108e36be7883.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: [qubes-announce] [UPDATE] QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)
On Thu, January 25, 2018 2:17 am, yreb...@riseup.net wrote: > On 2018-01-24 15:12, Andrew David Wong wrote: >> >> These packages will migrate from the security-testing repository to the >> current (stable) repository over the next two weeks after being tested >> by the community. > > > 1) > The latter (security) packages will migrate, I'd assume this means ? Yes, this is the standard model for deploying all updates including security. They appear in testing first for bleeding edge users, then stable for everyone. Sometimes bugs are found in the testing phase causing the package to be pulled, so unless you are comfortable rolling back packages yourself you should leave it on stable. > 2) > Where would I find the repositories in dom0 for the track I'm currently > using? If you haven't changed it manually, you are on stable. > 3) > after doing the 1x securitytesting repo update, how do I check which Xen > package is now installed? In dom0, "dnf list installed". > and/or how do I bring up the GUI > update manager when it doesn't actually need to update it doesn't persist No GUI, but in dom0 you can force it to check for updates with "sudo qubes-dom0-update". Might not be following your question here. -- 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/5877f3a839a49a8520367e507d47c1f8.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Please help with custom template build
On Wed, January 24, 2018 7:42 pm, Krišjānis Gross wrote: > On Tuesday, 23 January 2018 19:36:00 UTC+2, Krišjānis Gross wrote: >> -> Verifying signatures... >> Filename: >> /home/krish/qubes-builder/cache/fc25/base_rpms/acl-2.2.52-13.fc25.x86_6 >> 4.rpm is not signed. Exiting! Just noticed you are using F27 for your build environment. Can you try F25? -- 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/d439ce9e014d0cdba2ccc4f0b8459396.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Please help with 8th Generation Intel i5
On Wed, January 24, 2018 7:09 pm, Krišjānis Gross wrote: > > I can not find a kern.log or dmesg. I did find the Xorg log files. (This > is all on the Fedora that I recently installed on this same hardware). > Xorg Log files attached. Try "sudo journalctl -b > journal.log". Review and redact any sensitive information (serial numbers, usernames, etc.) then reply here with it attached. -- 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/c82c15c702f99652584acc1e5bebd3d0.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installation error: need at least 3mb more on /boot/efi
On Thu, January 25, 2018 10:14 am, darkla...@gmail.com wrote: > 4.0. I'll try asap. Sorry, thought of a third option right after hitting send... You might have leftover junk in the EFI partition from other OSes. You could look around in /boot/efi/EFI to see if there's anything to delete to free up space. It's pretty easy to end up with a non-booting system if there are other OSes on the same drive, so use caution if that's the case (don't think it is in yours). -- 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/e8c41ed6b808222e0a4e4f4ad9516b8f.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: When creating a fresh sys-usb
On Wed, January 24, 2018 1:34 pm, ThierryIT wrote: > Global settings / default template ? > > > > Le mercredi 24 janvier 2018 15:32:55 UTC+2, ThierryIT a écrit : > >> Hi, >> >> >> What template does it use ? >> How to make it change (from fedora to debian template) if I need to do >> it ? >> >> Thx Look in VM Settings for sys-usb. -- 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/8e213aa0fc23ba76266bb91326a1ad62.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes 4.0 hvm crashes on boot after probing EDD
On Wed, January 24, 2018 1:18 pm, pixel fairy wrote: > starting a standalone hvm with > > qvm-start myhvm --cdrom=myappvm:/home/user/Downloads/linux.iso > > the bootscreen quits just after > > Probing EDD (edd=off to disable)... ok Set Kernel to "" [none]. -- 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/758144428aaa572d70d4408ec64bbdcd.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installation error: need at least 3mb more on /boot/efi
On Thu, January 25, 2018 9:10 am, darkla...@gmail.com wrote: > Hi, > as per title, when trying to install on a laptop (with new partitions > automatically created by the installer) I get this error. I've seen > another person with the same problem but he was upgrading qubes, qhereas > I'm on a fresh install. > Thanks for your help! 3.2 or 4.0? In 3.2 I believe the installer re-uses the existing EFI partition instead of creating a new one. 4.0 might be the same. So a couple options are: - completely wipe the drive before installing Qubes on it (e.g. secure erase if SSD). If that doesn't work, - manually specify partition sizes on install. I'd set EFI at 512MB. -- 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/b68aa0996c307e02b9399141ff8f0ba6.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] i3 under Qubes 4 RC3
Hey all, I installed i3 when first set up my machine, but I can't seem to get it working.. Has anyone else experienced issues with i3? In my case, no applets are shown in the bar and I cannot start any programs from VM's (any VM). If I run qvm-ls, it shows that VM's are running, and if I try to do somethings like qvm-run firefox, my CPU responds. Just a peculiar issue, but makes i3 unusable for me nonetheless.. Any feedback appreciated :) Cheers! -- 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/8a0771c6-0756-41d0-b7a7-f46cbf94b45c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kernel Panic on a Lenovo Yoga 300 11-iby on attempt at install
Den torsdag den 25. januar 2018 kl. 14.40.14 UTC+1 skrev WolfSkin: > On Thursday, 25 January 2018 13:36:18 UTC, WolfSkin wrote: > > Basically my issue is that I am getting a kernel panic when I try > > installing qubes-os on my laptop both in UEFI and legacy mode. > > The kernel panic can be seen here: https://imagebin.ca/v/3pPwokGAMAVB and I > > sadly can't provide a hastebin dump since I have no way to log the error in > > text form (at least none that I'm aware of). > > > > I have followed the steps in the uefi-troubleshooting docs page, to no avail > > > > Steps to reproduce: > > - Buy this laptop > > - Burn the iso to usb using etcher or rufus after having verified file > > integrity via checksums and signature > > - Boot to the usb in uefi or legacy > > > > What I expect to happen: > > - Normal boot to the installer > > > > What I get instead: > > - Attempts to boot, manages to get to the loading bar on legacy, not even > > close on uefi > > - Then kernel panic (as seen in picture) > > > > Any help with this would be greatly appreciated > > Since I can't edit the above afaik, this is both on R4-rc3 and R3.2 Did you try the steps from this doc page? https://www.qubes-os.org/doc/thinkpad-troubleshooting/#instructions-to-create-usb-installation-medium-for-newer-uefi-only-thinkpads DISCLAIMER: I have a ThinkPad X270, but I installed in legacy mode, so I haven't tried this myself.. Perhaps someone with more knowledge can assist, if this fails :) -- 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/9df52da3-ce82-4036-92a1-a23a0f40bc17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Running Windows from Qubes VM ?
On Fri, January 12, 2018 2:53 pm, ThierryIT wrote: > Hello, > > > I am not able to use "qvm-start" because the HVM I have created is > "Empty". > Dom0 is able to see my Windows 7 hard drive: > /dev/sdc2 /run/media/user/32E...CCB type fuseblk > > > From Dom0 I am able to have access to all my Window 7 files. > > > Any ideas ? > > > Thx > > > Le vendredi 12 janvier 2018 13:59:56 UTC+2, awokd a écrit : > >> On Fri, January 12, 2018 6:48 am, ThierryIT wrote: >> >>> Hello, >>> >>> >>> >>> I have a laptop with two internal Hard Drives. >>> One HD with Windows 7 the second Hard Drive with Qubes on it. >>> Is it possible to run Windows 7 from a VM's Qubes instead of building >>> a Win dows's VM ? >>> >> >> You might be able to create a Win 7 HVM inside Qubes, then use >> qvm-start win7 --drive /dev/sdb5 (or wherever your Win7 bootable >> partition is located) to start it. Never tried it though. Can you provide the exact error message? Not sure why qvm-start would care it's empty, it will still boot from a CDROM then 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/8889817fd5428891fa0923ab9d6aa32c.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Failed to start Qubes DB agent after upgrade fedora 24 to 25 (r3.2)
On Thu, January 11, 2018 9:03 pm, pa...@kc.pl wrote: > On Thursday, 11 January 2018 21:58:32 UTC+1, awokd wrote: > > >> You can run qvm-backup from the command line. I thought there was a way >> to start the GUI one too but am not finding it. > > I have no qvm* commands available. Nor qubes-dom0-*. > Probably I can't also attach any external device at this point. > > > I have only qubesctl command and qubesdb-* commands available. Sorry then, no idea how that would have happened. You can maybe copy out the VMs' image files directly from /var/lib/qubes/appvms and mount them after repairing your install to recover the contents. -- 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/6ab97da0645c86c0b51331c2ba9c4b8d.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] A question for the Qubes community: multiboot documentation
Thats ofcourse an option to, all ideas and input are welcome. Also cooloutac, believe me, I will make sure to put some big warning at the beginning to advise against this, and inform them of the dangers. -- 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/eu0LAh3c-C_-kFKNnUx3JTRVLjUDiUqCswbOEITLlUC6ZqnNVXnCdsaHvYUFSKET1c7NUbo6J3evDIma84DMgOdqiKKYYAYpKfbKJZFdVpk%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Failed to start Qubes DB agent after upgrade fedora 24 to 25 (r3.2)
On Thu, January 11, 2018 8:49 pm, Pawel G wrote: > On Thursday, 11 January 2018 21:12:22 UTC+1, awokd wrote: > > >> If you back up the VMs first, you can reinstall then restore the VMs. >> In >> 3.2, go to Qubes VM Manager, then System menu, and choose Backup. Best >> if you can do this to an external drive so the backups don't get wiped >> by mistake on the install! > > Is this the only way? No recovery mode? :) Qubes VM Manager is not > running unfortunetly, so no go for me. You can run qvm-backup from the command line. I thought there was a way to start the GUI one too but am not finding 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/52cef5d38984e014dffa22387918afb3.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Failed to start Qubes DB agent after upgrade fedora 24 to 25 (r3.2)
On Thu, January 11, 2018 7:37 pm, Pawel G wrote: > I upgraded dom0 (following "Installing and using Windows-based AppVMs" > doc): > > > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > qubes-windows-tools > > and not long after that I upgraded all my VMs from f-24 to f-25. OK, that's different, that should be fine. dom0 is still on f-24 then, just your VMs are upgraded. > > I use my laptop for a few weeks puting it into hibernation mode. After > restart - you know the story. I haven't found anything in bash_history > what would damage qubes, aside from those updates. I don't know what could have broken your QubesDB then, unless maybe you ran just "sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing" at some point? That would have upgraded Xen and everything except the VMs to the testing repo, which is not always stable. > Is it possible to reinstall base system and have my VMs and data not > earased (like from ISO installer)? If you back up the VMs first, you can reinstall then restore the VMs. In 3.2, go to Qubes VM Manager, then System menu, and choose Backup. Best if you can do this to an external drive so the backups don't get wiped by mistake on the install! -- 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/2d445e8d9d4eba66e0f617acc25bb6a7.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
AW: [qubes-users] Re: Qubes Manager is coming back in Qubes 4.0-rc4!
Andrew David Wong wrote: > Specifically, it will not duplicate functionality > that is already provided by the new 4.0 > widgets. Specific examples include attaching > and detaching block devices, attaching and > detaching the microphone, and VM CPU > usage. Great news that the Qubes Manager will come back. Linux has always be about free choice and as Qubes Manager will be an additional way to interact with Qubes the users who don't want, don't have to use it. I am also voting for a Qubes Manager which has nearly full functionally, as I don't like to use different places to do stuff. Maybe this can also be configured, so that you have "lean mode" and an "full mode" or something similar. As mentioned: choice is good. The current user interface results in much more "mouse meters" compared to Qubes 3.2 Thanks to the Qubes Team that they're listening to the user base. [799] -- 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/rXY2pHVr2yJByJ7mdrDFoCDBJ02dDONU0rKKipV8Qv-rvHeSzreelj0wFkX7pZauueBFTGd3ow1FR0kNx5pDp-0qsbPm-5HJhb1DH3mggYc%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Running Windows from Qubes VM ?
On Sat, January 13, 2018 7:49 am, ThierryIT wrote: > Hi, > Seems to work better even if I am still not able to boot my windows. > With "fdisk" I can see that my bootable HDD is "sdc1". > From Dom0, when doing a : qvm-start vm-test --hddisk /dev/sdc1, I do have > a popup from my Windows drive. > > Booting from CDROM error code failaure 2 > Booting from Hard drive, failed no bootable disk > > > No bootable device ... > > > Ideas ? > > > > > Le vendredi 12 janvier 2018 17:43:56 UTC+2, awokd a écrit : > >> On Fri, January 12, 2018 2:53 pm, ThierryIT wrote: >> >>> Hello, >>> >>> >>> >>> I am not able to use "qvm-start" because the HVM I have created is >>> "Empty". >>> Dom0 is able to see my Windows 7 hard drive: >>> /dev/sdc2 /run/media/user/32E...CCB type fuseblk >>> >>> >>> >>> From Dom0 I am able to have access to all my Window 7 files. >>> >>> >>> >>> Any ideas ? >>> >>> >>> >>> Thx >>> >>> >>> >>> Le vendredi 12 janvier 2018 13:59:56 UTC+2, awokd a écrit : >>> >>> >>>> On Fri, January 12, 2018 6:48 am, ThierryIT wrote: >>>> >>>> >>>>> Hello, >>>>> >>>>> >>>>> >>>>> >>>>> I have a laptop with two internal Hard Drives. >>>>> One HD with Windows 7 the second Hard Drive with Qubes on it. >>>>> Is it possible to run Windows 7 from a VM's Qubes instead of >>>>> building a Win dows's VM ? >>>>> >>>> >>>> You might be able to create a Win 7 HVM inside Qubes, then use >>>> qvm-start win7 --drive /dev/sdb5 (or wherever your Win7 bootable >>>> partition is located) to start it. Never tried it though. >> >> Can you provide the exact error message? Not sure why qvm-start would >> care it's empty, it will still boot from a CDROM then too... Maybe the boot sequence doesn't search hard drives attached like that, in which case it won't work. -- 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/7ec59ad1b949d11baf1a7a319b7af1de.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] A question for the Qubes community: multiboot documentation
Great! Would you consider including instructions on how to multiboot between Qubes OS 3.2 (main system) and Qubes OS 4 (test/future system)? I'd love to test and play with 4RCx but need to have a stable environment for work (3.2). I can see where your coming from, but I dont know if it would be practicel to include documentation for something that will only be used so shortly, because it wont be long before qubes 4 gets released, and writing the documentation correctly takes some time. Anyhow, people are always free to contribute it if people deem in neccesary :). -- 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/2rHyQ8ddSUb3vC5ZFpsYavhju-SJJds5EEQa-Y4IjwK50jY2GFJxoBL_TJui445dm6a9U1TfWy8OL0UZfYrNjrZM8c7m96b0LoIAU3nAKfo%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Do Qubes v4.0-RC3 have stronger hardware limitations?
On Tue, January 30, 2018 1:23 pm, pascal.mignot.u...@gmail.com wrote: > I've tried to install Qubes v4.0-RC3 on an HP ProBook 650 laptop. > > > The installation interface prevent me to proceed, saying that my hardware > is not compatible with Qubes v4.0. > So my question is: what additional hardware constraints have been added > between Qubes 3.2 and 4.0 to disqualify my laptop? In dom0, run "qubes-hcl-report" and provide the 5 HVM: through Remapping: lines towards the end. If you see a message about "unknown", reboot and run it again. I think 4.0 requires the first 3 lines. -- 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/d1e726773eecff9b7330defef2779ad7.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 installation will not boot on Dell Inspiron 7000 Gaming series laptop
On Tue, January 30, 2018 5:14 am, freddycribb...@gmail.com wrote: > I have installed Qubes OS 3.2 to a secondary SSD in an attempt at > The UEFI entry is successfully created by the installer, but upon Dual booting Qubes isn't really recommended. Better to have a separate physical machine if possible. I'm guessing, but I think the problem might be because there is usually only one EFI partition per system, and it's the one on your primary SSD. The UEFI programmers probably only ever tested a single drive with Win10, maybe booting once from an external drive. You could switch both Oses to grub2/legacy boot and try that way. Another option might be to do a full backup of your Windows SSD and leave it enabled during the Qubes install. Select the EFI partition on your primary drive when installing Qubes. Make sure to do the full backup because it could break things. -- 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/121b883c8955ec44a4b1662d7db7e5cb.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent
On Mon, January 29, 2018 10:53 pm, ludwig jaffe wrote: > Yes, I want to repair my qubes-vm-manager. Did you In Qubes Manager, go to the View menu and click Show/Hide Inactive VMs? > made a back-up and I want to modify config files by hand so the tools do > what they should do. So I need to de-register the vms I deleted by hand, > and I need to tell qubes-vm-manager which vms are there. I wonder if it > uses the tools qvm- in order to do its work. If you are sure you want to manually edit the qubes config, it's in /var/lib/qubes/qubes.xml. Make sure to make a backup of it 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/3723801e0c6818e9f6f21d36da068386.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent
On Mon, January 29, 2018 10:25 pm, ludwig jaffe wrote: > On Monday, January 29, 2018 at 9:14:38 AM UTC-5, Yuraeitha wrote: > >> On Monday, January 29, 2018 at 1:06:13 PM UTC+1, ludwig jaffe wrote: >>> The Qubes-VM-Manager only shows running VMs and not all the VMs that >>> are there, but from the menue button one can start the shells of these >>> VMs, >>> which causes the vms to be started. >>> >>> Also I can not change the disk size of private.img in the shutdown >>> personal vm. And maybe others. > Hi, as there is RC-4 of something, it is clever to stick with qubes3.2 > until there will be 4.1. Also I would like to know how the qubes manager > works, in order to fix it my self (maybe, I need to edit some XML), if > nobody wants to help. I'm sticking with 3.2 on my primary system until 4.0 is released, but rc4 is looking like it will be pretty close to ready. Are you talking about your two questions above? In Qubes Manager, go to the View menu and click Show/Hide Inactive VMs. If you are trying to enter a smaller number to shrink it, I don't think you can. Back up the personal VM's data, delete the VM, create a new one, and restore the 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/c4a2e17023ecf8f03db6c43d79d33902.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to deal with Yubikey ?
On Thu, February 1, 2018 8:58 am, ThierryIT wrote: > If I did understood well, when using Qubes 4.0r3, there is no sys-usb ... If you chose not to set one up on install there wouldn't be, but usually you should unless using a usb keyboard maybe. You can still add one now; check the docs. -- 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/e1faa309e2e2704c82fbabcacb489fad.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installing in UEFI (Ryzen 1800X, ASRock Fatal1ty X370 Professional Gaming)
On Thu, February 1, 2018 10:21 am, Willem D wrote: > I found the report on Github: > https://github.com/QubesOS/qubes-issues/issues/2838 which describes the > same issue as I have. I would like to debug the problem, but I require > assistance with that. To workaround the problem, try using Refind. To actually debug it, I think Qubes is using a modified version of Fedora 25's installer. Does that one work on your system? Not aware of any log files that get generated that early (especially if it can't find a file system interface). -- 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/71bc6b64211aa9ce08655d4496263dce.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] sudden reboot?!
On Thu, February 1, 2018 6:47 am, evo wrote: > Hi all! > > > I have sometimes big problem with Qubes 3.2. > Just now, by writing an email... suddenly my laptop rebooted. Without > any errors. Blackscreen and reboot. > > This was the second time, but after rather large period. > > > how can i manage it?? You can check journalctl to see if it had a chance to log anything before the reboot but if Xen is crashing you might need a serial console connection to debug 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/e5ae47021dd443510449b70171a8f321.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] noscript xss warning on qubes os site
On Thu, February 1, 2018 9:54 am, pixel fairy wrote: > noscript, the firefox extention, pops up the following about the qubes > site, > > NoScript detected a potential Cross-Site Scripting attack > > > from [...] to https://www.qubes-os.org. > > Suspicious data: > > > window.name Not seeing this in Tor Browser 7.5 with Noscript 5.1.8.4 when I browse to https://www.qubes-os.org. Where are you seeing 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/9d8d9781fd5379f7339482fb070d316f.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to deal with Yubikey ?
On Fri, February 2, 2018 6:03 am, ThierryIT wrote: > > I have installed "qubes-usb-proxy" on my StandaloneVM. > -> qvm-usb l : sys-usb:4-2 Yubico_Yubikey_4_U2F+CCID > > > -> qvm-device usb attach vm-name sys-usb:4-2 : Device attach failed: No > device info received, connection failed, check backend side for details -> > same things How did you create sys-usb? Have you installed qubes-input-proxy-sender in 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/c44ec4660c7ec36039088ec5550addec.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Windows Tools
On Fri, February 2, 2018 9:24 am, yreb...@riseup.net wrote: > so, I created an win7 HVM ; and I think installed windows tools, but when > I read through the qubes docs, the instructions seem to be > circular. > I guess the benefit of the AppVM over the HVM is Qubes integration for > copy and paste and anything else practical? Qubes integration for copy/paste is one of the features provided by Qubes Windows Tools. Others are described on https://www.qubes-os.org/doc/windows-tools-3/. If you aren't sure what you'd use templates for, just go with an HVM. QWT installed properly in your Win7 HVM will allow secure copy/paste etc. -- 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/c7b143f8c2f3cabfdea732684ab0afba.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] reboot sys-net
On Fri, February 2, 2018 11:05 am, Bernhard wrote: > On 02/02/2018 11:58 AM, Ilpo Järvinen wrote: > >> On Fri, 2 Feb 2018, Bernhard wrote: >>> That would allow to confortably reboot sys-net For a bit more blunt force approach, you could qvm-kill sys-net then use the procedure "Reconnecting VMs after a NetVM reboot" on https://www.qubes-os.org/doc/firewall/ to reconnect it. Have not thoroughly tested. -- 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/289528855d40ca7fa0bff173a2a3d753.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to deal with Yubikey ?
On Sat, February 3, 2018 7:16 am, ThierryIT wrote: >> sys-usb:4-1 Logitech_USB_Receiver >> sys-usb:4-2 Yubico_Ybikey_4_U2F+CCID >> >> >> qvm-usb attach vm_name sys-usb:4.2 qvm-usb: error: backend vm 'sys-usb' >> doesn't expose device '4.2' You need to use "4-2", not "4.2". >> And it is not possible for me to un-attached the key through this >> widget ... I noticed that too. Might be https://github.com/QubesOS/qubes-issues/issues/3215. -- 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/3bb9bd0e484a0f770b785a62d573e016.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Anon-whonix browser fails to connect to tor in Qubes 3.2, any ideas?
On Sat, January 27, 2018 11:46 am, code9n wrote: > Running the WhonixCheck from the default anon-whonix app vm in the Qubes > manager list; the fail warning basically says: > > SocksPort test [fails]. ... (curl exit code: [7] - [failed to connect to > host]) > > The browser - anon-whonix app vm (default)/Tor browser - opens like > normal to the Whonix page but checking the 'check IP' link from there > won't connect and if I search for https://check.torproject.org the top > result says I'm not using tor. I can't connect to .onion sites but > surface browsing's fine. > > Checking the IP address keeps coming back to the same one in Germany even > if I reload / change Identity / reboot. (I'm not in Germany). > > It persists over cold re-boots. > I've tried making a new anon-whonix app vm with the same results. > Everything has been fine since install - maybe 6 months ago. > All updates are up to date including the recent tor browser update to 7.5 > (64 bit). In Qubes Manager/System/Global settings, make sure your Default netVM is set to sys-whonix. I can't explain the Germany IP though. Do you have a VPN or ProxyVM set up somewhere in the mix? > > yzxd on the sub reddit (Thanks, yzxd) had a similar problem on non-Qubes > Whonix and solved it by "going into the Gateway VM, stopping Tor, opening > the folder named "Tor Data" and deleting all the files inside, and > finally restarting Tor". > > But I see from issue #1137 the Qubes team deliberately made that > persistent: > > > https://github.com/Whonix/qubes-whonix/commit/a9f24f5d0b700a0cd710e52eb17 > 0875d635c22a9 > > > so I'm wary to mess with that. > > Would that be likely to work in this instance? Or Does anyone have any > ideas for a fix or would just re-installing the entire Whonix system > following: > > > https://www.qubes-os.org/doc/whonix/install/ > > > be better...? Re-installing the whole Whonix system or even Qubes might be the best approach if you can't figure out where that Germany IP is coming from. -- 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/9f301641083c9bfac14af969c329487f.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] ERROR: Device attach failed
On Sat, January 27, 2018 3:00 pm, beso wrote: > On Saturday, January 27, 2018 at 4:33:47 PM UTC+2, awokd wrote: > >> On Sat, January 27, 2018 2:20 pm, beso wrote: >> >> >>>> On Sat, January 27, 2018 6:31 am, beso wrote: >>>> >>>> >>>>> ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [: >>>>> Illegal >>>>> number: stash: printf: I/O error. >>>>> How to solve this problem? >>>>> >>>>> >> >>> Sorry, >>> >> >> No trouble! >> >> >>> Qubes - 3.2; >>> Attached device - Samsung M3 Portable 1TB; >>> Command I used to attach to one of my appVm - qvm-usb -a appvm >>> sys-net:3-1; >>> >> >> I'm assuming the ";" at the end of sys-net:3-1 is a separator and not >> actually part of the command you are entering, right? Has this device >> worked before on your system or is this the first time you are trying >> it? If it was working before, when did it start giving you the error? >> > > Yes, that is separator here. No, it never worked. If you're running through an external USB hub, try a direct port. I've also seen some people have had trouble with USB 3.0, so use a 2.0 direct port if possible. If neither of those help, hopefully someone else will have a better idea! -- 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/2abf36b03f29635c6ee1f7566c0c624c.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] ERROR: Device attach failed
On Sat, January 27, 2018 2:20 pm, beso wrote: >> On Sat, January 27, 2018 6:31 am, beso wrote: >> >>> ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [: >>> Illegal >>> number: stash: printf: I/O error. >>> How to solve this problem? >>> > Sorry, No trouble! > Qubes - 3.2; > Attached device - Samsung M3 Portable 1TB; > Command I used to attach to one of my appVm - qvm-usb -a appvm > sys-net:3-1; I'm assuming the ";" at the end of sys-net:3-1 is a separator and not actually part of the command you are entering, right? Has this device worked before on your system or is this the first time you are trying it? If it was working before, when did it start giving you the error? -- 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/7c63a2dafe233ac59c97f8438aa94f25.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
AW: [qubes-users] Qubes Manager / Qubes 4.0 R3 ?
Hello, ThierryIT wrote: > Hi, Not possible anymore to hide "un-running > VMs" ? Ist Qubes Manager already available in 4rc3? I haven't read anything and thought that it will come with Qubes 4rc4. [799] -- 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/tbI3qHvl8r4Cnkt-ZYbOlNTuTC3uhhV42IuLHW6M0pSyHukwQJXtNxgTatV69qsMb8se3jnMDq3-6o9ZnO1Z-fDs1Hauy3PJGnW0aXl-3XU%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] PANIC!!! data panic (disc full) / want to mount nas with nfs and backup all in /var/lib/cubes
On Sun, January 28, 2018 5:26 pm, ludwig jaffe wrote: > Hi some systems got too big and now my dom0 is full. > > > data panic (disc full) / want to mount nas with nfs and backup all in > /var/lib/cubes > > > In a normal system I would setup an insulated air gap network and take a > big nas server mount nfs to the root-fs of dom0 and say as root cp -a > /var/lib/cubes /net/nas/bck. > And then I would clean up and remove some VMs with rm -rf as I could undo > it when I got the VMs booted and cleaned of all the shit that got > downloaded. > > Now I can not connect the dom0 to a nic. > Is there a trick to do it? > booting a rescue linux from a stick would be a way but I first want to try > using qubes-os and changing a thing in the configs. 4.0? I think the "Qubes way" would be to boot from your install media, pick Rescue mode, and get enough free space to be able to boot the full system. 3.2 I guess you'd have to use a live image; can't remember if there's a rescue mode. I honestly can't tell you how you'd go about attaching a NIC to dom0. USB might be an easier choice, but same there- not something I've ever looked into! -- 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/af6fa238c914843414e88dbac40a24ab.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Network turns off when I close laptop lid, and I can't restart it
workarounds, fixes: https://github.com/QubesOS/qubes-issues/issues/3486 -- 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/kLUYryhOUdITkAaWqlAyt6ajYx0jie5i_JwSdQU03zI7Qz2wM0IpomMc9aUjaYF7kZHiNJOvqYoCcNSZra9SPPwM2HpC-WqGLverg2fKciM%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Anon-whonix browser fails to connect to tor in Qubes 3.2, any ideas?
I would ask on the Whonix Forum. https://forums.whonix.org/ -- 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/aJ1V4QSx0UbFs1cSmb2yVujSxb3EFwcladO21nkVDsnfiQG-VQ_7F0Z5sJGujtRaSQA2U5Qd9q8halk4nPLHHRiDejMz-iDgwvbwVLr4JM0%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0-rc3 not installing on Lenovo P71
On Sun, January 28, 2018 2:33 am, Yuraeitha wrote: > > Awkward same-time posting x) > But listen to awokd, he has more experience than I do. Not that much more! Unfortunately, on these boot issues most come down to trial and error like you said... -- 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/785a33dcc7e6cd626f7585bd9e485e08.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0-rc3 not installing on Lenovo P71
On Sun, January 28, 2018 2:13 am, joeh9...@gmail.com wrote: > I burned the ISO to USB stick then started to install Qubes but got the > following: > > > [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup > failure, AE_NOT_FOUND (20170531/dswload-210) [0.093383] ACPI > Exception: AE_NOT_FOUND, During name lookup/catalog > (20170531/psobject-252) > [0.093539] ACPI Exception: AE_NOT_FOUND, (SSDT:ProjSsdt) while loading > table (20170531/tbxfload-220) [0.098243] ACPI Error: 1 table load > failures, 12 successful (20170531/tbxfload-246) [2.376031] Couldn't > get size: 0x800e [ 137.216201] dracut-initqueue[566]: Looks like a buggy firmware. See if your manufacturer has a bios update. Could maybe try turning off power saving since some messages sort of sound related. If you don't care about EFI, you could disable it and boot and install in legacy mode. If you want EFI, could try booting Refind, then the installer from 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/3899d232c9b8d69f53a3a43bdf9ed6e8.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?
On Sun, January 28, 2018 7:46 am, ThierryIT wrote: > > I am a bit lost with Qubes 4.0 RC3 ... > Before moving to 4.0, I have done my VM's backup. > How to restore them to Qubes 4.0 ? Please check out https://www.qubes-os.org/doc/upgrade-to-r4.0/. Let me know if you have any questions; you might be the first one to try it out. -- 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/716b58a8f1160852ac7ebbd5e7e31bb6.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?
On Sun, January 28, 2018 1:58 pm, ThierryIT wrote: > Hi, > > > I have installed Qubes 4 without any problem. > I have done the dom0 upgrade. > I am able to start the system. > > > But I do not have any "Qubes Manager" ... That might be only available in the Testing repository, not in Stable yet. In dom0, try running: sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing then look for Qubes Manager again. You only have to do this once, afterwards you can go back to the regular "sudo qubes-dom0-update" for updates. If you don't care about having Qubes Manager, you could also run "qubes-backup-restore" from dom0 to jump directly to the restore interface. -- 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/44de6e0e7f275786e65e94f5ae6fb00b.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to deal with Yubikey ?
On Thu, February 1, 2018 3:46 pm, ThierryIT wrote: > What am I doing wrong ? > > > I have a Yubikey4 U2F + CCID. > Not detected with "qvm-block" > Detected as sys-usb:4-2 by dom0 (qvm-usb). > > > I have tried: > > > - qvm-device usb attach vm_name sys-usb:4-2 (device attached failed) > - qvm-device block attach vm_name sys-usb:4-2 (backend vm 'sys-usb' > doesn't expose device 4-2) Another poster said these aren't block devices, so don't try to use those commands on it. "qvm-device usb attach vm_name sys-usb:4-2" should work. What does "qvm-usb attach vm_name sys-usb:4-2" do? If it's the same error, did you install qubes-usb-proxy in your templates? See https://www.qubes-os.org/doc/usb/. -- 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/c1c03258b0d8c328fff7a3550edb84fe.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes and Whonix now have next-generation Tor onion services!
On Thu, February 1, 2018 7:53 pm, alexclay...@gmail.com wrote: > I see on the Whonix website that's linked to it simply says: > > > "To access the v3 onion address, Whonix users must install the latest Tor > 3.2.9 client in Whonix-Gateway ( sys-whonix ) via the > stable-proposed-updates repository." > > Any idea the commands to do this from the terminal for the whonix-gw vm? > I've edited the Torrc file before but that's the extent of anything I've > ever done with Whonix. Seems to be out of proposed and in stable now, so all you should have to do is update your whonix-gw and whonix-ws templates as usual. -- 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/37fe19c963ba44264684a822c9501e19.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] after update no VM 'starts' apps anymore.
On Tue, January 30, 2018 1:51 am, awokd wrote: > On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users wrote: > >> Is this a known issue? >> >> >> >> I can start a VM using qvm-start, but when I use qvm-run nothing >> happens, it hangs forever. Even commands that don't need a X server. For >> any qube of the various OSs I run. > > qvm-run works on both powered on and off VMs on my 4.0 on testing repo. > qvm-run works on powered on (only) VMs on my 3.2 stable. I ran into an odd issue trying to update today when dom0 was on testing but whonix-gw was on current. $releasever wasn't getting replaced with the version number so qubes-dom0-update was trying to pull from "%36releasever" subdirectory. Switching whonix-gw to testing and updating first resolved it. Were your templates and dom0 using the same repository or mixed? -- 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/9179a3664026a7d2bfa6958537c29b61.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Networking unavailable on Dell XPS 9350, QubesOS 4
On Wed, January 31, 2018 2:39 pm, jaya...@gmail.com wrote: > What do you mean it is easy to do? Where do you get a compatible wireless > card, that is definitely supported by Qubes anyway? > > I somehow imagined that getting appropriate driver should be simpler :/ It's not necessarily a driver issue; more of a Xen (on which Qubes is based) pass-through issue. Of the subset of wireless NICs that work problem-free on Linux, there's a smaller subset that Xen can pass-through problem-free and an even smaller subset that can be passed through a QEMU/Xen stub-domain (which is what Qubes uses). I think it comes down to how virtualization friendly the hardware manufacturer laid out their BARs and MSI pages and whether MSI interrupts work (and who knows, maybe there's a QEMU or some other bug somewhere in there too). I have success with an AR9565 on R4.0 but not an AR928x. If you're going to be shopping for another wireless card, maybe pick one then search this mailing list for problem/success reports, or identify which laptops come with it then search https://www.qubes-os.org/hcl/ and see if those laptops are reported problem free with R4.0? Longer term, I wonder if a section should be added to https://www.qubes-os.org/hcl/ specifically to list known compatible/incompatible network cards under Qubes R4.0? Could be painful to maintain if we expand it to cover PCI devices in general... -- 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/8fa99630352fccb4fa0b19e7f7248272.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to deal with Yubikey ?
On Sun, February 4, 2018 7:16 am, ThierryIT wrote: > > I have check it, but when doing a "dnf list installed "qubes-*" on my > sys-usb, I can see that qubes-usb-proxy is installed: > qubes-usb-proxy.noarch 1.0.12-1.fc26 @qubes-vm-r3.2-current Shouldn't > be: 4.0 current instead ? Yes, should be 4.0. Did you see the recommendation in https://www.qubes-os.org/doc/upgrade-to-r4.0/ to not restore your R3.2 templates to R4.0? Sounds like that might be what happened. Make sure all your AppVMs are using an R4.0 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/e86aec81bd463767ec7ba46bf27ade66.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Issues with 4.0 rc4
On Sun, February 4, 2018 4:00 pm, Yuraeitha wrote: > On Sunday, February 4, 2018 at 1:10:59 PM UTC+1, Nuno Branco wrote: > Reply to #3 In addition to what Yuraeitha wrote, check https://github.com/QubesOS/qubes-issues/issues/3470. > Reply to #4 qvm-prefs vmname kernel "" Then do your qvm-start --cdrom. -- 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/cdb1abd941656da756acec8e6bd7352e.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Manager / Qubes 4.0 R3 ?
On Sun, February 4, 2018 7:14 pm, 'Tom Zander' via qubes-users wrote: > The biggest issue i ran into is that Qubes4 is just too immature to > actually use for more than browsing and email. It was too painful for my > desktop full-time work machine. I tried for 2 months, my significant other > stated that I had been extraordinary patient with Qubes when I finally > stopped using it ;) > > My problems are widespread; > * the documentation is very out-of-date. Working on it (where other contributors haven't already)! Am about halfway through now. > * The graphics pipeline is hopelessly > outdated. Its about a decade behind the industry. It's also been more secure than most of the industry for those 10 years. ;) But no point rehashing the related GSoC threads. Your suggestion there seemed valid. I hope you continue to run the released version of 4.0 on a secondary machine at least. I think you provide a valuable viewpoint. -- 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/cd459af052eaeba5682ae14f5376a99b.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Clobbered FirewallVM — how can I get the firewall running again?
On Sun, February 4, 2018 4:55 pm, Demi Obenour wrote: > > > On 02/04/18 14:15, donoban wrote: > >> On 02/04/2018 08:05 PM, demioben...@gmail.com wrote: >> >>> My FirewallVM doesn’t seem to be running the Firewall service. How >>> can I set that up? >>> >> Could you paste "systemctl status qubes-firewall" on it? If it's unload >> or dead try start/restart it. >> > It is running normally: Are you running templates fresh out of the box? Try updating them. -- 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/e89fe2c1f3d734c526033da239f019c4.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] hdparm?
On Mon, February 5, 2018 4:37 pm, 'Guillaume Bertin' via qubes-users wrote: > Hi, > > > I don't manage installing hdparm in dom0. No package... > > > Have I missed something? Should harddisk management be done outside of > dom0? Usually, for security reasons you should avoid installing software directly in dom0 (https://www.qubes-os.org/doc/copy-from-dom0/). You can force it by manually downloading, copying in the package, and installing, but you'll have to also handle dependency resolution yourself. If you only need to run hdparm once or twice, you might want to boot from a live image instead and run it from there. Don't forget to verify signatures! -- 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/44ca67693b5bdbb780a6ba0dd6e02fa3.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] after update no VM 'starts' apps anymore.
On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users wrote: > Is this a known issue? > > > I can start a VM using qvm-start, but when I use qvm-run nothing happens, > it hangs forever. Even commands that don't need a X server. For any qube of > the various OSs I run. qvm-run works on both powered on and off VMs on my 4.0 on testing repo. qvm-run works on powered on (only) VMs on my 3.2 stable. I did notice some weirdness starting things on a recent update but a reboot cleared it up. > Is there any way to connect to the VM and get a tty? Think serial-line > fallback. Enable Debug mode? Sorry, don't know about your other questions. -- 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/5d3b226f9ae90d84f64ab8b6164df003.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?
On Sun, January 28, 2018 4:42 pm, ThierryIT wrote: > I have done my restore. > Do have some bugs, will open a ticket in Github tomorrow. > But I do have an error when trying to add "devices" for my netVM: > > > Error: Device tab: > Can't attach pci device to VM in pvh mode ?? > > > What is the pvh mode ? That's one of the new remediations for Spectre/Meltdown. In order to attach a PCI device, you have to switch your NetVM back to HVM mode. You can do that in VM Settings GUI or dom0 command with qvm-prefs. -- 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/5bf3a6f35c4b09ac6ea2ed9e66f25dc0.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
AW: [qubes-users] Re: Split GPG and Emacs/mu4e: able to retrieve email but not send
Hello Rumsey, >> I can now send email using emacs/mu4e >> and Qubes split gpg I am also interested in this setup. Can you give me some more information what needs to be done to start from a plain installation? Something like a copy of the relevant configuration files (stripping out the personal configuration of course by replacing it with something like MAILSERVER.COM, loginn...@domain.com, YOUR-GPG-KEY-ID etc). Would really appreciate this, to get things up and running. [799] -- 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/Sg7yaE_MsuJN4TeW35SHra2JoVzrnA5Ju4d1usmuSHjFE2zAaLQSBRiop-v-7zMqrQ3UEVwM3hk6QlfVrv9qXzHRAIZfg2_p_N24FdlhePg%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Manager / Qubes 4.0 R3 ?
Why are you complaining about bugs when running a ".0rc" version? They're to be expected; if not the point of release candidates. If you want stable, run R3.2. I'm still using that as my daily driver, but from what I see of R4.0rc4 it's to the point where I'm comfortable switching as soon as I can fit it into my work stream. Others already have and are (happily) running it daily. -- 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/47530f9e6a56871059db71d9c1e21bb6.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 4.0-rc4 Install Help
On Sat, February 3, 2018 1:37 pm, Shashank wrote: > Hi I’ve been trying to install qubes 4.0 rc4 in my dell xps15 > But I am not able to get the installation done. > and the message below goes on repeating Watchdog: BUG: soft lockup - cpu > stuck for 22s[xorg:1325] Is it trying to initialize a driver in the message immediately before the first soft lockup? If so, try disabling the corresponding device from your BIOS setup. -- 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/f7f2367639770c46d8d877cacbf7b807.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 4.0-rc4 Install Help
On Sat, February 3, 2018 2:29 pm, Shashank wrote: > Here is the full error: > Starting Installer, one moment > Anaconda 25.28.9-10 for Qubes R4.0-rc4 started. > *Installation log files are stored in /temp during the installation > *shell is available on TTY2 > *If the graphical Installation interface fails to start, try again > With the Inst.text bootoption to start text Installation > *when reporting a bug add logs from /temp as separate text/plain > attachments > > 09:82:43 Not asking for VNC because we don’t have a network > > > 09:83:48 x startup failed, aborting Installations > stuck for 22s! [Xorg:1296] > > 09:83:48 x startup failed, aborting Installations > stuck for 23s! [Xorg:1296] > > The installation cannot continue and the system will reboot > > > Press ENTER to continue > > > At the bottom of the screen it says PANE DEAD Add nomodeset to your installer's boot options. If that doesn't work, try the "Inst.text bootoption to start text Installation". -- 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/a93460763b11be123434bd8573f3d4ff.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] hdparm?
On Mon, February 5, 2018 5:22 pm, donoban wrote: > > On 02/05/2018 06:21 PM, donoban wrote: > >> On 02/05/2018 05:37 PM, 'Guillaume Bertin' via qubes-users wrote: >> >>> I don't manage installing hdparm in dom0. No package... > > Sorry I mean 'sudo qubes-dom0-update hdparm' That's interesting, what version of Qubes? I tried that before (thought it was hdparm too) and ran into the same missing package issue. -- 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/bc8c9bbc119e81a03bb7db7356af2e5f.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Manager / Qubes 4.0 R3 ?
On Mon, February 5, 2018 5:57 pm, 'Tom Zander' via qubes-users wrote: > On Monday, 5 February 2018 08:00:35 CET 'awokd' via qubes-users wrote: > > Release candidates are, like the word describes, not made unless the > developers are thinking that its ready to release but needs more > real-world testing to make sure. That's fine, but it doesn't negate my main point of if your main goal is stability, you should be running R3.2. That's what it's there for. If you want to help out the project and don't mind a few rough edges, by all means try out R4.0 and contribute bug reports and/or code fixes if possible. -- 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/012dc00cbcdbc1ee86182622317ae4bb.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] hdparm?
On Mon, February 5, 2018 5:43 pm, donoban wrote: > On 02/05/2018 06:38 PM, 'awokd' via qubes-users wrote: > >> On Mon, February 5, 2018 5:22 pm, donoban wrote: >>> Sorry I mean 'sudo qubes-dom0-update hdparm' Sure enough, I tried the above on both versions and it worked just fine. (But the warnings in https://www.qubes-os.org/doc/copy-from-dom0/ still apply.) Thanks for the info! -- 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/3ac68b13f4e3c5057fc2b2054d5ecbab.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 4.0-rc4 install on Lenovo G505S - no network
On Thu, February 8, 2018 1:58 am, dbr287 wrote: > This worked fine. Applied 2 patches, and rebuild coreboot, flashed, and > re-ran R4.0rc4 install, works like a charm. Thanks again for the prompt > response. Great! They are pretty unique laptops. PS Don't suppose you (or anyone else reading and interested) are any good at C++? Would be nice to get that Coreboot patch re-activated and working properly. I can usually hack my way around code but that AGESA code base is beyond my skill-set. -- 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/518a0c838a52d3aed8bf8a2152d02e08.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Windows on R4 (rc4) - DVD or iso not detected
On Fri, February 9, 2018 10:25 am, Alex Dubois wrote: > On Friday, 9 February 2018 08:35:17 UTC, awokd wrote: > >> On Fri, February 9, 2018 8:25 am, Alex Dubois wrote: >> Try >> qvm-prefs win7 kernel "" > > @awokd, I've created a pull request to update the doc > https://github.com/QubesOS/qubes-issues/issues/3055 Thank you! Found it under https://github.com/QubesOS/qubes-doc/pull/576. I'm planning on leaving the Win7 on R4.0 documentation to the future maintainer of QWT 4.0 right now, but that question comes up a lot. It applies to other OSes in an HVM too, maybe it should also be a FAQ? -- 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/2318b87c152156fc16efdbdcceb15d99.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to set/hange propterty 'Qubes.default_dispvm'?
On Fri, February 9, 2018 8:11 am, Johannes Graumann wrote: > and fail to understand/find where that particular property is set, > respectively may be changed ... Check qubes-prefs 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/230307780e4b9e0c0991a85f21be3d2d.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Windows on R4 (rc4) - DVD or iso not detected
On Fri, February 9, 2018 8:25 am, Alex Dubois wrote: Try qvm-prefs win7 kernel "" -- 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/fa3ce3600e1c5df04258d58cb441fc2c.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
