-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2015-04-24 21:29, Marek Marczykowski-Górecki wrote:
> On Fri, Apr 24, 2015 at 12:27:18PM -0700, Micah Lee wrote:
>> I'm running Qubes 3.0-rc1, and I'm trying to install Qubes
>> Windows Tools in a win7 HVM.
>
>> In dom0 when I run:
>
>> sudo qubes-dom0-update qubes-windows-tools
>
>> I get the error:
>
>> No package qubes-windows-tools available.
>
>> And while I expect it not to work because I didn't install it,
>> when I run:
>
>> qvm-start win7 --install-windows-tools
>
>> It fails with a traceback that ends with:
>
>> libvirt.libvirtError: internal error: libxenlight failed to
>> create new domain 'win7'
>
> Take a look at "Known issues"[1] section:
>
> "There is no Qubes Windows Tools for Qubes R3.0 yet. We are working
> on this"
>
> [1]
>
https://www.qubes-os.org/doc/InstallationGuideR3.0rc1/#known-issues
>
>
>
>
To expand on that, we've run into a lot of problems with our current
GPL Xen PV drivers for Windows in R3. Mainly, they just didn't
implement some functionality that's needed for our new libvchan (and
qrexec). I implemented the missing stuff but then I've also
experienced really strange PV disk behavior that leads to unbootable
OS, and that's not fun to debug (the PV disk driver doesn't report any
errors, but the OS somehow maps wrong partition structure on the PV
disks).
In the end I decided to use the new Xen PV drivers [1]. Their code is
of much higher quality, they are actively developed, and most
importantly, they work on Qubes R3. Still, they lack some core
functionality (foreign grant mapping) but that can be mostly ported
from my work on the GPL drivers. They also lack driver-user mode
interfaces for most functionality. Implementing this is what I'm doing
now. I estimate 2-4 weeks until our Windows Tools are fully
functional. After that it's Windows 8 support and its totally
different display driver model ;)
[1]
http://www.xenproject.org/developers/teams/windows-pv-drivers.html
- --
Rafał Wojdyła
Qubes Tools for Windows developer
-----BEGIN PGP SIGNATURE-----
iQEcBAEBAgAGBQJVOp52AAoJEIWi9rB2GrW7ma8IAJNVzk2LXw+jfIpa8T8I8nP6
VYw+2uWKGKtO5QzidHF8MH6USAiJtLN+558AAedRglmykm9t6FdbySbbP6sGuNDb
/0/dY4rcWgzr2fM22ALEtK+BtZsmIlEFA1yjCS7pFpoGt9f/NK4Yv2PD5hBNKdPl
BydFpN4Cp40RrTWhH47P2Ydo5uWGW//15K9HPR9HzJc2CEEF+viw7kMH5KUw2r+R
Vm1wAQqCPvwodqnA0YAQcUOMQdJEbhHzsf1jp2eQYmoTmGjxBipSIQlqH2637FYJ
elVAaFQ2yBdE9AsxTvGrxgJ3jsZY4Fdf5uTf68UzAr6iI5q8vFfsLD949ca6KiQ=
=HrSl
-----END PGP SIGNATURE-----