Can't make QWT work

Szewcu · March 2, 2022, 10:43am

Hi, I’m new in Qubes. Firstly I was really impressed by how everything looks so simple, and ready to use. But for last few days I’m trying to force QWT to work. I read the guide many times, and now I think I followed every point that is there. One thing that I see is that on Windows Xen PV Bus driver is always marked as not working.

Then when I install QWT and add
qvm-features <VMname> gui 1
qvm-prefs <VMname> qrexec_timeout 300

GUI not starting. I also tried adding

qvm-features <VMname> gui-emulated 1
qvm-features <VMname> qrexec 1

and in that case I have GUI like before any of that change, but still not have qubes integration, and VM is killed when timeout occurs.

My qubes version:

xen_version            : 4.14.3
Linux 5.10.90-1.fc32.qubes.x86_64
  
Installed Packages:  
  
grub2-qubes-theme.x86_64                          	5.14.4-2.fc32 
kernel-qubes-vm.x86_64                            	1000:5.10.90-1.fc32.qubes 
python3-qubesadmin.noarch                         	4.1.20-1.fc32 
python3-qubesdb.x86_64                            	4.1.12-1.fc32 
python3-qubesimgconverter.x86_64                  	4.1.16-1.fc32 
qubes-anaconda-addon.noarch                       	4.1.8-1.fc32 
qubes-artwork.noarch                              	4.1.12-1.fc32 
qubes-artwork-anaconda.noarch                     	4.1.12-1.fc32 
qubes-artwork-plymouth.noarch                     	4.1.12-1.fc32 
qubes-audio-daemon.x86_64                         	4.1.19-1.fc32 
qubes-audio-dom0.x86_64                           	4.1.19-1.fc32 
qubes-core-admin-addon-whonix.noarch              	4.0.2-1.fc32 
qubes-core-admin-client.noarch                    	4.1.20-1.fc32 
qubes-core-dom0.noarch                            	4.1.24-1.fc32 
qubes-core-dom0-linux.x86_64                      	4.1.17-1.fc32 
qubes-core-dom0-linux-kernel-install.x86_64       	4.1.17-1.fc32 
qubes-core-qrexec.x86_64                          	4.1.16-1.fc32 
qubes-core-qrexec-dom0.x86_64                     	4.1.16-1.fc32 
qubes-core-qrexec-libs.x86_64                     	4.1.16-1.fc32 
qubes-db.x86_64                                   	4.1.12-1.fc32 
qubes-db-dom0.x86_64                              	4.1.12-1.fc32 
qubes-db-libs.x86_64                              	4.1.12-1.fc32 
qubes-desktop-linux-common.noarch                 	4.1.11-1.fc32 
qubes-desktop-linux-manager.noarch                	4.1.11-1.fc32 
qubes-dom0-meta-packages.noarch                   	4.1.20-1.fc32 
qubes-gpg-split-dom0.x86_64                       	2.0.55-1.fc32 
qubes-gui-daemon.x86_64                           	4.1.19-1.fc32 
qubes-gui-dom0.x86_64                             	4.1.19-1.fc32 
qubes-img-converter-dom0.x86_64                   	1.2.11-1.fc32 
qubes-input-proxy.x86_64                          	1.0.26-1.fc32 
qubes-input-proxy-receiver.x86_64                 	1.0.26-1.fc32 
qubes-input-proxy-sender.x86_64                   	1.0.26-1.fc32 
qubes-libvchan-xen.x86_64                         	4.1.7-1.fc32 
qubes-manager.noarch                              	4.1.22-1.fc32 
qubes-menus.noarch                                	4.1.11-1.fc32 
qubes-mgmt-salt.noarch                            	4.1.13-1.fc32 
qubes-mgmt-salt-admin-tools.noarch                	4.1.13-1.fc32 
qubes-mgmt-salt-base.noarch                       	4.1.4-1.fc32 
qubes-mgmt-salt-base-config.noarch                	4.1.1-1.fc32 
qubes-mgmt-salt-base-topd.noarch                  	4.1.3-1.fc32 
qubes-mgmt-salt-config.noarch                     	4.1.13-1.fc32 
qubes-mgmt-salt-dom0.noarch                       	4.1.13-1.fc32 
qubes-mgmt-salt-dom0-qvm.noarch                   	4.1.4-1.fc32 
qubes-mgmt-salt-dom0-update.noarch                	4.1.8-1.fc32 
qubes-mgmt-salt-dom0-virtual-machines.noarch      	4.1.16-1.fc32 
qubes-pdf-converter-dom0.x86_64                   	2.1.12-1.fc32 
qubes-release.noarch                              	4.1-0.27 
qubes-release-notes.noarch                        	4.1-0.27 
qubes-repo-templates.noarch                       	4.1.2-1.fc32 
qubes-rpm-oxide.x86_64                            	0.2.3-1.fc32 
qubes-usb-proxy-dom0.noarch                       	1.1.1-1.fc32 
qubes-utils.x86_64                                	4.1.16-1.fc32 
qubes-utils-libs.x86_64                           	4.1.16-1.fc32 
xfce4-settings-qubes.x86_64                       	4.0.5-2.fc32

