well I have read the documentation of installing Qubes Windows Tools. Especially the known limitations of that software on, link: -issues/issues/3585 . Also I discovered this video tutorial on you-tube: =1mGop1B-kqU . The author, Mr. Chris Titus, of this video, which is from October 27th in 2019. Came to the conclusion that it is at that moment not advisable to install Qubes Tools for Windows.
Therefore I have this question: Do you think this issue changed in the meantime? Or is it better to wait for some time until the team of Qubes OS have programmed the necessary software. So that everything is running smoothly.
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:...
Hi,
Thank you so much for your advice so far. I managed to complete on web site -os.org/doc/windows-tools/ up to step Nr. 9. However there is no window appearing if I start my Windows 10 VM. My task manager is telling me that I use 42 % of my memory which is 16 GB. And if I want to shutdown the Windows 10 VM after 8 minutes of nothing visible happening, I have to kill it. Since there are some processes running inside the VM, which are not visible to me.
Hi,
as far as I can see I followed the instructions on this page.
However I unchecked memory balancing and I gave the windows 10 StandaloneVM Initial memory 5000 MB.
Is this what you are referring to?
Thank you.
Stay healthy & safe
Warning: The content below describes Qubes Windows Tools installation in Qubes R4.0. The text has been updated to reflect the newer R4.1 release and QWT recent development. Please see this updated document for instructions for Qubes R4.1 and the...
However now I am following the instructions of the official Qubes OS instructions. Therefore I include 2 screenshots of my last 2 configuration steps. After step Nr. 7 my GUI of Windows 10 is not starting anymore. So I think that my mistake is in this installation of the Qubes Windows Tools.
According to the Taskmanager the CPU does not do anything.
I researched this Forum a lot but nothing suits my problem.
I tried reinstalling everything, I tried a different machine, I tried a different Snap Version (2.0), I tried choosing different Resolutions (10,20,60), I tried to process it without SNAP (via Command prompt) and I tried everything withouth upgrading numpy manually. I am left clueless.
Now it works. In SNAP and as a standalone.
I got some bugs during the process, for example a DEM is needed, otherwise Sen2Cor assumes a flat surface. Now I have to figure out how get a DEM into the process. But thats enough stuff for a whole new forum topic. All I can say is that I solved my problem. It took me more than a week to figure everything out. I am not happy about it. But it runs now.
Hi tayi,
sorry for my late reply this time, I tried to write the path in the blank of PYTHON_BIN and worked. Probably this has no sense as Onishambles suggests but it worked. I have read in the forum that sometimes happen a tool is not working and after doing nothing it works. I think SNAP will be a powerful tool but we have to be patient because it needs to be polished.
you are working with an outdated version of sen2cor. Please use the new vesrion 2.2.1 from here:
-party-plugins-2/sen2cor and read the release notes.
The problem with the windows oath names is fixed among lots of other issues.
There will not be any further support given on v.2.0.6.
Hi umwilm,
I installed sen2cor 2.2.1 successfully and i have the same problem - after i tried to process Sentinel-2 Scene. Nothing happens and black console window appear.
Any idea how to proceed ?
Thanks,
Ori
I found people talking about Qemu/KVM on Reddit, so I decided to try. Main reason why I wanted to try because I want to move away from VirtualBox that I can never enable folder sharing, and VMWare which is paid.
It is quite confusing when you first started. I started with virt-manager and had no clipboard sharing enabled. By default, virt-manager is using SPICE. The key to this tutorial is, install spice-guest-tools and Spice WebDAV daemon.
Open the download page ( ) on your Windows Guest, scroll down a bit until you found Windows binaries under Guest, click the Windows guest tools link to start the download. Or you can use this link
Download and install spice-webdavd in Windows Guest. Pay attention on the file extension. You will want to donwload .msi file which usually larger than the other. Or you can just use this link for the latest installer
Works like a charm! Is the only tutorial I have found with all step by step to share folders between windows guest and Linux host. (Arch Linux host / Windows 10 guest). The only thing is that only one shared folder is possible but anyway if you want to go from VirtualBox to QEMU for Windows guests, sharing folder is nowadays the only thing it is not as good as VirtualBox. Anyway this tutorial rocks!
d3342ee215