• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Resource Allocation, CPU

Y

YeOldeStonecat

[H]F Junkie
Joined
Jul 19, 2004
Messages
11,330
Recent "P2V" product...original server was SBS2K3 running on an old Dell PE600, original P4 2.4 or 2.6 or something. ESXi on donated Proliant ML350 G3 with a Xeon 2.6.

The P2V went well last night. She is a will remain the only guest virtual machine on this box. Question about the CPU resource allocation, by default ESXi left it at a limit of 1315 MHz. I figured it was prepared to split the CPU for a 2nd guest VM. Based on that assumption, I put a check in the box for "Unlimited". Good move? Did it matter? Did it hurt?
 
If it's the only guest on that box, allowing it unlimited resources is fine. It does seem a waste to only have the single guest on his box. Is there a reason you went through with the p2v to get it as a vm, when you only intend to run the single guest?
Posted via [H] Mobile Device
 
My intention of doing this "P2V" project was a method of moving their server to newer better hardware.

It's a non-profit organization, thus cannot afford oodles of a consultants rate.
They are a wide area network.
With Microsoft Small Business Server...doing a SwingIT migration, or a complete rebuild, all of those would have taken a huge amount of time....with 45-ish workstations 'n laptops locally and in 6x remote offices 'n courthouses.

Old server was a piss poor old Dell server PowerEdge SC600...basically a glorified Dimension desktop....pair of IDE hard drives in software RAID1, etc.

I basically took the ESXi approach as a way to "bare metal move" the server to newer faster more server grade server hardware. The donated Proliant server ML350 G3 with 6x 10k SCSI drives RAID 5, more RAM. So yes it will be the only guest on this physical machine.

Basically took a whole 6 hours from start to finish..started at 330pm yesterday afternoon, the Convert to V client took about 4.5 hours to complete, my dorking around for another hour...she was up and in production by 9pm.. Versus a couple of days if using the old fashioned approach of SwingIT or fresh rebuild or some other migration technique.
 
You must log in or register to reply here.
Back
Top