Qubes Windows Tools for R3

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

We've just released first testable version of Qubes Windows Tools for
R3. This should still be considered highly experimental, so do not use
it for anything serious (or at least make frequent backups).
The package can be installed by issuing in dom0:
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable
qubes-windows-tools
Then proceed as usual:
https://www.qubes-os.org/doc/WindowsAppVms/#installing-qubes-support-tools-in-windows-7-vms

Known issues includes:
- there is no way to upgrade VM migrated from R2, yet
- template-based VMs are not yet supported (more precisely: user
profile is not migrated to a VM private disk, so changes in AppVM
will be lost after restart)
- in some cases VM crashes (BSOD) during shutdown
- application menu generation is slow
- application icons are not properly retrieved

It might be also a good idea to install updates from current-testing
repository, especially qubes-core-dom0-3.0.15, which contains multiple
fixes for HVM support.

- --
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 v1

iQEcBAEBAgAGBQJVk3/9AAoJENuP0xzK19csCd8IAIe8Qh6Q6TiCmHxIwVKkAmcY
uLSpt9hEQQrmkiZuMaUpw1mWxFO3AW9y5cHOpnkzm19TkX8ejDflGzw/5s4/wE7j
mVDORVs6LLXnvw1yzlhSNjlFK34KkiqPLgJWllZxWiOePR9qxaBcoCYnViEY7ZaF
ywuaGEXC6/ySMysFTT01qnCtfPTARwkxme+DbQBGS8ytUBDXzU3QxXabOTNYCv5o
qKauVSIHsT7RLHif8ZT/v1ZFnFl6pjj/91JZ0WjwSZ2qY+rNKas6pj0x+Ro4hO8C
ijBEhYSWWuoggtU1ZHpCs10poHKSWzOIqIZQ6a0QUKf3kQ48jlUuLi7ebqGxNX8=
=dKpG
-----END PGP SIGNATURE-----

[Rafał Wojdyła]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2015-07-01 07:51, Marek Marczykowski-Górecki wrote:
> Hi all,
>
> We've just released first testable version of Qubes Windows Tools
> for R3. This should still be considered highly experimental, so do
> not use it for anything serious (or at least make frequent
> backups). The package can be installed by issuing in dom0: sudo
> qubes-dom0-update --enablerepo=qubes-dom0-unstable
> qubes-windows-tools Then proceed as usual:
> https://www.qubes-os.org/doc/WindowsAppVms/#installing-qubes-support-t
ools-in-windows-7-vms
>
> Known issues includes: - there is no way to upgrade VM migrated
> from R2, yet - template-based VMs are not yet supported (more
> precisely: user profile is not migrated to a VM private disk, so
> changes in AppVM will be lost after restart) - in some cases VM
> crashes (BSOD) during shutdown - application menu generation is
> slow - application icons are not properly retrieved
>
> It might be also a good idea to install updates from
> current-testing repository, especially qubes-core-dom0-3.0.15,
> which contains multiple fixes for HVM support.
>

If you encounter any BSODs I'd like to see the memory.dmp file from
Windows as well as Xen logs (/var/log/xen/console/guest-* in dom0).

Currently UAC is not disabled by the installer since the gui agent can
handle elevation prompts. As always, installing some VNC server in the
VM might be a good idea in case the gui agent fails badly.

There is one annoying issue with the gui agent: if you don't have
autologon enabled and seamless mode is on, sometimes the logon screen
is displayed as an override-redirect popup (a window that blocks other
windows) and keyboard input doesn't work for it. In such case use
Windows on-screen keyboard for password input (accessibility icon on
the lower left). I'll try to fix this pretty soon but it highlights a
need for some dom0 mechanism to get rid of such (potentially
malicious) windows (independent of current dom0 window manager).

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

