Re: [qubes-users] Open several files in THE SAME dispVM
On Fri, Jan 17, 2020 at 05:40:50PM +0100, r.wiesb...@web.de wrote: Hey, Is there a way to open a bunch of files in the same dispVM ? Yes, I can copy/move those files and open them in the dispVM, that is what I do right now - but it would be nice if there was a simpler way to do so. I agree, the `qvm-open-in-dvm` script should follow the same syntax as `qvm-move` and `qvm-copy` -- it should be able to take multiple files as an argument. -- 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/20200118021444.GA1049%40danwin1210.me.
Re: [qubes-users] Debugging a sleep/suspend problem on Razer Blade Stealth 2016 - Qubes
On Tuesday, January 14, 2020 at 7:58:11 AM UTC-3, Abel Luck wrote: > > Abel Luck: > > Hi there, > > > > I'm debugging similar resume issues, though on different hardware. > > Hopefully you don't mind if we share tips in this thread. > > > > > >>> I couldn't find anything related to those acpi devices. I thougth > first > >> that there was a driver for > >>> them, so I should just rmmod those drivers before sleep and insmod > when > >> wakeup, but couldn't find > >>> anything. There's this issue > >> https://ubuntuforums.org/archive/index.php/t-2393029.html which have > >>> those exact hash matches, but no answer. > >> > >> I don't know a lot about pm_trace, but it seems like there might be a > >> problem decoding the hash. > >> Normally it should show you a PCI address, /sys device name, driver > name, > >> or something more > >> specific (see example in link below). > >> > >> According to s2ram kernel documentation: > >> > >> If no device matches the hash (or any matches appear to be false > >> positives), the culprit may be a > >> device from a loadable kernel module that is not loaded until after the > >> hash is checked. You can > >> check the hash against the current devices again after more modules are > >> loaded using sysfs: > >> > >> cat /sys/power/pm_trace_dev_match > >> > >> > https://www.kernel.org/doc/html/latest/power/s2ram.html#using-trace-resume > >> > >> However, in qubes we may also have the opposite problem. Qubes takes > over > >> your network cards and > >> sometimes USB controllers in early userspace, so the drivers are not > >> available anytime. To disable > >> this behavior for USB controllers, remove rd.qubes.hide_all_usb from > the > >> kernel cmdline. For > >> network cards it's a little more complicated. > >> > >> You can try modifying the qubes initramfs hook. First, make sure there > are > >> no VMs configured to > >> start automatically at boot. Move > >> /usr/lib/dracut/modules.d/90qubes-pciback/ to your home > >> directory, or open the qubes-pciback.sh file and comment out the last 9 > or > >> so lines (from "for dev > >> in $HIDEPCI"). Rebuild the initramfs. Then, do the pm_trace again as > you > >> did before. Then, try > >> pm_trace_dev_match as described in the link above. > >> > >> It might give you better information about the problem device, or it > might > >> just give you the same > >> info as before, but it's something to try. > >> > >> If it doesn't work, don't forget to put that file back how it was, and > >> rebuild initramfs again. > >> > > > > Thanks for this tip. Using this method I was able to get a "hash > matches" > > line in my dmesg whereas before I didn't get one. > > > > I am also debugging a suspend resume issue but with a Asus z390 I Aorus > Pro > > Wifi motherboard on a desktop (and an nvidia gpu unfortunately). > > > > Some interesting facts: > > > > 1) the pci device that matched was "INT34B9:00". I can't really find > > much info about what this device is, it doesn't correspond to anything > > under lspci. /sys/bus/acpi/devices/INT34B9:00/uid contains the value > > "SerialIoUart1" > > > > 2) suspend and resume works when I execute "echo mem > > /sys/power/state". > > However when I execute the suspend from xfce or run systemctl suspend, > the > > resume fails (with a black screen but the keyboard lights up). > > > > >> Just some general tips: try kernel-latest, and Qubes R4.1, if you > haven't > >> yet. > > > Some interesting news, TL;DR is that I got suspend/resume working! > Here's how: > > > I updated dom0 to kernel-latest, booted again and with all vms off > tested suspend with this script: > > ``` > #!/bin/sh > > sync > echo 1 > /sys/power/pm_trace > echo mem > /sys/power/state > ``` > > Resume worked. However as soon as I turned on sys-usb it failed to > resume again, with the monitor staying off but the keyboard lights > turning on. > > At this point I went into my bios and disabled all the devices I could: > wlan adapter, ethernet adapter, graphics, etc. > > Throughout this point I was constantly checking for the "hash matches" > devices in dmesg and looking at /sys/power/pm_trace_dev_match. Also I > had edited qubes-pciback.sh as described by Claudia. There was never a > clear smoking gun that revealed some particular device, and the values > seemed to change with every reboot or configuration. However at one > point I noticed 'drm' in pm_trace_dev_match, and this would prove > useful later. > > My motherboard has integrated intel graphics (igfx) but also a PCIe > nvidia card. Eventually I happened upon the bios configuration where I > enabled integrated graphics (I had no option to disable the nvidias card > aside from physically removing it). > > Booting into Qubes using the igfx output, I noticed 'drm' in the > pm_trace_dev_match, which I know has something to do with the nouveau > driver. So I disabled
Re: [qubes-users] Debugging a sleep/suspend problem on Razer Blade Stealth 2016 - Qubes
On Saturday, January 11, 2020 at 4:37:17 PM UTC-3, Claudia wrote: > > January 9, 2020 1:55 AM, "Guerlan" > > wrote: > > > First of all, here's the HCL for my Razer Blade Stealth 2016 4K > touchscreen 16gb RAM 512gb SSD: > > > https://groups.google.com/forum/#!searchin/qubes-users/razer$20blade|sort:date/qubes-users/PalZ-1inx > > A/D3mQ4OI3CAAJ > > > > When I close the lid and open again, keyboard wont ligth up, screen wont > turn on (it's LED so I can > > see a brigth black when it turns on), and hitting keyboard or touchpad > does nothing. I have to > > reboot. I don't know, however, if keyboard not ligthing when I open the > lid is because sys-usb, > > which contains the keyboard, is not waken. Every other aspect of the > laptop seems to be working > > perfectly. > > When you're testing, make sure there are no VMs set to start on boot, > especially not sys-net and > sys-usb, and make sure rd.qubes.hide_all_usb is not set. You can try to > get that stuff working > later on. > > Does pressing caps lock or num lock turn on/off their lights on the > keyboard? Does ctrl-alt-delete, > or Alt-SysRq-B (you have to enable it first) cause it to reboot? If you > suspend with sound playing, > can you hear it when you try to resume? > > > I followed Ubuntu's guide on kernel suspend bugs: > https://wiki.ubuntu.com/DebuggingKernelSuspend > > > > Then, following what they suggest > > > > `sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"` > > > > and find the lines that says hash matches in dmesg rigth after reboot > (what does that mean?) > > > > Well, I found two: > > > > ``` > > [ 3.583591] ima: Allocated hash algorithm: sha1 > > [ 3.593050] input: AT Raw Set 2 keyboard as > /devices/platform/i8042/serio0/input/input4 > > [ 3.638808] Magic number: 0:929:176 > > [ 3.638867] acpi device:39: hash matches > > [ 3.638893] acpi device:0c: hash matches > > [ 3.639073] rtc_cmos 00:01: setting system clock to 2016-01-01 12:09:51 > UTC (1451650191) > > ``` > > > > I couldn't find anything related to those acpi devices. I thougth first > that there was a driver for > > them, so I should just rmmod those drivers before sleep and insmod when > wakeup, but couldn't find > > anything. There's this issue > https://ubuntuforums.org/archive/index.php/t-2393029.html which have > > those exact hash matches, but no answer. > > I don't know a lot about pm_trace, but it seems like there might be a > problem decoding the hash. > Normally it should show you a PCI address, /sys device name, driver name, > or something more > specific (see example in link below). > > According to s2ram kernel documentation: > > If no device matches the hash (or any matches appear to be false > positives), the culprit may be a > device from a loadable kernel module that is not loaded until after the > hash is checked. You can > check the hash against the current devices again after more modules are > loaded using sysfs: > > cat /sys/power/pm_trace_dev_match > > https://www.kernel.org/doc/html/latest/power/s2ram.html#using-trace-resume > > However, in qubes we may also have the opposite problem. Qubes takes over > your network cards and > sometimes USB controllers in early userspace, so the drivers are not > available anytime. To disable > this behavior for USB controllers, remove rd.qubes.hide_all_usb from the > kernel cmdline. For > network cards it's a little more complicated. > > You can try modifying the qubes initramfs hook. First, make sure there are > no VMs configured to > start automatically at boot. Move > /usr/lib/dracut/modules.d/90qubes-pciback/ to your home > directory, or open the qubes-pciback.sh file and comment out the last 9 or > so lines (from "for dev > in $HIDEPCI"). Rebuild the initramfs. Then, do the pm_trace again as you > did before. Then, try > pm_trace_dev_match as described in the link above. > > It might give you better information about the problem device, or it might > just give you the same > info as before, but it's something to try. > > If it doesn't work, don't forget to put that file back how it was, and > rebuild initramfs again. > > > Then I asked for help on a forum and they found this problematic line on > my dmesg: > > > > `[ 2.543596] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM` > > > > seems like ASPM is disabled on my Qubes. I don't know why. Should this > be considered a bug? Is > > there anything I can do to get it working? This looks promising. > > > > It's worth noting that on Ubuntu 18, 19, Fedora 30, Linux Mint, etc, all > these systems work like a > > charm with the sleep process. I can close the lid and open and it works. > So the problem seems to be > > **related to Qubes**. I even tried qubes most recent dom0 kernel, based > on 5.x linux kernel, but > > the problem persists. > > There's a pretty big difference between Fedora and Qubes. R4.0 is based on > Fedora 25, not 30. Also > have you tried suspend on any of those OSes with Xen
[qubes-users] How different from bare metal linux is Qubes NVME interaction?
I have a problem where any linux distro in my Razer Blade Stealth will suffer from NVME corruption (nvme enters in read only mode) many times a day. I tried the most recent kernel, old ones, etc. Tried opening a bug in canonical launchpad, got some help, some kernel patches to try, but none worked. I made two independent tests that prove it's not a problem in my notebok or SSD: 1, I bougth a brand new SSD, same problem. 2: neither Windows or Qubes will give the error. Actually, I installed Qubes just to see what would happen, because I wanted to run something non linux in my machine just to test. Turns out something in Qubes makes the dom0 access the NVME without any problems. The way I think Xen/Qubes NVME interaction works is like this: xen has pci front and back drivers. Front is in xen, back is in dom0. dom0 then accesses the NVME through PCI. The nvme driver in dom0 is the same as the nvme driver in my older bare metal linux distributions which had the bug, so I can only think the bug happens in the PCI level, because it's the only thing different here. Can someone with better understanding of Xen and Qubes give me a better picture and maybe guess what's happening and why I don't feel the bug at all in Qubes? -- 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/e77b4739-f44e-4265-b267-09a08ca45aa3%40googlegroups.com.
Re: [qubes-users] Re: qvm-create-windows-qube 2.0
On 2020-01-15 01:36, shiftedreality wrote: > You pointed me in the right direction. I was using Debian 10 as my default > Qubes template. Debian 10 is supposed to be supported as a template. I didn't realize the Debian 10 template qube didn't come with cURL. Bug fixed, thanks for catching that. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/64c89ed3-c824-15e5-b0f5-055420eba578%40zohomail.eu.
Re: [qubes-users] qvm-create-windows-qube 2.0
On 2020-01-17 13:25, M wrote: > Can I create a Windows 10 Pro VM qube or does it have to be a Windows 10 > Enterprise LTSC VM qube ? > Yes, Windows 10 Pro, Enterprise AND Enterprise LTSC are all supported. -- 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/01511771-9e86-4991-ad43-83c0667cabe3%40zohomail.eu.
Re: [qubes-users] qvm-create-windows-qube 2.0
On 2020-01-17 17:40, scall...@posteo.net wrote: > Am I correct that the windows-mgmt qube is just for setting up the Windows qube and can be deleted? Certainly keeping it would expedite creating new Windows qubes in the future though. Yes, that's correct. The windows-mgmt qube may be deleted afterwards if you are sure that there are no more Windows qubes you would like to create. -- 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/e3709038-e653-430b-38ee-10d298852b45%40zohomail.eu.
Re: [qubes-users] Resizing template vm works, but doesn't fix running out of space -- because updates use something called disp-mgmt
Well, I tried again and the upgrade worked. I don't get it. I changed the size of the template yesterday, and it didn't work. Today, I didn't change anything, and it did. The only thing that changed this time was that I hard-power-cycled the machine, where before I had merely shut down the vms, and then brought them up again. So, I think you are right -- after changing the size of the template vm, I had to "really" power cycle everything instead of just shutting it down using the qubes manager. Go figure. Thanks billo -- 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/8c0176d7-67c7-43f8-bb96-e9d6ee366819%40googlegroups.com.
Re: [qubes-users] Open several files in THE SAME dispVM
On 2020-01-17 11:40, r.wiesb...@web.de wrote: Hey, Is there a way to open a bunch of files in the same dispVM ? Yes, I can copy/move those files and open them in the dispVM, that is what I do right now - but it would be nice if there was a simpler way to do so. You could write a set of scripts for that fairly easily, depending on your personal use-case. Option A One possibility is to have your local script first start the DispVM instance spawning a File Manager, then figure out the new DispVM name, and in a loop send all the files to that DispVM instance. Then Use the File Manager to open the documents, and when you close the file manager the DispVM goes away. If you need to retain the documents use the file manager to send them back first. Option B 1) The first script adds all the files to a single tarfile and then calls qvm-open-in-dvm for that one archive file. You can try playing with using "Open With Other Application" from your File Manager to kick off the script, but that might just call the script multiple times. 2) Then in the DispVM and have the default app for '*.tgz' be your script set to extract and open the individual documents with their respective applications. Both the sending and receiving scripts could live in the respective templates so that all AppVMs could send multiple files and the DispVM could extract and deal with them according to the xdg default applications for the document types. If you don't like assigning the *.tgz to have a special handler you can always create the tgz file and rename it to use a unique extension not assigned to any current application. Mime/XDG association https://superuser.com/questions/162092/how-can-i-register-a-custom-protocol-with-xdg Option C Create a temporary file system in a file and then use qvm-block to clone the files and attach and mount that fs into the DispVM. When finished delete/wipe the temporary file. -- 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/191cc953-0469-53c9-efe3-f319280bff49%40jhuapl.edu.
Re: [qubes-users] qvm-create-windows-qube 2.0
Thanks Dominique. Everything working now including Qubes Windows Tools - i can copy files over at least. This is great. Am I correct that the windows-mgmt qube is just for setting up the Windows qube and can be deleted? Certainly keeping it would expedite creating new Windows qubes in the future though. scallyob On 17.01.2020 14:16, Dominique St-Pierre Boucher wrote: Concerning the download of ISO, if you open a teminal in the windows-mgmt qube that is created by the script, there is a script in /home/user/Documents/qvm-create-windows-qube/windows-media/isos/ named download-windows.sh Run that script, it will tell you what are the options. Do not forget to give network access to the windows-mgmt qube before starting the download and to remove the access after. One of the possible reason you were not able to install Windows 10 is because of the version. The Windows 10 iso you got is probably not an Enterprise Eval version so the key wont work. Dominique On Thursday, January 16, 2020 at 10:48:02 PM UTC-5, scal...@posteo.net wrote: Thanks Elliot for posting this. I'm trying this now. I saw the note saying you could download a different version of Windows in the qvm-create-windows-qube.sh. But I didn't see how that was done. Seems like you can just reference an already downloaded iso, which is what I did. I already had a Windows 10 iso. So I set it to use that iso and to use the answer file provided for win10x64-enterprise-eval.xml, but ran into the problem below. But maybe it is because of the iso i'm using? On 13.01.2020 10:48, 'Elliot Killick' via qubes-users wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Hardcoding trial product key in answer files (or anywhere) is no longer necessary, Windows will use embedded trial key without any user interaction by default This doesn't seem to be the case. I'm getting the following: on "Commencing first part of Windows installation process..." in the install.sh script I get a popup from "Windows Setup" that says Windows cannot read the setting from the unattend answer file." I click "OK" and it reboots to a black screen from SeaBIOS that ends with "No bootable device." * windows-mgmt is air gapped What is this qube used for? Is it just for the setup? Can I delete it after done? Thanks. -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d871a2b3-e34b-4eec-b89a-47f07dec0bc5%40googlegroups.com [1]. Links: -- [1] https://groups.google.com/d/msgid/qubes-users/d871a2b3-e34b-4eec-b89a-47f07dec0bc5%40googlegroups.com?utm_medium=email_source=footer -- 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/e0c6ea93c0ee5056b053d199d531d602%40posteo.net.
[qubes-users] Open several files in THE SAME dispVM
Hey, Is there a way to open a bunch of files in the same dispVM ? Yes, I can copy/move those files and open them in the dispVM, that is what I do right now - but it would be nice if there was a simpler way to do so. Thank you -- 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/8a0e0ace-ede1-752d-6453-a73828a1a9a4%40web.de.
Re: [qubes-users] Resizing template vm works, but doesn't fix running out of space -- because updates use something called disp-mgmt
>I got a ping saying there was an update for my fedora-30 template VM, So, I >started the Qubes updater. I then get the error that it needs an additional >34 MB to install the kernel image. No problem, I think. So I go to the >documentation and look up how to increase the size of the template VMs. Easy >peasy -- I increase the size of the Fedora-30 template by a couple of gigs, >and reboot-- and the new space shows up. Great I think. I start the updater >and get the same error. I then watch it happen, and when I start the updater, >it opens something called the "disp-mgmt-fedora-30" vm, which I didn't even >know existed. Obviously, changing the size of the fedora template vm didn't >change the size of this. > >How do I change the size of the "disp-mgmt-fedora-30" vm -- and is it safe to >to? I assume it's hidden from me for a reason... I had a similar issue, but more space was required. I increased the "System storage max. size" by a couple GB on the Fedora-30 template, attempted the update install again, and it was successful. To do this, go to the "Qube Settings" of the fedora-30 template, and under the "Disk storage" section of the "Basic" settings tab, increase the "System storage max. size:" by whatever amount you need. I'm not sure if it is a requirement for the Qube (the fedora-30 template in this case) to be powered off, but I doubled checked and made sure mine was before making this change. I apologize in advance if the formatting of this isn't correct, and a second apology for forgetting to copy the mailing list the first time. --Cody -- 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/GfE4PR5RH8x8bLDwgXN4Z7HR5CpR77ap_wpIF6RLiGBqP1Xt_UPt3GkREQNZpaEB6u7tujvzs_wc4vH6JChU8t3MAQonWcRwEVslbO05VrA%3D%40protonmail.com. publickey - cody.r.gardner@protonmail.com - 0x848675CB.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] qvm-create-windows-qube 2.0
Can I create a Windows 10 Pro VM qube or does it have to be a Windows 10 Enterprise LTSC VM qube ? -- 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/3695138b-0511-4ab6-b2f5-c555487a0371%40googlegroups.com.
Re: [qubes-users] qvm-create-windows-qube 2.0
Concerning the download of ISO, if you open a teminal in the windows-mgmt qube that is created by the script, there is a script in /home/user/Documents/qvm-create-windows-qube/windows-media/isos/ named download-windows.sh Run that script, it will tell you what are the options. Do not forget to give network access to the windows-mgmt qube before starting the download and to remove the access after. One of the possible reason you were not able to install Windows 10 is because of the version. The Windows 10 iso you got is probably not an Enterprise Eval version so the key wont work. Dominique On Thursday, January 16, 2020 at 10:48:02 PM UTC-5, scal...@posteo.net wrote: > > Thanks Elliot for posting this. I'm trying this now. I saw the note > saying you could download a different version of Windows in the > qvm-create-windows-qube.sh. But I didn't see how that was done. Seems > like you can just reference an already downloaded iso, which is what I > did. I already had a Windows 10 iso. So I set it to use that iso and to > use the answer file provided for win10x64-enterprise-eval.xml, but ran > into the problem below. But maybe it is because of the iso i'm using? > > On 13.01.2020 10:48, 'Elliot Killick' via qubes-users wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > * Hardcoding trial product key in answer files (or anywhere) is no > > longer necessary, Windows will use embedded trial key without any > > user interaction by default > > This doesn't seem to be the case. > I'm getting the following: > on "Commencing first part of Windows installation process..." in the > install.sh script > I get a popup from "Windows Setup" that says Windows cannot read the > setting from the unattend answer file." I click "OK" and it > reboots to a black screen from SeaBIOS that ends with "No bootable > device." > > > * windows-mgmt is air gapped > > > What is this qube used for? Is it just for the setup? Can I delete it > after done? > > Thanks. > > > -END PGP SIGNATURE- > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d871a2b3-e34b-4eec-b89a-47f07dec0bc5%40googlegroups.com.
