Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On Friday, 2 March 2018 21:26:33 UTC, Alex Dubois wrote: > On Friday, 2 March 2018 19:54:43 UTC, Alex Dubois wrote: > > On Saturday, 10 February 2018 01:20:22 UTC, Marek Marczykowski-Górecki > > wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > On Fri, Feb 09, 2018 at 11:11:50AM -0800, b...@gmail.com wrote: > > > > On Wednesday, February 7, 2018 at 8:13:42 PM UTC-5, Marek > > > > Marczykowski-Górecki wrote: > > > > > For anyone interested, here is instruction how to setup build > > > > > environment: > > > > > https://github.com/QubesOS/qubes-builder-windows/ > > > > > > > > > > I know Rafał "Omeg" used Visual Studio for development, but I have no > > > > > idea if anything special was needed there. I see vs2012, vs2013, > > > > > vs2015 > > > > > etc directories in relevant repositories. > > > > > > > > Hi Marek, > > > > > > > > If you have time... > > > > > > > > Just FYI, the instructions you linked to above no longer work. I say > > > > this based on more than several hours of trying to figure out how to > > > > build the tools. I get all the way, without errors or warnings, to the > > > > last step, which is `make qubes`. That step throws an error about rpm > > > > not being installed: "No rule to make target > > > > 'please.install.rpm.and.try.again', needed by 'check.rpm'. Stop." > > > > > > Hmm, exactly this issue should be fixed by: > > > https://github.com/QubesOS/qubes-builder-windows/commit/5a637757d69dc952b0d19ef0cb86574ba54e0717 > > > > > > Check if you have qubes-builder/qubes-src/builder-windows/builder.conf, > > > with that content. Or, maybe something have changed in cygwin in the > > > meantime? What is the output of "uname -o" command? > > > > > > - -- > > > 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/THMrX1ywFAlp+uU4ACgkQ24/THMrX > > > 1yw4ogf+MdN914rsdJV65ROfwFzHFhYRdEdG2KSH+GrrdTmdORI26IG1E4Z4qSwK > > > aB9sTDnwb2+qkjv9yVDYM3qpL7GGyfp2TgbFwFwEFrs3L07ryc7eWW1mhNcq+Wgn > > > aCPAVOQDN8gNm/GjC3hr22aJPfe/S+XKw3I5f3xegfN49M08jKpiI2U+6jkK0BTW > > > okMh+wFFWfIgiOadoFPHwdD4fEq7pMDBcGwuZadIx9LXNRU6F52HH0sBN8eV1cZg > > > 2a2h8vLClriEvqb3lM3Nr8AQ8+F+R2+SQc1pcF4RC0y/6qXQB8byVx9Oig/Rs6tE > > > v8cOGsTOSMlo2PnuUBFeeEr124jEnw== > > > =aHm1 > > > -END PGP SIGNATURE- > > > > I am trying to bring the build env up to date. > > MinGW was probably selected initially with the view to: > > 1- cross-compile some components which comes from linux > > 2- ensure no GPL lock-in (as initially these components were closed source) > > > > Would you now if this still apply or if the Unix stack is only used for > > file management (i.e. not compiling with gcc)? Cygwin would allow easier > > installation of python, bash, make, git in a single env. > > At the moment I am using: > > - MinGW/MSYS (legacy) > > - Windows Git version (launched from the most recent MinGW (using mingw-get) > > - Windows Embeded Python (in preparation, have not tested it) > > > > I am hoping to make the windows build compatible with vs2017 and WDK10. > > But for now, I have only automated > > - qubes-builder set-up from get-be.ps1 file > > > > sourceforge being DDOSed these last few days does not help... > > Sorry, I found some use of gcc. So MinGW is required. To be more precise, I found some copy of mingw/bin/gcc to /mingw/bin/cc, no actual use so far. But I am going to stick to the current set-up of mingw. There are places where patches are applied to various build binaries. -- 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/0905bf8d-4f0a-41a8-88c5-0fc80d086006%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On Friday, 2 March 2018 19:54:43 UTC, Alex Dubois wrote: > On Saturday, 10 February 2018 01:20:22 UTC, Marek Marczykowski-Górecki wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > On Fri, Feb 09, 2018 at 11:11:50AM -0800, b...@gmail.com wrote: > > > On Wednesday, February 7, 2018 at 8:13:42 PM UTC-5, Marek > > > Marczykowski-Górecki wrote: > > > > For anyone interested, here is instruction how to setup build > > > > environment: > > > > https://github.com/QubesOS/qubes-builder-windows/ > > > > > > > > I know Rafał "Omeg" used Visual Studio for development, but I have no > > > > idea if anything special was needed there. I see vs2012, vs2013, vs2015 > > > > etc directories in relevant repositories. > > > > > > Hi Marek, > > > > > > If you have time... > > > > > > Just FYI, the instructions you linked to above no longer work. I say this > > > based on more than several hours of trying to figure out how to build the > > > tools. I get all the way, without errors or warnings, to the last step, > > > which is `make qubes`. That step throws an error about rpm not being > > > installed: "No rule to make target 'please.install.rpm.and.try.again', > > > needed by 'check.rpm'. Stop." > > > > Hmm, exactly this issue should be fixed by: > > https://github.com/QubesOS/qubes-builder-windows/commit/5a637757d69dc952b0d19ef0cb86574ba54e0717 > > > > Check if you have qubes-builder/qubes-src/builder-windows/builder.conf, > > with that content. Or, maybe something have changed in cygwin in the > > meantime? What is the output of "uname -o" command? > > > > - -- > > 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/THMrX1ywFAlp+uU4ACgkQ24/THMrX > > 1yw4ogf+MdN914rsdJV65ROfwFzHFhYRdEdG2KSH+GrrdTmdORI26IG1E4Z4qSwK > > aB9sTDnwb2+qkjv9yVDYM3qpL7GGyfp2TgbFwFwEFrs3L07ryc7eWW1mhNcq+Wgn > > aCPAVOQDN8gNm/GjC3hr22aJPfe/S+XKw3I5f3xegfN49M08jKpiI2U+6jkK0BTW > > okMh+wFFWfIgiOadoFPHwdD4fEq7pMDBcGwuZadIx9LXNRU6F52HH0sBN8eV1cZg > > 2a2h8vLClriEvqb3lM3Nr8AQ8+F+R2+SQc1pcF4RC0y/6qXQB8byVx9Oig/Rs6tE > > v8cOGsTOSMlo2PnuUBFeeEr124jEnw== > > =aHm1 > > -END PGP SIGNATURE- > > I am trying to bring the build env up to date. > MinGW was probably selected initially with the view to: > 1- cross-compile some components which comes from linux > 2- ensure no GPL lock-in (as initially these components were closed source) > > Would you now if this still apply or if the Unix stack is only used for file > management (i.e. not compiling with gcc)? Cygwin would allow easier > installation of python, bash, make, git in a single env. > At the moment I am using: > - MinGW/MSYS (legacy) > - Windows Git version (launched from the most recent MinGW (using mingw-get) > - Windows Embeded Python (in preparation, have not tested it) > > I am hoping to make the windows build compatible with vs2017 and WDK10. > But for now, I have only automated > - qubes-builder set-up from get-be.ps1 file > > sourceforge being DDOSed these last few days does not help... Sorry, I found some use of gcc. So MinGW is required. -- 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/c02a9d12-f56a-4c80-ab4b-280ec2f86a53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Mar 02, 2018 at 11:54:43AM -0800, Alex Dubois wrote: > I am trying to bring the build env up to date. > MinGW was probably selected initially with the view to: > 1- cross-compile some components which comes from linux > 2- ensure no GPL lock-in (as initially these components were closed source) > > Would you now if this still apply or if the Unix stack is only used for file > management (i.e. not compiling with gcc)? Cygwin would allow easier > installation of python, bash, make, git in a single env. AFAIK mingw is _not_ used for building any windows component in the current version. See WIN_COMPILER option in Makefile.builder of each component, and its description in builder-windows/Makefile.windows. There was such attempt in the past, but we've abandoned it quite early. What is used is msys, as a convenient bundled shell+git set. - -- 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/THMrX1ywFAlqZsh8ACgkQ24/THMrX 1yw2+ggAjMGW+uZKMG3UHnlfuqoaD2FgHPr86fj/9R1nTF3TfpvDBQaVTgozQfAT L229h7YDHTtBzYAUbV9sWA/kEHc3002cYnMWfvtSRbFxCalU4NydaRhODw74RVGa OMHVaTfTzZsCkmKmvT/ckiRBhw527xBmuA5a78UBpx4/xvFnoDPGOR+tSafRDftE Zi337b8SDQuYSl3RmeeY5JEKk4b/2uYjQ2j32/oiHC8oDAYYu/GdVF/aJTChqGAg X5we83DpOqILt79GUw7lKHf/RI9Z7O3r5fHeUlqrvKr71oGfS5EADSkNE3WpnXaM 7FWye1XuSaV6Xf4D2sZ1tzI/y6qZlg== =8kvB -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/20180302202022.GM7364%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On Saturday, 10 February 2018 01:20:22 UTC, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Fri, Feb 09, 2018 at 11:11:50AM -0800, b...@gmail.com wrote: > > On Wednesday, February 7, 2018 at 8:13:42 PM UTC-5, Marek > > Marczykowski-Górecki wrote: > > > For anyone interested, here is instruction how to setup build > > > environment: > > > https://github.com/QubesOS/qubes-builder-windows/ > > > > > > I know Rafał "Omeg" used Visual Studio for development, but I have no > > > idea if anything special was needed there. I see vs2012, vs2013, vs2015 > > > etc directories in relevant repositories. > > > > Hi Marek, > > > > If you have time... > > > > Just FYI, the instructions you linked to above no longer work. I say this > > based on more than several hours of trying to figure out how to build the > > tools. I get all the way, without errors or warnings, to the last step, > > which is `make qubes`. That step throws an error about rpm not being > > installed: "No rule to make target 'please.install.rpm.and.try.again', > > needed by 'check.rpm'. Stop." > > Hmm, exactly this issue should be fixed by: > https://github.com/QubesOS/qubes-builder-windows/commit/5a637757d69dc952b0d19ef0cb86574ba54e0717 > > Check if you have qubes-builder/qubes-src/builder-windows/builder.conf, > with that content. Or, maybe something have changed in cygwin in the > meantime? What is the output of "uname -o" command? > > - -- > 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/THMrX1ywFAlp+uU4ACgkQ24/THMrX > 1yw4ogf+MdN914rsdJV65ROfwFzHFhYRdEdG2KSH+GrrdTmdORI26IG1E4Z4qSwK > aB9sTDnwb2+qkjv9yVDYM3qpL7GGyfp2TgbFwFwEFrs3L07ryc7eWW1mhNcq+Wgn > aCPAVOQDN8gNm/GjC3hr22aJPfe/S+XKw3I5f3xegfN49M08jKpiI2U+6jkK0BTW > okMh+wFFWfIgiOadoFPHwdD4fEq7pMDBcGwuZadIx9LXNRU6F52HH0sBN8eV1cZg > 2a2h8vLClriEvqb3lM3Nr8AQ8+F+R2+SQc1pcF4RC0y/6qXQB8byVx9Oig/Rs6tE > v8cOGsTOSMlo2PnuUBFeeEr124jEnw== > =aHm1 > -END PGP SIGNATURE- I am trying to bring the build env up to date. MinGW was probably selected initially with the view to: 1- cross-compile some components which comes from linux 2- ensure no GPL lock-in (as initially these components were closed source) Would you now if this still apply or if the Unix stack is only used for file management (i.e. not compiling with gcc)? Cygwin would allow easier installation of python, bash, make, git in a single env. At the moment I am using: - MinGW/MSYS (legacy) - Windows Git version (launched from the most recent MinGW (using mingw-get) - Windows Embeded Python (in preparation, have not tested it) I am hoping to make the windows build compatible with vs2017 and WDK10. But for now, I have only automated - qubes-builder set-up from get-be.ps1 file sourceforge being DDOSed these last few days does not help... -- 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/d9f80775-76a4-465d-bb72-d795f228b720%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Kernel regression affecting VM network interface attach/detach operations
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
M. Vefa Bicakci:
> Hello all,
>
> I noticed that the following commit causes a regression in QubesOS when
> a VM's network interface is detached and re-attached a few times in a row:
>
> 5b5971df3bc2775107ddad164018a8a8db633b81
> ("xen-netfront: remove warning when unloading module")
>
> The regression exhibits itself via VM unresponsiveness to qrexec commands
> and heavier than usual CPU utilization involving the xenbus and xenwatch
> kernel threads in the VM whose network interface had been
> detached/re-attached.
>
> This commit has been back-ported to the kernel trees for versions 4.9.80 and
> 4.14.17, which is why QubesOS's testing kernel (based on 4.14.18) is also
> affected.
Thanks, for tracking this down! And sorry that I missed your report
until now (Otherwise I would already have included it in the latest
kernel PR).
> I am currently using QubesOS R3.2, but I believe this issue affects R4.0 as
> well.
I'm observing this behavior on R4.0.
Will try if reverting fixes the problem for me.
> Reverting this commit appears to resolve the regression for the time being. I
> haven't had the time to formulate a proper correction.
Did you find out yet why this change is broken?
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE3E8ezGzG3N1CTQ//kO9xfO/xly8FAlqZnTsACgkQkO9xfO/x
ly+XJBAAq3D4TT3+k6v7U5zWe6VqyxuSZOYHMrdUmNUTRp9Q+6+48jK7/gn1QkLX
VY8i/eIqgqn+OAIWi2oFmT9gtWtP+++cml90OY+BLeQg6C0ZnszHgHzISDFYWeAQ
7aHDBBmP+b3B4Jf2aWFHLeZjbyURJIF9z00xGfb7NAcHjFHlSJXAt19GMevjcy0H
G/rxpsW2ebgrnN3YVIJhqgCJrnpr3uoSWL3PozumnnFaxUDuxv/3MaVy5bJJTdz8
3ndcAN7rn35j8hB+Ionc47IBbzfRsfLSBYPUA01iaQIEnkK+55tEQlLDW8LCyrnc
dlMliCoWAqjkr1gruNI+oMnDq/Zm1d7qBzI7+ZvDPui3GFV4C+/A3Bca4bak5tVb
u/P6pfCMpE/StFN9/CttImfjqEG72rIOq4lHKYOZ7pdC4N3nUYVlLOYDvmVOoEwy
SuLhVoMAn+QWk48FSSioA72N7hh/Y70GjDb+I1JhfHnkas9AJ62b0dw46TNgo2jR
FOyCokgRTaxidGuIoKMTo6v0MljVnlC907H2Dn/et0lpuiUch71jv/S7SjCnzEGr
tExeMOjFGo5vgE6nyaoQQuT/PZXJMUHHOLtYwljM/MslqaW1R04WbDxKX389x8uF
5QAm4t334lk6JgIQTEz+Zk92Wvchd78WqWGwUE6RcWIOxb+rtVo=
=az44
-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/efaec423-a5da-68f7-7a16-8aed217193be%40invisiblethingslab.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-devel] Re: Kernel regression affecting VM network interface attach/detach operations
On Sunday, February 11, 2018 at 5:07:15 PM UTC-5, m.v.b wrote:
> Hello all,
>
> I noticed that the following commit causes a regression in QubesOS when
> a VM's network interface is detached and re-attached a few times in a row:
>
>5b5971df3bc2775107ddad164018a8a8db633b81
>("xen-netfront: remove warning when unloading module")
Hi m.v.b:
Have you submitted this to the qubes-issues git project?
https://github.com/QubesOS/qubes-issues
I quickly searched for xenbus (from your POC) and network, but I didn't find
anything in the right timeframe. Probably worth submitting.
Brendan
--
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/e4b47f16-3758-4846-b766-7b575dbd2994%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