Windows VM is running Windows 10 Home 21H2 build 19044.1566 - freshly downloaded ISO (Polish 64-bit) from MS and all updates after install.

Szewcu · March 2, 2022, 11:24am

Ok, according to MS forum this driver issue is probably caused by insuficient power settings. So i think it can be caused by manually performed powercfg -H off that was addvised in installation guide.

Szewcu · March 2, 2022, 2:42pm

It was dead end. Still can’t make QWT work.

jevank · March 2, 2022, 3:14pm

What guide do you mean?

Szewcu · March 2, 2022, 3:18pm

and follow first:

github.com

Qubes-Community/Contents/blob/master/docs/os/windows/windows-vm.md



Installing a Windows VM
=======================

Simple Windows install
----------------------

If you just want something simple and you can live without some features.

Works:
- display (1440x900 or 1280x1024 are a nice fit onto FHD hw display)
- keyboard (incl. correct mapping), pointing device
- network (emulated Realtek NIC)

Does not work:
- copy & paste (the qubes way)
- copying files into / out of the VM (the qubes way)
- assigning USB devices (the qubes way via the tray applet)
- audio output and input

This file has been truncated. show original

and then:

github.com

Qubes-Community/Contents/blob/master/docs/os/windows/windows-tools.md


Qubes Windows Tools
===================

Qubes Windows Tools are a set of programs and drivers that provide integration of Windows AppVMs with the rest of the Qubes system. Currently the following features are available for Windows VMs after installation of those tools:

-   **Qubes Video Driver** - provides for the Seamless GUI mode that integrates apps windows onto the common Qubes trusted desktop
-   **File sender/receiver** - Support for [secure clipboard copy/paste](https://www.qubes-os.org/doc/copy-paste/) between the Windows VM and other AppVMs
-   **File sender/receiver** - Support for [secure file exchange](https://www.qubes-os.org/doc/copying-files/) between the Windows VM and other AppVMs
-   **Copy/Edit in Disposable VM** - Support for editing files in DisposableVMs as well as for qvm-run and generic qrexec for the Windows VM (e.g. ability to run custom service within/from the Windows VM)
-   **Xen PV drivers** for Windows that increase performance compared to qemu emulated devices

Below is a breakdown of the feature availability depending on the windows version:

|             Feature                  |  Windows 7 x64 | Windows 10 x64 |
| ------------------------------------ | :------------: | :------------: |
| Qubes Video Driver                   |        +       |       -        |
| Qubes Network Setup                  |        +       |       +        |
| Private Volume Setup (move profiles) |        +       |       +        |
| File sender/receiver                 |        +       |       +        |

This file has been truncated. show original

Szewcu · March 2, 2022, 3:31pm

I freshly installed Win 10 more then 10 times up to now. It always ends the same. What I do is:
1.) Creating HVM not based on any kernel with 4096 MB RAM, 50GB system storage and 10GB privat storage space, 2 cores and memory balancing not ticked, no internet connection.
2.)Boot HVM from ISO and install Windows on 50GB Disk 0
3.)Reboot after installation connect to sys-firewall and update
4.) Install 7zip, unpack xenvbd and xenbus
5.) Install xenvbd and xenbus (no popup to reset after installing xenbus, and driver matched as not working from the beginning)
6.) Reboot
7.)Install QWT (from C:) with unticked, Xen PV disk drivers, Move user profiles and one more that was unchecked by default and as I understand it is option for Win 7.
8.)Reboot
9.) Add settings for VM in dom0