iQEcBAEBAgAGBQJVk8bpAAoJEIWi9rB2GrW7nZMH/RdyPOClXLxss36MLf5sa1LY
fSTzZL5Ai9OzeCIL8tZH8VY+SsnCL7+N1rPsLZh6G+sR8FOEbJyKlxDY4PJgtAJL
vR07eMNSS58lPevK6QFvQ497tYXS4OZOJDIy3UYRL1VgSMCrbMovMeKojZcRloOC
sqHjzv59qHUSjWFv5aGTyAllHQXKjGZRUkL5hQuD/UPgBM4gAGdIPITVpyl+YX5D
pwA75BOQe4SCdrBbTQmLBgf/aKw8rx078U9jYukP0UH6gkUkAUMS0pNFEcAy8isZ
a4qmxRCW+fDsoccwZFLT7rYxS3MDx4Szn8v8+iCcTzdLiAbJH+5Bzydoa3c62ks=
=GSeu
-----END PGP SIGNATURE-----

[Vít Šesták]

Is it really pushed to the R3's repository?

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable qubes-windows-tools
2015-07-01T19:17:11+0000
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running command on VM: 'sys-firewall'...
Loaded plugins: langpacks, post-transaction-actions, yum-qubes-hooks
No package qubes-windows-tools available.
Error: Nothing to do


$ yum search windows
======================================= N/S matched: windows =======================================
libwmf-lite.x86_64 : Windows Metafile parser library

  Name and summary matches only, use "search all" for everything.

Regards,
Vít Šesták 'v6ak'

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Jul 01, 2015 at 12:33:46PM -0700, Vít Šesták wrote:
> Is it really pushed to the R3's repository?
>
> $ sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable
> qubes-windows-tools
> 2015-07-01T19:17:11+0000
> Using sys-firewall as UpdateVM to download updates for Dom0; this may take
> some time...
> Running command on VM: 'sys-firewall'...
> Loaded plugins: langpacks, post-transaction-actions, yum-qubes-hooks
> No package qubes-windows-tools available.
> Error: Nothing to do

Now it is...

- --
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 v1

iQEcBAEBAgAGBQJVlFgVAAoJENuP0xzK19csTkAH/jusk2YTJ4g9HXSd+hyNPY9M
JCfsUIajJYI2YiAvRVJQqgakMr2aX76QkmfBkZU+8VHnOxSVkHgnKjYOJEnDSmTh
VLpdl1lX0f3Jzz5dM5ucYPMK7xfRqNAHokdP9zn9SssrhW0HxFZJgKgfo3pP9xCB
I+WSNXVPH9VPktLcDqoBsc8QXcLxQMlktf6hPJqhtnnpABkKSt3NaWFq9gawbmBO
JGUJ9dl7ou7+znwxcEwZfA/UcX4DLQpXxSw67nvwDevLwBvX+tCbQF5UCcuhCumG
5RUamvauqABsyr0N0K4mxGhmTDo/PGP+t3fgLMF8Bh2tUmy2xkA0T8jTCQDkfOI=
=1a07
-----END PGP SIGNATURE-----

[7v5w7go9ub0o]

On 07/01/2015 01:51 AM, Marek Marczykowski-GĂłrecki wrote:
>
> Known issues includes:
> - there is no way to upgrade VM migrated from R2, yet
>

IIUC, the best way to "migrate" (?) a Windows HVM is to:

1. Start up R2; Remove Qubes R2 drivers/toolkit from Windows HVMs using
a forthcoming R2 "uninstall drivers" tool
2. Backup WVM in R2
3. Fresh install Qubes R3; Restore WVM backup into Qubes R3; install
Qubes R3 drivers/toolkit.

Questions:

Has the R2 "uninstall Qubes Windows drivers/toolkit" tool been released
yet?

How could I determine this without writing to the mailing list?

[Vít Šesták]

My first experience with that:

