Piit, thanks for your investigation and nice tutorial!
Have you managed to get Windows HVM into real full screen mode without installing Windows Tools GUI? Setting *allow_fullscreen=true* in */etc/qubes/guid.conf *does not seem to enable it anyway (it stays grayed out on window bar -> More actions -menu). I have dual monitor setup (1920x1200 Displayport-0 and 1920x1080 DVI-0), but I've managed to install GUI tools (as you did) by only setting dom0 resolution the same as in Windows and detaching the other monitor. As soon I add the other monitor, Windows wouldn't start no matter if seamless mode is on or off. HOWEVER if I add the 2nd monitor only AFTER starting Windows, it works nicely and I can use Windows both in full screen mode (in 1st or 2nd monitor) or in seamless mode. Also switching between seamless and normal mode from VM Manager is possible in real-time :) Some things I noticed (only 1 monitor in use): - some of the Windows Updates have incompatibilities with QWT. Whether Network Tools are installed or not, DHCP would not work, but manual configuration would resolve situation. - Seamless mode starts anyway even if it is not enabled in VM Manager when the VM is booted the first time after GUI tools installation. After that, it boots as it is configured in VM manager. - starting in seamless mode is very erratic (about 50% of the times the startup fails and restart is needed). - starting without seamless mode works slightly better (starts in full screen by default but works as windowed as well), but can get stuck as well during boot - shutdown from VM Manager does not work (seamless or not), but "shutdown /s /t 0" from windows command line works even in seamless mode After changing between seamless and normal modes and booting few times, the VM would not start anymore (stuck at Starting Windows screen). Only after many restarts between normal and safe mode (which works), would normal mode boot again.. Here are attached logs from one of the times it was stuck during boot (one monitor): http://txt.do/5bcf7 http://txt.do/5bcf2 http://txt.do/5bcfv http://txt.do/5bcfn http://txt.do/5bcfw http://txt.do/5bcfb http://txt.do/5bcf3 http://txt.do/5bcfi and logs when starting with two monitors (always gets stuck): http://txt.do/5bcp6 <http://txt.do/5bcf7> http://txt.do/5bcpj <http://txt.do/5bcf7> http://txt.do/5bcp4 <http://txt.do/5bcf7> http://txt.do/5bcpl <http://txt.do/5bcf7> http://txt.do/5bcpq <http://txt.do/5bcf7> http://txt.do/5bcpc <http://txt.do/5bcf7> http://txt.do/5bcpm <http://txt.do/5bcf7> http://txt.do/5bcph <http://txt.do/5bcf7> http://txt.do/5bcpx <http://txt.do/5bcf7> http://txt.do/5bcpu <http://txt.do/5bcf7> http://txt.do/5bcpf <http://txt.do/5bcf7> http://txt.do/5bcpz <http://txt.do/5bcf7> I noticed there was 2 different log files for qga and 4 for qrexec-wrapper. But I deleted all logs in safe mode before starting VM in normal mode, so these logs should be only from one run. I noticed that behaviour got more erratic after setting more verbose log levels (5) and sometimes it would BSOD as well (SYSTEM_SERVICE_EXCEPTION, STOP: 0x0000003B (...) ). Maybe race condition? I can send dump files and Xen logs somewhere also if you're interested. Using Q3.1 with stock kernel 4.1.13-9 and latest QWT (3.0.4-1). HW: Intel i7-5820K with Asrock X99 WS. GFX card is GTX980 with stock Nouveau driver. On Wednesday, March 16, 2016 at 12:26:49 AM UTC+2, [email protected] wrote: > > Hello, > > after spending some more hours trying to figure out what breaks my windows > 7 VM as soon as I install the Qubes Windows Tools, I would like to share > what I found out so far. > > In short: > It seems that the installation of the "Qubes GUI Agent" within the Qubes > Windows Tools create some kind of problem on the Windows 7 VM, as this > triggers if I can use the VM or not. > > More detailed description to revalidate my experience. > (as this is targeted also at newbies, which will find this via Google, > while troubleshooting, I have included every step), sorr :-) > > > Install a Win7 VM in Qubes OS 3.1 > ================================= > > - Create Windows VM > qvm-create win7 --hvm --label orange > > - Increase initial RAM and max RAM to 4GB (4096) > > - Install Windows from .ISO > qvm-start win7 --cdrom=/home/piit/Downloads/windows_7-Pro-64bit-DE.iso > > - Several reboots (=restarts) until Windows is running > > - Start VM as final test -> GUI available? > qvm-start --debug win7 > > - Clone VM to have a working copy if you screw up during the next steps > (win7-plain) > > - Install qubes-windows-tools > qubes-dom0-update --enablerepo=qubes*testing qubes-windows-tools > or: > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > qubes-windows-tools > > - Disable User Login > Start > cmd.exe (as Administrator) > netplwiz > Uncheck "Users must enter a user name and password to use this computer" > Double check that change have been applied > Reboot (Login should happen automatically) > > - Launch windows with Windows Tools ISO > qvm-start win7 --install-windows-tools > > - Copy Windows Tools to c:\tools > > - Allow unsigned drivers (as described in the Readme.txt) > > - Increase Timeout > qvm-prefs -s win7 qrexec_timeout 300 > > - Install Qubes Tools for Windows > - disable: Xen PV Disk Drivers > - disable: Qubes GUI Agent > will ask for a restart after installation > > - Next startup will show an information windows: > "Qubes Tools for Windows > Qubes private disk image initialized as disk D:. > User profiles directory will be moved there during the next system > boot. > [OK]" > Choose "Restart Now" > > - On next startup a few command messages will appear, then the desktop is > available > If you check the application menu in Qubes OS, you will find all Windows > available there :-) > > - Clone the VM to have a working backup, if you screw up your VM during > the next steps (win7-ready) > > - Restart win7 VM and launch the "Qubes Tools for Windows" Installer again > (c:\tools\qubes-tools-WIN7x64-3.0.4.1.msi) > > - Choose "Change" and install "Qubes GUI Agent", which we have disabled > during the first start. > > - Open VM Settings and check under the "Basic" Tab if "Seamless GUI" is > disabled > > - Restart VM and check what happens. In my case the VM was booted into > seamless mode (even when this was deactivated in the settings) > > - Try to start a windows application from the Qubes OS menu, like > Calculator. In my case the icon showed a little bouncing calculator-icon, > but no app came up. > > - Shutdown VM via right click in Qubes VM Manager. As this didnÄt work > within 20 seconds I choose the option "Kill VM" in the popup-window > > - Try to restart VM in debug mode "qvm-start --debug win7" > which leads to a Bluescreen of Death with the message: > "Quota Underflow" > > - At this point I have purged my VM and startet the Clone VM (win7-ready). > > > Any suggestions if the problem is on my site (misconfiguration at some > point) or within the Qubes Windows Tools package (especially the "Qubes GUI > Agent")? > > At least I'm glad to have Win7 running in "Full Desktop Mode". > > regards > > - Piit > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e1d494c9-821b-42bb-8f87-75f2c4d41a61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
