Re: [qubes-devel] Permission denied when using Qubes().domains
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Mar 07, 2018 at 02:07:25AM +0100, Marek Marczykowski-Górecki wrote: > There is https://dev.qubes-os.org/projects/core-admin/en/latest/ > for qubesd side, and > https://dev.qubes-os.org/projects/core-admin-client/en/latest/ for > client side. The latter one have actual content accessible through > module index. > Generic concepts are explained in the former, client side mostly expose > subset of functions from qubesd (internally through Admin API). > > Wojtek, could you add links to both of those sites from > http://dev.qubes-os.org/? > Both are already linked from https://www.qubes-os.org/doc/ Done. Sorry for the delay. - -- pozdrawiam / best regards _.-._ Wojtek Porczyk .-^' '^-. Invisible Things Lab |'-.-^-.-'| | | | | I do not fear computers,| '-.-' | I fear lack of them.'-._ : ,-' -- Isaac Asimov `^-^-_> -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJavOePAAoJEL9r2TIQOiNRhQ8QAJWWs6XrE5vWoHlXFiHrFuTA CuhXiZbUyZqFHdRAlkrxS1UW0NSAK3rlYlyrK7Uqgu4o5CX+otpIxSyNdNZqGCJI Dv8LZnNAoQQstCoxV8r/dlurEukiZ/XwkGi3iTlHKmmCeoBqBwaitTaXm+LEfnzA C9k/nbYqNSD2lyHOzrC9zZjRFp5xp6n61DDbLbewcS3mgPa9EM6ySpBx8EXmtm2Z jSZu1grIGtTuhInqlOElp+vhKO9CjjeSQ0K/Cn7/tu0vCKxMAQ6msr5eF/Hkd34e 8onGLi0ErEn1JHbsvYloDFJdRMKAQQjB8/yemiLRueehUmoY7xYTft8E6NbmpBb5 KrC1UGb2ED1V/05dIv5FPoSg2IAPkgzm7+VHf3jcnS/PfKsWmLcXXtNUpA+j06nE DhNhGFGC0geEmqCgLdDMT2+f48WBLdHvhVla6j3P33abw3+56iSgx2HXnk/GSPK3 xF0ZfSLu0B6bsIot59ArSDmlzEg+BeAG4cnZlRQV5aiRikrAUG29Vht1Iq8Uu9L5 DDJH2CCJkA1QEckEmcWUf4ZWDqjFd2sZwm1XQclHGvAEA72ux/JHxY5lrjOHjHQO KQzpsos/bAWRwOFv/RJRMp5PX8An/RYRi/CDSoFuPEXqCWad0Y7q54+4/vR7IQiq mBchsEOrlesxPhHWG7rx =Npi6 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20180329131806.GA4236%40invisiblethingslab.com. For more options, visit https://groups.google.com/d/optout.
[qubes-devel] kernel downgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, As I have hit by this bug booth in 4.0 and 3.2 versions: https://github.com/QubesOS/qubes-issues/issues/3657 I have to downgrade the kernel, then prevent updating from this version. If I try it under 4.0 I got this error: (https://pastebin.com/vy4X4w8U) [user@dom0 ~]$ sudo qubes-dom0-update kernel-latest-4.14.12 kernel-latest-qubes-vm-4.14.12 Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Fedora 25 - x86_64 - Updates2.3 MB/s | 24 MB 00:10 Fedora 25 - x86_64 2.6 MB/s | 50 MB 00:19 Qubes Dom0 Repository (updates) 1.0 MB/s | 3.0 MB 00:02 Qubes Templates repository 12 kB/s | 8.3 kB 00:00 Last metadata expiration check: -1 day, 22:01:22 ago on Thu Mar 29 18:22:53 2018. Dependencies resolved. Package Arch VersionRepository Size Installing: kernel-latest x86_64 1000:4.14.12-1.pvops.qubes qubes-dom0-current 46 M kernel-latest-qubes-vm x86_64 1000:4.14.12-1.pvops.qubes qubes-dom0-current 63 M Transaction Summary Install 2 Packages Total download size: 108 M Installed size: 108 M DNF will only download packages for the transaction. Downloading Packages: (1/2): kernel-latest-4.14.12-1.pvops.qubes.x86_ 1.2 MB/s | 46 MB 00:38 (2/2): kernel-latest-qubes-vm-4.14.12-1.pvops.q 1.3 MB/s | 63 MB 00:47 - - Total 2.3 MB/s | 108 MB 00:47 Complete! The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Qubes OS Repository for Dom0 84 MB/s | 209 kB 00:00 No package kernel-latest-4.14.12 available. No package kernel-latest-qubes-vm-4.14.12 available. that means the updateVM can successfully download that specific version, but in dom0 the update script failing... Any suggestion how to solve this? And if I succed, how can I lock my system to this kernel version? Thanks. - -- Zrubi -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEw39Thm3rBIO+xeXXGjNaC1SPN2QFAlq8/PcACgkQGjNaC1SP N2SHyhAAu5SQw3D/uYFDFzGEr3LcbG+16guDpqJoW3zBOeH1QhC56b/xEZDecZw6 qy5+DWpmAQnb3LAUxEAx3eAeJWzmJ7f/GPqs5Z1/u6wiDX/kyG5p8BMK1w0OgGHO L4zGjEQ7sO9Ob0HpRSMPhYMPdzq0MJDQ1LcDCA4iK4obinwhTmacS1BifQmtWBQ9 ivv8LFzTKfd/ci5fGd9q9/LM8nouAQNUwnyTRAA/ND1JFnlQTgjaEYbN9kA0jmO6 wVkY+ik4L64UNMghLdbpf0w9ix5wpSPQgNMbE8KRGKul405YQZvcn4iYsTd9YtoP X4ju/QziflV+51mI6fXpNNKQ2jgCImG7IkzDcegBjwHZdEA/XoELDYSGn3UcdYbx DV7tm5F1P0Rl1rvHvqy3FUPf9uoBXk4Ar4320groVGSFn1iZZILkhIRLdpWzX0EE P7kWVW/CzWnfSsXlcLqIoSWsmU79enK90spLnt1HJHVCpDf0hoQwCGGRj9dl7x8k Y05vLf412SNfLMTK2+xzlrJBKxPsFlJvgQsDH3qmQRRidz9Rt4F3jGhEZN/P32bt INXY6gofO6viMTNZ4lQzsAz0jBmc0zOYDgM0IbTtwuymMdZuPcJ9wQmIJosv1qDo zl9HRAqYn4EHpS7bbSMKPTW5ehMQ7o8MNBQpOGMol0OJnlt1qsc= =NUD3 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/6aad5023-ab2b-55ca-7a02-ec34e32691ed%40zrubi.hu. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] kernel downgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/29/2018 04:49 PM, Zrubi wrote: > Any suggestion how to solve this? Try this: sudo qubes-dom0-update --action=downgrade [kernel packages] > And if I succed, how can I lock my system to this kernel version? Add the following line into /etc/yum.conf or /etc/dnf/dnf.conf _outside_ of the section marked with "QUBES BEGIN" and "QUBES END": exclude=kernel* Cheers, Patrik -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECa/mcuUTuKPtNWQ7XB5x3wMfmuUFAlq9AMMACgkQXB5x3wMf muUY0g//c4Rqgkoy43dT4QH9sDLapLakFz+BADLlLR+IJXgTKUSFQV8NDVv85HOE O6LSaocP/kCoEOeA6AuM3YqWoeYesAWxig1bGlaX4ERgSjq7ORgLUhBFiWwmhBMZ Om5gSPecCTg6IEjjuP6DNxAn4XmNd6svGWBi53h0Ckiq/VB4txiivjo0yiqsxEsv 3EvFOUXAdXv4/ZWCbqxwxF5K/3D3ClStzszNRhsLAnF3svnP10hn2e7bC9336lyN OeK1ortmOH8DR2u5r4y/OlDG1geF5iwsbeqhIfQH68iyosE4ZtU94LLObnHMv23M 82S9gNi6BK0dUWhjy4BRoWdKwV5xqyELtytNpOZ7GC806U9yHSUaX/O+CPgj8fbB l3N5JI2SVmpGLdaBV3D0E1fguaZaZ3Y5Ou9A+x4iJqkTD8za2BmP370qE1p4RZBt yuC2LpUTaLslT6y/HJZCRlGBqfbRrZitxXopf+A3Bt25PYhq/IwRQlv/zbdeI+Cs eLiYiU1ZHbxZziFEqFztppsTL9v90B1S785LlPX1LXfj1dVvveDw9O37FwHc1s96 ScAQq0x9JP1hcfhqCV8WokWmMjhhlnTw91LmmlqKX/7NyPvqnEbywxOCvwkm6WXV U3gJBnJOs40OQIjd4MFC4Kvai63M0nuzMFiajW2SrvIvfiIBvi8= =tj6D -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/6a817da9-49d0-d475-52fa-73e9b20212a3%40gmail.com. For more options, visit https://groups.google.com/d/optout. 0x031F9AE5.asc Description: application/pgp-keys 0x031F9AE5.asc.sig Description: PGP signature
Re: [qubes-devel] What are we gonna do about Intel's move to kill off LegacyBios before 2020?
I believe soon we will be seeing an "Intel will be forcing Secure Boot by 2025" news article with all the usual talking head idiots saying that such a thing is fine because red hat provides a signed kernel and grub so you can "still run linux" (their linux, not yours) I believe by 2030 only "business" expensive laptops will allow you to run linuxgotta love the change over to non-owner controlled right? ARM laptops are also good if they use an owner controlled high performance CPU design from a reputable company, there are some decent ones from AppliedMicro that are as fast as a 4 core sandy bridge CPU when you combine all 16 cores. I believe one of the ways forward is making a 1U open laptop design that can accept any standard ATX motherboard, this would mean being able to use many of the superior non-x86 owner controlled desktop embedded boards like the performance ARM boards from gigabyte (ex: the MP30) which support uboot so as to not get locked in to intel's terrible uefi ecosystem. If the TALOS 2 is successful there are plans for a TALOS bricktop apparentlyheres to hoping many people buy the T2! (and get to enjoy the speed and freedom) -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/d18406e6-af29-ac88-a11c-287f67b2ba5f%40gmx.com. For more options, visit https://groups.google.com/d/optout. 0xDF372A17.asc Description: application/pgp-keys
Re: [qubes-devel] Re: dom0 update for ppc64le support
On Sun, March 25, 2018 4:14 pm, Thierry Laurion wrote: > Le dimanche 25 mars 2018 12:09:24 UTC-4, Thierry Laurion a écrit : >> >> I'm not sure I follow. >> Xen doesn't support Power architecture. Does it? >> https://unix.stackexchange.com/questions/91368/xen-hw-virtualization-on- >> power-architecture > > No it doesn't. Is there a status update on the development of the > abstraction layer? I'm curious about this as well. If one's end goal was Qubes running on non-x86 arch., what would be the best approach to pursue? A. Port Xen to Power, then Qubes (classic workstation with a handful of high GHz threads) B. Locate blob free ARM hardware, then port Qubes to ARM (Xen on ARM already exists; Qubes Air on multiple ARMs?) C. Add missing functionality/security to KVM, then port Qubes to a supported platform on it (this sounds as hard as option A to me, but don't have a good idea of the complexities) D. Despair and stay on x86 Of course, Qubes on all the architectures/hypervisors would be ideal but given limited resources, which makes the most sense over the next couple years? P.S. Thanks, Qubes team, for 4.0 final! -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/ca42f0f030652204a2e252ab279beff3.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Re: dom0 update for ppc64le support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Mar 29, 2018 at 11:20:41PM -, 'awokd' via qubes-devel wrote: > On Sun, March 25, 2018 4:14 pm, Thierry Laurion wrote: > > Le dimanche 25 mars 2018 12:09:24 UTC-4, Thierry Laurion a écrit : > > >> > >> I'm not sure I follow. > >> Xen doesn't support Power architecture. Does it? > >> https://unix.stackexchange.com/questions/91368/xen-hw-virtualization-on- > >> power-architecture > > > > No it doesn't. Is there a status update on the development of the > > abstraction layer? > > I'm curious about this as well. If one's end goal was Qubes running on > non-x86 arch., what would be the best approach to pursue? > > A. Port Xen to Power, then Qubes (classic workstation with a handful of > high GHz threads) > B. Locate blob free ARM hardware, then port Qubes to ARM (Xen on ARM > already exists; Qubes Air on multiple ARMs?) > C. Add missing functionality/security to KVM, then port Qubes to a > supported platform on it (this sounds as hard as option A to me, but don't > have a good idea of the complexities) > D. Despair and stay on x86 > > Of course, Qubes on all the architectures/hypervisors would be ideal but > given limited resources, which makes the most sense over the next couple > years? IMO realistically options C or B are the best. Which one will happen depends on multiple factors, including having a company willing to pay for it... > P.S. Thanks, Qubes team, for 4.0 final! :) - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqzbrQACgkQ24/THMrX 1yw3Agf/eoFIPe5r71NGTTySzasOdJomuyV9tChlTYUGUsKEwyW9TsU+zvIIkX8a 8YSXa8orjidGBbGKyggyYxzStIUPURRTgQbmeEyGH2QFW/2HbZ4iwTj7aTyE1VaS kXCXELTmdmAiOU8jP6BNRvSqGriqt8QC8FzG3f5RKNLHVWS0iwTucV8UCUKf+AJ9 M4IY4h0GLABEJUSst7NA/y2VfpYYm3stAtNojkMV6feuVpgJIj5LC/hccdEiF/zg uh21DsBmcA8b+2sfNHY19nYl7UbJqo90roaVbOKUUg292TZct9h1rlraHFukTeiW hbl0eo8SSuUXtKsNMNgCXEJJK7kVHg== =v2of -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20180329232622.GJ8343%40mail-itl. For more options, visit https://groups.google.com/d/optout.