1. I first tried to install it on an IEVM (see https://modern.ie ), but those are only 32b and thus unsupported by QWT at the moment. (The README.txt suggests that there are 32b drivers, though.) But OK, maybe it is better to have stable 64b drivers first. OK, I'll install it on my Windows 7 Home Premium x64 VM.
2. Nice license :)
3. Installation takes very long time (note that I have Windows VM on HDD), maybe 20 minutes. For some time, there is no visible HDD activity and it stays on the same progress level, so it looks like frozen, but it is not. Installation finishes after some time.
4. After reboot, some drivers are installed and I have no network access. But I am told to reboot. OK.
5. After next reboot, I still have no network access :( I get no IP address at all.
6. I also have no Qubes tools working, namely both qrexec and guiagent are told they aren't installed.

Maybe qubes-core-dom0-3.0.15 or dom0 reboot will fix it, I will try it later. But I am not sure if I will have a time for that in this/next week.

Regards,
Vít Šesták 'v6ak'

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Jul 01, 2015 at 06:23:07PM -0700, Drew White wrote:
> Hi Marek,
>
> Bit of an issue with the Windows tools installation...
>
> --- Alternate Click VM
> --- Start VM for Window Tools installation
> ----- Error starting VM 'Win7x64': internal error: libxenlight failed to
> create a new domain 'Win7x64'.
>
> I can start the VM normally, but not that way.
> Have downloaded and installed the tools as per instructions.
>
> There is no log in the location in question for that machine.

Check /var/log/libvirt/libxl/Win7x64.log.

- --
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 v1

iQEcBAEBAgAGBQJVlPjWAAoJENuP0xzK19cs2i0IAI93u6GoNPnL05DPc/cqagYI
uhY36I6jRJWtxQhmW5Xkri/O7/z9u9uU6J8G9eCmzSrriIsHnNNISJfDjGHpSYgo
yJbrryVLR4hr5q6CzhKXiskHY8DZfrqkfgj5R3HiQn1ppQthpe2h1J0QV1gw3sJl
0gsCNg6MChki2XN66L8clfEA3o+EIuEBYQK4sIKlt5sIXCIerT7CluNHZWT6gV40
SQtE9Itop2AJJcbHXdd/tTITHQTCLlmmLG+y+U+ESvggIhSV3mXaw08CK6w+uMJF
/HoOgIw9xFv1EU9TFPAN7dkbV3evYUFyM4geoammkwpeWagfY/NoqIWIB9B6tHo=
=wgDN
-----END PGP SIGNATURE-----

[Vít Šesták]

After installing the new version of qubes-core-dom0 (current-testing) and reboot, the agent partially works, but rather randomly:
* I got list of applications to the start menu.
* I can get no GUI no matter if debug mode is on or off.
* I sometimes can use qvm-run -p <vm-name> cmd.
* Networking does not seem to work now. I got some autoconfiguration IPv4 and Link-local IPv6 address, but I am unable to access the Internet (empty lines removed):
C:\Windows\system32>tracert 8.8.8.8
tracert 8.8.8.8
Tracing route to 8.8.8.8 over a maximum of 30 hops
  1  Transmit error: code 1231.
Trace complete.
* When I try to shut down the WinWM, I sometimes get the following message:
The GUI agent that runs in the VM 'ysoft-win' implements outdated protocol (0:0), and must be updated.
To start and access the VM or template without GUI virtualization, use the following commands:
qvm-start --no-guid vmname
sudo xl console vmname
* I got one a very strange error condition:
1. I run qvm-start -p wmname tasklist
2. I run qvm-start -p wmname cmd
3. I performed several commands there with large output.
4. I pressed Ctrl+C, which killed the cmd.
5. I run qvm-start -p wmname cmd again, but I got some output from tasklist. Even stranger, the output was not red, but while (the default foreground color). This looks like a bug in dom0's part, as a bug in AppVM's part should not cause the text to be white.

Maybe the random behavior is caused by timeout. I'll enlarge the timeout.

Regards,
Vít Šesták 'v6ak'

[Rafał Wojdyła]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2015-07-02 16:04, Vít Šesták wrote:
> After installing the new version of qubes-core-dom0
> (current-testing) and reboot, the agent partially works, but rather
> randomly: * I got list of applications to the start menu. * I can
> get no GUI no matter if debug mode is on or off. * I sometimes can
> use qvm-run -p <vm-name> cmd.

I've been seeing strange behaviour today with the build from the qubes
repo. Check your /var/log/xen/console/hypervisor.log for errors like
these:
(XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 6, error -22

> * Networking does not seem to work now. I got some
> autoconfiguration IPv4 and Link-local IPv6 address, but I am unable
> to access the Internet (empty lines removed):
> C:\Windows\system32>tracert 8.8.8.8 tracert 8.8.8.8 Tracing route
> to 8.8.8.8 over a maximum of 30 hops 1 Transmit error: code 1231.
> Trace complete.

Yes, this is caused by different Xen network interface name, for now
you can set the IP/GW manually.

> * When I try to shut down the WinWM, I sometimes get the following
> message: The GUI agent that runs in the VM 'ysoft-win' implements
> outdated protocol (0:0), and must be updated. To start and access
> the VM or template without GUI virtualization, use the following
> commands: qvm-start --no-guid vmname sudo xl console vmname * I got
> one a very strange error condition: 1. I run qvm-start -p wmname
> tasklist 2. I run qvm-start -p wmname cmd 3. I performed several
> commands there with large output. 4. I pressed Ctrl+C, which killed
> the cmd. 5. I run qvm-start -p wmname cmd again, but I got some
> output from tasklist. Even stranger, the output was not red, but
> while (the default foreground color). This looks like a bug in
> dom0's part, as a bug in AppVM's part should not cause the text to
> be white.
>
> Maybe the random behavior is caused by timeout. I'll enlarge the
> timeout.
>

It seems that currently if the qrexec_timeout expires you need to
manually start gui daemon in dom0.

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

iQEcBAEBAgAGBQJVlWoLAAoJEIWi9rB2GrW7iQMH/iwEH8njrl132BR1A1q4i3Vt
T6xj/1vZikj68RznO2TNSWLJJFSejQg9MqkifPom5jqTTNvqGm/JvcNkmMUJtnng
Co2s+wBtdKXukwM7Nh4SE5LrGOPWQLr2qdtcs80ygLsclv8rG9pYLsv0vx3cOkI9
v7MrP7FV0dfsFIkc/k41swxODhy8HQVRhWKnYv4ntaTglgKqkiw9zf1wCpPT8iMf
agvNAku1C+AH8LBbHMqDy05csILPA6N8v2dB8LjzYj0jSUtgi16+h/qfy8kb3A7Q
6dATHteGOGHjTInqBNczukGe4TV8pijhXIy8nA6whSBH08Yz8ouma5L/nVnbxis=
=Cp3W
-----END PGP SIGNATURE-----

[Vít Šesták]

OK, I've configured the network. Someone might find that useful:

1. Run in dom0: qvm-run -p -u SYSTEM windowsVM cmd
2. Then, you can type the following comand: netsh interface ip set address name="Local Area Connection 2" static 10.137.XXX.YYY 255.255.255.255 10.137.XXX.1
You can get the VM IP in the Qubes VM Manager.

So, networking works for now, but GUI does not. In the VM's GUID log, there is only:

Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128

qrexec log:
Rpc allowed: ysoft-win dom0 qubes.NotifyTools

guest-VMNAME.log: nothing

guest-VMNAME-dm.log: https://gist.github.com/v6ak/a935e6ec6c6f6c0f3cc9

Maybe I should try removing the recent tuning of video resolution.

Regards,
Vít Šesták

[Vít Šesták]

Quick workaround for a non-working GUI: set guiagent_installed to false. I have to do that repeatedly, as a successful boot sets it back to true. Part of the inte-VM communication seems to work (e.g. guiagent is always turned on), while some other partially works (qvm-run sometimes works and sometimes hangs) and some completely don't work for me (GUI through guiagent).

The netsh-based workaround for network does the trick until a reboot, but I have a batch file for that.

Regards,
Vít Šesták 'v6ak'

[Vít Šesták]

Sorry for split posting, but I've found something more:

1. When I started Windows with disabled guiagent and then used qvm-run on that VM from dom0, it tried to start the guiagent and it caused a BSOD. Likely a driver's fault. Rafał, can I send you the log files privately? Where is the memory.dmp located?

2. There is probably some bug in dom0's counterpart (GUID?). When guiagent_installed is true, but seamless_gui_mode is false, then it should IMHO open a virtual screen (before any OS boot) as usual, but it doesn't.

Regards,
Vít Šesták 'v6ak'

[Rafał Wojdyła]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2015-07-03 07:44, Vít Šesták wrote:
> Sorry for split posting, but I've found something more:
>
> 1. When I started Windows with disabled guiagent and then used
> qvm-run on that VM from dom0, it tried to start the guiagent and it
> caused a BSOD. Likely a driver's fault. Rafał, can I send you the
> log files privately? Where is the memory.dmp located?
>

Yes. It's usually in c:\windows. Logs from dom0 would also be nice
(/var/log/xen/console/guest-*-dm.log).

> 2. There is probably some bug in dom0's counterpart (GUID?). When
> guiagent_installed is true, but seamless_gui_mode is false, then
> it should IMHO open a virtual screen (before any OS boot) as usual,
> but it doesn't.

Did you try qvm-start --debug vmname? That should always show the
fullscreen gui from stubdomain.

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

iQEcBAEBAgAGBQJVll2KAAoJEIWi9rB2GrW7qQkH/1No+gS578B7yptEKU01sGcL
u8YdDp3qae7n8T+6zw/Y1vEpEmT+YINpEa+y/eTNuOXz+HgB3P+cahrR/KqdKkCS
pdMLJxGWPUAhb2jDqwp/aQG2ByiLeti23Vf5yeIGxoz/B7vGu2Kf+RIX6ywJJleP
CImFiF2cFkQnjbgjHCv+NWbMyecMR9yl/+pYBq+D8lkHY9X2wYDGLb1xxoU+vnZV
GcPc/5foGt39ItBt5gJPy3kYBzR5dV0uWPW42UNvqK5ggjklbL4LNUSK4dioORe8
G+Fad1GikQHImjEv21r9tK2AFIrG+M4WsOLCeJNd8z6D/sfW11tKoMeb39/sS+A=
=npmu
-----END PGP SIGNATURE-----

[Jeremias E.]

Hello,

what is the command for installing: qubes-core-dom0-3.0.15?
Or in which repo is the package?

Best regards
  J. Eppler

[Marek Marczykowski-Górecki]

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

On Tue, Jul 14, 2015 at 08:54:58AM -0700, Jeremias E. wrote:
> Hello,
>
> what is the command for installing: qubes-core-dom0-3.0.15?
> Or in which repo is the package?

It is currently in testing repository (actually there is 3.0.17). You
can install it with:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
qubes-core-dom0

- --
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 v1

iQEcBAEBCAAGBQJVpUUdAAoJENuP0xzK19csrXEH/0JYmCSmXuRc/l6wkHuA+ISj
K8jxGreR9MI/j39+iLQdTrR0juxn/l2mXy9h+RGFHFbOJkU+URcPPArforJDNQ5/
6PXzjsPplYbBIlQzmYXN0GvtdqMcD/3bTjYera40C5r2hmCjUNf8oV7xlf8kHR+L
fdgQoS6cEnYhWVE9A/9PHHnP3u0ETsz4kt9gvRqgnsrhV2au8Yt1bvZdT7pIssTL
WOtaZvNUy8XHSmxTz2528/Z9q0cbdKkUaLsOonRWq46LhMRPZsUExQS5S96eVrb5
zKBhsTWR6doLX+cswrEQX48nuGNHQs9nHJF8yWJyrmDKpDqn+CIt9feyHionpgA=
=QJ4L
-----END PGP SIGNATURE-----

[Vít Šesták]

I am sorry for the delay, but I was offline for some time.

I can't find the memory.dmp :(

C:\Windows>dir /s *.dmp
 Volume in drive C has no label
 Volume Serial Number is ****-****
File Not Found

I have Windows 7 Home Premium SP1 x64.

Regards,
Vít Šesták 'v6ak'

[Rafał Wojdyła]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2015-07-14 22:58, Vít Šesták wrote:
> I am sorry for the delay, but I was offline for some time.
>
> I can't find the memory.dmp :(
>
> C:\Windows>dir /s *.dmp Volume in drive C has no label Volume
> Serial Number is ****-**** File Not Found
>
> I have Windows 7 Home Premium SP1 x64.
>
> Regards, Vít Šesták 'v6ak'
>

No problem, I was able to fix the issue in the meantime :)

>
> On Friday, July 3, 2015 at 12:01:52 PM UTC+2, omeg wrote:
>
> On 2015-07-03 07:44, Vít Šesták wrote:
>> Sorry for split posting, but I've found something more:
>
>> 1. When I started Windows with disabled guiagent and then used
>> qvm-run on that VM from dom0, it tried to start the guiagent and
>> it caused a BSOD. Likely a driver's fault. Rafał, can I send you
>> the log files privately? Where is the memory.dmp located?
>
> Yes. It's usually in c:\windows. Logs from dom0 would also be nice
> (/var/log/xen/console/guest-*-dm.log).
>
>> 2. There is probably some bug in dom0's counterpart (GUID?).
>> When guiagent_installed is true, but seamless_gui_mode is false,
>> then it should IMHO open a virtual screen (before any OS boot) as
>> usual, but it doesn't.
> Did you try qvm-start --debug vmname? That should always show the
> fullscreen gui from stubdomain.
>

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

iQEcBAEBAgAGBQJVpZpXAAoJEIWi9rB2GrW7MP8H/1kce7zzgoGo11teNwNBCrCB
Jo/gxF+g7rKCV1QkbnhzTYIztooKZQ+atWHNIErWTcwxRN8m7MhhXjMuWXrvO12v
HTEANl04io/8ZpV3x5Z9z3BabM+65XEsmvkL8jZN9x72UR0UmBp68QqzkGZn6yc4
nj6gaN7eeLkddCY4kCPdzGrmCUMQcA9UpU77+6m6eTt4zrZV0bQ6KkiXIUcmPsJN
/DA1gp1QZxbZSfvb1XKBD2oQJ8RULfubYAVOlX/++SD5LHYNU4DG1xr08QdC8vNp
tjnXz9EvRjycuzf/9dFgC3GP+yEFS1r/4ab0XYX8sG3/F2g6rlZQS76ByjFnBE4=
=QMBg
-----END PGP SIGNATURE-----

[7v5w7go9ub0o]

On 07/14/2015 07:25 PM, Rafał Wojdyła wrote:

<snip thread hijack>

> No problem, I was able to fix the issue in the meantime :)
>

