Re: [qubes-users] Shutdown Delay
Hi, I also experience(d) shutdown delays in the beginning of my qubes OS experience in about 1/10 shutdowns. I never had any NFS mounts or alike that should have caused it. After thrawling through the journalctl messages there was always some VM that waited for a process to exit. Instead of decreasing the shutdown time delay in systemd for dom0 any every appVM, I decided to manually shutdown the appVMs and shutdown dom0 afterwards, which eradicated the problem near to complete. In fact I don't remember the last time i had to wait for a reboot/shutdown. A simple alias in .bashrc for user in dom0 did the trick for me. alias shutdown='qvm-shutdown --all --wait;sync;sudo shutdown -h now' alias reboot='qvm-shutdown --all --wait;sync;sudo reboot' Hope this is useful for you guys --- Ursprüngliche Nachricht --- Von: Ulrich Windl Datum: 28.12.2022 11:00:57 An: qubes-users@googlegroups.com Betreff: [qubes-users] Shutdown Delay Hi! Am I the only one that sees extra shutdown delays? It seems that everything is unmounted, but still thing hang; unsure what that is. See attachment. What surprises me is that crypto seems to be stopped before unmount. Regards, Ulrich -- 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/9818d02c-f3ba-4a63-9492-e5ea418c6794%40rz.uni-regensburg.de. Your E-Mail. Your Cloud. Your Office. eclipso Mail & Cloud. https://www.eclipso.de -- 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/b7f0009835aa8240ea99f95829fae53b%40mail.eclipso.de.
Re: [qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide
Hi, the error message is: $ lunch android_x86_64-userdebug hardware/libsensors/sensors.mk:3: error: _nic.PRODUCTS.[[device/generic/x86_64/android_x86_64.mk]]: "vendor/opengapps/build/opengapps-packages.mk" does not exist. 08:18:12 dumpvars failed with: exit status 1 Just creating the missing file, of course, doesn't fix that problem. Anyone an idea? >Hi, >i updated to previous versions to build the recent android-9.0-r2, which works >fine, but opengapps won't compile. >I can't remember the correct error message, something with >vendor/opengapps/build/opengapps-packages.mk not found. >Will try again later. >Anyone? --- Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- 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/e9fc177fa1c880ad1a51dfbba488b320%40mail.eclipso.de.
Re: [qubes-users] Android-x86 7.1-r2 with GAPPS installation guide
Hi, the error message is: $ lunch android_x86_64-userdebug hardware/libsensors/sensors.mk:3: error: _nic.PRODUCTS.[[device/generic/x86_64/android_x86_64.mk]]: "vendor/opengapps/build/opengapps-packages.mk" does not exist. 08:18:12 dumpvars failed with: exit status 1 Just creating the missing file, of course, doesn't fix that problem. Anyone an idea? >Hi, >i updated to previous versions to build the recent android-9.0-r2, which works >fine, but opengapps won't compile. >I can't remember the correct error message, something with >vendor/opengapps/build/opengapps-packages.mk not found. >Will try again later. >Anyone? --- Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- 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/b07376316d8b7b35246d0c16a14f3683%40mail.eclipso.de.
[qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide
Hi, i updated to previous versions to build the recent android-9.0-r2, which works fine, but opengapps won't compile. I can't remember the correct error message, something with vendor/opengapps/build/opengapps-packages.mk not found. Will try again later. Anyone? # Create a builder AppVM based on (whonix-14-ws or) Debian in which you'll build android-x86. # You'll need 300GB for android-x86 sources and temp build files and swap. # Extend private storage size to 300GB via GUI or in dom0: # qvm-volume extend android-builder:private 300g # Add 30GB swap in builder VM: sudo fallocate -l 30G /home/user/swapfile sudo chmod 0600 /home/user/swapfile sudo mkswap /home/user/swapfile sudo swapon /home/user/swapfile # Add the following repository to /etc/apt/sources.list (openjdk-8 is required, but it is not available under Debian 10): # skipped, works with openjdk-11 too # deb https://deb.debian.org/debian sid main # Install packages in whonix-14-ws (or Debian) template: sudo apt-get update sudo apt-get install openjdk-11-jdk gnupg flex bison gperf build-essential \ zip zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev \ x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev libxml2-utils \ xsltproc unzip gettext libyaml-dev dosfstools syslinux syslinux-utils \ xorriso mtools makebootfat lunzip git-core curl python-pip libssl-dev bc \ libelf-dev git-lfs python-pip git-core curl clang libncurses5 \ libncurses5-dev # In builder VM run: sudo ln -s /sbin/mkdosfs /usr/local/bin/mkdosfs sudo pip install prettytable Mako pyaml dateutils --upgrade export _JAVA_OPTIONS="-Xmx8G" echo 'export _JAVA_OPTIONS="-Xmx8G"' >> ~/.profile echo "sudo swapon /tmp/swapfile" >> /rw/config/rc.local # Download android-x86 sources: mkdir android-x86 cd android-x86 curl https://storage.googleapis.com/git-repo-downloads/repo > repo chmod a+x repo sudo install repo /usr/local/bin rm repo git config --global user.name "Your Name" git config --global user.email "r...@example.com" # chose what version: https://www.android-x86.org/source.html , https://osdn.net/projects/android-x86/releases/71931 # repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b oreo-x86 -m android-x86-8.1-r1.xml repo init -u git://git.osdn.net/gitroot/android-x86/manifest -b pie-x86 -m android-x86-9.0-r2.xml # ::TODO:: needs fixing # To add GAPPS to your build you need to add the build system, and the wanted sources to your manifest. ## Edit .repo/manifests/android-x86-8.1-r1.xml and add the following towards the end: # Edit .repo/manifests/android-x86-9.0-r2.xml and add the following towards the end: # https://github.com/opengapps/; /> https://gitlab.opengapps.org/opengapps/; /> # Download sources: # download ~27GB, disk usage ~63GB # repo sync --no-tags --no-clone-bundle --force-sync -j$( nproc --all ) # 2 threads sufficient repo sync --no-tags --no-clone-bundle --force-sync -j2 # If you choose to add GAPPS, then edit file device/generic/common/device.mk # and add at the beginning: # # OpenGAPPS GAPPS_VARIANT := pico GAPPS_PRODUCT_PACKAGES += Chrome \ KeyboardGoogle \ LatinImeGoogle \ GoogleTTS \ YouTube \ PixelIcons \ PixelLauncher \ Wallpapers \ PixelLauncherIcons \ WebViewGoogle \ GoogleServicesFramework \ GoogleLoginService GAPPS_FORCE_BROWSER_OVERRIDES := true GAPPS_FORCE_PACKAGE_OVERRIDES := true GAPPS_EXCLUDED_PACKAGES := FaceLock \ AndroidPlatformServices \ PrebuiltGmsCoreInstantApps # And at the end add: # # OpenGAPPS $(call inherit-product, vendor/opengapps/build/opengapps-packages.mk) # OpenGapps changed their repo to require git-lfs. There may be a better way to do this, # but if you're building with GApps, this gets the right files. It takes a while: # disk usage opengapps ~37GB # cd vendor rm -r opengapps git clone https://github.com/opengapps/opengapps.git cd opengapps git lfs install ./download_sources.sh --shallow x86_64 cd ../../ # Edit android-x86 sources for XEN compatibility: sed -i -e 's|/sys/block/\[shv\]d\[a-z\]|/sys/block/\[shv\]d\[a-z\] /sys/block/xvd\[a-z\]|g' bootable/newinstaller/install/scripts/1-install sed -i -e 's|/sys/block/\[shv\]d\$h/\$1|/sys/block/\[shv\]d\$h/\$1 /sys/block/xvd\$h/\$1|g' bootable/newinstaller/install/scripts/1-install sed -i -e 's|hmnsv|hmnsvx|g' bootable/newinstaller/initrd/init # Edit android-x86 sources for Debian build environment: sed -i -e 's|genisoimage|xorriso -as mkisofs|g' bootable/newinstaller/Android.mk # Configure build target: # https://source.android.com/setup/build/building # # user Limited access; suited for production # userdebug Like user but with root access and debug capability; preferred for debugging # eng Development configuration with additional debugging tools # . build/envsetup.sh lunch android_x86_64-userdebug # ::TODO:: breaks here # mkdir vendor/opengapps/build # touch vendor/opengapps/build/opengapps-packages.mk # Configure
Re: [qubes-users] Re: Suspend and high load issues on AppVM shutdown
Hi, thank you for advice! I tried 4.1 pre release with kernel-latest/-qubes-vm and acpi_sleep=old_ordering. This finally did the trick. Stock kernel gives me a green screen and system freeze after resuming and unlocking xscreensaver. Btrfs also works great. I noticed that dom0 really hogs up the cpu after shutdown of huge appvms. For some reasons qubes still creates a -back revision just to delete it afterwards again, though revisions_to_keep is set to 0. Using btrfs i don't even need to set that config to 0, it shutdowns in like 1-2 seconds. This is one great step towards moving to qubes os. Is there an ETA for 4.1 release date yet? Thanks for both your help I appreciate it >Hi, >if you have the time and maybe a spare SSD/HDD available you could try the >pre-release version of Qubes 4.1. >It solved several issues for me but of course it isn't bug free and I don't >know if it is regarded as safe to use securely already. --- Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- 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/55dd6bbd65d032a71f2daa4946afcf69%40mail.eclipso.de.
Re: [qubes-users] Re: Suspend and high load issues on AppVM shutdown
Hi, thanks for your replies. I searched through HCL and the mailing list for similiar problems regarding suspend bugs but without luck. Tried several approaches from latest-kernel/-qubes-vm, shutting down all AppVMs first, upgrading/downgrading BIOS, echo 1 > /sys/power/pm_trace && suspend, etc. There is one similar HCL entry for my B450 mainboard but without further info (all green except untested tpm). Regarding high system load on AppVM shutdown: My approach is to put as many (offline) data as possible in a networkless vault. Of course for security reasons: it has personal data, music files, iso files, work backup files and much more, but also for my backup strategy: instead of backing up +500GB each time, i just mount my external drive into the vault and copy only file changes with rsync. My backup time decreases from an hour down to a couple of minutes max. Switching from fedora-30 to fedora32 and debian-10 template won't change system load on shutdown significantly. Whole system runs on a SSD with luks encryption. I didn't make deep changes into the system with which i could explain this strange behaviour. Used default settings during installation. The vault has 1TB private storage reserved using the qubes manager. Is that too much? I'm gonna test Qubes 4.1 in the next few days. --- Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- 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/13072582860b582e3061eac9b9bdf4ec%40mail.eclipso.de.
[qubes-users] Suspend and high load issues on AppVM shutdown
Hello, i'm new to qubes and i like the security aspect it provides. During testing i noticed 2 problems i couldn't solve. 1. The resume from suspend function doesn't work for me. The Computer powers on again, but the screen stays black. Keyboard and mouse don't work either. Using other linux distributions force me to use acpi_sleep=old_ordering to make suspend work. Trying to boot qubes with that kernel option @multiboot and @module in grub doesn't help. 2. Having AppVMs with several hundred GB, e.g. 500GB in vault leaves the system crippled and often completly unresponsive for 1-2 minutes. Some kworkerd process in dom0 eats up 100% of a single core. This happens every time, even when i boot up the AppVM in question and shut it down immediately again. The more GB the AppVM uses the longer the shutdown takes. Seeing the HDD Led flashing nonstop during the shutdown made me curious about the snapshot feature. Unfortunately, setting the qvm-volume revert snapshot config from 1 to 0 didnt help. Neither with existing AppVMs nor with newly created AppVMs. Any help is appreciated Good day --- Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- 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/b7f507949d7d6476165841eb016ce7ea%40mail.eclipso.de.
