Closed Bug 431726 Opened 17 years ago Closed 17 years ago

Create two new win32 VMs from win2k3sp2-ref-vm

Categories

(Release Engineering :: General, defect)

x86
Windows Server 2003
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Unassigned)

References

Details

Can you please create a new win32 VM, called moz2-win32-slave2.build.mozilla.org? Note: while the usual linux VM has three disks 9.7gb/20gb/15gb, can you pls create this new VM with slightly larger 3rd disk of 30gb? ie create 9.7gb/20gb/30gb disks?
Actually, we need two VMs. Can you also create a moz2-win32-slave3.build.mozilla.org same as above?
Summary: Create new win32 VM from win2k3sp2-ref-vm → Create two new win32 VMs from win2k3sp2-ref-vm
Assignee: server-ops → mrz
Whiteboard: pending bm-vmware03
moz2-win32-slave02 IN A 10.2.71.118 moz2-win32-slave03 IN A 10.2.71.119
Boxes are up on the ESX 3.5 server with updated vmware-tools. I haven't ever created the extra drives - that's been something you guys have done so I'll leave that for you. Create the drives on netapp-d-fcal1.
Assignee: mrz → nobody
Component: Server Operations → Release Engineering
QA Contact: justin → release
For both of these VMs, I've added the additional drives. Each slave now has 9.7gb/20gb/30gb drives, created on netapp-d-fcall. I've also verified that the independent checkbox is unchecked (see details in bug#425291). mrz: does it look ok, or did I miss anything? Just want to sanity check before we start doing work on these VMs.
Whiteboard: pending bm-vmware03
mrz just gave these a once over, all looked ok. Talked with mrz and nthomas about next steps in terms of setup for NTFS vs FAT32. I've now formatted up both of these machines as follows: C: NTFS (9.7gb) D: NTFS (20gb) E: FAT32 (30gb) F: cdrom Closing this bug. Bug#431755 tracks installing rest of toolchain and buildbot.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
The CDROM really breaks vmotion - do you really need it? I ran into quite a few that had an attached ISO that I had to remove before vmotion would work.
(In reply to comment #6) > The CDROM really breaks vmotion - do you really need it? > I ran into quite a few that had an attached ISO that I had to remove before > vmotion would work. Nope, no need for CDROM, so feel free to remove if that makes your life easier. The cdrom has always been in the refimage historically, but as bhearsum pointed out in email, we can always add it later if we ever find a situation where we need it!
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.