...and call these: moz2-win32-slave11 moz2-win32-slave12 moz2-win32-slave13 Once these are created, we'll use them as additional builder slave for mozilla-central.

VM's being deployed right now.

moz2-win32-slave11 10.2.71.188 moz2-win32-slave12 10.2.71.189 moz2-win32-slave13 10.2.71.190

(In reply to comment #2) > moz2-win32-slave11 10.2.71.188 > moz2-win32-slave12 10.2.71.189 > moz2-win32-slave13 10.2.71.190 Each of these new VMs is missing "drive E", so reopening. Its interesting that VI client shows these new VMs each have 3 disks defined (for C, D, E respectively), even though the E drive is not mounted. I cant spot the difference in setup between these three new VMs and other pre-existing VMs that have 3 disks, all correctly mounted, so reopening bug.

They are there - in Disk Management you'll need to do a Rescan Disks and then initialize the 30GB disk. I think this is something build's done in the past?

(In reply to comment #4) > They are there - in Disk Management you'll need to do a Rescan Disks and then > initialize the 30GB disk. I think this is something build's done in the past? Yeah, that's right.

rescanned and added.

(In reply to comment #5) > (In reply to comment #4) > > They are there - in Disk Management you'll need to do a Rescan Disks and then > > initialize the 30GB disk. I think this is something build's done in the past? > Yeah, that's right. I stand corrected. Didnt remember doing that myself, but its been a while. I've now added this necessary step to our "PostSetup" instructions at: https://wiki.mozilla.org/index.php?title=ReferencePlatforms/Win32 ...unless of course, this is something IT would want to do for us for future VM requests? (In reply to comment #6) > rescanned and added. I see them now. Thanks I also note that the RAM on these slaves has been fixed (now 2gb not 1gb). Thanks Phong.