> - -- Rafał Wojdyła Qubes Tools for Windows developer
> https://www.qubes-os.org/

Rafał, at one time you were going to devise software to remove Windows
tools/drivers from R2 Win HVMs, before backing them up and restoring
them in fresh R3 installations.

Is that still the plan?

[Rafał Wojdyła]

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

That is indeed the plan. I need to fix one more issue that popped up
in qrexec v3 but after that I'll be preparing the R2->R3 migration tool.

- --
Rafał Wojdyła
Qubes Tools for Windows developer
https://www.qubes-os.org/

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJVpo6WAAoJEIWi9rB2GrW7+qMIALS38tsOpcjnuW+WqvqQl+eo
40EATPHwBwqwRyEoMY5t5QoglRy1NHXcFJ5j5uo2nOTgzUvjcz7wA82czL4/+/0e
pGrYxohD+hEKx17yfN+PzfZSMEgrznNcFpGx9vSdBqEOn1rVKDCpfFY6E6E+G0Ji
EMzmQGHAtqrnZvI1dGbRdi0gkTHfHU+lPP1ZBMuqbaRLNU1x7RJBgH/0+7CgT2Ra
Bpni5IX+WaVd4FP23pUF65bTFv48BhYdJifCuMHyxleNwT9G/vJxAmCsif4xWW2q
ILf9uPiz9N+h3ocPFfKeblS33qezeINK7/B+6UHmCbMvmDSOOweTxI1YfXRH3dQ=
=PLHF
-----END PGP SIGNATURE-----

