Re: [qubes-users] Re: Does Qubes support Intel Turbo Boost?
> Actually it has 4 cores and 8 threads. In xenpm's output, there're 2 lines > saying '[CPUx] failed to get cpufreq parameter', 'x' being 1 and 3. This is a bug in xenpm when 'smt' is off, as discussed in here: https://github.com/QubesOS/qubes-issues/issues/4456 Still need help with turbo boost. In vm, frequency shown in 'powertop' does indicate turbo boost's presence, but I highly doubt its reliability since the number never goes under max base frequency, and doesn't correspond to real cpu usage. -- 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/7947e2f5-f4da-4f08-9acb-75ac075130a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes OS 4.0.1-rc2 has been released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Qubes Community, We're pleased to announce the second release candidate for Qubes 4.0.1! Features: - Fixes for bugs discovered in 4.0.1-rc1 - All 4.0 dom0 updates to date - Fedora 29 TemplateVM - Debian 9 TemplateVM - Whonix 14 Gateway and Workstation TemplateVMs - Linux kernel 4.14 Qubes 4.0.1-rc2 is available on the Downloads page: https://www.qubes-os.org/downloads/ What is a point release? - A point release does not designate a separate, new version of Qubes OS. Rather, it designates its respective major or minor release (in this case, 4.0) inclusive of all updates up to a certain point. Installing Qubes 4.0 and fully updating it results in the same system as installing Qubes 4.0.1. What should I do? - - If you're currently using an up-to-date Qubes 4.0 installation, then your system is already equivalent to a Qubes 4.0.1 installation. No action is needed. Regardless of your current OS, if you wish to install (or reinstall) Qubes 4.0 for any reason, then the 4.0.1 ISO will make this more convenient and secure, since it bundles all Qubes 4.0 updates to date. It will be especially helpful for users whose hardware is too new to be compatible with the original Qubes 4.0 installer. Release planning - Since the most severe bugs related to Fedora 29 have been addressed, we expect that this will be the final release candidate for 4.0.1. As usual, you can help by reporting any bugs you encounter. [1] If no major problems are discovered in this release candidate, 4.0.1 should follow in approximately three weeks. [1] https://www.qubes-os.org/doc/reporting-bugs/ This announcement is also available on the Qubes website: https://www.qubes-os.org/news/2018/12/18/qubes-401-rc2/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlwZ2joACgkQ203TvDlQ MDBFcA/8COFybMGZlmd5hzyyRbx3iD7O4bjOOVsS+B7WpmLf1FMsQoXknxMqZTF+ s1kwdFOmtNrVRBQ7zTJK2cgKq26bOkhm0MvqU/vyyaF2nOu/kvDsWPPxmbMIpW6Q 9144ayqDmpdyjMZYxsFOgiVlE0bVDipUKcZbKV73Ny2EY5TtwgtRZJFgH3NHjwKH ZjJgkDlDN+2IMp3/kjsow2mCzJzZZl9YaqSZ5T1JioXXV1A/p3/N7cefJQB1YDgx ZhCciGrYQ84bq3xC3JqfKTXVw0UKZtSZz56e6kfbjoV947AB6V0RfBbXQxJ1e/o4 KC+mSJfCJ2wXTQLp9g5bZY216PVTSSw60eH/Ncm7iwvK65fMNZ5A0FxkMfIcikac C2tGMuO8DIMHpOD1EYaosPkSr6ZusdwWv4VoIZWrkB/qqKw85czxcCiGryuFe5Zy FlKyML92mTRT0tOy3nMN12m+NyVrfxwic8OojQnksCBucmhNOzn/T89dLZGSZs+F f8NNYTkWmDiwiSpVaJJtrpdbByGeNO4Wy4exLpUnseBD8Y57dwez0mgH1zAuJxZi EUplM/955VYCUMbEQ62pzwJdPLS7o+f6fXBmcf87ORjZ9JSN7PZXDXLGNvLNUcBZ 7e1+5F8rj+TRs1Wh6cD1yXCLSAIy68iud1Xuis3xTq/OoQBU0zQ= =kIol -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 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/6fda2037-b0b5-c6c7-3f13-db0ebdafaf6a%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Does Qubes support Intel Turbo Boost?
On Wednesday, December 19, 2018 at 12:10:19 AM UTC-5, awokd wrote: > I think xenpm is supposed to work the best. Qubes disables SMT for > security, so if you only have 2 real cores that's all you'll see. Actually it has 4 cores and 8 threads. In xenpm's output, there're 2 lines saying '[CPUx] failed to get cpufreq parameter', 'x' being 1 and 3. -- 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/62d87212-8736-41d6-aa14-1ed6d379ba64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Does Qubes support Intel Turbo Boost?
qubesuserma...@gmail.com: The most promising result is given by xenpm, however only info of 2 cores out of 4 are listed. I think xenpm is supposed to work the best. Qubes disables SMT for security, so if you only have 2 real cores that's all you'll see. -- 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/42cf367c-8366-1ae5-699e-2b0cb4218010%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Updating to whonix-14. Error: "ImportError: No module named qubesadmin.exc"
jeppewr...@gmail.com: Hi all, I'm quite new to Qubes and Linux in general yet I have manged to run Qubes OS as my main desktop for several weeks. At the moment I'm fiddling with networking, more specifically I'm trying to get whonix-14 working, as Qubes comes with an outdated version(!?). First I removed all traces of the old outdated Whonix (including qubes-core-admin-addon-whonix.noarch) on my system. Then I ran "sudo qubesctl state.sls qvm.whonix-ws-dvm" according to the documentation: https://www.whonix.org/wiki/Qubes/Install After getting "bash: qubesctl: command not found" i reinstalled "qubes-core-admin-addon-whonix.noarch" with no effect. After that I tried searhing dom0 repo for salt and found "qubes-mgmt-salt.noarch" witch i also installed, it seems to help the first problem, but qubesctl seems broken. When running the command i get this in return: File "/usr/bin/qubescl", line 11, in import qubessalt File "/usr/bin/python2.7/site/packages/qubessalt/__init__.py", line 10, in import qubesadmin.exc ImportError: No module named qubesadmin.exc How do i fix this and get whonix-14 installed properly? Thanks! I'm wondering if removing qubes-core-admin-addon-whonix.noarch broke some other packages accidentally. Might be quickest to backup your AppVMs, reinstall, restore, and try again? You might want to manually install the newer Whonix templates (ws & gw) first, then try that "sudo qubesctl state.sls qvm.whonix-ws-dvm" command 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/a3a9ab08-41e4-7add-7421-a571dc99fa91%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] disk space management
dimi: On Monday, December 17, 2018 at 10:40:45 AM UTC+2, awokd wrote: 1) I usually use qvm-remove to delete VMs, but Qube Manager should do exactly the same thing. Are you making sure they're shutdown before deleting? 2) rm to delete the old menu entries and log files. I guess lvremove to get rid of the old volumes listed with lvs, my assumption being Qubes will realize they are gone and handle the entries in /dev/qubes_dom0 appropriately. Haven't encountered this problem before. 3) Also lvremove. 1) Yes, VM's are shutdown before removing. I am double, tripple checking before any delete action. 2) ok 3) ok Thank you for teaching me awokd, lvremove /dev/qubes_dom0/vm-leftover-private did it. Will reboot once i am done cleaning up, quiet a few leftovers here. And you are saying that your lvs does not show you any traces of left over VM's? How could i prevent that from future happing? Dreadfully go through a Qubes reinstall, i had some problems with Anaconda and restore backuped VMs? Correct, no leftovers in my lvs and I've had 4.0 installed since it released and multiple VMs created and deleted, so I'm not really sure how you might have ended up with those! -- 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/d7637b10-1d97-bd0c-7132-080d111fb986%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Does Qubes support Intel Turbo Boost?
The most promising result is given by xenpm, however only info of 2 cores out of 4 are listed. -- 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/d1f74554-6c6a-4c92-bd91-e73dea190896%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Does Qubes support Intel Turbo Boost?
Also, what would be the best way to check current CPU frequency on Qubes? I've tried multiple ways to get cpu frequency and turbo state, but they either give contradictory/fixed results or don't work. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0393633a-1fd7-476c-8e43-9406e4915ac9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Where is Qubes' idea of private image size coming from?
On Tue, Dec 18, 2018 at 09:18:06PM +0100, Achim Patzner wrote: > Hi! > > I just ran out of space in my Bulder VM again and wanted to extend it a > bit, but somehow PRIV-CURR and PRIV-MAX do not like each other that > much: > > [ap@dom0 bin]$ qvm-ls --disk BuilderNAME STATE DISKPRIV- > CURR PRIV-MAX PRIV-USED ROOT-CURR ROOT-MAX ROOT- > USEDBuilder Halted 124948 124948 2048 6100% 0 > 10240 0%[ap@dom0 bin]$ > > Before I start doing something stupid (like reporting a non-issue or > shooting my own foot): Where is that 2GB PRIV-USED coming from and how > do I correct it? The image file itself has a size of 128GB right now... > > > Achim 6100% used. Impressive. I'm not clear if you tried to extend first or checked the sizes first. You can see the code in /usr/lib/python3.5/site-packages/qubesadmin/tools PRIV-MAX comes from vm.volumes[private].size - it's strange that that should be showing the default 2G size. Just to be safe I would backup anything you have on the BuilderVM. What does qvm-volume info Builder:private show? You could try then resizing with extend. -- 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/20181218235307.55thugbyay2ttyk3%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Going old school
Just ordered a (native - no USB conversion) Logitech PS/2 keyboard and mouse and a PS/2 splitter since I only have one PS/2 port. -- 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/76acc2ca-7c60-4f88-a431-3832b8d51215%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Where is Qubes' idea of private image size coming from?
Hi! I just ran out of space in my Bulder VM again and wanted to extend it a bit, but somehow PRIV-CURR and PRIV-MAX do not like each other that much: [ap@dom0 bin]$ qvm-ls --disk BuilderNAME STATE DISKPRIV- CURR PRIV-MAX PRIV-USED ROOT-CURR ROOT-MAX ROOT- USEDBuilder Halted 124948 124948 2048 6100% 0 10240 0%[ap@dom0 bin]$ Before I start doing something stupid (like reporting a non-issue or shooting my own foot): Where is that 2GB PRIV-USED coming from and how do I correct it? The image file itself has a size of 128GB right now... Achim -- 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/1ac155022bbe53a17b5a28f8977d6c84e0468250.camel%40noses.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Dom (0) error under install. ver 4.0
tirsdag den 18. december 2018 kl. 19.52.57 UTC+1 skrev Jorgen: > Hi > > I am trying to install ver 4.0 on my HP Elitebook 2560P. It has a Intel core > i5 processor (2450m VT-X with EPT, more details here: https://goo.gl/iJTcdM), > so I guess it should be compatible?! > > But I get the attached error at the end of the install, and after that no > VM's are available :-( > > I really miss Qubes-OS so any help would be appreciated. > > Best regards > Jorgen OH wait, it might be this issue: https://goo.gl/1gghEh I will get back to you after trying to switch locale -- 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/7bdd885c-abbd-4ebd-bfc7-510299799507%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: dom0 error
On 12/18/18 7:28 PM, cooloutac wrote: On Sunday, December 16, 2018 at 8:13:52 AM UTC-5, Roy Bernat wrote: while trying to update dom0 getting error sys-firewall command failed with code 1 Roy I'm getting the same thing. Updates go through but just wondering why the error and if it should be a concern. https://github.com/QubesOS/qubes-issues/issues/4616 -- 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/7130ca43-bc26-e74e-f988-e3f3b2f9259d%40hackingthe.net. For more options, visit https://groups.google.com/d/optout. smime.p7s Description: S/MIME Cryptographic Signature
[qubes-users] Re: dom0 error
On Sunday, December 16, 2018 at 8:13:52 AM UTC-5, Roy Bernat wrote: > while trying to update dom0 > > getting error sys-firewall command failed with code 1 > > Roy I'm getting the same thing. Updates go through but just wondering why the error and if it should be a concern. -- 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/e9cfdfe5-509e-4db5-a8b1-94108fd97673%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] thunderbird, open link in AppVM
Since upgrade to new Template fedora 29 in R4, clicking links does not open up the menu. Email Attachments do start in dispVM. Not sure if this link select AppVM feature was build into r4 or if i used some github repo. -- 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/4abf5d63-dfeb-49d2-ba8f-7e9e7ead6963%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] default-mgmt-dvm template switch
Just wanted to make sure that the new default-mgmt-dvm can be switched to use fedora-29 template in Qubes Manager? -- 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/c73d899d-e2ce-4361-9d6b-ede8c536c86a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520
El martes, 18 de diciembre de 2018, 6:05:18 (UTC+1), Yassine escribió: > > Regarding issues with when unplugging thunderbolt after boot, this is due to > PCI hotplugging being disabled (for obvious security reasons) - more details > here https://github.com/QubesOS/qubes-issues/issues/1673 > > @Jim: following awokd's procedure you should be able to get UEFI working, > also the configuration that I described for installation and > post-installation were tested with UEFI only > > Now if you reboot and the PCI devices served by the thunderbolt/usb-c are not > present anymore, you'll have to manually remove them from the list of pci > devices that are passed through to your NetVM or UsbVM. > Same for when you boot with the thunderbolt attached, you'll have to reattach > the pci devices to the VM for passthrough. Thank you Yassine! now I fully understand why this happens. I don't really care if I have to reboot to make it work, but the problem is even after reboot, it is not detected, so I have to turn off sys-firewall + sys-net, unplug the adapter and plug it again and finally start the VMs again for it to work, what is a bit of a PITA. I'd be happy if it was recognized directly when booting, even if a later disconnects make it stop working... Have any of you been able to achieve something like this at least? 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 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/bf3aaa23-f4d0-4a43-9116-b300c03cd67d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
