Current Windows instructions?

[IX4 Svs]

Hello

The instructions over at https://www.qubes-os.org/doc/hvm/ still say:

==
Using Template-based HVM domains

TODO (Coming in Qubes R2 beta 3).
==

What is the current authoritative source for instructions on building template-based Windows VMs?

Thanks,

Alex

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Here it is:

https://www.qubes-os.org/doc/windows-appvms/

I'll update that other page. Thanks!

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXsm8VAAoJENtN07w5UDAw+fwP+gKt7DpzIWoAPgHcp9j7BJku
+c6pLyshzEoSedI3OrStbViS4P8SxK1fGeTbY2LUCS2DTqkFo/Mb5x1AJNWcDrRa
3XPnC2NEfnKWgSgMmmWS0685qSBTiHTejHh+/8zf8OMOsrejPdcn6KhMZEzbLSq0
+4v88JcuM1XLhTy2H1W4/i39yxD8T0spIF+emMS47a/c9wKztC8cA87TktSTytpI
Hg/ODC2XMjvsxsTMybd6VKTeXgF4MFFAcp7Elbq5u53eFzWyEG1Yg1xoFtXCMROv
We2mVe4mJhzACVuBCPPNMD4k4PHn/lBiG4AX/wCNBucvLe//oLfHNhOjXE2gLK1M
/BdurHQVigXG8+FZsehOdjgHEot1ae48H71In50K+3aMHQpTEEYG6GqGq1T9tHzk
QGKC79p9XXvB/YgkhzVnA4csJ2ksjOBh4R68dICfXvJ2zT8z22kRpokvthDl8WjP
/6qjtvdrF2DwSnHhBQfzEya2pZtZy5Mv1VC/h84GuHxOPtRSC4JEBXh/JmQTYysw
CxQn+24cb+3S0rQhLm68V7c7f6Uv6xS24xzAK/dOVSxKkhu1itgBM3ySZrh8a3mx
P/HBIabCcb6XUsumfuQ4M7Tvaqos3tvJT6AUkDgG3AQQ500u1Mmsuj0MRpXz5ApQ
KSiMwrPVvJfQ/d+wYdZK
=M7Jo
-----END PGP SIGNATURE-----

[Drew White]

On Tuesday, 16 August 2016 11:40:44 UTC+10, Andrew David Wong wrote:
> Here it is:
>
> https://www.qubes-os.org/doc/windows-appvms/
>
> I'll update that other page. Thanks!
>

I see the instructions, but has the seamless issues been resolved yet?
Or do they still remain?

Will the tools be working any time soon?

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-16 00:24, Drew White wrote:
> On Tuesday, 16 August 2016 11:40:44 UTC+10, Andrew David Wong wrote:
>> Here it is:
>>
>> https://www.qubes-os.org/doc/windows-appvms/
>>
>> I'll update that other page. Thanks!
>>
>
> I see the instructions, but has the seamless issues been resolved yet? Or
> do they still remain?
>

Are you referring to this issue?

https://github.com/QubesOS/qubes-issues/issues/1896

If so, it looks like it was closed recently, so the patch should be available
for testing soon.

> Will the tools be working any time soon?
>

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXszsaAAoJENtN07w5UDAwNF0QAJdblELCYGhiCyoUp4VGIt5v
pt0nprLLyPozcuAbLTuUTNftBd+s/8O0jszEYDixdIJuO0IBeSALk2xLzIvB3rI/
RAxNrptMabaEaK9/S4tnVFmKvQpogbLx1GotmWuk5G+veDUjXk4WhiCzeuY/XwVA
60DEj1JpBbilASsoKNkPpHLeD1g4IMcv/oiZ54DvzokhCFb1L99Ob61Aeyu/1m3j
oz2e5eqvUxqaM1BkI3ZqdXMAyhGkqHsrlV0uO5gHJmaIJs/erSb6QCcTTocrH4xr
egtQgZFJ0fDYgQZp/mFVfLJgb6BH7GyX0O7HE0Qks+3d0VClmZFb/7ZiC8pFul9u
yx+CI7oOrtk02LbBxzfrZymlDFzfPocyS0l1OrEM55PcGIBbGqVqf9kPXma9a3Ft
PKM8Z6d9DzZhijSkl85noenzCR5ls7B363pYPeZEY1OFbTlorTiGE3A5y/Vi07r+
l+RyGbyvrUuG4Uv6xaxE6ONSZMHiW497Qiz3LdeLeY6tQrEg+yxh8v9VeXXQc8EZ
t+UaAbP34FFe4saUBubuCBVVL0aAZf/iF0GJC1JNJBF+G0NslBBzhAKW1qcUirrY
Rc3mMFTZBG69mf6s9su2iwo+oNid16rIwlETa6zRsmduw6Src4VLeScaKkE1t1SP
CRrNe+TVljQcTUzMGSaj
=sF0Q
-----END PGP SIGNATURE-----

[Drew White]

