Re: [qubes-users] Realtek wifi adapter rtl8821ce
On Saturday, April 6, 2019 at 12:44:58 AM UTC+5:30, awokd wrote: > Jayen Desai wrote on 4/5/19 3:55 PM: > > Hello, > > > > I have realtek wifi adapter in my lenovo laptop ideapad 330 15arr model. It > > is not recognised by sys-net VM. I have downloaded the driver package from > > the following link: > > > I think development workflow is different in Qubes OS. Any pointers, help, > > ideas? > > If you haven't already, try switching sys-net to use the debian-9 > template. It might work with no extra effort. If not, check to see if > there's a firmware package available (in Debian). > > https://www.qubes-os.org/doc/managing-vm-kernel/ is instructive. Note > "[i]nstalling additional kernel modules is cumbersome." The key is that > since kernels are supplied by dom0, you can't just compile in a module > in a template. > > An ugly way to make it work would be to clone debian-9 to a standalone > VM, boot using its local kernel, compile in your module, then use that > as your sys-net. It would break several Qubes protection features if you > do that. Fedora would also work if you can get u2mfn/DKMS working. The > better way to do it is described in the above link, or you could > purchase a better supported Wifi card. :) Thanks awokd for your help. I think the best option for me would be to go in for a supported wifi card. Can you suggest a supported wifi card which supports wireless AC standards and will work out-of-the box with Qubes OS R4.0? -- 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/3fb9380d-1c18-47c7-8fde-cf65c61498eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Corebooted G505s Suspend/Resume Fails
2019. április 1., hétfő 23:21:07 UTC időpontban awokd a következőt írta:
> Trying to debug this; not something I use often but would be nice to
> figure it out. Under Linux Mint 19.1 (no noises please, it was
> convenient for troubleshooting), suspend "just works"- I close the lid,
> power light starts blinking off & on, opening lid resumes normally.
> Under Qubes 4.0.1, closing the lid acts like above, but resume hangs on
> a black screen and the CPU fan slowly spinning up to full speed. Holding
> down power button isn't enough to recover- although it will power off,
> when I power back on it's still stuck the same way. I have to pull the
> battery and power cable to get it to boot. I've tried:
>
> - shutting down sys-net and sys-usb prior to suspend
> - shutting down just sys-usb (since only those devices have no-strict-reset)
> - adding mem_sleep_default=deep to kernel boot options
> - adding mem_sleep_default=shallow to kernel boot options [resulted in
> only screen going to sleep but not coming back]
> - adding acpi.ec_no_wakeup=1 to kernel boot options
>
> Dmesg says "ACPI: (supports S0 S1 S3 S5)" and /sys/power/mem_sleep says
> "s2idle shallow [deep]". The last log lines before it enters suspend are:
>
> dom0 systemd[1]: Starting Suspend...
> dom0 systemd-sleep[3586]: Suspending system...
> dom0 kernel: PM: suspend entry (deep)
>
> Then nothing until I force a reset.
>
> Any suggestions for a more intelligent way to troubleshoot? Logs or
> settings I can look at somewhere in Mint that would give me a hint how
> it's managing to successfully resume?
This issue is due to a xen patch ("Fix resume, when using microcode upgrade"),
that has been included when releases changed from xen-4.8.3-4 to xen-4.8.3-5.
This patch checks the availability of previous CPU features (..Spectre) during
resume, and results in a xen panic on G505s - IMHO due to the static nature how
the most recent (0x600111f) AMD microcodes need to be compiled in Corebooted
systems.
It is no use to revert the whole patch, because it'll break the other xen
patches introduced since. But you can:
diff -ur a/xen/arch/x86/acpi/power.c b/xen/arch/x86/acpi/power.c
--- a/xen/arch/x86/acpi/power.c 2019-03-31
+++ b/xen/arch/x86/acpi/power.c 2019-03-31
@@ -256,9 +256,9 @@
microcode_resume_cpu(0);
-if ( !recheck_cpu_features(0) )
+/*if ( !recheck_cpu_features(0) )
panic("Missing previously available feature(s).");
-
+*/
/* Re-enabled default NMI/#MC use of MSR_SPEC_CTRL. */
ci->spec_ctrl_flags |= (default_spec_ctrl_flags & SCF_ist_wrmsr);
spec_ctrl_exit_idle(ci);
have this workaround, which solves the issue until someone provides a working
solution on CB'd systems with AMD Fam15h. (..and also assesses the possible
security impacts...)
Of course you'll need to recompile git:qubes-vmm-xen, but that is
straightforward.
There could be some strange kernel messages in dom0 after resume, and you might
have issues in sys-net devices waking up, but this mostly works fine (with
kernel 4.14.103 --> kernels 4.19-xx still have issues with the radeon module)
--
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/858aefa1-dc2a-46ad-ad31-7539a12bc2e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes Os 4.0 - problem with performance
On Fri, Apr 05, 2019 at 06:38:19PM +, 'awokd' via qubes-users wrote: > Cranix wrote on 4/5/19 3:18 PM: > > Hello, > > I have PC with 8GB RAM, hdd and AMD FX X-6. Qubes Os 3.2 was working > > fine. Unfortunately Qubes Os 4.0 is very slow. Booting up takes ~15min, > > then spawning VM takes about 5 minutes or more. What is worse appvms > > itselfs are slow. I mean they need significant amount of time to respond > > to my actions. They are so slow that this system is practicly unusable. > > > > Text mode stuff and web browser are rather torelabre in terms of > > performance. Kicad is usuable, especially loading it's libraries takes > > ages. > > > > i have laptop with 8GB ram and SSD and both Qubes 3.2 and 4.0 works > > fine. > > > > I have no idea how i can fix this problem. I can run benchmarks and/or > > paste logs, just please tell me what will be helpfull to troubleshoot > > this problem. Should i update my hardware? A have asked a few people on > > IRC but we did not managed to find source of this problem. > > Check the following for warnings: > /var/log/Xorg.0.log > /var/log/xen/console/hypervisor.log > journalctl -b > > > I'm trying to analyse diferences between Qubes Os 3.2 and 4.0. > > Are new features in CPU used in Qubes 4.0 that are not used in Qubes > > 3.2? Something related to storage? > > Yes, see > https://www.qubes-os.org/faq/#can-i-install-qubes-4x-on-a-system-without-vt-x-or-vt-d. I see Qubes 4 running fine on x230 with HDD and 8GB RAM. Boot up time of 15 mins? There's something seriously wrong. VM starting 5 mins? SERIOUSLY wrong. Certainly check those logs. Try systemd-analyze blame to see if there are any services need attention, and systemd-analyze plot for a graphical view. -- 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/20190405235902.326wfuoio26shjtp%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: is this time issue ever going to be properly fixed?
On Fri, Apr 05, 2019 at 08:28:12PM +, 'awokd' via qubes-users wrote: > Jon deps wrote on 4/5/19 10:21 AM: > > On 4/5/19 6:21 PM, 'awokd' via qubes-users wrote: > > > Jon deps wrote on 4/4/19 4:30 PM: > > > > > > > > on rebooting my taskbar time is for some reason not persisting Again ! > > > > I can try explaining but there seem to be too many moving > > > > parts to ever get this to stop breaking on random reboots ? > > > > > > > > > > > I know it was supposed to have been fixed at one point and I had > > > > been using a different template that wasn't broken, maybe I > > > > need to go find that manual fix and try it again though my > > > > debian-10 was just an upgrade not a new template , but maybe > > > > the upgrade broke ntp or something , doesn't explain why > > > > fedora-29 would be broken > > > > > > Yes, going back to fedora-28 or debian-9 should fix it. It's > > > possible the issue re-occurred in fedora-29. Try the same manual fix > > > there. > > > > > > Think Qubes' policy is only the current version of Debian is > > > supported, so if you choose to upgrade to 10 it's entirely possible > > > you'll break things. If I remember right, there will be an > > > announcement once 10 is supported and available for download as a > > > template. > > > > > > > > > > > > > PS: is it a bad idea to upgrade (which I've done successfully to > > debian-10) if the templates are not available, guess I was thinking > > the fact that I was able to upgrade means there were templates there > > ... > > It's not a bad idea per se, just unsupported. That means there's a higher > chance of you running into problems with Qubes related utilities, and any > fixes or workarounds from the Qubes OS team will be low priority compared to > versions they actively support. However, if you are able to contribute by > testing out new versions and possibly developing fixes, that can save them > time! > Also, lets not forget that Debian10 is "testing" - it's liable to break, and doesnt get security updates like stable. There are issues with some Qubes packages in buster - fixing them hasnt been a high priority until the buster freeze. -- 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/20190405234847.lw33b55rxnckduiu%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Audio Recording
Excellent! I guess I had been jamming it with ALSA or pulseaudio. Its working now. So how does one write command line code to change the volume (I want to define a i3 key)? thanks, Jon -- 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/21644661-f146-485b-870f-850a2d5fcbb8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520
Nicklas Williams wrote on 4/5/19 9:43 PM: On Wednesday, April 3, 2019 at 2:33:16 PM UTC-7, awokd wrote: Nicklas Williams wrote on 4/3/19 9:30 PM: Thanks for your help. The issue here is that I cannot get to the loader. If i boot to USB it works after the kernel params listed above, but this model cannot do legacy boot to internal drives. I have to do UEFI install but UEFI fails before I get to anaconda. I need to be able to change the original ISO somehow to add the kernal params to turn off nouveau but because ISO is a read only file, it doesn't work. I tried copying the files to a folder, then making an ISO from the folder, but that method does the same thing. It will attempt to boot, then either go to the "dracut timeout" screen, or it just goes to a blank screen with no further activity. Very frustrating, since I bought this laptop specifically to use Qubes, now im finding out that I can't install it. Is there any way to edit the qubes ISO file so I dont have the nouveau driver activated? Every method ive tried tells me "read only file" Try "apt install isomaster" in Debian. So I attempted to use ISOmaster and it worked fine, however whenever I tried to write the file in rufus it wouldnt give me the option of creating it in DD mode. No matter how I save this ISO after editing, it never allows me to write it in DD mode like the original ISO. I can still attempt to boot but it takes me to the "dracut initqueue error" and fails. The issue here is getting the ISO created properly and after 100 tries on multiple systems, USBs etc i still havent managed to get it working. I've tried every procedure I found online and I have not gotten it to install other than on USB legacy mode, but then it wont boot from the internal drive in legacy mode. Sorry, hoped that would be a shortcut! Here's a different way: https://www.engetsu-consulting.com/blog/installing-qubes-4-0-on-laptops-with-nvidia-gpus-that-do-not-support-the-nouveau-driver. Got it from https://www.mail-archive.com/qubes-users@googlegroups.com/msg27111.html. Step #4 doesn't look right to me in that email, I think you'd only want to use one editor. -- 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/aa71fdb2-926d-c18e-1bea-51edc842986e%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520
On Wednesday, April 3, 2019 at 2:33:16 PM UTC-7, awokd wrote: > Nicklas Williams wrote on 4/3/19 9:30 PM: > > Thanks for your help. The issue here is that I cannot get to the loader. > > If i boot to USB it works after the kernel params listed above, but this > > model cannot do legacy boot to internal drives. I have to do UEFI install > > but UEFI fails before I get to anaconda. I need to be able to change the > > original ISO somehow to add the kernal params to turn off nouveau but > > because ISO is a read only file, it doesn't work. I tried copying the > > files to a folder, then making an ISO from the folder, but that method does > > the same thing. It will attempt to boot, then either go to the "dracut > > timeout" screen, or it just goes to a blank screen with no further > > activity. Very frustrating, since I bought this laptop specifically to use > > Qubes, now im finding out that I can't install it. Is there any way to > > edit the qubes ISO file so I dont have the nouveau driver activated? Every > > method ive tried tells me "read only file" > > > > Try "apt install isomaster" in Debian. So I attempted to use ISOmaster and it worked fine, however whenever I tried to write the file in rufus it wouldnt give me the option of creating it in DD mode. No matter how I save this ISO after editing, it never allows me to write it in DD mode like the original ISO. I can still attempt to boot but it takes me to the "dracut initqueue error" and fails. The issue here is getting the ISO created properly and after 100 tries on multiple systems, USBs etc i still havent managed to get it working. I've tried every procedure I found online and I have not gotten it to install other than on USB legacy mode, but then it wont boot from the internal drive in legacy mode. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/acd0ad90-e0f5-476d-bff8-60ecdcb53ecf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] File system check
Franz wrote on 4/5/19 7:08 PM: Hello, A friend who is helping me debug some errors downloading a cryptocurrency blockchain suggested a file system check. He thinks it is a hard disk/file system problem. He suggested booting with a rescue disk and checking the whole disk for errors. Which is the proper way to do that with Qubes? Can't answer your question directly, but for the application you describe you shouldn't have to. Assuming you're running the blockchain app in its own AppVM, that's the only filesystem you'd need to check which you can do with the standard commands from a Terminal session on it. If there are any lower level storage issues, they should show up there 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/1ee4454b-5034-f59c-4b32-96f213ebac63%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Confused about virtualization's protections
Mark Newman wrote on 4/5/19 8:00 PM: I understand how Xen works to compartmentalize one VM from another. What I don't understand is how or if it can help protect from things like rootkits, key loggers and especial the Intel Management Engine backdoor. (See: https://www.eff.org/deeplinks/2017/05/intels-management-engine-security-hazard-and-users-need-way-disable-it) I am not a security professional, and am hoping someone can explain so I can understand. Qubes helps protect from these threats by making it more difficult to exploit them. Unauthorized code needs to install that rootkit or key logger on a machine somehow. See https://www.qubes-os.org/intro/ for an overview. If an Intel ME exploit needs to run some software on the local machine, Qubes will make it harder for it to communicate with what it needs. However, compromise that takes place solely at the hardware level is not something Qubes can protect from nor claims to. Qubes can't protect from a network attack directly against Intel ME, for example. Some users therefore use a non-onboard NIC and are also interested in Coreboot, ME Cleaner, and/or an older AMD laptop that does not have a management engine. -- 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/af367eea-7a7c-9fd8-d157-f8c692b465e6%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: is this time issue ever going to be properly fixed?
Jon deps wrote on 4/5/19 10:21 AM: On 4/5/19 6:21 PM, 'awokd' via qubes-users wrote: Jon deps wrote on 4/4/19 4:30 PM: on rebooting my taskbar time is for some reason not persisting Again ! I can try explaining but there seem to be too many moving parts to ever get this to stop breaking on random reboots ? I know it was supposed to have been fixed at one point and I had been using a different template that wasn't broken, maybe I need to go find that manual fix and try it again though my debian-10 was just an upgrade not a new template , but maybe the upgrade broke ntp or something , doesn't explain why fedora-29 would be broken Yes, going back to fedora-28 or debian-9 should fix it. It's possible the issue re-occurred in fedora-29. Try the same manual fix there. Think Qubes' policy is only the current version of Debian is supported, so if you choose to upgrade to 10 it's entirely possible you'll break things. If I remember right, there will be an announcement once 10 is supported and available for download as a template. PS: is it a bad idea to upgrade (which I've done successfully to debian-10) if the templates are not available, guess I was thinking the fact that I was able to upgrade means there were templates there ... It's not a bad idea per se, just unsupported. That means there's a higher chance of you running into problems with Qubes related utilities, and any fixes or workarounds from the Qubes OS team will be low priority compared to versions they actively support. However, if you are able to contribute by testing out new versions and possibly developing fixes, that can save them time! -- 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/4353d655-f6f4-4857-773d-981745546189%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: is this time issue ever going to be properly fixed?
On 4/5/19 6:21 PM, 'awokd' via qubes-users wrote: Jon deps wrote on 4/4/19 4:30 PM: on rebooting my taskbar time is for some reason not persisting Again ! I can try explaining but there seem to be too many moving parts to ever get this to stop breaking on random reboots ? I know it was supposed to have been fixed at one point and I had been using a different template that wasn't broken, maybe I need to go find that manual fix and try it again though my debian-10 was just an upgrade not a new template , but maybe the upgrade broke ntp or something , doesn't explain why fedora-29 would be broken Yes, going back to fedora-28 or debian-9 should fix it. It's possible the issue re-occurred in fedora-29. Try the same manual fix there. Think Qubes' policy is only the current version of Debian is supported, so if you choose to upgrade to 10 it's entirely possible you'll break things. If I remember right, there will be an announcement once 10 is supported and available for download as a template. PS: is it a bad idea to upgrade (which I've done successfully to debian-10) if the templates are not available, guess I was thinking the fact that I was able to upgrade means there were templates 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/f51d5673-53fe-5c2e-aa3d-f2a975768145%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: is this time issue ever going to be properly fixed?
On 4/5/19 6:21 PM, 'awokd' via qubes-users wrote: Jon deps wrote on 4/4/19 4:30 PM: on rebooting my taskbar time is for some reason not persisting Again ! I can try explaining but there seem to be too many moving parts to ever get this to stop breaking on random reboots ? I know it was supposed to have been fixed at one point and I had been using a different template that wasn't broken, maybe I need to go find that manual fix and try it again though my debian-10 was just an upgrade not a new template , but maybe the upgrade broke ntp or something , doesn't explain why fedora-29 would be broken Yes, going back to fedora-28 or debian-9 should fix it. It's possible the issue re-occurred in fedora-29. Try the same manual fix there. Think Qubes' policy is only the current version of Debian is supported, so if you choose to upgrade to 10 it's entirely possible you'll break things. If I remember right, there will be an announcement once 10 is supported and available for download as a template. appreciate the reply. ya, iirc, the templates being there sometimes precedes the announcements, so I went on ahead. guess my thinking was that once it was fixed it would stay fixed then afterwards, but guess I can run one template just for sys-net if I must fwiw, setting it manually with timedatectl and not even rebooting, and it ( the taskbar clock and what I think whonix wants ) seems to have reverted to UTC or some random hour actually ... as long as I know I can fix it, I'll sort it out I guess :/ -- 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/9ae32bb0-467f-5db5-476f-d7210f98c29f%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Confused about virtualization's protections
I understand how Xen works to compartmentalize one VM from another. What I don't understand is how or if it can help protect from things like rootkits, key loggers and especial the Intel Management Engine backdoor. (See: https://www.eff.org/deeplinks/2017/05/intels-management-engine-security-hazard-and-users-need-way-disable-it) I am not a security professional, and am hoping someone can explain so I can understand. Thanks, -- 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/18782191554494400%40myt3-c573aa6fc782.qloud-c.yandex.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Missing sys-USB, Reinstall?
Ray Joseph wrote on 4/5/19 4:30 PM: I have recently install V4 on a laptop. I noticed there is no sys-USB. What is the appropriate method to produce one? "sudo qubesctl state.sls qvm.sys-usb", but see https://www.qubes-os.org/doc/usb-qubes/ . I currently have no network connection either. The newly installed system had sys-net attached with the two USB controllers and no nic. So I removed the two USB controllers and added the nic. The vm no longer errors out when booted. Let's continue troubleshooting that in your other thread. I am concerned there may be more problems I have not seen yet. This is a new install; is there something I did wrong that would have caused these error? I am going on two weeks trying to fix what I have. Nothing wrong; you may have checked the box that says to combine USB and Network into the same qube. Should I just attempt to reinstall? I don't know what I should do differently. No, the steps you've already done and the command above will cover 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/e4051892-8988-f553-c403-c8848aaa993c%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Realtek wifi adapter rtl8821ce
Jayen Desai wrote on 4/5/19 3:55 PM: Hello, I have realtek wifi adapter in my lenovo laptop ideapad 330 15arr model. It is not recognised by sys-net VM. I have downloaded the driver package from the following link: I think development workflow is different in Qubes OS. Any pointers, help, ideas? If you haven't already, try switching sys-net to use the debian-9 template. It might work with no extra effort. If not, check to see if there's a firmware package available (in Debian). https://www.qubes-os.org/doc/managing-vm-kernel/ is instructive. Note "[i]nstalling additional kernel modules is cumbersome." The key is that since kernels are supplied by dom0, you can't just compile in a module in a template. An ugly way to make it work would be to clone debian-9 to a standalone VM, boot using its local kernel, compile in your module, then use that as your sys-net. It would break several Qubes protection features if you do that. Fedora would also work if you can get u2mfn/DKMS working. The better way to do it is described in the above link, or you could purchase a better supported Wifi card. :) -- 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/8f1cb5c0-4062-c1dc-8d5e-443f9fcfa249%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't Start Network, V4
Thank you. It is great to learn where/what I need to read. -- 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/b0b20163-1d41-4aa5-983b-d4f456c714e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] File system check
Hello, A friend who is helping me debug some errors downloading a cryptocurrency blockchain suggested a file system check. He thinks it is a hard disk/file system problem. He suggested booting with a rescue disk and checking the whole disk for errors. Which is the proper way to do that with Qubes? Best -- 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/CAPzH-qAOMs7y-OMCfEpZ2JyJd9VcTbP1dNwbbL9xoKP86xYuyg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Change default DisposableVM for sys-whonix?
By default, even though launching from this VM is disabled on install, it is set to dvm-fedora. Might it not be better that it be (none) or perhaps a whonix-ws dvm? I believe that even if the user enabled the capability, under the OOTB configuration, this change probably doesn't provide any additional security as root on sys-whonix can bypass onion routing. However, I believe some users tunnel TOR via VPNs and if there were perhaps an attack on the tor networking or other components in sys-whonix, AND the user turned on the capability, a default value of (none) or whonix-ws might be safer. B -- 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/4894ddbf-b928-4711-8cc5-5dcc2abab073%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes Os 4.0 - problem with performance
Cranix wrote on 4/5/19 3:18 PM: Hello, I have PC with 8GB RAM, hdd and AMD FX X-6. Qubes Os 3.2 was working fine. Unfortunately Qubes Os 4.0 is very slow. Booting up takes ~15min, then spawning VM takes about 5 minutes or more. What is worse appvms itselfs are slow. I mean they need significant amount of time to respond to my actions. They are so slow that this system is practicly unusable. Text mode stuff and web browser are rather torelabre in terms of performance. Kicad is usuable, especially loading it's libraries takes ages. i have laptop with 8GB ram and SSD and both Qubes 3.2 and 4.0 works fine. I have no idea how i can fix this problem. I can run benchmarks and/or paste logs, just please tell me what will be helpfull to troubleshoot this problem. Should i update my hardware? A have asked a few people on IRC but we did not managed to find source of this problem. Check the following for warnings: /var/log/Xorg.0.log /var/log/xen/console/hypervisor.log journalctl -b I'm trying to analyse diferences between Qubes Os 3.2 and 4.0. Are new features in CPU used in Qubes 4.0 that are not used in Qubes 3.2? Something related to storage? Yes, see https://www.qubes-os.org/faq/#can-i-install-qubes-4x-on-a-system-without-vt-x-or-vt-d. -- 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/5df2302d-4bad-5158-31ed-12a4e803814b%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't Start Network, V4
Ray Joseph wrote on 4/5/19 3:37 AM: unman, Thank you. On opening sys-net, there were two USB controllers already attached, one was 00:14.0. So I removed both and added the nic. Sys-net is now running. So I now want to test it. I thought I could just open a vm such as debian, but I found it says it can't have networking. Further reading said networking can be enabled in the Basic tab. I am guessing sys-firewall should be the choice. Then connect with Tor. Bootstrap phase stuck on 5% (10 minutes before I stopped it). There is only one AP and it is open (out of my control). Any suggestions on progressing? Skip Tor for now and verify you have network connectivity with a standard browser & AppVM like "Work". You can't browse from 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/13acaf88-edda-b9f9-38b7-a953fb21de35%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] is this time issue ever going to be properly fixed?
Jon deps wrote on 4/4/19 4:30 PM: on rebooting my taskbar time is for some reason not persisting Again ! I can try explaining but there seem to be too many moving parts to ever get this to stop breaking on random reboots ? I know it was supposed to have been fixed at one point and I had been using a different template that wasn't broken, maybe I need to go find that manual fix and try it again though my debian-10 was just an upgrade not a new template , but maybe the upgrade broke ntp or something , doesn't explain why fedora-29 would be broken Yes, going back to fedora-28 or debian-9 should fix it. It's possible the issue re-occurred in fedora-29. Try the same manual fix there. Think Qubes' policy is only the current version of Debian is supported, so if you choose to upgrade to 10 it's entirely possible you'll break things. If I remember right, there will be an announcement once 10 is supported and available for download as a 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/93d6ee0c-2896-75f2-151c-20a076bfe5c3%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] FIGLIO DI PUTTANA PAOLO BARRAI ("IL PEDOFILO DEL BITCOIN": COME LO CHIAMANO IN TUTTO IL MONDO). COL
FIGLIO DI PUTTANA PAOLO BARRAI ("IL PEDOFILO DEL BITCOIN": COME LO CHIAMANO IN
TUTTO IL MONDO). COL FIDUCIARIO DI NDRANGHETA, OLIVER CAMPONOVO, E COL
CRIMINALE BRUCIA RISPARMI, FEDERICO IZZI (FALLIMENTARISSIMO TRADER ZIO ROMOLO),
LAVA € ASSASSINI. A LUGANO!!!
E' UN BASTARDO PEDERASTA ASSASSINO PAOLO BARRAI (FACEBOOK)! OLTRE CHE NOTO
RICICLA SOLDI MAFIOSI! ED E' ANCHE UN PEDOFILO CHE EFFETTUA FILM PORNO
STUPRANDO BAMBINI: PAOLO BARRAI! E TANTO QUANTO, COCAINOMANE PAZZO E MANIACO
FACENTE FILM PORNO EFFETTUANDO SESSO ORALE CON CAVALLI: PAOLO BARRAI ( NON PER
NIENTE E' NOTISSIMO IN TUTTO IL MONDO COME " CCC CIUCCIA CAZZI DI CAVALLO PAOLO
BARRAI")! E' LADRO, TRUFFATORE, SEMPRE FALSO, INCAPACISSIMO IN BORSA, AZZERANTE
E RISPARMI DI TUTTI E SEMPRE: PAOLO BARRAI! E' NAZI-ST-ALKER VIA INTERNET,
MANDANTE DI OMICIDI, E' TORTURATORE OMICIDA: PAOLO BARRAI!
IL TUTTO INSIEME
-AL FIDUCIARIO DI MAFIA, CAMORRA E NDRANGHETA: OLIVER CAMPONOVO
https://www.corrieredellacalabria.it/cronaca/item/141842-il-riciclaggio-delle-cosche-in-svizzera-facevano-tutti-cosi/
https://www.ilfattoquotidiano.it/2018/05/17/ndrangheta-e-riciclaggio-in-canton-ticino-cosi-fan-tutti-un-fiduciario-si-confessa-alla-tv-svizzera/4360372/
http://www.areaonline.ch/La-storia-del-fiduciario-ticinese-di-fiducia-della-ndrangheta-29f7ee00
http://ilpunto-borsainvestimenti.blogspot.com/2017/10/cryptopolis-il-debutto-di-un-figlio.html
- AL PORCO BRUCIA RISPARMI, RICICLA SOLDI MAFIOSI: FEDERICO IZZI DI ROMA
(CRIMINALISSIMO TRADER ZIO ROMOLO)
https://in.memory.of.e.tern.al/comp.lang.tcl/thread/4226231
- AL NOTO SATANISTA, LADRONE, TRUFFATORE, PEDOFILO ECONOMISTA PAOLO CARDENÁ DI
CRIMINALISSIMO BLOG VINCITORI E VINTI
https://www.py.cz/pipermail/python/2017-September/013036.html
- AL NOTO AVVOCATO PEDERASTA ED ASSASSINO DANIELE MINOTTI DI RAPALLO E GENOVA
https://grokbase.com/t/python/python-list/148jckyh1w/avvocato-pedofilomosessuale-ed-assassino-daniele-minotti-facebook-oltre-che-nazi-megalava-euro-mafiosi-e-come-detto-mandante-di-omicidi-o-suicidate-stalker-di-eroe-civile-michele-nista-su-ordine-di-tiranno-fasciocamorrista-silvio-berlusconi
- AL NOTO PEDOFILO NAZISTA E KU KLUK KLANISTA ARNOLD CAZARES DI LAREDO TEXAS
https://www.linkedin.com/in/arnoldcazares
- AL FIGLIO DI PUTTANA STALKER VIA INTERNET, NONCHE' PURE NOTISSIMO PEDOFILO
LUCA MORISI ( CHE AMA FARSI CHIAMARE ^ SATANAZISTISSIMENTE^ ... LA BESTIA, IN
QUANTO FACEVA PARTE DELLE BESTIE DI SATANA, LE QUALI ERANO NOTORIAMENTE
TUTT'UNO CON LEGA LADRONA
https://danielesensi.blogspot.com/2010/01/la-disperazione-di-una-mamma-mio-figlio.html
ED A CUI INFATTI FAREMO FARE UNA FINE "BESTIALISSIMA"
https://www.tpi.it/2018/10/27/luca-morisi-salvini/ )
EFFETTUA MEGA TRUFFE, ORDINA OMICIDI, FINANZIA PEDOFILIA ON LINE, RICICLA SOLDI
SUPER ASSASSINI A LUGANO!!!
1
Appena abbiamo comprato Finter Bank Zurich dai massoni nazifascisti Pesenti,
immediatamente abbiamo chiuso tutti i conti connessi, al, tanto quanto, massone
nazifascista, nonche' famosissimo ladro, truffatore, azzera risparmi di ognuno
che gli abbocca via iternet e non solo, nonche' criminalissimo pedofilo Paolo
Barrai. Di delinquentissima Medicalchain, di delinquentissima Cryptolab S A, di
delinquentissima Bigbit, di delinquentissima Bgbit News Channel e
delinquentissima @bigbitnewschannel. Attraverso i quali strumenti, lui ed il
fallitissimo, idiota, davvero deficente, incapace, fallimentare trader Federico
Izzi di Roma (che campa, di fatto, riciclando soldi mafiosi e facendo film
pedopornofrafici, tanto e' vero che sta merda criminalissima di Federico Izzi
di Roma, e' noto sulle rivere del Tevere, da chiunque, come "Er Zio Romolo
incula bambini e pure come Er Zio Romolo della Camorra"). Sti due pezzi di
merda criminalissimi spennano " i polli del web¨, vendendo loro abbonamenti
annuali su criptovalute e non solo, totalmente fallimentari ( delinquentissimo
servizio chiamato Bigbit)
Che ti fan perdere tutti, tutti, e di nuovo tutti i risparmi ( posso mostrarvi
centinaia di casi, venuti, disperati, a piangersene da me, a proposito).
Insieme al figlio di puttana Natale Ferrara di Reggio Calabria, uno scarafaggio
della Ndrangheta ( e di fallimentarissima Eidoo).
2
Si, proprio cosi', insieme al figlio di puttana Natale Massimiliano Ferrara di
Reggio Calabria, uno scarafaggio della Ndrangheta ( e di fallimentarissima
Eidoo).
Imboscatosi qui in Svizzera, per non finire in galera, ben appunto, a Reggio
Calabria. Che ha rifilato a la merda di Ico completamente fallimentare chiamata
Eidoo, crollata da 7 dollari a 0.60 dollari.
Ora, l'altrettanto merdone nazipedofilo Donald Trump sta cercando di tirargli
su detta merda, il tutto, ovviamente, mentre lo stesso nazipedofilo merdone
Donald Trump, tira su, come al solito, anche, i suoi tre grammi giornalieri di
cocaina, presso la White "Powder" House) . Torniamo in ogni caso, ora, al punto
iniziale, bitte.
Appena noi di Bank Vontobel Zurich abbiamo comprato Finter B
[qubes-users] Missing sys-USB, Reinstall?
I have recently install V4 on a laptop. I noticed there is no sys-USB. What is the appropriate method to produce one? I currently have no network connection either. The newly installed system had sys-net attached with the two USB controllers and no nic. So I removed the two USB controllers and added the nic. The vm no longer errors out when booted. I am concerned there may be more problems I have not seen yet. This is a new install; is there something I did wrong that would have caused these error? I am going on two weeks trying to fix what I have. Should I just attempt to reinstall? I don't know what I should do differently. Any suggestions? -- 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/a86490d8-db21-4b3c-8ebb-d056c9038986%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Realtek wifi adapter rtl8821ce
Hello, I have realtek wifi adapter in my lenovo laptop ideapad 330 15arr model. It is not recognised by sys-net VM. I have downloaded the driver package from the following link: https://github.com/endlessm/linux/tree/master/drivers/net/wireless/rtl8821ce Since sys-net VM is based on fedora 29 template, I have tried to follow the steps given in the link below to make it work in sys-net VM: https://nova.moe/solve-realtek-rtl8821ce-driver-on-fedora/ However when I try to compile the package, I get the following error: [user@sys-net rtl8821ce]$ ls Kconfig clean hal include platform runwpa Makefile core ifcfg-wlan0 os_dep rtl8821c.mk wlan0dhcp [user@sys-net rtl8821ce]$ vi Makefile [user@sys-net rtl8821ce]$ pwd /home/user/rtl8821ce/rtl8821ce [user@sys-net rtl8821ce]$ make make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.14.74-1.pvops.qubes.x86_64/build M=/home/user/rtl8821ce/rtl8821ce modules make[1]: Entering directory '/usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build' make[2]: *** No rule to make target '/home/user/rtl8821ce/rtl8821ce/core/rtw_cmd.o', needed by '/home/user/rtl8821ce/rtl8821ce/8821ce.o'. Stop. make[1]: *** [Makefile:1527: _module_/home/user/rtl8821ce/rtl8821ce] Error 2 make[1]: Leaving directory '/usr/lib/modules/4.14.74-1.pvops.qubes.x86_64/build' make: *** [Makefile:1902: modules] Error 2 [user@sys-net rtl8821ce]$ pwd I think development workflow is different in Qubes OS. Any pointers, help, ideas? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cf29f7b4-1b3b-4194-b1b6-3bc4529019f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: "Qubes Devices" widget not working anymore
On Friday, April 5, 2019 at 10:34:21 AM UTC-4, Lorenzo Lamas wrote: > On Friday, April 5, 2019 at 3:15:44 PM UTC+2, john@gmail.com wrote: > > On Thursday, April 4, 2019 at 3:53:49 PM UTC-4, Lorenzo Lamas wrote: > > > Try updating to qubes-desktop-linux-manager 4.0.17 in current-testing. > > > > Thanks, Lorenzo. It is fixed now, however, I believe I made the mistake of > > enabling the repo rather than just installing the package from the repo. > > Nothing terrible happened, but now every time a new VM is started there's a > > loud "pop" from my speakers, and it's uneffected by the volume control > > within Qubes. Not terrible, but it means every time I open a disposable VM > > there's a loud pop (I'll turn down my speakers). > > > > If you or anyone has any suggestions regarding that that would be fantastic. > > > > Thanks. > > John > > You could try rolling back the update: > "You could look at 'sudo dnf history' in dom0 to identify the last > update, then roll back to the prior one: > > sudo dnf rollback > > So if the update that caused the problem is transaction 150, specify 149 > on the command line." > > And then install only qubes-desktop-linux-manager from current-testing: "sudo > qubes-dom0-update --enablerepo=qubes-dom0-current-testing > qubes-desktop-linux-manager". You may need to add "--best --allowerasing" to > that. Again, thank you for this. Unfortunately, rolling back presents me with an error message that "A transaction connot be undone" and mentions "No package qubes-manager-0:4.0.28-1.fc25.noarch available." I'm going to just live with it, and learn my lesson. 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/4ddea6cd-e1d2-49e0-ba75-dbf29df93ed3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes Os 4.0 - problem with performance
Hello, I have PC with 8GB RAM, hdd and AMD FX X-6. Qubes Os 3.2 was working fine. Unfortunately Qubes Os 4.0 is very slow. Booting up takes ~15min, then spawning VM takes about 5 minutes or more. What is worse appvms itselfs are slow. I mean they need significant amount of time to respond to my actions. They are so slow that this system is practicly unusable. Text mode stuff and web browser are rather torelabre in terms of performance. Kicad is usuable, especially loading it's libraries takes ages. i have laptop with 8GB ram and SSD and both Qubes 3.2 and 4.0 works fine. I have no idea how i can fix this problem. I can run benchmarks and/or paste logs, just please tell me what will be helpfull to troubleshoot this problem. Should i update my hardware? A have asked a few people on IRC but we did not managed to find source of this problem. I'm trying to analyse diferences between Qubes Os 3.2 and 4.0. Are new features in CPU used in Qubes 4.0 that are not used in Qubes 3.2? Something related to storage? -- 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/20190405151836.GA7687%40hackerspace.pl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Subgraph
On Friday, April 5, 2019 at 2:02:35 PM UTC+2, Steven Walker wrote: > Does anybody know if subgraph is still a work in progress, or has it been > discontinued now? > > Steve Afaik Subgrap OS in its old form is dead, but it is replaced with Subgraph Citadel which is still a (slow) work in progress. -- 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/bf0c5935-a681-4b82-8534-ea0e2434e1a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: "Qubes Devices" widget not working anymore
On Friday, April 5, 2019 at 3:15:44 PM UTC+2, john@gmail.com wrote: > On Thursday, April 4, 2019 at 3:53:49 PM UTC-4, Lorenzo Lamas wrote: > > Try updating to qubes-desktop-linux-manager 4.0.17 in current-testing. > > Thanks, Lorenzo. It is fixed now, however, I believe I made the mistake of > enabling the repo rather than just installing the package from the repo. > Nothing terrible happened, but now every time a new VM is started there's a > loud "pop" from my speakers, and it's uneffected by the volume control within > Qubes. Not terrible, but it means every time I open a disposable VM there's a > loud pop (I'll turn down my speakers). > > If you or anyone has any suggestions regarding that that would be fantastic. > > Thanks. > John You could try rolling back the update: "You could look at 'sudo dnf history' in dom0 to identify the last update, then roll back to the prior one: sudo dnf rollback So if the update that caused the problem is transaction 150, specify 149 on the command line." And then install only qubes-desktop-linux-manager from current-testing: "sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-desktop-linux-manager". You may need to add "--best --allowerasing" to 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 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/c779ccfe-18bb-46e3-8a5d-69934822c1bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: "Qubes Devices" widget not working anymore
On Thursday, April 4, 2019 at 3:53:49 PM UTC-4, Lorenzo Lamas wrote: > Try updating to qubes-desktop-linux-manager 4.0.17 in current-testing. Thanks, Lorenzo. It is fixed now, however, I believe I made the mistake of enabling the repo rather than just installing the package from the repo. Nothing terrible happened, but now every time a new VM is started there's a loud "pop" from my speakers, and it's uneffected by the volume control within Qubes. Not terrible, but it means every time I open a disposable VM there's a loud pop (I'll turn down my speakers). If you or anyone has any suggestions regarding that that would be fantastic. Thanks. John -- 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/664655de-4f4b-45b4-86ac-ef87168f9181%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Subgraph
https://www.youtube.com/watch?v=iixvQWx7IOM On Fri, Apr 05, 2019 at 05:02:34AM -0700, Steven Walker wrote: Does anybody know if subgraph is still a work in progress, or has it been discontinued now? Steve -- 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/8c19aabb-f3bb-460a-8b19-93e9dcfbc7ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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/20190405131332.j464dvv54go6w52d%40web.local. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Subgraph
Does anybody know if subgraph is still a work in progress, or has it been discontinued now? Steve -- 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/8c19aabb-f3bb-460a-8b19-93e9dcfbc7ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Hyperthreading on or off?
On Thursday, April 4, 2019 at 11:05:09 AM UTC, brend...@gmail.com wrote: > On Thursday, April 4, 2019 at 5:10:39 AM UTC-4, donoban wrote: > > On 4/3/19 11:54 PM, jr...@gmail.com wrote: > > > Looking for guidance on best practices for Qubes configuration: > > > given the vulnerabilities that have been reported with > > > Hyperthreading, it would seem to be a no-brainer that it should be > > > disabled, but I don’t see anyone coming right out and saying so. > > > Curious what this group thinks. > > > > If you mean that disabling it could be too drastic solution or the > > risk in real-world conditions is too low, you could be right. > > > > I read a paper about this where the attacker needed a lot of time > > while other VM was running an infinite loop using a SSL key (no real > > world behavior). So probably, in real conditions this is very very > > hard to exploit. > > > > On the other side, Qubes security model and sense of existence is to > > guarantee that some compromised VM can not compromise other VMs or the > > whole system so just disabling could be reasonable too. > > Makes sense to me: Qubes policy is to enforce safer defaults. User can > modify, at their own risk. > > Layperson's thought: perhaps there could be a CPU allocation strategy in Xen > that allocates cores instead of logical CPUs? That may mitigate the security > issue if the workload would benefit from Hyperthreading (aka SMT). > > Whether this is significantly safer than the default logical CPU allocation > w/ hyperthreading really depends upon the CPU cache strategies in effect, > perhaps. E.g. contemporary Intel CPUs (packages?) have three or more levels > of cache and some interesting cache topologies including cross-core caches... > > Some support software-selectable caching strategies as well for parts of the > cache. > > Brendan would that work, without static allocation? I'd assume Xen regulates time slices, so that there's always a chance that the cache will still contain stuff from activity generated in/by another VM. I guess you could flush that every time, but I'm sure that generates more than a little overhead. -- 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/b1efe6ed-bdde-4f1c-94e3-6bf4c4cd9353%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