jevank · March 2, 2022, 3:34pm

Unfortunately doc is outdated. Take a look this thread

Szewcu · March 2, 2022, 3:49pm

I’m little bit confused. Should I cross compile and install newest QWT or that from ftp also should work? If second what I’m doing wrong? In those reports there is nothing about installing additional xendrivers. So are they detracted in this solution?

jevank · March 2, 2022, 4:23pm

Building from source is the optimal way to make it work for now.

Szewcu · March 2, 2022, 4:37pm

Ok, just build it. I will check if that works. When it will be officially released? With all certificates etc?

jevank · March 2, 2022, 4:39pm

github.com/QubesOS/qubes-issues

Qubes Windows Tools (QWT) on R4

opened 08:23AM - 14 Feb 18 UTC

taradiddles

help wanted C: doc C: windows-tools T: task P: default

**!! EDIT Feb. 2022 !!** - QWT works with R4.0 and R4.1 thanks to the work of @…jevank et al. so most of this post is outdated (there are a few minor outstanding issues but the main stuff - copy/paste, copy files, ... - works). - QWT [is on its way](https://github.com/QubesOS/qubes-issues/issues/3585#issuecomment-1049118557) to be available as a qubes rpm package (contrib or official). - See [this wiki forum post](https://forum.qubes-os.org/t/windows-qwt-user-reports/9687) for a quick installation howto and contributed user reports about what works and what doesn't with various windows versions. - QWT's current github repo is [here](https://github.com/tabit-pro/qubes-windows-tools-cross), issues are [there](https://github.com/tabit-pro/qubes-windows-tools-cross/issues). **!! THE CONTENT BELOW IS OUTDATED !!!** See Marek's [comment](https://github.com/QubesOS/qubes-issues/issues/3585#issuecomment-403785567) (some issues remain); install with ~~~ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-windows-tools ~~~ **Note** however that upgrading from QWT3 often fails (see below), and installing QWT4 in *clean* windows HVMs [doesn't work](https://groups.google.com/d/msg/qubes-users/i36AbxtgwgI/eSZdrsuWBgAJ) for some users. Clone your VM before attempting anything ! - 1st install: follow the [official doc](https://www.qubes-os.org/doc/windows-tools/) - upgrade from the 3.2 version: clone your vm first ! ; temporarily set `debug` to true and `qrexec_timeout` to a large value (eg. 600) or the vm will be killed before you'll be able to complete the setup (it takes a bit of point&click). * [FAILS] VM with SP1 and no other windows updates / **upgrading** over 3.2: at the following reboot, windows fails to boot and tries to repair files, which as usual doesn't fix anything (the VM might boot at some point, without the tools installed) * [TODO] VM with SP1 and no other windows updates / **remove** 3.2 version first and then install 4.0.0 * [TODO] VM with latest windows updates / **upgrade** over 3.2 * [TODO] VM with latest windows updates / **remove** 3.2 version first and then install 4.0.0 --- [The purpose of this issue is to gather user experience and document the installation of R3.2's QWT in Windows HVMs on R4, bugs found and workarounds until the tools are fixed (and hopefully have a new [maintainer](https://groups.google.com/d/msg/qubes-devel/tBqwJmOAJ94/t5KgmST2BAAJ)).] #### Qubes OS version: Qubes 4.0 #### Affected TemplateVMs: Windows HVMs #### Edits - Nov 13 * add gateway network setting in issue 1 - June 23 * add @mossy-nw 's comment about properly checking the rpm sig - May 7 * add note about VM qvm-prefs issue when creating a VM based on a windows template - Apr 23 * add AppVM based on win TemplateVM issue - Mar 11 * revert note about qvm-copy/move failing, it works fine (transient errors because of update mismatch on my system). - Mar 5 * add note that since [qsb #38](https://www.qubes-os.org/news/2018/02/20/qsb-38/) qvm-copy/move fails with 'request refused' because the tools aren't updated. * add qvm-prefs vmname default_user <user> to fix copy location ; reference [here](https://groups.google.com/d/msg/qubes-users/SdmqyKDXwU0/sl9LczO-BwAJ) - Feb 28 * add `rpm -K` for rpm sig check (seen such questions in qubes-users ML) * add comment by @AJolly / QWT won't install with the 'move profiles' option disabled - Feb 18 * more info on networking (DNS ips, ... + disabling the qubes net service) * copied some of the commands needed from the official QWT install guide * note about windows update + Xen VBD driver --- #### QWT installation Prerequisite: win7 x64 VM (see https://www.qubes-os.org/doc/windows-vm/). Get the last QWT rpm [here](https://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/qubes-windows-tools-3.2.2-3.x86_64.rpm). In order to check the rpm's signature you'll have to import Qubes Release 3 Signing Key in the VM where you are confirming the rpm signature. Get the key [here](https://keys.qubes-os.org/keys/qubes-release-3-signing-key.asc) . Check the key fingerprint as follows: ~~~ gpg2 --fingerprint --import --import-options show-only --dry-run qubes-release-3-signing-key.asc ~~~ Or alternatively, ~~~ gpg2 --import qubes-release-3-signing-key.asc gpg2 --fingerprint "Qubes OS Release 3" ~~~ And compare with the key's well-known fingerprint, which should be `C522 61BE 0A82 3221 D94C A1D1 CB11 CA1D 03FA 5082` Import the key to the VM's rpm keyring: ~~~ sudo rpm --import qubes-release-3-signing-key.asc ~~~ You can now check the rpm's signature (more info on rpm signatures [here](https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-check-rpm-sig.html)): ~~~ rpm -K qubes-windows-tools-3.2.2-3.x86_64.rpm ~~~ You should get `qubes-windows-tools-3.2.2-3.x86_64.rpm: digests signatures OK`. If not, check that the rpm is properly downloaded, that the signing key is imported, ... Extract the iso from the rpm: `rpm2cpio qubes-windows-tools-3.2.2-3.x86_64.rpm | cpio -idmv` And start the VM (assuming the iso is in the 'untrusted' VM): `qvm-start --cdrom=untrusted:/home/user/qubes-windows-tools.iso win7new` From the QWT install [guide](https://www.qubes-os.org/doc/windows-tools/): * win cmd: `bcdedit /set testsigning on` * win cmd: `netplwiz` / uncheck 'Users must enter a user name and password...' * in dom0: qvm-prefs vmname qrexec_timeout 300 Note about Windows Update: * updating the machine is *not* required provided you don't enable the storage driver (disabled by default) in QWT' setup. QWT works on a bare SP1 install as well as in fully updated. See @dmoerner's [comment](https://github.com/QubesOS/qubes-issues/issues/3585#issuecomment-366471111) below on how to install updates. * _however_, a fully updated Windows seems to be required in order to install xen's VBD (storage) PV driver: - on "stock" SP1, installing Xen's PV driver from either QWT or from Xen's [official site](https://www.xenproject.org/downloads/windows-pv-drivers/winpv-drivers-81/winpv-drivers-820.html) results in either a BSOD or endless unfixable reboots. - after a full Windows Update (takes hours), installing Xen's official driver works flawlessly. Haven't tested when installing QWT *with* the storage PV driver *after* updates. Note about QWT's 'move user profiles' options: @AJolly [reports](https://github.com/QubesOS/qubes-issues/issues/3585#issuecomment-368065710) that QWT wouldn't install with the option disabled. #### Issue 1 - Networking isn't set up properly The PV adapter's status is stuck at "Identifying"; pinging an *ip* works but pinging a *host* fails, indicating a problem with DNS resolution. A tcpdump on sys-firewall indeed shows that DNS requests are sent to the gateway's ip and are rejected. The reason is that in R4 VMs [are now using](https://www.qubes-os.org/doc/vm-interface/) the exposed "/qubes-{primary,secondary}-dns" values, while R3.2's Windows Tools still use /qubes-gateway (whose IP in R4 is different from /qubes-primary-dns). Workaround: disable the "Qubes Network Setup" service (with gui/`msconfig`, or `sc config "QubesNetworkSetup" start= disabled` in a command prompt) and configure the network manually. Settings: * DNS{1,2}: 10.139.1.1, 10.139.1.2 * Subnet: 255.255.255.0 * IP: to find the VM's ip, run `qvm-prefs vmname visible_ip` in dom0. Caveat: a cloned/restored/... VM will likely have its IP changed so you'll have to remember to update your network settings. * Gateway: to find the ip, run `qvm-prefs vmname visible_gateway` in dom0 #### Issue 2 - Copy/Move functions * If the username you log on with in Windows is different than `qvm-prefs vnname default_user` (usually 'user'), then the 'QubesIncoming' folder is located in `C:\Windows\System32\config\systemprofile\Documents\QubesIncoming\` (and launching .exe's directly from this folder sometimes fail, in which case one has to copy the .exe somewhere else (eg. on the desktop) and run it from the new location). Fix it with `qvm-prefs vnname default_user winusername` where `winusername` is the username you log on with in windows. * In R4 the qvm-{copy,move} operations don't require the destination VM as argument: the destination VM is later typed by the user in a dom0 popup gui. When using R3.2 tools in R4 and copying/moving a file from/to a Windows VM, the user will be presented with a "destination VM" popup menu twice - once in the windows VM and once in dom0 (it is OK to leave the VM field blank in windows though). #### Issue 3 - inter VM copy/paste doesn't work Workaround: copy text in files and copy/move them accross VMs. #### Issue 4 - creating Windows AppVMs based on a Windows TemplateVM Problem: the private disk is present in the AppVM but QWT doesn't initialize it if it's empty (format + relocate user profiles). As a result user profiles aren't found at startup and the AppVM is stuck at "Preparing your desktop" for a 2-3 minutes until it timeouts. The vm is then barely usable because of the lack of user profiles. Workaround (work in progress): copy the private disk of the TemplateVM to the AppVM - see [this ML thread](https://groups.google.com/d/msg/qubes-users/TJZQbB9CvrU/j6Zu1ZaJCQAJ) Problem 2: Qubes doesn't copy a template VM's prefs when creating a VM so the new VM's prefs will be the "default" ones and won't be set properly for windows ; eg. ~~~ qvm-prefs winTemplate kernel -> '' qvm-prefs winTemplate virt_mode -> 'hvm' qvm-prefs winTemplate memory -> '2096' qvm-create --template winTemplate --label red wintest qvm-prefs wintest kernel -> '4.4.18-1' qvm-prefs wintest virt_mode -> 'pvh' qvm-prefs wintest memory -> '400' ~~~ Solution: set the preferences to match those of the templateVM. #### Fixing QWT See [this message](https://groups.google.com/d/msg/qubes-devel/tBqwJmOAJ94/xmFCGJnuAwAJ) from Marek. * Networking isn't set up properly: use /qubes-primary-dns ; looks trivial ( https://github.com/QubesOS/qubes-core-agent-windows/blob/master/src/network-setup/qubes-network-setup.c) * Copy/Move functions: fix the copy/move functions/gui not to require any argument (https://github.com/QubesOS/qubes-core-agent-windows/blob/master/core-agent-windows.wxs)

Szewcu · March 2, 2022, 5:29pm

Ok, now it works. My last question. Are attaching USB devices should work in this release or not (for me it not work, and in reports from that topic I also see that people writing about that but some time ago - then most posts is about how the documentation should be updated)?

jevank · March 2, 2022, 5:36pm

USB and audio support do not related with QWT. It can be enabled via dom0 commands:

qvm-features [windows-qube] stubdom-qrexec 1
qvm-features [windows-qube] audio-model ich6

Szewcu · March 2, 2022, 6:40pm

THX. I added this options to VM. But USB still not working. Can this be related to version of USB? On Virtualbox there was separate drivers for USB 3.0.

error_usb

Also I want to ask about Xen Network driver. I installed it and then network stop working. So I simply uninstall that device from device manager, and Internet are back. But aren’t the Xen driver better?

jevank · March 2, 2022, 6:53pm

Did you reboot VM? Emulated USB NEC controller should appears in Device Manager.

The performance with Xen network drivers is better, but there are issues with DHCP. We placed script (qnetwork_setup.bat) to manual assign IP address and it is enough to setup standalone VM, but not enough to use with template based VM.

Szewcu · March 2, 2022, 7:03pm

Yes, I restarted the VM, also added repos from that post, update dom0 and reboot qubes.

Don’t have such a device in DM. Now the error is different
error_usb2
.

jevank · March 2, 2022, 7:17pm

That is not necessary since all packages already in stable repos.

Could you place output from qvm-features [win-qube] ?

Szewcu · March 4, 2022, 3:34pm

I have a typo in one of the features that @jevank figured out on pm. So for now everything seems to work.