On Wednesday, 17 August 2016 02:11:15 UTC+10, Andrew David Wong wrote:
> Are you referring to this issue?
>
> https://github.com/QubesOS/qubes-issues/issues/1896
>
> If so, it looks like it was closed recently, so the patch should be available
> for testing soon.
>
> > Will the tools be working any time soon?
> >
>

Yes, that is one of the issues that I'm talking about.

I had thought if it was closed it means that there was a patch that was tested and fully working. Because then that means that the issue is no longer an issue and can then be closed.

Since I have not seen a patch for it and I'm still at the latest version of Windows Tools and they are still broken as they have been since Qubes 2, I was thinking the ticket should still be open.

I will give it a bit of time for it to be released to the public, since it must just be a private thing, and then I'll make the issue open again if the issue remains.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-08-16 17:18, Drew White wrote:
> On Wednesday, 17 August 2016 02:11:15 UTC+10, Andrew David Wong wrote:
>> Are you referring to this issue?
>>
>> https://github.com/QubesOS/qubes-issues/issues/1896
>>
>> If so, it looks like it was closed recently, so the patch should be
>> available for testing soon.
>>
>>> Will the tools be working any time soon?
>>>
>>
>
> Yes, that is one of the issues that I'm talking about.
>
> I had thought if it was closed it means that there was a patch that was
> tested and fully working. Because then that means that the issue is no
> longer an issue and can then be closed.
>
> Since I have not seen a patch for it and I'm still at the latest version of
> Windows Tools and they are still broken as they have been since Qubes 2, I
> was thinking the ticket should still be open.
>