[Vít Šesták]

On Wednesday, July 15, 2015 at 1:25:16 AM UTC+2, omeg wrote:

No problem, I was able to fix the issue in the meantime :)

Great! I'll wait for next public release…

[Rafał Wojdyła]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2015-07-22 16:47, tonisn...@gmail.com wrote:
> After installing the windows tools, the vm doesnt boot to gui
> anymore. qrexec_installed/guiagent_installed/seamless_gui_mode are
> still false and after setting them to true and trying to start a
> program in the VM I get:
>
> qvm-run -a win7-2 cmd.exe Running command on VM: 'win7-2'...
> Starting the VM 'win7-2'... --> Loading the VM (type = HVM)... -->
> Starting Qubes DB... --> Setting Qubes DB info for the VM... -->
> Updating firewall rules... --> Starting the VM... --> Starting the
> qrexec daemon... Waiting for VM's qrexec
> agent.......................................connected Traceback
> (most recent call last): File "/usr/bin/qvm-run", line 199, in
> <module> main() File "/usr/bin/qvm-run", line 194, in main r =
> vm_run_cmd(vm, cmdstr, options) File "/usr/bin/qvm-run", line 64,
> in vm_run_cmd gui = options.gui, filter_esc = options.filter_esc)
> File
> "/usr/lib64/python2.7/site-packages/qubes/modules/01QubesHVm.py",
> line 356, in run return super(QubesHVm, self).run(command,
> **kwargs) File
> "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py",
> line 1499, in run self.start(verbose=verbose, start_guid = gui,
> notify_function=notify_function) File
> "/usr/lib64/python2.7/site-packages/qubes/modules/01QubesHVm.py",
> line 381, in start return super(QubesHVm, self).start(*args,
> **kwargs) File
> "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py",
> line 1786, in start extra_guid_args=extra_guid_args) File
> "/usr/lib64/python2.7/site-packages/qubes/modules/01QubesHVm.py",
> line 412, in start_guid super(QubesHVm, self).start_guid(verbose,
> notify_function, extra_guid_args=["-Q"], **kwargs) TypeError:
> start_guid() got multiple values for keyword argument
> 'extra_guid_args'
>
I think a dom0 fix for that is in the testing repository. Anyway, I'd
wait a few more days for the new Windows Tools release that fixes a
lot of problems with the first build.

