The VMWare host has a single 2ghz quad-core proc and 16gbytes of RAM. The original box that the file/printer server was and now is again running on has a single 2.8ghz HT Xeon with 1g RAM.
We used the VMWare converter to virtualize the box, but the virtualization seems not to be the issue, as it happened again after I reverted to the original box. Kurt On Mon, Mar 30, 2009 at 16:52, Joseph L. Casale <[email protected]> wrote: > I was just typing the same thing, I think he meant the original physical > server had 1 proc/1 gig ram, not the esx host. > How did the OP virtualize it? What method did you use? > jlc > > > > From: Jonathan Link [mailto:[email protected]] > Sent: Monday, March 30, 2009 5:48 PM > To: NT System Admin Issues > Subject: Re: Virtualized server issue... > > > > Lemme see. How many cores on that proc? 1 GB physical RAM on host with the > (only?) guest allocated 2 GB? While it is possible to overcommit memory, > that only has a benefit in a multi-guest environment, where ESX can share > common memory pages between different guests running the same OS. IME, > Windows generally likes to grab that first GB for the OS if it thinks it's > available. Unfortunately, it's not available in your case, since you have > some overhead for ESX. Try dropping it down to 768 or 512. What did ESX > recommend for the guest? You might even want to start with that. > > > > In my (limited) experience there's almost no reason to allocate more than 1 > virtual proc to a guest, unless some application on that guest requires > multiple processor. IIRC, that's a VMWare best practice. I certainly > wouldn't see a need for dual procs in a file/print server. How many cores > on your processor? > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