The way we handle issues is typically and roughly as follows: Once a commit that
purports to fix an issue is committed, the issue is closed by that commit. The
code in that commit then goes to the appropriate testing repo, where it stays
for a while (while it's being tested) before eventually moving to the stable
repo, where stable it gets installed by the majority of live systems as part of
an update or new release. So, there can be a considerable lag time between the
time when an issue is closed on GitHub and and the time when the code actually
starts running on live, stable end user systems.

> I will give it a bit of time for it to be released to the public, since it
> must just be a private thing, and then I'll make the issue open again if
> the issue remains.
>

So, as Marek said, in this particular case, the updated package has already been
uploaded to the testing repo for 3.2. If you're on R3.2, and if you're willing
to test this package (and you're certainly under no obligation to do so), then
you can do so now by following the instructions here (under "Testing
repositories"):

https://www.qubes-os.org/doc/software-update-dom0/#tocAnchor-1-1-3

I believe the correct repo is current-testing. If so, your command would be:

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing <package>

If this is, indeed, the right place, then you can see a list of available
packages here (or from the command line):

http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/

The only packages containing the word "windows" are different versions of
qubes-windows-tools, so I gather this is what you want. If that's correct,
then the command would be:

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing \
qubes-windows-tools

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXs7MlAAoJENtN07w5UDAw8QoP/3e/kxbqPng22O7IWnJ3X9i9
Nv8O5+V5e4C7gFlTAe+25nYZMZ1KhFzk1z95XWGbQtolhBYoIrOclbwo8Ef1HzlT
SG1xpMEEhw2ZKh71QDG7SsYdAXHAR1n0Zoij288xYxtfHh4FrdjYufVGQQd+QJ81
4A6u3Dd/+ApOZRVBUXzBEHmmgFCIPY+xOmSPe35sHxzBTEHhlVWP7knkVy6HkoY6
wWl12agqt/bWUShZsEmKuR7XHz3EF7BKQHkesKVjdnA8EIv1nrDdLoy/f7sRFoU5
3jl/67xyMjznhU/5fQODEEBSpH466+WrdlKScOUjcAO18QWU7PbQijeP0tpXwhSK
iqEOevM/uECoFTIeFYI5xMlgFImJ1BFtveBX3bsd78aOQgkkkC9E/+4BQmBwcXnG
HVXeEyci8p7pJNzu0pNmOiqEOza5UeZmcZ9OXqv6Fm6LrsLOmi5B4ZX3UkhMgg79
355JFTnzx2kHf3zz2HdOqfBy+qBXV/d4ZvGETJVfd5LU1VzIzgNpx432rjr8BTLJ
wffpMuc47Nr9t4tyozJWeIwyeZQrArd3aYTLPDwOt8G+N/QrRzJK8B6IZc7wBYiz
j+9hN4kFwr6ypJ8/rKgcqZlsmaJQB0E4WX4GjOD8fzkVTuD5zX0bFAhpdCPvd2bP
VQpxNU8WQCu2voAM+BFQ
=p7qg
-----END PGP SIGNATURE-----

[3n7r...@gmail.com]

On Wednesday, August 17, 2016 at 12:43:27 AM UTC, Andrew David Wong wrote:
>
> So, as Marek said, in this particular case, the updated package has already been
> uploaded to the testing repo for 3.2. If you're on R3.2, and if you're willing
> to test this package (and you're certainly under no obligation to do so), then
> you can do so now by following the instructions here (under "Testing
> repositories"):
>
> https://www.qubes-os.org/doc/software-update-dom0/#tocAnchor-1-1-3
>
> I believe the correct repo is current-testing. If so, your command would be:
>
> $ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing <package>
>
> If this is, indeed, the right place, then you can see a list of available
> packages here (or from the command line):
>
> http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/
>
> The only packages containing the word "windows" are different versions of
> qubes-windows-tools, so I gather this is what you want. If that's correct,
> then the command would be:
>
> $ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing \
> qubes-windows-tools
>

Andrew, I don't see qubes-windows-tools 3.2.x in the R3.1-current-testing repo. Is that an oversight or is QWT 3.04 the last update for R3.1? I wouldn't expect R3.1 to get any new features but if QWT3.2 is improving stability, it'd be great to get it if possible.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

That's a good question. I can confirm what you're seeing (in terms
of what's available in the Qubes repos), but I'm not sure whether
it's intended.

Rafał, is QWT 3.2 supposed to be available in the R3.1 repo, or is
it only for R3.2?

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJX1KyYAAoJENtN07w5UDAwBIMP/0zlqkVIlAUKVdbZFN7onrHd
XYZeKQYoCqm84CkgF2Uzgwq5FI025/au4zYgKnE4ISnBnLJXlXWal4Y9MA8wL0Yk
rDmcBEcC8i1fLvyTYyqszJTXZeY1seG8fHfKz5DWTaegJD9topHBnJpaD3+oZnjz
UsD7O3c3zefujgXABocy9cZG9HwtbK+SHbMVSVajgwpRhqeqAo+Ztt1ZN0aNj64n
IABfilK6fFYdlZX+8GEw+oY5oahb0tvs5GUzJ+Fv1L3TXnpZw6HwjrF9B84nrpvh
VpnoMkeh4tEZWoE2wCrv0bJVCXbWqwhZddAxx1625AJivXSglrQglyBVKs78nQ0P
a9GxJyYZewFdNdFkoJ/pin/gFVSzimlqRShg/kJsfELFWxoO5iEj+xUcM0ozg5SK
Azwsb2EGE83n/yitBrcBYek+9EmHdQiSYAI2OdIXwg/EDuUS3UarulKMkvcTCMDx
yKoO/KDNFz8v2x63CVdWsijulT3hZeitqIoWomuzdt3Bj534x6pAIdv/BcMNnon/
sjwlefXsX/UMCTIwkQAwjAZGfQeu2xulAghis0sK9bOYfe7tVOmK02tO8wPf02My
LqIHnQebJyEtJrgi8mMNIIcTvj5zxCqfITG6OEbj4HN6sJ087vqQBIzknkf/RnLA
92YN6+sSnDkzIGCaDvsB
=/Vvj
-----END PGP SIGNATURE-----

[Rafał Wojdyła]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

It should be AFAIK. Marek should know more as he's the one uploading
the packages.

- --
Rafał Wojdyła
Qubes Windows Tools developer
https://qubes-os.org/
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJX1UCAAAoJEIWi9rB2GrW7kR8IAI2aHElf3GDAfoGbPSPqMqZH
invFvb3BM0ttxfOgQefTjQPfDyMXYDmmeQICQIaRrKR6CcrqRKlt1gpXMRLuyVdx
dy9Zdjh9Rbw79s1lP2ws9DfGYQbUok0Vi8+wDeP8rXEVkd9v5g9SXkgO6M+A8l8y
aHksxCcTiuw3Qh6N+d3If6NjJf2fpIUyT18yKeeXZkW3jLe/iBgoCUGeONmoVppR
/VpSaHFWTG0UPapeF9Pac/OIC0jwlp8kFl4GaufI7vUGYZZAKh71RxiGqz+kL8FK
s+5NHwfmm58HzasfzvCbQHFFlKp9ng3oWLwxcCg74iKc3eCia9LkiupP+HtU+9g=
=D6mJ
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I haven't tested this version on 3.1, but I think it should work. Just
uploaded to current-testing.

- --
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-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX1U5lAAoJENuP0xzK19cs/mYH/2hOJ9mMPieMZYkTkknAVTKE
qieDxkbmcC920Kv5Rl52EOguitY8ObG2cXIs970oflMPfLii7EVXex/WYERYx1VG
VF6Cd7+4YW9EQk4Vt2mX7ez1swJn85WgG2CO4C37nqSsK/5JTeSKVJ4Hty+gqntG
p4upgIlbTPSdC/Vfkopo4Bklo1CzGJKmLsHCD7uZvUJiJ05KEdl5BSBzn6KxrbeL
104nJ7/NHz9anzf9uz+QQWhu0iDTTZfd65WuKLsOqPfomIBuB2gGUdfOzPqcziD9
fcJFbuWpoDWq3VeEyaDlKlMgGSw7aWhNFK1cExglnKyhiHudX4lHfr2hRuz40uA=
=EOnE
-----END PGP SIGNATURE-----