> Second try: [tonis@dom0 ~]$ qvm-run -a win7-2 cmd.exe Running
> command on VM: 'win7-2'... --> Starting Qubes GUId... Connecting to
> VM's GUI agent: .connected --> Sending monitor layout... -->
> Waiting for qubes-session... (hanged here a long time, before I
> pressed ctrl+c) ^CTraceback (most recent call last): File
> "/usr/bin/qvm-run", line 199, in <module> main() File
> "/usr/bin/qvm-run", line 194, in main r = vm_run_cmd(vm, cmdstr,
> options) File "/usr/bin/qvm-run", line 64, in vm_run_cmd gui =
> options.gui, filter_esc = options.filter_esc) File
> "/usr/lib64/python2.7/site-packages/qubes/modules/01QubesHVm.py",
> line 356, in run return super(QubesHVm, self).run(command,
> **kwargs) File
> "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py",
> line 1546, in run retcode = subprocess.call(args, **call_kwargs)
> File "/usr/lib64/python2.7/subprocess.py", line 524, in call return
> Popen(*popenargs, **kwargs).wait() File
> "/usr/lib64/python2.7/subprocess.py", line 1376, in wait pid, sts =
> _eintr_retry_call(os.waitpid, self.pid, 0) File
> "/usr/lib64/python2.7/subprocess.py", line 478, in
> _eintr_retry_call

>


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

iQEcBAEBAgAGBQJVr++PAAoJEIWi9rB2GrW78/0H/1C3LzbVGrVwiuHYVyj7xO4z
ZZNjQhf+ROYnHurLSMwNHUo7ec6ifO845lvrc8kuxeI/gfH0d0XTP+vtJdD1wciU
R4rPG82u/hmGJeX8ueNy859ceg46lkMSLpBa7WAAhumwv9Z/rgy5sj6rbQ4U1tKX
cLqReDHbBEGvnX2NScgR8lBiz70PlmkEtXwO1UwybQilY9T0PHizRcS8ZCCyPT8d
D1+iDEZvGHw09VhpHq10gzRUyTBagoMaJXDYWOuWGMCzXc5AbpygSYba0P/AGzIG
bXbLG8OCbYim5Ostc8ylDbbpgT4lmCnCmHHQP+MvUC60D1dPgOI3dkytEvY2QnY=
=K4RI
-----END PGP SIGNATURE-----