I tried qvm-create-windows-qube with R4.1 and QWT-cross and it works quite well.
At now it needs to allow file copying in deprecated policy file, so first we have to create it
Then all works as usual except QWT installation, which is need to be done manual in opened window. This is because of MSI package instead of exe file, but I think it will not be a problem to automate.
Second manual action is choosing target on Filecopy operation to copy files to windows qube at one of last stages.
@GWeck application launch from menu didn’t get any problem. Could you try this commands to recreate menu items with your case qvm-appmenus --remove [windows-qube] qvm-sync-appmenus [windows-qube]
If it not helps show output of manual starting application qvm-run -p --service [windows-qube] qubes.StartApp+Accessories-Paint
FWIW: In the recent surveys we’ve run, we’ve gotten MANY requests for Windows 10 support. I don’t think there’s anyone who does not want it, tbh.
Resourcing is the 100% issue. Short of a community contribution coming in that can be fully tested and fully resiliant and fully functional. Which is how this designer is trying to say “works!” but isn’t quite sure how to in this world I understand to be absudly complicated—but for good reasons.
Please do not let my assertions above, interfere with folks trying to crack this tough nut. Just wanted to chime-in that it IS a desired feature by many, and that the only reason the core team has not “prioritized it” (BIG air-quotes) is because it is but a toilet in the bathroom that is Qubes OS… and the core team is all 100% right now on keeping the water running and draining well.
Recreating the menu item via qvm-appmenus --remove and qvm-sync-appmenus did the trick: Now Windows 7 applications can be started from the XFCE menu, too.
By the way, I am using Windows 7 SP1 Professional, fully updated.
To make long story short, did anyone manage to create a script for single-click win10 template deployment with modern QWT that would not require any manual trickery in the middle?
You can build it with instructions and copy to dom0 after that qvm-run -p dispXXX -- cat /home/user/qubes-builder/qubes-packages-mirror-repo/dom0-fc32/rpm/qubes-windows-tools*.noarch.rpm > qubes-windows-tool.rpm
After building the rpm and iso, I install the rpm to dom0. I also start the Windows 10 HVM (restored from the backup) with the iso and install the new Qubes windows tools.
But copy and paste doesn’t work.
I use the iso file at chroot-dom0-fc32/mock/fedora-32-x86_64/root/builddir/build/BUILD/qubes-windows-tools-4.1/qubes-windows-tools-4.1.65.iso in the qube for building QWT.
The command does not work because QWT is not yet packaged and available
for 4.1
You’ll need to comment out that line from the script.
The qubes-windows-tools package provides an iso image that can be
attached to the Windows qube at start up using qvm-start --install-windows-tools
The proposal here is to build an iso image yourself, and manually
transfer it in to dom0.
You can then use qvm-start --cdrom to start the Windows qube with the
iso attached.
Can you make a template this way? Also, it is Win7, so next step would require hacking ESU :-/ Also last time I checked qvm-create-windows-qube it required manual actions like “pause installation, fix private volume issues and continue”
Of course, no reason why you can’t have a Windows template.
If you don’t move the User directory from xvda, then your Windows
TemplateBasedVMs will be disposables. Neat.
I checked now this QWT version with the new Qubes R4.1 beta, and it behaves quite similar to the fully updated Qubes R4.1 alpha - not really surprising!
QWT works for both W7 and W10, and I can copy files to other VMs; so qrexec is working. Screen resolution is still restricted to the few values described above, and the start button of W7 is still missing if the VM is set to seamless mode.
For both W7 and W10, I could not start applications from the XFCE menu, and the trick with the re-creation and syncing of the appmenus did not work. Trying to start a command via qvm-run -p --service [windows-qube] qubes.StartApp+Accessories-Paint does not work either for W7 - this command just does not terminate, and it does not produce any output. For W10, the command starts the application.
For W10, qvm-features gui has to be set in order to make the window visible.
