Is there any easy way to migrate from aws x64 to arm arch? like without configuring a new arm based server and installing packages and file? it is currently running with Amazon linux AMI, we wish to change it to Amazon linux AMI 2.
I just wanna know if there is some tool/method to proceed with this.
Do dual CPUs on a modern server actually provide redundancy? If one fails can the server be rebooted and run on the remaining CPU?
In the past I have come across the case where CPU 0 always had to be present so if CPU 1 had failed it would reboot fine but if CPU 0 failed you had to physically swap CPU 1 intyo the cpu 0 socket. I would hope this restriction is no-longer present in modern dual CPU servers but wanted to confirm that.
I have actually been told by HP that dual CPUs do not offer any redundancy because they both have to be present but not sure that is correct.
Why is there a /usr/lib and a /usr/lib32 directory but only a /usr/bin and no /usr/bin32 directory on a AMD64 64-bit-install of Ubuntu? If or when Debian/Ubuntu start supporting multi-target-architecture binaries in their ELF's will this directory branching become unnecessary?
I'm searching for good rules of thumb to understand when NOT to virtualize a machine.
For example, I know that a fully CPU-bound process with near 100% utilization is probably not a good idea to virtualize, but is there any sense in running something which leverages the CPU most of the time a "substantial amount" (say 40 or 50%)?
Another example: if I virtualize 1000 machines, even if they are only lightly or moderately utilized, it would probably be bad to run that all on a host with only 4 cores.
Can someone summarize hints about virtualization based on machine workload or sheer number of guest machines when compared to host resources?
I typically virtualize on Windows hosts using VirtualBox or VMWare, but I'm assuming this is a pretty generic question.
My primary question is in the title, and can be answered as simply as that. However, I think some background information may be relevant.
I'm doing some research into upgrading one of our three year old Dell PE 1950's to be a heavyweight (for a 1U) DB server. The CPUs are currently two entry-level Xeon 5110s (1.6 GHz, Dual Core, "Woodcrest" family).
I've been researching and pricing OEM parts in the Xeon 5400 (2.0 to 3.4 GHz, Quad Core, "Harpertown" family).
In the course of this research I've learned that there are two steppings: C0 and E0, however I can't find many plain-English specifics as to what is different, besides their release dates of Nov. '07 and Aug. '08 respectively. All I can see is "XSAVE/XRSTOR instructions were added", but what does that mean for my needs?
Normally I'd just not care and get the E0 to play it safe because it's the latest & greatest for this family of CPUs. However, I have found some rather significant pricing differences between the C0 and E0 steppings as shown here:
Model Speed (GHz) E0 USD x 2 C0 USD x 2 E5405 2.0 570 560 E5410 2.33 740 520 E5420 2.5 860 1020 E5430 2.66 1020 1010 E5440 2.83 ? ? E5450 3.0 1560 1580 X5450 3.0 ? ? X5460 3.16 N/A 1020 X5462 2.8 1160 1120 X5470 3.33 1420 N/A E5472 3.0 ? 1430 X5472 3.0 ? 740 ** X5482 3.2 ? 1620
? = Could not find price from "reputable" vendor, yet.
Prices are for two CPUs
Note the cost of the C0 X5472, $740 -- the equivaent of the E0 E5410.
Now, until I priced the X5472 I was leaning towards the E5410 or E5420. However I'd be foolish to ignore the C0 price anomaly.
I'm not going to ask for a recommendation, but I would like to know if that is a misleadingly low price.