Checked correct settings (limiting on color depth set, settings correct in VI), but screen resolution refuses to be 1280 x 1024. Not sure what else to do here to get the correct resolution.
[Morping from "screen resolution on moz2-win32-slave26 incorrect."] From grepping over the vmx files, we need to add the svga lines at https://wiki.mozilla.org/ReferencePlatforms/Win32#Clean_rebooting_setup_.28VNC.2C_autologin.2C_audio_driver.29 to the vmx files of moz2-win32-slave24 thru 29. Alice made a start on slave26. The default resolution is still set to 1024x768 on the refplatform, so that and all recent clones need fixing up.
Ref platform had these done OK: v12 - Screen Resolution Set so Unittests will pass * Run GPEDIT.MSC; * Go to: Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Terminal Services; * Open the policy 'Limit maximum colour depth'; * Set this to 'Enabled and 24 bit' * Verify that the screen resolution is set to: 1280 x 1024, 24bit color and v14 - Clean rebooting setup (VNC, autologin, audio driver) Enable the VM to use the proper resolution and screendepth in the console session: * Shutdown & poweroff the VM. * Edit the .vmx file and add the following lines: svga.maxHeight = 1024 svga.maxWidth = 1280 svga.vramSize = 16777216 But not the resolution part of v14 - Reboot * Reboot and login over VNC as cltbld * Set screen resolution to 1280x1024x32 That's done now.
* moz2-win32-slave08,24,25,26,27,28,29 now set to 1280x1024x32 (was 1024x768x32). Had a bunch of fun with three of them, see below * checked other moz2 windows slaves, all fine * new try-win32-slave10/11/12 now set to 1280x1024x32 * checked other try windows slaves, all fine * but: try-win32-slave01,03,05,07,09 & moz2-win32-slave07,15,16 have 40MB of video ram, so they have higher resolutions than 1280x1024 available. I don't know if I care enough, comments ? Still to do * try-win3213/14/15 when Phong is finished with them The fun bit: "svga.vramSize = 16777216" wouldn't stick and it kept getting put back to "4194304" (4MB). Eventually solved by removing from the VI inventory, fixing vmx file, registering on command prompt of an ESX server (and migrating back into the right resource pool). I don't recall us hitting this before but we did play with VM > Edit Settings today in VI, so perhaps that's a bad thing to be doing. Also, setting vramSize doesn't seem to take in Edit Settings, but the width and height did, so there seems to be some filtering going on.
(In reply to comment #3) > * but: try-win32-slave01,03,05,07,09 & moz2-win32-slave07,15,16 have 40MB of > video ram, so they have higher resolutions than 1280x1024 available. I don't > know if I care enough, comments ? Actually, all of these have the wrong max resolution svga.vramSize = "16777216" svga.maxHeight = "1770" svga.maxWidth = "2360" while just try-win32-slave09 has 40MB of vram, which makes the fix alot less painful.
Done. Just need to get try-win32-slave13,14,15 to be finished.
try-win32-slave13,14,15 also done. --> FIXED