Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
All, Really interested to get this working for Windows 8/10. If anyone needs testers for Windows 10 I'm available! -Chris -- 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/6ef306ce-23df-4d5d-ba2c-4fbb7e697e55%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 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] Are there currently anyone assigned to update Qubes-Windows-Tools?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Feb 09, 2018 at 11:11:50AM -0800, brendan.h...@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- -- 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/20180210012014.GU2070%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 Friday, 9 February 2018 19:20:40 UTC, awokd wrote: > On Fri, February 9, 2018 6:52 pm, Ivan Mitev wrote: > > @ bowabos & awokd > > > > > > On 02/09/18 20:19, bowa...@gmail.com wrote: > > > So, do you think I should try to submit a PR for some of > > the info present on the wiki page ? > > I think bowabos is already in process of doing this, but I can't find the PR? > > > Or may I send a link of the wiki page > > to the qubes-users@ ML first (so that people don't loose time going > > through the same issues), > > This shouldn't hurt, but please also mention what you said about it being > an unofficial staging area and content will be moved to the official docs, > etc. > > > and then wait that nobody has problems with the > > current set of install instructions before submitting a PR ? > > I wouldn't wait on future ones. If you've verified them yourself, go ahead > and submit. > > >> I second that, Ivan you've done a lot of work. I am not used to > >> opensource collaboration, so please feedback on my social "skills", I > >> feel I've jump the guns. So apologies. > > > > no problem at all - it seems that we're several people trying to install > > windows HVM on R4 and we all publish our findings at the same time ! > > I don't think anyone jumped the gun. > > I see adubois also has a PR out here for Windows doc patches, do they > cover the current wiki content? > https://github.com/QubesOS/qubes-doc/pull/578 This pull request cover just the minimum so that Windows can be installed (qvm-create + correct VM shell configuration). But if someone running R4 should be able to install win7 now without issues. QWT is not covered. I will have only limited capacity to help this week but will happily give a shot at reviewing the all Windows section after. However I will do that after fixing my Yubikey integration solution that I have promised to someone https://github.com/adubois/qubes-app-linux-yubikey -- 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/e5c732f8-b65e-4657-a266-42386385b767%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 Fri, February 9, 2018 6:52 pm, Ivan Mitev wrote: > @ bowabos & awokd > > > On 02/09/18 20:19, bowa...@gmail.com wrote: > So, do you think I should try to submit a PR for some of > the info present on the wiki page ? I think bowabos is already in process of doing this, but I can't find the PR? > Or may I send a link of the wiki page > to the qubes-users@ ML first (so that people don't loose time going > through the same issues), This shouldn't hurt, but please also mention what you said about it being an unofficial staging area and content will be moved to the official docs, etc. > and then wait that nobody has problems with the > current set of install instructions before submitting a PR ? I wouldn't wait on future ones. If you've verified them yourself, go ahead and submit. >> I second that, Ivan you've done a lot of work. I am not used to >> opensource collaboration, so please feedback on my social "skills", I >> feel I've jump the guns. So apologies. > > no problem at all - it seems that we're several people trying to install > windows HVM on R4 and we all publish our findings at the same time ! I don't think anyone jumped the gun. I see adubois also has a PR out here for Windows doc patches, do they cover the current wiki content? https://github.com/QubesOS/qubes-doc/pull/578 -- 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/0fef413a97e65666ecea56b3a25b1de4.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
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." Granted, I think the reason is that in addition to the documented step of copying windows-tools.conf to builder.conf, there are probably some other configuration changes (not listed) to make the windows build environment work...but I don't know what they are. Using a new stable, up to date Win7 HVM install on Qubes R4, I followed the instructions without problems using the following variations to resolve some issues: - changing to a user account without spaces in it for better mingw32 pathname resolution. - hosting qubes-builder directory initially in the user download directory as well as later in C:\DEV - installing free VS2013 community release in either the standard location [hybrid of C:\program files and C:\program files (x86)] as well as in c:\vs2013 -- as documented, copying windows-tool.conf to builder.conf Lastly, while trying to figure out what the gap is in the instructions that lead to "make qubes", the last line, failing I tried: -- copying in all of the various files from that repository into the qubes-builder directory (no filename conflicts, basically a folder tree merge), and attemping to swap makefiles, etc. -- looking for conflicting pathnames to VS2013 in the qubes files, etc. and fixing them to match my current environment. What obvious thing am I missing? Thanks, 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/1f35d245-dedd-409b-9fce-c1d2ef01958f%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?
@ bowabos & awokd On 02/09/18 20:19, bowa...@gmail.com wrote: On Friday, 9 February 2018 18:10:24 UTC, awokd wrote: On Fri, February 9, 2018 5:56 pm, Ivan Mitev wrote: I saw on qubes-users that you're updating the official documentation, that's great. Not only me! Some of the documents have already been updated, and others are being addressed by people with more knowledge in those areas. I *really* don't want to sound like I'm duplicating some of your work, or making your work harder. You're definitely not doing either. See https://github.com/QubesOS/qubes-issues/issues/3495 . I'm listing items (Windows 7 docs for a relevant example) that I'm skipping because I haven't used it enough to provide good documentation. My main concern was that *somebody* was going to push stuff from the wiki to the docs, and it not just sit out there confusing users with two knowledge sets. :) OK :) I just read issue #3495, you have a lot more knowledge of the official docs than I do. So, do you think I should try to submit a PR for some of the info present on the wiki page ? Or may I send a link of the wiki page to the qubes-users@ ML first (so that people don't loose time going through the same issues), and then wait that nobody has problems with the current set of install instructions before submitting a PR ? I second that, Ivan you've done a lot of work. I am not used to opensource collaboration, so please feedback on my social "skills", I feel I've jump the guns. So apologies. no problem at all - it seems that we're several people trying to install windows HVM on R4 and we all publish our findings at the same time ! On the documentation side, from my point of view, the security side on this area of the doc needs to be reviewed to address the iso in Dom0 (we should not do or encourage it) I also though of that. I'll try to test with --cdrom and the iso in an untrusted VM (it just worked for the tools so I don't know why I had to use a loop device on dom0). -- 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/a9631d61-8a85-e279-d27e-a746af8264ba%40maa.bz. 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, 9 February 2018 18:10:24 UTC, awokd wrote: > On Fri, February 9, 2018 5:56 pm, Ivan Mitev wrote: > > > > > I saw on qubes-users that you're updating the official documentation, > > that's great. > > Not only me! Some of the documents have already been updated, and others > are being addressed by people with more knowledge in those areas. > > > I *really* don't want to sound like I'm duplicating some of > > your work, or making your work harder. > > You're definitely not doing either. See > https://github.com/QubesOS/qubes-issues/issues/3495 . I'm listing items > (Windows 7 docs for a relevant example) that I'm skipping because I > haven't used it enough to provide good documentation. > > My main concern was that *somebody* was going to push stuff from the wiki > to the docs, and it not just sit out there confusing users with two > knowledge sets. :) I second that, Ivan you've done a lot of work. I am not used to opensource collaboration, so please feedback on my social "skills", I feel I've jump the guns. So apologies. On the documentation side, from my point of view, the security side on this area of the doc needs to be reviewed to address the iso in Dom0 (we should not do or encourage it) - -- 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/ce9b653c-dcb2-4b12-bd29-1d0a882790dd%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 Fri, February 9, 2018 6:10 pm, awokd wrote: > On Fri, February 9, 2018 5:56 pm, Ivan Mitev wrote: > > > > >> I saw on qubes-users that you're updating the official documentation, >> that's great. > > Not only me! Some of the documents have already been updated, and others > are being addressed by people with more knowledge in those areas. And to give credit where it's due, Andrew David Wong and Marek have also been instrumental in filling in my knowledge gaps. -- 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/745ddfb49d4aa7f195c98bb52f24a386.squirrel%40tt3j2x4k5ycaa5zt.onion. 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, 9 February 2018 17:56:49 UTC, Ivan Mitev wrote: > On 02/09/18 18:05, 'awokd' via qubes-devel wrote: > > On Thu, February 8, 2018 4:50 pm, Ivan Mitev wrote: > > > >> > >> IMHO a public wiki - official or not - should not replace the current > >> documentation: someone may add unsecure instructions (willingly or not) > >> and there will always be users who blindingly copy/paste instructions. > > > > That and divergence between the two sets of documentation, possibly by > > neglecting one or the other. > > > >> My idea behind a public wiki was to have a "staging" area that would > >> lower the bar for writing official documentation (eg. understanding pull > >> requests isn't needed), as well as easing "community" testing/debugging > >> (like providing workarounds or step-by-step instructions like now with > >> Windows HVMs). > > > > This sounds good; should avoid divergence. > > I fully agree about the divergence issue, that's why I plan to delete > the content on the public page(s) after it's pulled in the official docs. > > >> If after some time the instructions are deemed good > >> enough, then they could be pulled into the official docs and removed from > >> the wiki. > > > > Will you be handling that step by submitting PRs against the official > > docs? How frequently? > > I've set up the windows HVM wiki page to help other people struggling > with the issues I've been through. It's a bit of an experiment and it > would be interesting to see if other users contribute content to this > specific page, or even add other pages (the latter would be an > indication that something is either missing or difficult to find in the > official docs). > > tl;dr; I don't really know how it'll work out, how frequently PRs would > have to submitted - and whether I'll submit them myself or other users > step in, etc. > > I saw on qubes-users that you're updating the official documentation, > that's great. I *really* don't want to sound like I'm duplicating some > of your work, or making your work harder. The wiki page is 100% public > so feel free to delete stuff and/or import it in the official document > at your convenience. > > BTW I've eventually managed to successfully install Windows 7 in R4 and > I've updated the wiki page accordingly. I see that user > bowa...@gmail.com also managed to install a win7 VM with exactly the > same commands, so maybe we've reached a working set of install > instructions and I could submit a PR (or you could copy/paste the > instructions in the official docs). > IMHO, given that people are now trying R4 and Windows HVMs (there's for > instance a post on qubes-users@ by Alex a sec ago) it would be helpful > to post the link of the updated official doc or the temporary wiki page > to the qubes-users@ ML. > > Let me know what you think... > > Best, > Ivan Hi, I just saw this post. Apologies, I had already submitted a PR https://groups.google.com/forum/#!topic/qubes-devel/tBqwJmOAJ94 with the minimal change to get the install working. -- 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/7eeb11a8-a6d0-46e7-8da2-c6a8ef162d4b%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 Fri, February 9, 2018 5:56 pm, Ivan Mitev wrote: > I saw on qubes-users that you're updating the official documentation, > that's great. Not only me! Some of the documents have already been updated, and others are being addressed by people with more knowledge in those areas. > I *really* don't want to sound like I'm duplicating some of > your work, or making your work harder. You're definitely not doing either. See https://github.com/QubesOS/qubes-issues/issues/3495 . I'm listing items (Windows 7 docs for a relevant example) that I'm skipping because I haven't used it enough to provide good documentation. My main concern was that *somebody* was going to push stuff from the wiki to the docs, and it not just sit out there confusing users with two knowledge sets. :) -- 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/1ad9cac489c152d1daf53725799072ba.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On 02/09/18 18:05, 'awokd' via qubes-devel wrote: On Thu, February 8, 2018 4:50 pm, Ivan Mitev wrote: IMHO a public wiki - official or not - should not replace the current documentation: someone may add unsecure instructions (willingly or not) and there will always be users who blindingly copy/paste instructions. That and divergence between the two sets of documentation, possibly by neglecting one or the other. My idea behind a public wiki was to have a "staging" area that would lower the bar for writing official documentation (eg. understanding pull requests isn't needed), as well as easing "community" testing/debugging (like providing workarounds or step-by-step instructions like now with Windows HVMs). This sounds good; should avoid divergence. I fully agree about the divergence issue, that's why I plan to delete the content on the public page(s) after it's pulled in the official docs. If after some time the instructions are deemed good enough, then they could be pulled into the official docs and removed from the wiki. Will you be handling that step by submitting PRs against the official docs? How frequently? I've set up the windows HVM wiki page to help other people struggling with the issues I've been through. It's a bit of an experiment and it would be interesting to see if other users contribute content to this specific page, or even add other pages (the latter would be an indication that something is either missing or difficult to find in the official docs). tl;dr; I don't really know how it'll work out, how frequently PRs would have to submitted - and whether I'll submit them myself or other users step in, etc. I saw on qubes-users that you're updating the official documentation, that's great. I *really* don't want to sound like I'm duplicating some of your work, or making your work harder. The wiki page is 100% public so feel free to delete stuff and/or import it in the official document at your convenience. BTW I've eventually managed to successfully install Windows 7 in R4 and I've updated the wiki page accordingly. I see that user bowa...@gmail.com also managed to install a win7 VM with exactly the same commands, so maybe we've reached a working set of install instructions and I could submit a PR (or you could copy/paste the instructions in the official docs). IMHO, given that people are now trying R4 and Windows HVMs (there's for instance a post on qubes-users@ by Alex a sec ago) it would be helpful to post the link of the updated official doc or the temporary wiki page to the qubes-users@ ML. Let me know what you think... Best, Ivan -- 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/1ad298f0-1164-f560-0f1e-66ce1e441458%40maa.bz. 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, 3 February 2018 18:58:14 UTC, Yuraeitha wrote: > On Saturday, February 3, 2018 at 5:06:20 AM UTC+1, Andrew David Wong wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > On 2018-02-02 17:19, Yuraeitha wrote: > > > > > > It seems omeg who has been maintaining Qubes-Windows-Tools the last > > > few years, has gone inactive > > > > He is instead working on other projects for ITL's corporate clients, > > so "inactive" is not quite accurate. > > > > > https://github.com/QubesOS/qubes-installer-qubes-os-windows-tools > > > and thus far, it looks like no one else has picked up the project. > > > > > > > Correct. > > > > > If it is not planned to be done any time soon, then that's alright, > > > I can live with that. I'm already immensely grateful for everything > > > the Qubes team has done. But it's not so easy for everyone though, > > > some people are more heavily reliant on Windows than others for > > > certain applications. > > > > > > This post is NOT a complaint or anything of the sorts, but instead > > > a question to settle expectations on the correct path, instead of > > > looking every day for a new update, which can be a lot of > > > uncertainty or for some people even anxiety and frustrations, when > > > on Qubes 4 without a means to get Windows 7 installed. Essentially > > > people who need Windows and would love to get Qubes 4, are caught > > > in-between without any idea when or even if Windows 7 will be > > > supported anytime in the near-term future. > > > > > > In other words, just knowing it won't be anytime soon is in a way > > > also very good news, because it puts expectations in the right > > > place instead of uncertainty. Any such news-update on what is going > > > on with it and what to expect, would be appreciated. > > > > > > > As far as I know, Qubes Windows Tools continues to remain on > > indefinite hold. We welcome anyone from the community with the > > requisite skills to take over development (or just pitch in here and > > there). > > > > > Also, I'm not entirely sure regarding the code itself, but it > > > should be somewhat close to Qubes 4 in the current > > > Qubes-Windows-Tools? For example the Qubes 3.2. Win7 restored from > > > backup in Qubes 4, seems to more or less work, somewhat smoothly, > > > but not perfect. If so, maybe someone else can help with bringing > > > Qubes-Windos-Tools to Qubes 4? Unfortunately I have no coding > > > skills of this sort though, otherwise I'd give it a shot. > > > > > > > Sorry, I don't know. > > > > - -- > > Andrew David Wong (Axon) > > Community Manager, Qubes OS > > https://www.qubes-os.org > > > > -BEGIN PGP SIGNATURE- > > > > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp1NS0ACgkQ203TvDlQ > > MDCZYw//X/AlrUieQTF4ebMSab60xahi5erwpQc87Yzvb7WLLYBEnmY19d60M8IT > > oOr6p3zroDc+VvwBW4vIcp4S7RUNIDbIyppulW+6eiFunQK8kZGpks+RKfntxwEq > > Z8MCFeVNCedn43AGc6DCOLFrSsQVUR0LKVGIcI/Lhoe60zdvoMofnlF2hHRzWqvb > > 9UYuu/Kiqyy8RVyNq1LSNJ4/5jIIFDoxk12Wngc3s22OU5/u6I2vlnUHHwDC/X6n > > kbWSa8ltdKIOpglWxf34G7G60kdQVLfqw88mFzGUMk02EOeGkErMuG39wzCCGWyA > > 0Yp+KWeUaTH7mzUVTHR4G0uuWlFx7IaXUWOSJVmuSjItCQ4s7qbZ8A78ajN1aLYd > > JhhVnM8jzDF8zkrAd6Ez+zRVa9im/m1puck3uNb8Ou6VD0FnRWowl6iz0ijRhXsF > > A6qgr4jiGqqp3OSvxActu32KbW2ogxrDQThztcJgY1DuhDF/Y6YBHRI9I92udQ6r > > +A5OKoIKe3cskntkF5lrSawqVtyD+lxuT00gwwJrolj1ixdHt8ufyezvJxDYZJac > > UIu4y95w4H28YoxCY5bmoMIB5ncl4kskKs7qFpNbVHs4d8GsW1NcT2fxNzslGtsV > > D7muRf9n/gX3Ui5wNwwjP0gVMD6RrsY4wRdt4Jzk87VVdJIEiXM= > > =LLLN > > -END PGP SIGNATURE- > > Thanks Andrew, this was exactly what I was looking for, much appreciated. > > I'm gonna settle in for a plan B as listed below, although it looks really > interesting if Elias will be looking into it. Maybe Marek or someone else > with insight into the code can help a little bit to get started? > > But for the time being, I might try install Qubes 3.2. as a plan B to create > some temporary unlicensed clean Win7 Qubes backup's, and see if I can > transfer them to various of other Qubes 4 systems. This is mostly needed for > my friends though, and I still need to figure out if this is allowed within > the use-cases of the Windows 7 license or not, they will use their own > licenses. > > This method is a bit cumberstone if the code inside the Win7 installed on > Qubes 3.2. is buggy and creates unreliable issues, like unreliable transfer > of data integrity. Hopefully nothing bad will happen. > > Also need different types of Windows 7 copies for different types of > licenses, which is a bit problematic, but not impossible. > > For now this temporary plan B, this might be a work around to get a new clean > Win7 on multiple of different Qubes 4 systems, although a bit cumberstone, > and uncertain possibility of data integrity risk. Hi All, Thanks for your help in the thread. On R4, in order to get Win7SP1 64Bit Pro installed I did qvm-create win7 --class StandaloneVM --property
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On Thu, February 8, 2018 4:50 pm, Ivan Mitev wrote: > > IMHO a public wiki - official or not - should not replace the current > documentation: someone may add unsecure instructions (willingly or not) > and there will always be users who blindingly copy/paste instructions. That and divergence between the two sets of documentation, possibly by neglecting one or the other. > My idea behind a public wiki was to have a "staging" area that would > lower the bar for writing official documentation (eg. understanding pull > requests isn't needed), as well as easing "community" testing/debugging > (like providing workarounds or step-by-step instructions like now with > Windows HVMs). This sounds good; should avoid divergence. > If after some time the instructions are deemed good > enough, then they could be pulled into the official docs and removed from > the wiki. Will you be handling that step by submitting PRs against the official docs? How frequently? -- 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/ec574595f27d4bf164c93297fcb55be1.squirrel%40tt3j2x4k5ycaa5zt.onion. 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, February 9, 2018 at 6:58:24 AM UTC+1, Ivan Mitev wrote: > > FYI I've just added a "Fresh install on R4" section. It's still a work > > in progress though: I get a cryptic msg in guest-win7-dm.log file a bit > > after the first part of the setup reboots the VM. > > > > qemu: /home/user/qubes-src/vmm-xen-stubdom-linux/build/qemu/exec.c:1187: > > cpu_physical_memory_snapshot_get_dirty: Assertion `start + length <= > > snap->end' failed. > > > For anybody following the thread - searching the web for a similar error > shows that it could be related to a problem with qemu's VGA [1] (if > that's indeed the problem here, there's a patch from Aug. 2017 [2], > maybe it's not yet in the xen stubdomain source used by qubes). > > Thinking it could be related to issue #2488 [3] I tried to use cirrus > instead of (std)vga but the instructions in the issue are specific to > R3.2 and it wasn't immediately clear where to change the configuration > (nothing in `virsh dumpxml vmname` either). Maybe there's simply no way > to use cirrus with the more modern stubdomain used by R4. > > Veering way off-topic from the OP - I'll open an issue once I manage to > do more tests. > > > [1] https://nvd.nist.gov/vuln/detail/CVE-2017-13673 > [2] https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg04685.html > [3] https://github.com/QubesOS/qubes-issues/issues/2488 Speaking of graphic errors, there is another one I noticed that was around in Qubes 3.2. but I noticed it's now also be present in Qubes 4. I did not realize earlier since until last few days, I had not used Windows my self at all on Qubes 4. The behavior is the interface locking and becoming immune to mouse clicks only (left and right mouse buttons), but keyboard and moving the cursor around still works fine, it's essentially only left+right mouse-buttons that stops working by the looks of it. The odd thing is it's relatively easy to quick-fix, since every time it's happened, clicking the middle mouse-button (or scroll-wheel mouse-button for those few mouses that have this ability), seems to fix this issue, 100%, always. The problem here is not so much the annoying thing that it happens, especially when it's this easy to fix. But more so if people using Windows are not aware of this quick-fix, and moreover, perhaps not everyone have a mouse with a middle-button or other mouse-button that resets the bug. Worse yet, may be laptop mouse-pads. Perhaps there are sufficient clues to track another quick-fix for people without a mouse with a middle-button to reset this bug? It'd also be interesting to see how common this issue is. I've seen it on three vastly different hardware setups running Qubes+Windows. So far if including past Qubes 3.2. installations where the bug also was present, this bug seems common? Does it happen to you as well? I've seen this issue at least once every Windows start over longer extended use (10+ minutes, and only happens if you click on the Windows interface menu's like folder and menu navigation buttons). -- 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/666349e2-45b9-4904-899d-343a80cc06b3%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 Thursday, February 8, 2018 at 11:50:23 AM UTC-5, Ivan Mitev wrote: > On 02/08/18 17:31, Yuraeitha wrote: > >> so, I found some time and created this: > >> > >> https://github.com/taradiddles/qubes-notes/wiki/Windows-VM > >> > FYI I've just added a "Fresh install on R4" section. It's still a work > in progress though: I get a cryptic msg in guest-win7-dm.log file a bit > after the first part of the setup reboots the VM. > > qemu: /home/user/qubes-src/vmm-xen-stubdom-linux/build/qemu/exec.c:1187: > cpu_physical_memory_snapshot_get_dirty: Assertion `start + length <= > snap->end' failed. For your win7 HVM VMs: - Did you add the meminfo-writer service to the services tab and then disable its checkbox? - Did you make sure the Include in memory balancing checkbox is disabled on the Advanced tab? 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/5ec3d7df-6613-4f3a-ad83-8f1796153cbe%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 Thursday, February 8, 2018 at 2:19:19 PM UTC-5, Ivan Mitev wrote: > On 02/08/18 20:00, Brendan Hoar wrote: > > For your win7 HVMs did you, in this order: > > - On the last tab, Services, add "meminfo-writer" and then uncheck the > > checkmark? > > meminfo-writer isn't enabled on this VM (the list of services is empty). My reading indicates that services *not displayed* get a default setting, which, for meminfo-writer, is enabled *I think*. Please advise me if I am wrong! With this assumption, you must add it to the list of displayed services and then uncheck to actually disable it for a VM. [If this is true, it might be worth someone updating the python UI code to do this automatically.] 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/9020216f-1b1d-491e-8c8e-f61962a3456c%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 02/08/18 20:00, brendan.h...@gmail.com wrote: On Thursday, February 8, 2018 at 11:50:23 AM UTC-5, Ivan Mitev wrote: FYI I've just added a "Fresh install on R4" section. It's still a work in progress though: I get a cryptic msg in guest-win7-dm.log file a bit after the first part of the setup reboots the VM. qemu: /home/user/qubes-src/vmm-xen-stubdom-linux/build/qemu/exec.c:1187: cpu_physical_memory_snapshot_get_dirty: Assertion `start + length <= snap->end' failed. For your win7 HVMs did you, in this order: - On the last tab, Services, add "meminfo-writer" and then uncheck the checkmark? meminfo-writer isn't enabled on this VM (the list of services is empty). - On the second tab, Advanced, uncheck the "Include in memory balancing" checkbox after you set the min/max RAM to 4096MB? Unchecking the checkbox greyed out the maxmem field (which should amount to set maxmem = memory, right ?) but unfortunately I still get the same error. Thanks for the ideas though ! -- 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/dff4422d-be05-15d4-3d2a-c4244e6ddd43%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On Thursday, February 8, 2018 at 11:50:23 AM UTC-5, Ivan Mitev wrote: > FYI I've just added a "Fresh install on R4" section. It's still a work > in progress though: I get a cryptic msg in guest-win7-dm.log file a bit > after the first part of the setup reboots the VM. > > qemu: /home/user/qubes-src/vmm-xen-stubdom-linux/build/qemu/exec.c:1187: > cpu_physical_memory_snapshot_get_dirty: Assertion `start + length <= > snap->end' failed. For your win7 HVMs did you, in this order: - On the last tab, Services, add "meminfo-writer" and then uncheck the checkmark? - On the second tab, Advanced, uncheck the "Include in memory balancing" checkbox after you set the min/max RAM to 4096MB? 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/a5d9e92a-ad7a-4ea0-a761-39ec162aa9ba%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 02/08/18 17:31, Yuraeitha wrote: @Ivan On Thursday, February 8, 2018 at 1:22:06 PM UTC+1, Ivan Mitev wrote: - I think it's great if you post your guide for others to see :) You can always leave a disclaimer, such as no code has not been audited in this particular case, however that it worked for a few of users who tried it (it worked for me on my first try, more to come though). If people have all available information, including the disclaimer, then they can make calls for themselves, so that responsibility is not put on you if something should go wrong. Well, strictly speaking there's no "guide" yet :) - only bits and parts in notes, ML posts or from the official qubes documentation. Marek's last post also provided a lot of informative stuff. Ideally there should be a wiki page with those tests and pieces of info, with more relaxed "commit" rights than the official Qubes docs so that users can freely change/fix the instructions until things settle down - at which point they could maybe be included in the official documentation. I see there's a handful of free wiki sites on the web, I'll try to setup a page on one of those. But as usual, not ETA - I have very little free time ; if you'd like you can go ahead and publish what you already have/found out and I'll definitely help with the content and tests. so, I found some time and created this: https://github.com/taradiddles/qubes-notes/wiki/Windows-VM It's a bit of a hodgepodge from various ML posts and my own notes. The edit policy is open to everyone, so anyone - feel free to add your own stuff. (I hope it's not a problem to create such an unofficial wiki; If it is I'll delete it and I'll try to make the doc a bit more pretty and send a PR for inclusion in the official doc; alternatively, such a wiki could be created in the qubes-doc repository). Ivan It's looking really good, it looks like you got every currently confirmed Windows issues on there in a well-written and easy to read page. This will definitely be helpful to point to for those switching from Q3.2. to Q4.0. and are asking about Windows support. FYI I've just added a "Fresh install on R4" section. It's still a work in progress though: I get a cryptic msg in guest-win7-dm.log file a bit after the first part of the setup reboots the VM. qemu: /home/user/qubes-src/vmm-xen-stubdom-linux/build/qemu/exec.c:1187: cpu_physical_memory_snapshot_get_dirty: Assertion `start + length <= snap->end' failed. Seems to be qubes related... I'll try to continue this over the week-end and I'll open an issue if Marek doesn't have a quick workaround until then :) I like your idea about an official Wiki page too for Qubes, in the fashion you described it. I imagine an easy to find link to such a Qubes wiki on the www.qubes-os.org website might be really good, so that more people may discover it and use it. And considering it's available on github, which seems like a big plus as well. It'd be interesting to know what the Qubes developers/staff feel about your wiki suggestion. Also the current doc section on the official website is becoming a bit over-cluttered as its growing over time. A wiki indeed seems like it might make good sense at this point, especially if more doc's are to appear on-wards. IMHO a public wiki - official or not - should not replace the current documentation: someone may add unsecure instructions (willingly or not) and there will always be users who blindingly copy/paste instructions. My idea behind a public wiki was to have a "staging" area that would lower the bar for writing official documentation (eg. understanding pull requests isn't needed), as well as easing "community" testing/debugging (like providing workarounds or step-by-step instructions like now with Windows HVMs). If after some time the instructions are deemed good enough, then they could be pulled into the official docs and removed from the wiki. -- 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/bf70f97a-76b2-33ca-091d-140e21228156%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
@Ivan On Thursday, February 8, 2018 at 1:22:06 PM UTC+1, Ivan Mitev wrote: > >> - I think it's great if you post your guide for others to see :) You > >> can always leave a disclaimer, such as no code has not been audited in > >> this particular case, however that it worked for a few of users who > >> tried it (it worked for me on my first try, more to come though). If > >> people have all available information, including the disclaimer, then > >> they can make calls for themselves, so that responsibility is not put > >> on you if something should go wrong. > > > > Well, strictly speaking there's no "guide" yet :) - only bits and parts > > in notes, ML posts or from the official qubes documentation. Marek's > > last post also provided a lot of informative stuff. > > > > Ideally there should be a wiki page with those tests and pieces of info, > > with more relaxed "commit" rights than the official Qubes docs so that > > users can freely change/fix the instructions until things settle down - > > at which point they could maybe be included in the official documentation. > > > > I see there's a handful of free wiki sites on the web, I'll try to setup > > a page on one of those. But as usual, not ETA - I have very little free > > time ; if you'd like you can go ahead and publish what you already > > have/found out and I'll definitely help with the content and tests. > > so, I found some time and created this: > > https://github.com/taradiddles/qubes-notes/wiki/Windows-VM > > It's a bit of a hodgepodge from various ML posts and my own notes. The > edit policy is open to everyone, so anyone - feel free to add your own > stuff. > > (I hope it's not a problem to create such an unofficial wiki; If it is > I'll delete it and I'll try to make the doc a bit more pretty and send a > PR for inclusion in the official doc; alternatively, such a wiki could > be created in the qubes-doc repository). > > Ivan It's looking really good, it looks like you got every currently confirmed Windows issues on there in a well-written and easy to read page. This will definitely be helpful to point to for those switching from Q3.2. to Q4.0. and are asking about Windows support. I like your idea about an official Wiki page too for Qubes, in the fashion you described it. I imagine an easy to find link to such a Qubes wiki on the www.qubes-os.org website might be really good, so that more people may discover it and use it. And considering it's available on github, which seems like a big plus as well. It'd be interesting to know what the Qubes developers/staff feel about your wiki suggestion. Also the current doc section on the official website is becoming a bit over-cluttered as its growing over time. A wiki indeed seems like it might make good sense at this point, especially if more doc's are to appear on-wards. -- 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/f8f6e1b9-cc56-481e-85bf-ff7770c30e02%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?
- I think it's great if you post your guide for others to see :) You can always leave a disclaimer, such as no code has not been audited in this particular case, however that it worked for a few of users who tried it (it worked for me on my first try, more to come though). If people have all available information, including the disclaimer, then they can make calls for themselves, so that responsibility is not put on you if something should go wrong. Well, strictly speaking there's no "guide" yet :) - only bits and parts in notes, ML posts or from the official qubes documentation. Marek's last post also provided a lot of informative stuff. Ideally there should be a wiki page with those tests and pieces of info, with more relaxed "commit" rights than the official Qubes docs so that users can freely change/fix the instructions until things settle down - at which point they could maybe be included in the official documentation. I see there's a handful of free wiki sites on the web, I'll try to setup a page on one of those. But as usual, not ETA - I have very little free time ; if you'd like you can go ahead and publish what you already have/found out and I'll definitely help with the content and tests. so, I found some time and created this: https://github.com/taradiddles/qubes-notes/wiki/Windows-VM It's a bit of a hodgepodge from various ML posts and my own notes. The edit policy is open to everyone, so anyone - feel free to add your own stuff. (I hope it's not a problem to create such an unofficial wiki; If it is I'll delete it and I'll try to make the doc a bit more pretty and send a PR for inclusion in the official doc; alternatively, such a wiki could be created in the qubes-doc repository). Ivan -- 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/2b8ae8fd-7582-3b25-5102-0df854a11ac1%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On 02/08/18 00:18, Yuraeitha wrote: @Ivan On Monday, February 5, 2018 at 7:50:30 AM UTC+1, Ivan Mitev wrote: On 02/04/18 19:26, Yuraeitha wrote: On Sunday, February 4, 2018 at 6:00:15 PM UTC+1, Ivan Mitev wrote: Also it seems like some functions "might (maybe)" work as intended, for example I can copy files between VM's and Win7, on a Win7 that was installed on Qubes 3.2., but backup restored on Qubes 4. Others seem like they can do this too. Also it seems it's a common problem not to be internet in the restored Q3.2-Win7, perhaps the code is different in regards to how it ties networking with Qubes 4? I have no idea about the rest of the mechanics from a users perspective though, and most certainly not as a developer as I unfortunately don't have such skills, I wish I could help more. I just spent a bit of time restoring my windows VM from 3.2, here are a few notes that might be helpful to work around some bugs that you're probably hitting too (I haven't filed any issues yet): - PVH/HVM: in the VM's settings gui, PVH is always displayed whatever the real pref value. -> use qvm-prefs vmname virt_mode to make sure you're really in HVM mode. - Networking: the PV network adapter was stuck at "Identifying" ; pinging an *ip* works but ping a host fails. tcpdump on sys-firewall shows that the requests were sent to the gateway's ip and were rejected. The reason seems to be that in R4.0 VMs are now using the exposed "/qubes-{primary,secondary}-dns" values, while in R3.2 the DNS server was the same as "/qubes-gateway" (see [1]). In my setup, "/qubes-{primary,secondary}-dns" are 10.139.1.{1,2} and /qubes-gateway is 10.137.0.6. DNS requests are rejected because they're sent to 10.137.0.6 instead of 10.139.1.{1,2} workaround 1-> manually set the DNS servers to /qubes-{primary,secondary}-dns ips. Ping and Internet Explorer worked, but the PV adapter was still suck at "identifying" and my Amazon Kindle for PC app complained about finding no network (it seems there's a windows "connectivity" API/flag that some apps use). However you will have to do this each time after boot since Qubes tools will reset the network settings. workaround 2-> in Program Files/Invisible.../Qubes.../bin/..., rename network-setup.exe to network-setup.exe.bkp to prevent Qubes tools from messing with your network settings, and manually set the VM's IP and DNS servers in the PV adapter network setting. Everything should then work OK, the only problem being that you'll have to make sure you keep your network settings synced (esp. the IP when you clone the VM). - Copying to/from the Win VM: works perfectly - you just have to type twice the destination VM (once in Windows, once in Qubes/dom0), since Qubes Tools aren't updated to reflect R4.0 new "way". note: before finding what was causing the connectivity problem I tried to update xen's windows PV drivers [2] but it broke the VM (ie. it wasn't starting anymore) so I had to restore it again. Anyway IIRC R3.2 Qubes Tool's drivers were at the same version as Xen's (8.2), so no need to fiddle with this. I was thinking about posting those steps on qubes-users@ but I don't feel I had done enough testing on my VM yet. I see you're quite active on qubes-users so feel free to redact/post some of my remarks if you think they'll help. [ an unofficial wiki would be a helpful bridge between the MLs and Qubes' official documentation: it's difficult to skim through all the related ML posts and IMO Qubes' official documentation shouldn't include crappy workaround hacks like the ones I've described above ]. [1] https://www.qubes-os.org/doc/vm-interface/ [2] https://www.xenproject.org/developers/teams/windows-pv-drivers.html @Evan Ivan :) Thanks Evan! This really looks promising, I will go and try it out tomorrow if I can scrap some free-time to try it out. I'll post here the moment I've tried it, hopefully I can get the internet working. BTW I assumed there was a single "Qubes Tools" service responsible for setting the network, launching qubesdb daemon, ..., but I noticed a bit after my post that each task was handled by a different service. So you can simply disable the "Qubes Network Setup" service instead of renaming the .exe Also, https://github.com/QubesOS/qubes-core-agent-windows/blob/master/src/network-setup/qubes-network-setup.c indeed shows that qubesGateway (/qubes-gateway) is used for DNS (line 287). The code is easy to understand and adding the new DNS variables, + setting the servers accordingly (if the variables aren't empty) should be straightforward. I don't have a Windows build environment to test any changes though. It's also very ensuring to hear that it's safe to copy files between Win7 and other VM's. I was a bit stressed out over this one due to worry of bit-rot. Well, it is working but I can't say how safe it is. But I imagine that R4.0 would disable such copy operations if they were deemed unsafe. I'll get back to you when I've tried this out,
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
Hi Marek, On 02/08/18 03:13, Marek Marczykowski-Górecki wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 07, 2018 at 02:18:59PM -0800, Yuraeitha wrote: @Ivan On Monday, February 5, 2018 at 7:50:30 AM UTC+1, Ivan Mitev wrote: On 02/04/18 19:26, Yuraeitha wrote: On Sunday, February 4, 2018 at 6:00:15 PM UTC+1, Ivan Mitev wrote: Also it seems like some functions "might (maybe)" work as intended, for example I can copy files between VM's and Win7, on a Win7 that was installed on Qubes 3.2., but backup restored on Qubes 4. Others seem like they can do this too. Also it seems it's a common problem not to be internet in the restored Q3.2-Win7, perhaps the code is different in regards to how it ties networking with Qubes 4? I have no idea about the rest of the mechanics from a users perspective though, and most certainly not as a developer as I unfortunately don't have such skills, I wish I could help more. I just spent a bit of time restoring my windows VM from 3.2, here are a few notes that might be helpful to work around some bugs that you're probably hitting too (I haven't filed any issues yet): - PVH/HVM: in the VM's settings gui, PVH is always displayed whatever the real pref value. -> use qvm-prefs vmname virt_mode to make sure you're really in HVM mode. - Networking: the PV network adapter was stuck at "Identifying" ; pinging an *ip* works but ping a host fails. tcpdump on sys-firewall shows that the requests were sent to the gateway's ip and were rejected. The reason seems to be that in R4.0 VMs are now using the exposed "/qubes-{primary,secondary}-dns" values, while in R3.2 the DNS server was the same as "/qubes-gateway" (see [1]). In my setup, "/qubes-{primary,secondary}-dns" are 10.139.1.{1,2} and /qubes-gateway is 10.137.0.6. DNS requests are rejected because they're sent to 10.137.0.6 instead of 10.139.1.{1,2} Yes, exactly. Actually /qubes-primary-dns entry is present on R3.2 too, but is the same as /qubes-gateway. workaround 1-> manually set the DNS servers to /qubes-{primary,secondary}-dns ips. Ping and Internet Explorer worked, but the PV adapter was still suck at "identifying" and my Amazon Kindle for PC app complained about finding no network (it seems there's a windows "connectivity" API/flag that some apps use). However you will have to do this each time after boot since Qubes tools will reset the network settings. workaround 2-> in Program Files/Invisible.../Qubes.../bin/..., rename network-setup.exe to network-setup.exe.bkp to prevent Qubes tools from messing with your network settings, and manually set the VM's IP and DNS servers in the PV adapter network setting. Everything should then work OK, the only problem being that you'll have to make sure you keep your network settings synced (esp. the IP when you clone the VM). - Copying to/from the Win VM: works perfectly - you just have to type twice the destination VM (once in Windows, once in Qubes/dom0), since Qubes Tools aren't updated to reflect R4.0 new "way". I guess this should be easy to fix, just need to skip the first prompt and provide "$default" as destination name in qrexec call. Looks this file is relevant: https://github.com/QubesOS/qubes-core-agent-windows/blob/master/core-agent-windows.wxs Compare "Copy to other VM" and "Edit in DispVM" entries. note: before finding what was causing the connectivity problem I tried to update xen's windows PV drivers [2] but it broke the VM (ie. it wasn't starting anymore) so I had to restore it again. Anyway IIRC R3.2 Qubes Tool's drivers were at the same version as Xen's (8.2), so no need to fiddle with this. There is also difference in emulated hardware - in R3.2 we use MiniOS based stubdomain, with "qemu-traditional" (vry old, mostly unmaintained qemu fork), while in R4.0 we use Linux based stubdomain, with recent version of upstream qemu (2.10.1 at the moment). This may cause problems when migrating HVMs between R3.2 and R4.0. There is a way to switch some VMs on R4.0 to the old qemu, and it is automatically done when restoring HVMs from R3.2 backup: qvm-features VMNAME linux-stubdom '' ('' means to _disable_ linux stubdomain...) When testing new installations, I recommend using new qemu (default settings when you create VM). You can copy windows tools installation iso from R3.2, it's in /usr/lib/qubes/qubes-windows-tools.iso. good to know ! (...) BTW I assumed there was a single "Qubes Tools" service responsible for setting the network, launching qubesdb daemon, ..., but I noticed a bit after my post that each task was handled by a different service. So you can simply disable the "Qubes Network Setup" service instead of renaming the .exe Also, https://github.com/QubesOS/qubes-core-agent-windows/blob/master/src/network-setup/qubes-network-setup.c indeed shows that qubesGateway (/qubes-gateway) is used for DNS (line 287). The code is easy to understand and adding the new DNS variables, + setting the servers accordingly
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
@awokd On Thursday, February 8, 2018 at 12:10:18 AM UTC+1, awokd wrote: > On Wed, February 7, 2018 10:38 pm, Yuraeitha wrote: > > > > > > Have you ever experienced crashes while running search files on disk from > > the Windows menu? If so, maybe we can turn off the search function to > > avoid any issues? > > Disk activity seems to trigger it for me too. I still get the occasional > crash when anti-virus scan runs for example, but it's been rare enough I > haven't looked into it any further. I already have search disabled so yes, > try it out too! Will do, hopefully it'll make a difference. It's frustrating that anti-virus does it too though. Maybe we can disable it on the AppVM, but only keep it enabled on the template of Windows? I never got around to get Windows template to work though, but I imagine it might be a way to bypass the anti-virus issue on daily use-cases. I'm pondering about the Superfetch service too, I recall from earlier days that Windows Superfetch could give issues, but as far as I remember it was never truly verified, at least not as an official note. Situations seem to be when having too little RAM on a hardware Windows install, perhaps it causes issues too with too little RAM on a VM install? I'll try disable mine, but I'm not sure if it will change anything related to the stability, other than its intended function of a bit faster application-start of course. Another issue I found, which I'm not yet sure is a problem or not, seems to be when closing Windows via the Qubes 4 widget, that it happens a lot, lot faster, compared to if you close Windows with the Windows own shutdown button, which is slow, but will eventually shutdown entirely in Qubes as well. I haven't verified it yet, but it does look like the Qubes 4 doesn't give room for updates to tick. Perhaps the intention here is that Qubes 4 widget is meant for AppVM versions of Windows, while the template should be shutdown with Windows's own shutdown command? It's fortunate that seamless mode doesn't have to be enabled on the Windows template to make use of the AppVM seamless mode. -- 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/3907a2ac-49b7-4486-be57-85055a880458%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 Thursday, February 8, 2018 at 2:13:42 AM UTC+1, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, Feb 07, 2018 at 02:18:59PM -0800, Yuraeitha wrote: > > @Ivan > > > > On Monday, February 5, 2018 at 7:50:30 AM UTC+1, Ivan Mitev wrote: > > > On 02/04/18 19:26, Yuraeitha wrote: > > > > On Sunday, February 4, 2018 at 6:00:15 PM UTC+1, Ivan Mitev wrote: > > > >>> Also it seems like some functions "might (maybe)" work as intended, > > > >>> for example I can copy files between VM's and Win7, on a Win7 that > > > >>> was installed on Qubes 3.2., but backup restored on Qubes 4. Others > > > >>> seem like they can do this too. Also it seems it's a common problem > > > >>> not to be internet in the restored Q3.2-Win7, perhaps the code is > > > >>> different in regards to how it ties networking with Qubes 4? I have > > > >>> no idea about the rest of the mechanics from a users perspective > > > >>> though, and most certainly not as a developer as I unfortunately > > > >>> don't have such skills, I wish I could help more. > > > >> > > > >> I just spent a bit of time restoring my windows VM from 3.2, here are a > > > >> few notes that might be helpful to work around some bugs that you're > > > >> probably hitting too (I haven't filed any issues yet): > > > >> > > > >> - PVH/HVM: in the VM's settings gui, PVH is always displayed whatever > > > >> the real pref value. -> use qvm-prefs vmname virt_mode to make sure > > > >> you're really in HVM mode. > > > >> > > > >> - Networking: the PV network adapter was stuck at "Identifying" ; > > > >> pinging an *ip* works but ping a host fails. tcpdump on sys-firewall > > > >> shows that the requests were sent to the gateway's ip and were > > > >> rejected. > > > >> The reason seems to be that in R4.0 VMs are now using the exposed > > > >> "/qubes-{primary,secondary}-dns" values, while in R3.2 the DNS server > > > >> was the same as "/qubes-gateway" (see [1]). In my setup, > > > >> "/qubes-{primary,secondary}-dns" are 10.139.1.{1,2} and /qubes-gateway > > > >> is 10.137.0.6. DNS requests are rejected because they're sent to > > > >> 10.137.0.6 instead of 10.139.1.{1,2} > > Yes, exactly. Actually /qubes-primary-dns entry is present on R3.2 too, > but is the same as /qubes-gateway. > > > > >> workaround 1-> manually set the DNS servers to > > > >> /qubes-{primary,secondary}-dns ips. Ping and Internet Explorer worked, > > > >> but the PV adapter was still suck at "identifying" and my Amazon Kindle > > > >> for PC app complained about finding no network (it seems there's a > > > >> windows "connectivity" API/flag that some apps use). However you will > > > >> have to do this each time after boot since Qubes tools will reset the > > > >> network settings. > > > >> > > > >> workaround 2-> in Program Files/Invisible.../Qubes.../bin/..., rename > > > >> network-setup.exe to network-setup.exe.bkp to prevent Qubes tools from > > > >> messing with your network settings, and manually set the VM's IP and > > > >> DNS > > > >> servers in the PV adapter network setting. Everything should then work > > > >> OK, the only problem being that you'll have to make sure you keep your > > > >> network settings synced (esp. the IP when you clone the VM). > > > >> > > > >> - Copying to/from the Win VM: works perfectly - you just have to type > > > >> twice the destination VM (once in Windows, once in Qubes/dom0), since > > > >> Qubes Tools aren't updated to reflect R4.0 new "way". > > I guess this should be easy to fix, just need to skip the first prompt > and provide "$default" as destination name in qrexec call. > Looks this file is relevant: > https://github.com/QubesOS/qubes-core-agent-windows/blob/master/core-agent-windows.wxs > > Compare "Copy to other VM" and "Edit in DispVM" entries. > > > > >> note: before finding what was causing the connectivity problem I tried > > > >> to update xen's windows PV drivers [2] but it broke the VM (ie. it > > > >> wasn't starting anymore) so I had to restore it again. Anyway IIRC R3.2 > > > >> Qubes Tool's drivers were at the same version as Xen's (8.2), so no > > > >> need > > > >> to fiddle with this. > > There is also difference in emulated hardware - in R3.2 we use MiniOS > based stubdomain, with "qemu-traditional" (vry old, mostly > unmaintained qemu fork), while in R4.0 we use Linux based stubdomain, > with recent version of upstream qemu (2.10.1 at the moment). > This may cause problems when migrating HVMs between R3.2 and R4.0. There > is a way to switch some VMs on R4.0 to the old qemu, and it is > automatically done when restoring HVMs from R3.2 backup: > > qvm-features VMNAME linux-stubdom '' > > ('' means to _disable_ linux stubdomain...) > > When testing new installations, I recommend using new qemu (default > settings when you create VM). You can copy windows tools installation > iso from R3.2, it's in /usr/lib/qubes/qubes-windows-tools.iso. > > (...) > > > > BTW I
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 07, 2018 at 02:18:59PM -0800, Yuraeitha wrote: > @Ivan > > On Monday, February 5, 2018 at 7:50:30 AM UTC+1, Ivan Mitev wrote: > > On 02/04/18 19:26, Yuraeitha wrote: > > > On Sunday, February 4, 2018 at 6:00:15 PM UTC+1, Ivan Mitev wrote: > > >>> Also it seems like some functions "might (maybe)" work as intended, for > > >>> example I can copy files between VM's and Win7, on a Win7 that was > > >>> installed on Qubes 3.2., but backup restored on Qubes 4. Others seem > > >>> like they can do this too. Also it seems it's a common problem not to > > >>> be internet in the restored Q3.2-Win7, perhaps the code is different in > > >>> regards to how it ties networking with Qubes 4? I have no idea about > > >>> the rest of the mechanics from a users perspective though, and most > > >>> certainly not as a developer as I unfortunately don't have such skills, > > >>> I wish I could help more. > > >> > > >> I just spent a bit of time restoring my windows VM from 3.2, here are a > > >> few notes that might be helpful to work around some bugs that you're > > >> probably hitting too (I haven't filed any issues yet): > > >> > > >> - PVH/HVM: in the VM's settings gui, PVH is always displayed whatever > > >> the real pref value. -> use qvm-prefs vmname virt_mode to make sure > > >> you're really in HVM mode. > > >> > > >> - Networking: the PV network adapter was stuck at "Identifying" ; > > >> pinging an *ip* works but ping a host fails. tcpdump on sys-firewall > > >> shows that the requests were sent to the gateway's ip and were rejected. > > >> The reason seems to be that in R4.0 VMs are now using the exposed > > >> "/qubes-{primary,secondary}-dns" values, while in R3.2 the DNS server > > >> was the same as "/qubes-gateway" (see [1]). In my setup, > > >> "/qubes-{primary,secondary}-dns" are 10.139.1.{1,2} and /qubes-gateway > > >> is 10.137.0.6. DNS requests are rejected because they're sent to > > >> 10.137.0.6 instead of 10.139.1.{1,2} Yes, exactly. Actually /qubes-primary-dns entry is present on R3.2 too, but is the same as /qubes-gateway. > > >> workaround 1-> manually set the DNS servers to > > >> /qubes-{primary,secondary}-dns ips. Ping and Internet Explorer worked, > > >> but the PV adapter was still suck at "identifying" and my Amazon Kindle > > >> for PC app complained about finding no network (it seems there's a > > >> windows "connectivity" API/flag that some apps use). However you will > > >> have to do this each time after boot since Qubes tools will reset the > > >> network settings. > > >> > > >> workaround 2-> in Program Files/Invisible.../Qubes.../bin/..., rename > > >> network-setup.exe to network-setup.exe.bkp to prevent Qubes tools from > > >> messing with your network settings, and manually set the VM's IP and DNS > > >> servers in the PV adapter network setting. Everything should then work > > >> OK, the only problem being that you'll have to make sure you keep your > > >> network settings synced (esp. the IP when you clone the VM). > > >> > > >> - Copying to/from the Win VM: works perfectly - you just have to type > > >> twice the destination VM (once in Windows, once in Qubes/dom0), since > > >> Qubes Tools aren't updated to reflect R4.0 new "way". I guess this should be easy to fix, just need to skip the first prompt and provide "$default" as destination name in qrexec call. Looks this file is relevant: https://github.com/QubesOS/qubes-core-agent-windows/blob/master/core-agent-windows.wxs Compare "Copy to other VM" and "Edit in DispVM" entries. > > >> note: before finding what was causing the connectivity problem I tried > > >> to update xen's windows PV drivers [2] but it broke the VM (ie. it > > >> wasn't starting anymore) so I had to restore it again. Anyway IIRC R3.2 > > >> Qubes Tool's drivers were at the same version as Xen's (8.2), so no need > > >> to fiddle with this. There is also difference in emulated hardware - in R3.2 we use MiniOS based stubdomain, with "qemu-traditional" (vry old, mostly unmaintained qemu fork), while in R4.0 we use Linux based stubdomain, with recent version of upstream qemu (2.10.1 at the moment). This may cause problems when migrating HVMs between R3.2 and R4.0. There is a way to switch some VMs on R4.0 to the old qemu, and it is automatically done when restoring HVMs from R3.2 backup: qvm-features VMNAME linux-stubdom '' ('' means to _disable_ linux stubdomain...) When testing new installations, I recommend using new qemu (default settings when you create VM). You can copy windows tools installation iso from R3.2, it's in /usr/lib/qubes/qubes-windows-tools.iso. (...) > > BTW I assumed there was a single "Qubes Tools" service responsible for > > setting the network, launching qubesdb daemon, ..., but I noticed a bit > > after my post that each task was handled by a different service. So you > > can simply disable the "Qubes Network Setup" service instead of renaming >
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On Wed, February 7, 2018 10:38 pm, Yuraeitha wrote: > > Have you ever experienced crashes while running search files on disk from > the Windows menu? If so, maybe we can turn off the search function to > avoid any issues? Disk activity seems to trigger it for me too. I still get the occasional crash when anti-virus scan runs for example, but it's been rare enough I haven't looked into it any further. I already have search disabled so yes, try it out too! -- 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/464d2dd904f520d68ff82d47a4ca4d4b.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
@awokd On Sunday, February 4, 2018 at 8:44:31 PM UTC+1, awokd wrote: > On Sun, February 4, 2018 5:23 pm, Yuraeitha wrote: > > > Another user in another Qubes 4 Win7 thread somewhere in Qubes-users > > mail-list, suggested to reduce the page-file for Windows SWAP inside the > > Windows VM. It worked for him, and when I tried it out, it worked for me > > too. It's possible this is what you encounter, try reduce the Windows > > page-file and see if it works? > > That was yours truly. I think it's more the act of setting the swap file > to a fixed size (of 1GB) that helped stabilize mine, but maybe you're > right and it's actually the size reduction. ohh, I apologize for forgetting your name at that time, back then most people were still strangers to me, and it takes a while for me to remember names. But I know I won't forget your name again now as I already remember it since a few topic discussions between back then and now ^.^ About the page-file size, I'm not sure either. I tried to restore a new Windows 7 backup again, and I tried giving the page-file 1.1GB as well as 2GB, to see if it would become unstable. It seems it was unstable on the first restart for the lower one (the one I started with), but after the second restart it became stable. This may also be due to the change of AppVM RAM which was 4GB before changing, and was given 2GB after changing the page-file. Which further complicates it. But after these two restarts, it was pretty smooth again, like the other Win7 I have tried it on before that. However, it once again became unstable during Windows updates + using the Search-files feature in Windows 7 start menu. Perhaps this instability is related to the drive's file-system (NTFS) of different and various sorts? It seems the page-file can remove the most frequent crashes by far, but a few others can cause it too, like searching the file-system while the system is busy with something else perhaps? I have a weak CPU on this laptop though, it's an Intel Core M-5Y10c @ 800Mhz. 8GB RAM. So I haven't used a strong system to test Win7 on. Although Windows 7 aside, everything in Qubes which is within normal-use runs more or less smoothly, and Windows 7 can run almost smoothly on this poor laptop. Although I'm not yet sure if running it on a stronger machine may make Win7 more smooth, or cause less crashes. Have you ever experienced crashes while running search files on disk from the Windows menu? If so, maybe we can turn off the search function to avoid any issues? -- 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/82bff806-e3b7-4465-b1c0-a84e3251cd83%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?
@Ivan On Monday, February 5, 2018 at 7:50:30 AM UTC+1, Ivan Mitev wrote: > On 02/04/18 19:26, Yuraeitha wrote: > > On Sunday, February 4, 2018 at 6:00:15 PM UTC+1, Ivan Mitev wrote: > >>> Also it seems like some functions "might (maybe)" work as intended, for > >>> example I can copy files between VM's and Win7, on a Win7 that was > >>> installed on Qubes 3.2., but backup restored on Qubes 4. Others seem like > >>> they can do this too. Also it seems it's a common problem not to be > >>> internet in the restored Q3.2-Win7, perhaps the code is different in > >>> regards to how it ties networking with Qubes 4? I have no idea about the > >>> rest of the mechanics from a users perspective though, and most certainly > >>> not as a developer as I unfortunately don't have such skills, I wish I > >>> could help more. > >> > >> I just spent a bit of time restoring my windows VM from 3.2, here are a > >> few notes that might be helpful to work around some bugs that you're > >> probably hitting too (I haven't filed any issues yet): > >> > >> - PVH/HVM: in the VM's settings gui, PVH is always displayed whatever > >> the real pref value. -> use qvm-prefs vmname virt_mode to make sure > >> you're really in HVM mode. > >> > >> - Networking: the PV network adapter was stuck at "Identifying" ; > >> pinging an *ip* works but ping a host fails. tcpdump on sys-firewall > >> shows that the requests were sent to the gateway's ip and were rejected. > >> The reason seems to be that in R4.0 VMs are now using the exposed > >> "/qubes-{primary,secondary}-dns" values, while in R3.2 the DNS server > >> was the same as "/qubes-gateway" (see [1]). In my setup, > >> "/qubes-{primary,secondary}-dns" are 10.139.1.{1,2} and /qubes-gateway > >> is 10.137.0.6. DNS requests are rejected because they're sent to > >> 10.137.0.6 instead of 10.139.1.{1,2} > >> > >> workaround 1-> manually set the DNS servers to > >> /qubes-{primary,secondary}-dns ips. Ping and Internet Explorer worked, > >> but the PV adapter was still suck at "identifying" and my Amazon Kindle > >> for PC app complained about finding no network (it seems there's a > >> windows "connectivity" API/flag that some apps use). However you will > >> have to do this each time after boot since Qubes tools will reset the > >> network settings. > >> > >> workaround 2-> in Program Files/Invisible.../Qubes.../bin/..., rename > >> network-setup.exe to network-setup.exe.bkp to prevent Qubes tools from > >> messing with your network settings, and manually set the VM's IP and DNS > >> servers in the PV adapter network setting. Everything should then work > >> OK, the only problem being that you'll have to make sure you keep your > >> network settings synced (esp. the IP when you clone the VM). > >> > >> - Copying to/from the Win VM: works perfectly - you just have to type > >> twice the destination VM (once in Windows, once in Qubes/dom0), since > >> Qubes Tools aren't updated to reflect R4.0 new "way". > >> > >> > >> note: before finding what was causing the connectivity problem I tried > >> to update xen's windows PV drivers [2] but it broke the VM (ie. it > >> wasn't starting anymore) so I had to restore it again. Anyway IIRC R3.2 > >> Qubes Tool's drivers were at the same version as Xen's (8.2), so no need > >> to fiddle with this. > >> > >> I was thinking about posting those steps on qubes-users@ but I don't > >> feel I had done enough testing on my VM yet. I see you're quite active > >> on qubes-users so feel free to redact/post some of my remarks if you > >> think they'll help. > >> > >> [ an unofficial wiki would be a helpful bridge between the MLs and > >> Qubes' official documentation: it's difficult to skim through all the > >> related ML posts and IMO Qubes' official documentation shouldn't include > >> crappy workaround hacks like the ones I've described above ]. > >> > >> > >> [1] https://www.qubes-os.org/doc/vm-interface/ > >> [2] https://www.xenproject.org/developers/teams/windows-pv-drivers.html > > > > @Evan > > Ivan :) > > > Thanks Evan! This really looks promising, I will go and try it out tomorrow > > if I can scrap some free-time to try it out. I'll post here the moment I've > > tried it, hopefully I can get the internet working. > > BTW I assumed there was a single "Qubes Tools" service responsible for > setting the network, launching qubesdb daemon, ..., but I noticed a bit > after my post that each task was handled by a different service. So you > can simply disable the "Qubes Network Setup" service instead of renaming > the .exe > > Also, > > https://github.com/QubesOS/qubes-core-agent-windows/blob/master/src/network-setup/qubes-network-setup.c > > indeed shows that qubesGateway (/qubes-gateway) is used for DNS (line > 287). The code is easy to understand and adding the new DNS variables, + > setting the servers accordingly (if the variables aren't empty) should > be straightforward. I don't have a Windows build environment to test any >
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On 02/04/18 19:26, Yuraeitha wrote: On Sunday, February 4, 2018 at 6:00:15 PM UTC+1, Ivan Mitev wrote: Also it seems like some functions "might (maybe)" work as intended, for example I can copy files between VM's and Win7, on a Win7 that was installed on Qubes 3.2., but backup restored on Qubes 4. Others seem like they can do this too. Also it seems it's a common problem not to be internet in the restored Q3.2-Win7, perhaps the code is different in regards to how it ties networking with Qubes 4? I have no idea about the rest of the mechanics from a users perspective though, and most certainly not as a developer as I unfortunately don't have such skills, I wish I could help more. I just spent a bit of time restoring my windows VM from 3.2, here are a few notes that might be helpful to work around some bugs that you're probably hitting too (I haven't filed any issues yet): - PVH/HVM: in the VM's settings gui, PVH is always displayed whatever the real pref value. -> use qvm-prefs vmname virt_mode to make sure you're really in HVM mode. - Networking: the PV network adapter was stuck at "Identifying" ; pinging an *ip* works but ping a host fails. tcpdump on sys-firewall shows that the requests were sent to the gateway's ip and were rejected. The reason seems to be that in R4.0 VMs are now using the exposed "/qubes-{primary,secondary}-dns" values, while in R3.2 the DNS server was the same as "/qubes-gateway" (see [1]). In my setup, "/qubes-{primary,secondary}-dns" are 10.139.1.{1,2} and /qubes-gateway is 10.137.0.6. DNS requests are rejected because they're sent to 10.137.0.6 instead of 10.139.1.{1,2} workaround 1-> manually set the DNS servers to /qubes-{primary,secondary}-dns ips. Ping and Internet Explorer worked, but the PV adapter was still suck at "identifying" and my Amazon Kindle for PC app complained about finding no network (it seems there's a windows "connectivity" API/flag that some apps use). However you will have to do this each time after boot since Qubes tools will reset the network settings. workaround 2-> in Program Files/Invisible.../Qubes.../bin/..., rename network-setup.exe to network-setup.exe.bkp to prevent Qubes tools from messing with your network settings, and manually set the VM's IP and DNS servers in the PV adapter network setting. Everything should then work OK, the only problem being that you'll have to make sure you keep your network settings synced (esp. the IP when you clone the VM). - Copying to/from the Win VM: works perfectly - you just have to type twice the destination VM (once in Windows, once in Qubes/dom0), since Qubes Tools aren't updated to reflect R4.0 new "way". note: before finding what was causing the connectivity problem I tried to update xen's windows PV drivers [2] but it broke the VM (ie. it wasn't starting anymore) so I had to restore it again. Anyway IIRC R3.2 Qubes Tool's drivers were at the same version as Xen's (8.2), so no need to fiddle with this. I was thinking about posting those steps on qubes-users@ but I don't feel I had done enough testing on my VM yet. I see you're quite active on qubes-users so feel free to redact/post some of my remarks if you think they'll help. [ an unofficial wiki would be a helpful bridge between the MLs and Qubes' official documentation: it's difficult to skim through all the related ML posts and IMO Qubes' official documentation shouldn't include crappy workaround hacks like the ones I've described above ]. [1] https://www.qubes-os.org/doc/vm-interface/ [2] https://www.xenproject.org/developers/teams/windows-pv-drivers.html @Evan Ivan :) Thanks Evan! This really looks promising, I will go and try it out tomorrow if I can scrap some free-time to try it out. I'll post here the moment I've tried it, hopefully I can get the internet working. BTW I assumed there was a single "Qubes Tools" service responsible for setting the network, launching qubesdb daemon, ..., but I noticed a bit after my post that each task was handled by a different service. So you can simply disable the "Qubes Network Setup" service instead of renaming the .exe Also, https://github.com/QubesOS/qubes-core-agent-windows/blob/master/src/network-setup/qubes-network-setup.c indeed shows that qubesGateway (/qubes-gateway) is used for DNS (line 287). The code is easy to understand and adding the new DNS variables, + setting the servers accordingly (if the variables aren't empty) should be straightforward. I don't have a Windows build environment to test any changes though. It's also very ensuring to hear that it's safe to copy files between Win7 and other VM's. I was a bit stressed out over this one due to worry of bit-rot. Well, it is working but I can't say how safe it is. But I imagine that R4.0 would disable such copy operations if they were deemed unsafe. I'll get back to you when I've tried this out, thanks! OK :) -- You received this message because you are subscribed to the Google Groups
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On Sunday, February 4, 2018 at 6:00:15 PM UTC+1, Ivan Mitev wrote: > > Also it seems like some functions "might (maybe)" work as intended, for > > example I can copy files between VM's and Win7, on a Win7 that was > > installed on Qubes 3.2., but backup restored on Qubes 4. Others seem like > > they can do this too. Also it seems it's a common problem not to be > > internet in the restored Q3.2-Win7, perhaps the code is different in > > regards to how it ties networking with Qubes 4? I have no idea about the > > rest of the mechanics from a users perspective though, and most certainly > > not as a developer as I unfortunately don't have such skills, I wish I > > could help more. > > I just spent a bit of time restoring my windows VM from 3.2, here are a > few notes that might be helpful to work around some bugs that you're > probably hitting too (I haven't filed any issues yet): > > - PVH/HVM: in the VM's settings gui, PVH is always displayed whatever > the real pref value. -> use qvm-prefs vmname virt_mode to make sure > you're really in HVM mode. > > - Networking: the PV network adapter was stuck at "Identifying" ; > pinging an *ip* works but ping a host fails. tcpdump on sys-firewall > shows that the requests were sent to the gateway's ip and were rejected. > The reason seems to be that in R4.0 VMs are now using the exposed > "/qubes-{primary,secondary}-dns" values, while in R3.2 the DNS server > was the same as "/qubes-gateway" (see [1]). In my setup, > "/qubes-{primary,secondary}-dns" are 10.139.1.{1,2} and /qubes-gateway > is 10.137.0.6. DNS requests are rejected because they're sent to > 10.137.0.6 instead of 10.139.1.{1,2} > > workaround 1-> manually set the DNS servers to > /qubes-{primary,secondary}-dns ips. Ping and Internet Explorer worked, > but the PV adapter was still suck at "identifying" and my Amazon Kindle > for PC app complained about finding no network (it seems there's a > windows "connectivity" API/flag that some apps use). However you will > have to do this each time after boot since Qubes tools will reset the > network settings. > > workaround 2-> in Program Files/Invisible.../Qubes.../bin/..., rename > network-setup.exe to network-setup.exe.bkp to prevent Qubes tools from > messing with your network settings, and manually set the VM's IP and DNS > servers in the PV adapter network setting. Everything should then work > OK, the only problem being that you'll have to make sure you keep your > network settings synced (esp. the IP when you clone the VM). > > - Copying to/from the Win VM: works perfectly - you just have to type > twice the destination VM (once in Windows, once in Qubes/dom0), since > Qubes Tools aren't updated to reflect R4.0 new "way". > > > note: before finding what was causing the connectivity problem I tried > to update xen's windows PV drivers [2] but it broke the VM (ie. it > wasn't starting anymore) so I had to restore it again. Anyway IIRC R3.2 > Qubes Tool's drivers were at the same version as Xen's (8.2), so no need > to fiddle with this. > > I was thinking about posting those steps on qubes-users@ but I don't > feel I had done enough testing on my VM yet. I see you're quite active > on qubes-users so feel free to redact/post some of my remarks if you > think they'll help. > > [ an unofficial wiki would be a helpful bridge between the MLs and > Qubes' official documentation: it's difficult to skim through all the > related ML posts and IMO Qubes' official documentation shouldn't include > crappy workaround hacks like the ones I've described above ]. > > > [1] https://www.qubes-os.org/doc/vm-interface/ > [2] https://www.xenproject.org/developers/teams/windows-pv-drivers.html @Evan Thanks Evan! This really looks promising, I will go and try it out tomorrow if I can scrap some free-time to try it out. I'll post here the moment I've tried it, hopefully I can get the internet working. It's also very ensuring to hear that it's safe to copy files between Win7 and other VM's. I was a bit stressed out over this one due to worry of bit-rot. I'll get back to you when I've tried this out, thanks! -- 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/dff8fb8f-fb54-4b60-8ca3-4ad15d0744ff%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 Sunday, February 4, 2018 at 1:57:26 PM UTC+1, Elias Mårtenson wrote: > On Sunday, 4 February 2018 03:09:41 UTC+8, Yuraeitha wrote: > > > Also it seems like some functions "might (maybe)" work as intended, for > > example > > I can copy files between VM's and Win7, on a Win7 that was installed on > > Qubes > > 3.2., but backup restored on Qubes 4. Others seem like they can do this > > too. > > Also it seems it's a common problem not to be internet in the restored Q3.2- > > Win7, perhaps the code is different in regards to how it ties networking > > with > > Qubes 4? I have no idea about the rest of the mechanics from a users > > perspective though, and most certainly not as a developer as I > > unfortunately > > don't have such skills, I wish I could help more. > > I have tried this, and in my case, the win7 VM crashed hard (with the VM > immediately disappearing with not error message to be seen) after a few > seconds > of use. > > While it was running, things worked fine (i.e. fast graphics updates etc) > which > leads me to believe that the graphics drivers are fine. It does seem to die > as > soon as I open the Explorer window, which somewhat narrows down the set of > potential causes. @Elias I think I encountered this issue too, without error logs it's hard to be sure though, but by the description it sounds a lot like it. Another user in another Qubes 4 Win7 thread somewhere in Qubes-users mail-list, suggested to reduce the page-file for Windows SWAP inside the Windows VM. It worked for him, and when I tried it out, it worked for me too. It's possible this is what you encounter, try reduce the Windows page-file and see if it works? Also if not reducing the page-file, more giving the VM more RAM works too, but it's a lot of wasting resources, especially on low RAM hardware. For example I have to give Win7 4GB RAM when I did not change the page-file in Windows. When it has 3GB or 3.5GB, then it crashes like your description. Once the page file has been reduced, counter-intuitively the RAM can now be 2.5GB without any crash so far. It seems a bit odd since the page-file SWAP should only be related to the drive space, but the relation between host VM allocated RAM, and guest drive SWAP page-file, somehow, indeed seems to be related to each others... I lack the understanding ,but it seems very counter-intuitive to me, yet it still worked. Hopefully this can fix your crash issues. -- 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/200413aa-03c0-41c2-9a11-743af2e274d6%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?
Also it seems like some functions "might (maybe)" work as intended, for example I can copy files between VM's and Win7, on a Win7 that was installed on Qubes 3.2., but backup restored on Qubes 4. Others seem like they can do this too. Also it seems it's a common problem not to be internet in the restored Q3.2-Win7, perhaps the code is different in regards to how it ties networking with Qubes 4? I have no idea about the rest of the mechanics from a users perspective though, and most certainly not as a developer as I unfortunately don't have such skills, I wish I could help more. I just spent a bit of time restoring my windows VM from 3.2, here are a few notes that might be helpful to work around some bugs that you're probably hitting too (I haven't filed any issues yet): - PVH/HVM: in the VM's settings gui, PVH is always displayed whatever the real pref value. -> use qvm-prefs vmname virt_mode to make sure you're really in HVM mode. - Networking: the PV network adapter was stuck at "Identifying" ; pinging an *ip* works but ping a host fails. tcpdump on sys-firewall shows that the requests were sent to the gateway's ip and were rejected. The reason seems to be that in R4.0 VMs are now using the exposed "/qubes-{primary,secondary}-dns" values, while in R3.2 the DNS server was the same as "/qubes-gateway" (see [1]). In my setup, "/qubes-{primary,secondary}-dns" are 10.139.1.{1,2} and /qubes-gateway is 10.137.0.6. DNS requests are rejected because they're sent to 10.137.0.6 instead of 10.139.1.{1,2} workaround 1-> manually set the DNS servers to /qubes-{primary,secondary}-dns ips. Ping and Internet Explorer worked, but the PV adapter was still suck at "identifying" and my Amazon Kindle for PC app complained about finding no network (it seems there's a windows "connectivity" API/flag that some apps use). However you will have to do this each time after boot since Qubes tools will reset the network settings. workaround 2-> in Program Files/Invisible.../Qubes.../bin/..., rename network-setup.exe to network-setup.exe.bkp to prevent Qubes tools from messing with your network settings, and manually set the VM's IP and DNS servers in the PV adapter network setting. Everything should then work OK, the only problem being that you'll have to make sure you keep your network settings synced (esp. the IP when you clone the VM). - Copying to/from the Win VM: works perfectly - you just have to type twice the destination VM (once in Windows, once in Qubes/dom0), since Qubes Tools aren't updated to reflect R4.0 new "way". note: before finding what was causing the connectivity problem I tried to update xen's windows PV drivers [2] but it broke the VM (ie. it wasn't starting anymore) so I had to restore it again. Anyway IIRC R3.2 Qubes Tool's drivers were at the same version as Xen's (8.2), so no need to fiddle with this. I was thinking about posting those steps on qubes-users@ but I don't feel I had done enough testing on my VM yet. I see you're quite active on qubes-users so feel free to redact/post some of my remarks if you think they'll help. [ an unofficial wiki would be a helpful bridge between the MLs and Qubes' official documentation: it's difficult to skim through all the related ML posts and IMO Qubes' official documentation shouldn't include crappy workaround hacks like the ones I've described above ]. [1] https://www.qubes-os.org/doc/vm-interface/ [2] https://www.xenproject.org/developers/teams/windows-pv-drivers.html -- 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/1816f087-cd22-a22f-dbcb-7d633c4e0ee6%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
On Sunday, 4 February 2018 03:09:41 UTC+8, Yuraeitha wrote: > Also it seems like some functions "might (maybe)" work as intended, for > example > I can copy files between VM's and Win7, on a Win7 that was installed on Qubes > 3.2., but backup restored on Qubes 4. Others seem like they can do this too. > Also it seems it's a common problem not to be internet in the restored Q3.2- > Win7, perhaps the code is different in regards to how it ties networking with > Qubes 4? I have no idea about the rest of the mechanics from a users > perspective though, and most certainly not as a developer as I unfortunately > don't have such skills, I wish I could help more. I have tried this, and in my case, the win7 VM crashed hard (with the VM immediately disappearing with not error message to be seen) after a few seconds of use. While it was running, things worked fine (i.e. fast graphics updates etc) which leads me to believe that the graphics drivers are fine. It does seem to die as soon as I open the Explorer window, which somewhat narrows down the set of potential causes. -- 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/82a27836-11e1-4a37-98f5-8d77ba26bfe9%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 Saturday, February 3, 2018 at 2:16:15 PM UTC+1, Elias Mårtenson wrote: > On Saturday, 3 February 2018 12:06:20 UTC+8, Andrew David Wong wrote: > > > As far as I know, Qubes Windows Tools continues to remain on > > indefinite hold. We welcome anyone from the community with the > > requisite skills to take over development (or just pitch in here and > > there). > > I wanted to be that person, and I did take an initial look. However, being an > experienced Unix developer was not much help in figuring out the issues with > the Windows tools. > > Is there some source of information that helps explain what the problem could > be, and where to start looking for it? > > Regards, > Elias @Elias It would be amazing if you can get the needed information and have a second look at it. I'm only speculating here, but could it be possible that the code is more or less the way it's supposed to be, but has just not been tested, verified, and then distributed on Qubes 4? If the precedent for release requirements is the expectation of quality before release, then perhaps the hindrance is just testing and verifying if it works? Also it seems like some functions "might (maybe)" work as intended, for example I can copy files between VM's and Win7, on a Win7 that was installed on Qubes 3.2., but backup restored on Qubes 4. Others seem like they can do this too. Also it seems it's a common problem not to be internet in the restored Q3.2-Win7, perhaps the code is different in regards to how it ties networking with Qubes 4? I have no idea about the rest of the mechanics from a users perspective though, and most certainly not as a developer as I unfortunately don't have such skills, I wish I could help more. -- 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/fac5da5a-a17b-444d-bc6a-7e24956954be%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 Saturday, February 3, 2018 at 5:06:20 AM UTC+1, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2018-02-02 17:19, Yuraeitha wrote: > > > > It seems omeg who has been maintaining Qubes-Windows-Tools the last > > few years, has gone inactive > > He is instead working on other projects for ITL's corporate clients, > so "inactive" is not quite accurate. > > > https://github.com/QubesOS/qubes-installer-qubes-os-windows-tools > > and thus far, it looks like no one else has picked up the project. > > > > Correct. > > > If it is not planned to be done any time soon, then that's alright, > > I can live with that. I'm already immensely grateful for everything > > the Qubes team has done. But it's not so easy for everyone though, > > some people are more heavily reliant on Windows than others for > > certain applications. > > > > This post is NOT a complaint or anything of the sorts, but instead > > a question to settle expectations on the correct path, instead of > > looking every day for a new update, which can be a lot of > > uncertainty or for some people even anxiety and frustrations, when > > on Qubes 4 without a means to get Windows 7 installed. Essentially > > people who need Windows and would love to get Qubes 4, are caught > > in-between without any idea when or even if Windows 7 will be > > supported anytime in the near-term future. > > > > In other words, just knowing it won't be anytime soon is in a way > > also very good news, because it puts expectations in the right > > place instead of uncertainty. Any such news-update on what is going > > on with it and what to expect, would be appreciated. > > > > As far as I know, Qubes Windows Tools continues to remain on > indefinite hold. We welcome anyone from the community with the > requisite skills to take over development (or just pitch in here and > there). > > > Also, I'm not entirely sure regarding the code itself, but it > > should be somewhat close to Qubes 4 in the current > > Qubes-Windows-Tools? For example the Qubes 3.2. Win7 restored from > > backup in Qubes 4, seems to more or less work, somewhat smoothly, > > but not perfect. If so, maybe someone else can help with bringing > > Qubes-Windos-Tools to Qubes 4? Unfortunately I have no coding > > skills of this sort though, otherwise I'd give it a shot. > > > > Sorry, I don't know. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp1NS0ACgkQ203TvDlQ > MDCZYw//X/AlrUieQTF4ebMSab60xahi5erwpQc87Yzvb7WLLYBEnmY19d60M8IT > oOr6p3zroDc+VvwBW4vIcp4S7RUNIDbIyppulW+6eiFunQK8kZGpks+RKfntxwEq > Z8MCFeVNCedn43AGc6DCOLFrSsQVUR0LKVGIcI/Lhoe60zdvoMofnlF2hHRzWqvb > 9UYuu/Kiqyy8RVyNq1LSNJ4/5jIIFDoxk12Wngc3s22OU5/u6I2vlnUHHwDC/X6n > kbWSa8ltdKIOpglWxf34G7G60kdQVLfqw88mFzGUMk02EOeGkErMuG39wzCCGWyA > 0Yp+KWeUaTH7mzUVTHR4G0uuWlFx7IaXUWOSJVmuSjItCQ4s7qbZ8A78ajN1aLYd > JhhVnM8jzDF8zkrAd6Ez+zRVa9im/m1puck3uNb8Ou6VD0FnRWowl6iz0ijRhXsF > A6qgr4jiGqqp3OSvxActu32KbW2ogxrDQThztcJgY1DuhDF/Y6YBHRI9I92udQ6r > +A5OKoIKe3cskntkF5lrSawqVtyD+lxuT00gwwJrolj1ixdHt8ufyezvJxDYZJac > UIu4y95w4H28YoxCY5bmoMIB5ncl4kskKs7qFpNbVHs4d8GsW1NcT2fxNzslGtsV > D7muRf9n/gX3Ui5wNwwjP0gVMD6RrsY4wRdt4Jzk87VVdJIEiXM= > =LLLN > -END PGP SIGNATURE- Thanks Andrew, this was exactly what I was looking for, much appreciated. I'm gonna settle in for a plan B as listed below, although it looks really interesting if Elias will be looking into it. Maybe Marek or someone else with insight into the code can help a little bit to get started? But for the time being, I might try install Qubes 3.2. as a plan B to create some temporary unlicensed clean Win7 Qubes backup's, and see if I can transfer them to various of other Qubes 4 systems. This is mostly needed for my friends though, and I still need to figure out if this is allowed within the use-cases of the Windows 7 license or not, they will use their own licenses. This method is a bit cumberstone if the code inside the Win7 installed on Qubes 3.2. is buggy and creates unreliable issues, like unreliable transfer of data integrity. Hopefully nothing bad will happen. Also need different types of Windows 7 copies for different types of licenses, which is a bit problematic, but not impossible. For now this temporary plan B, this might be a work around to get a new clean Win7 on multiple of different Qubes 4 systems, although a bit cumberstone, and uncertain possibility of data integrity risk. -- 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
Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-02-03 07:16, Elias Mårtenson wrote: > On Saturday, 3 February 2018 12:06:20 UTC+8, Andrew David Wong > wrote: > >> As far as I know, Qubes Windows Tools continues to remain on >> indefinite hold. We welcome anyone from the community with the >> requisite skills to take over development (or just pitch in here >> and there). > > I wanted to be that person, and I did take an initial look. > However, being an experienced Unix developer was not much help in > figuring out the issues with the Windows tools. > > Is there some source of information that helps explain what the > problem could be, and where to start looking for it? > > Regards, Elias > Here's all the relevant documentation I'm aware of: https://www.qubes-os.org/doc/windows-tools-3/ https://www.qubes-os.org/doc/windows-debugging/ Omeg and Marek (CCed) may be able to provide better direction. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp1/ZkACgkQ203TvDlQ MDDnow/9HqNYHCfzwXfRh54thay67YuY6Hf6pMUmomY5i5/ctrHEqsnxrFOA8v5s h6celuDds/IYhs9/E6j9aDi6Xrfa4hTn/YpmcZc8Cijw1hUrmrTHsOeMNqfG2mcW 3TmUhrJ55Ds7GN47MK1haYf630EfzoolCowGs5FHN+YWWnHkdxQlH7szpqb33KiY VGBKJcPM7FI7av6g8Y8Qn7GehIei9CoHDm7N3YLq98pFcfKrQLASrpU4O5S+eLkB MXIMG6FYRqnxwiGPuJ02uLdtM9X421tWX2ViPt+3S+aKfd05mubkh2oPYZBRhB+W ZiQPlK9l2VEL8TtW7YrYrJYZmcJt5Gy/QoZa10IBICwu37NcphixQ2PiO8U0bPz6 0GxuGbQT6hUZnZuquG9kwXHDK4oD2AltFoFj6/W8aslS5B0RjgcQQBcgHWoHVsv4 fgoRVasgFCMgm7lCgrChBszqS223sbbshCMCu6tyUJCfxcfRpak77uVGvQyJ3xQv 1auT7deeSkxyEEdDHNiEl8pD7MhC+0rc2H+2nOgaq3ZGL3OlOx13omaaC9Vhi2hx 7Dr62HPxz64X8nLbuaacAGDLAam4AWK0WtmDFSll7cDz6Sm78HCoNwIHgXh9x3Sj 9aF2XCB7Yr00sDj+wEreb5YB8meNl3R4aBlVNBpZ2ar64OKst30= =uBDG -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/97e78590-fbca-36c3-5b0d-9a3dae0f102d%40qubes-os.org. 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, 3 February 2018 12:06:20 UTC+8, Andrew David Wong wrote: > As far as I know, Qubes Windows Tools continues to remain on > indefinite hold. We welcome anyone from the community with the > requisite skills to take over development (or just pitch in here and > there). I wanted to be that person, and I did take an initial look. However, being an experienced Unix developer was not much help in figuring out the issues with the Windows tools. Is there some source of information that helps explain what the problem could be, and where to start looking for it? Regards, Elias -- 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/982dc0b2-f912-40b0-ab6d-523b788069dc%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: SHA512 On 2018-02-02 17:19, Yuraeitha wrote: > > It seems omeg who has been maintaining Qubes-Windows-Tools the last > few years, has gone inactive He is instead working on other projects for ITL's corporate clients, so "inactive" is not quite accurate. > https://github.com/QubesOS/qubes-installer-qubes-os-windows-tools > and thus far, it looks like no one else has picked up the project. > Correct. > If it is not planned to be done any time soon, then that's alright, > I can live with that. I'm already immensely grateful for everything > the Qubes team has done. But it's not so easy for everyone though, > some people are more heavily reliant on Windows than others for > certain applications. > > This post is NOT a complaint or anything of the sorts, but instead > a question to settle expectations on the correct path, instead of > looking every day for a new update, which can be a lot of > uncertainty or for some people even anxiety and frustrations, when > on Qubes 4 without a means to get Windows 7 installed. Essentially > people who need Windows and would love to get Qubes 4, are caught > in-between without any idea when or even if Windows 7 will be > supported anytime in the near-term future. > > In other words, just knowing it won't be anytime soon is in a way > also very good news, because it puts expectations in the right > place instead of uncertainty. Any such news-update on what is going > on with it and what to expect, would be appreciated. > As far as I know, Qubes Windows Tools continues to remain on indefinite hold. We welcome anyone from the community with the requisite skills to take over development (or just pitch in here and there). > Also, I'm not entirely sure regarding the code itself, but it > should be somewhat close to Qubes 4 in the current > Qubes-Windows-Tools? For example the Qubes 3.2. Win7 restored from > backup in Qubes 4, seems to more or less work, somewhat smoothly, > but not perfect. If so, maybe someone else can help with bringing > Qubes-Windos-Tools to Qubes 4? Unfortunately I have no coding > skills of this sort though, otherwise I'd give it a shot. > Sorry, I don't know. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp1NS0ACgkQ203TvDlQ MDCZYw//X/AlrUieQTF4ebMSab60xahi5erwpQc87Yzvb7WLLYBEnmY19d60M8IT oOr6p3zroDc+VvwBW4vIcp4S7RUNIDbIyppulW+6eiFunQK8kZGpks+RKfntxwEq Z8MCFeVNCedn43AGc6DCOLFrSsQVUR0LKVGIcI/Lhoe60zdvoMofnlF2hHRzWqvb 9UYuu/Kiqyy8RVyNq1LSNJ4/5jIIFDoxk12Wngc3s22OU5/u6I2vlnUHHwDC/X6n kbWSa8ltdKIOpglWxf34G7G60kdQVLfqw88mFzGUMk02EOeGkErMuG39wzCCGWyA 0Yp+KWeUaTH7mzUVTHR4G0uuWlFx7IaXUWOSJVmuSjItCQ4s7qbZ8A78ajN1aLYd JhhVnM8jzDF8zkrAd6Ez+zRVa9im/m1puck3uNb8Ou6VD0FnRWowl6iz0ijRhXsF A6qgr4jiGqqp3OSvxActu32KbW2ogxrDQThztcJgY1DuhDF/Y6YBHRI9I92udQ6r +A5OKoIKe3cskntkF5lrSawqVtyD+lxuT00gwwJrolj1ixdHt8ufyezvJxDYZJac UIu4y95w4H28YoxCY5bmoMIB5ncl4kskKs7qFpNbVHs4d8GsW1NcT2fxNzslGtsV D7muRf9n/gX3Ui5wNwwjP0gVMD6RrsY4wRdt4Jzk87VVdJIEiXM= =LLLN -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/0b5e46bd-cc88-d4f7-9140-ec7727df91a3%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.