[qubes-users] Script net-vm of dvm at startup
Good day Qubes community, I have multiple sys-vpn machine connecting to different vpn provider. I would like to have a DVM that ask at startup which sys-vpn machine to use as its net-vm. I was wondering if anyone had done it before? Or if anyone had brilliant idea how I could do it. Thanks Dominique -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/924a2a46-ffdc-403a-a69b-e5bfdc5f4b0c%40googlegroups.com.
[qubes-users] AppVM won't start any application
Hi, I am a new user and I'm very happy with the OS. I installed it a few days ago and I seem to have an issue. I would delete and re-create the qube but it could be a helpful opportunity for both me and you to debug some issue. I have a qube based on debian-10 fully updated. It didn't have any particular configuration, a bigger volume as I planned on using it more. Suddenly it won't start any program, not even the terminal. >From /var/log/xen/console, it seems like the AppVM is starting: [.[0;32m OK .[0m] Reached target .[0;1;39mRemote File Systems.[0m. Starting .[0;1;39mVirtualization daemon.[0m... Starting .[0;1;39mPermit User Sessions.[0m... Starting .[0;1;39mDeferred execution scheduler.[0m... Stopping .[0;1;39mNFSv4 ID-name mapping service.[0m... Stopping .[0;1;39mNFS Mount Daemon.[0m... [.[0;32m OK .[0m] Stopped .[0;1;39mNFSv4 ID-name mapping service.[0m. [.[0;32m OK .[0m] Stopped .[0;1;39mNFS Mount Daemon.[0m. [.[0;32m OK .[0m] Started .[0;1;39mPermit User Sessions.[0m. [.[0;32m OK .[0m] Started .[0;1;39mGetty on tty1.[0m. [.[0;32m OK .[0m] Started .[0;1;39mSerial Getty on hvc0.[0m. [.[0;32m OK .[0m] Reached target .[0;1;39mLogin Prompts.[0m. [.[0;32m OK .[0m] Created slice .[0;1;39msystem-systemd\x2dfsck.slice.[0m. Starting .[0;1;39mFile System Check on /dev/xvdb.[0m... [.[0;32m OK .[0m] Created slice .[0;1;39mUser Slice of UID 1000.[0m. Starting .[0;1;39mUser Runtime Directory /run/user/1000.[0m... [.[0;32m OK .[0m] Started .[0;1;39mUser Runtime Directory /run/user/1000.[0m. Starting .[0;1;39mUser Manager for UID 1000.[0m... [.[0;32m OK .[0m] Started .[0;1;39mDeferred execution scheduler.[0m. [.[0;1;31mFAILED.[0m] Failed to start .[0;1;39mFile System Check on /dev/xvdb.[0m. See 'systemctl status systemd-fsck@dev-xvdb.service' for details. [.[0;1;33mDEPEND.[0m] Dependency failed for .[0;1;39m/rw.[0m. [.[0;1;33mDEPEND.[0m] Dependency failed for .[0;1;39m/home.[0m. [.[0;1;33mDEPEND.[0m] Dependency failed for .[0;1;39mSession c3 of user user.[0m. [.[0;1;33mDEPEND.[0m] Dependency failed for .[0;1;39mSession c1 of user user.[0m. [.[0;1;33mDEPEND.[0m] Dependency failed for .[0;1;39mSession c2 of user user.[0m. [.[0;32m OK .[0m] Started .[0;1;39mUser Manager for UID 1000.[0m. [ 25.704176] loop: module loaded [ 25.716721] squashfs: version 4.0 (2009/01/31) Phillip Lougher [.[0;32m OK .[0m] Started .[0;1;39mSnappy daemon.[0m. Starting .[0;1;39mWait until snapd is fully seeded.[0m... [ 26.676431] fbcon: Taking over console Debian GNU/Linux 10 vm hvc0 vm login: A popup now appears (it wasn't appearing before): "Domain has failed to start: Snapshot origin LV vm-debian-10-root not found in Volume group qubes_dom0". Another popup: "Device /tmp/sanity... removed (deleted)", I don't know if it's related. When I shut down the AppVM, it "restart by itself". When I shut it down again then it doesn't boot anymore. Where can I find more logs on this, how should I 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/JDtigFBN-MvPmYiNC03t1wCt6NrAvr6d1Gr5PVcB1V6ZURaiqopBTiXKWas3JTUXNdhuPQ-En7PYwN1Qj24l3Lef5O-ZUnSZvg1Zi6tCr54%3D%40protonmail.com.
[qubes-users] HCL - MSI GS65
Required LEGACY mode in BIOS and disable nvidia drivers during installation. Problematic : setting brightness using keys (but not a big issue) WiFi sleep mode - required some minor fix in GRUB rest works fine. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABZ%3DSx8zOkMcHhO9efM-n9YcavnDyinGk_Cb9qhEJW2VVFK7iw%40mail.gmail.com. Qubes-HCL-Micro_Star_International_Co___Ltd_-GS65_Stealth_Thin_8RF-20200423-201459.yml Description: application/yaml
Re: [qubes-users] Storing AppVMs on Secondary Drives
Am Dienstag, 21. April 2020 21:42:31 UTC+2 schrieb dono...@unseen.is: > > > > - On Apr 21, 2020, at 12:31 PM, qubes-users > wrote: > > > > Am Dienstag, 21. April 2020 17:47:58 UTC+2 schrieb unman: >> >> On Tue, Apr 21, 2020 at 05:56:33AM +0200, 'J??rg Widmann' via qubes-users >> wrote: >> > Hello, >> > >> > I'm trying to add a second HDD to my system. I followed the guide on >> > https://www.qubes-os.org/doc/secondary-storage/, everything but the >> last >> > step seems to work. >> > >> > qvm-pool --add poolhd0_qubes lvm_thin -o >> > volume_group=qubes,thin_pool=poolhd0,revision_to_keep=2 >> > >> > usage: qvm-pool [--verbose] [--quiet] [--help] [-o options] >> > [-l | -i POOLNAME | -a NAME DRIVER | -r NAME | -s >> POOLNAME >> > | --help-drivers] >> > >> > qvm-pool: error: failed to add pool poolhd0_qubes: Got empty response >> from >> > qubesd. See journalctl in dom0 for details. >> > >> > journalctl: >> > >> > dom0 qubesd[31119]: permission denied for call >> > b'admin.pool.Add'+b'lvm_thin' (b'dom0' ??? b'dom0') with payload of 75 >> bytes >> > >> >> "permission denied" - try call with sudo ? >> > > Am Dienstag, 21. April 2020 17:47:58 UTC+2 schrieb unman: >> >> On Tue, Apr 21, 2020 at 05:56:33AM +0200, 'J??rg Widmann' via qubes-users >> wrote: >> > Hello, >> > >> > I'm trying to add a second HDD to my system. I followed the guide on >> > https://www.qubes-os.org/doc/secondary-storage/, everything but the >> last >> > step seems to work. >> > >> > qvm-pool --add poolhd0_qubes lvm_thin -o >> > volume_group=qubes,thin_pool=poolhd0,revision_to_keep=2 >> > >> > usage: qvm-pool [--verbose] [--quiet] [--help] [-o options] >> > [-l | -i POOLNAME | -a NAME DRIVER | -r NAME | -s >> POOLNAME >> > | --help-drivers] >> > >> > qvm-pool: error: failed to add pool poolhd0_qubes: Got empty response >> from >> > qubesd. See journalctl in dom0 for details. >> > >> > journalctl: >> > >> > dom0 qubesd[31119]: permission denied for call >> > b'admin.pool.Add'+b'lvm_thin' (b'dom0' ??? b'dom0') with payload of 75 >> bytes >> > >> >> "permission denied" - try call with sudo ? >> > > yes I have tried with sudo, same error > -- > > Make sure you're not trying to use existing names for the new pool, vol, > etc. That's probably not the issue - just tossing that out. > i tried with different names but no luck same 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/48ae022f-4e32-42dd-b8ff-488f5f60baf0%40googlegroups.com.
Re: [qubes-users] Me (anon-whonix AppVM) -> Tor -> VPN, settup with Mullvad VPN
Chris Laprise: > On 4/21/20 11:30 AM, taran1s wrote: >> Thank you, this did the trick ^^ Link is up. I will test it with the >> setup me -> sys-whonix -> ProxyVM setup -> >> clearnet_Tor_unfriendly_services ;) >> >> If I understand it well, I can select a new VPN country for the >> particular session just by executing sudo cp any_country_I_need.ovpn >> vpn-client.conf right? >> > > Yes, that will work. To change without restarting the VPN VM, you can do: > > sudo service qubes-vpn-handler stop > sudo cp some_location.ovpn vpn-client.conf > sudo service qubes-vpn-handler start > All is working well. Thank you very much Chris. At the end it is actually very easy to set up and run. The point was my luck of experience in basic commands related to Linux and most probably selecting wrong mullvad setup files for my planned routing (me->tor->vpn). Now it is much clearer. You mention in your previous email "I suggest you look at an introduction to Linux command line". Do you have any good resource for that? Thank you 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ac626b17-6ee7-4ac7-47cc-9eeff99141b8%40mailbox.org. 0xA664B90BD3BE59B3.asc Description: application/pgp-keys
Re: [qubes-users] Pulseaudio update error - fedora-31
On 22/04/2020 21.54, 'Max Andersen' via qubes-users wrote: > > Hi everyone, > > I remember some time ago we had issues with pulseaudio on earlier > templates, and I believe a reinstall of pakages fixed the issue. I > can't seem to get myself out of trouble with this one on fedora-31. > > When doing update I get: > > user@fedora-31 ~]$ sudo dnf update > Last metadata expiration check: 0:50:13 ago on Wed Apr 22 20:44:57 2020. > Dependencies resolved. > > Problem 1: package pulseaudio-qubes-4.0.27-1.fc31.x86_64 requires > pulseaudio = 13.0, but none of the providers can be installed > - cannot install both pulseaudio-13.99.1-3.fc31.x86_64 and > pulseaudio-13.0-1.fc31.x86_64 > - cannot install both pulseaudio-13.0-1.fc31.x86_64 and > pulseaudio-13.99.1-3.fc31.x86_64 > ... This happens probably because we don't have automatic builds of pulseaudio-qubes packages when upstream releases new packages. -- Rudd-O http://rudd-o.com/ -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/46ee7908-f053-7e17-feac-4180866bea09%40rudd-o.com.
