RE: Timeline for EOS HMC x86 -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

vHMC running on x86 will continue to be supported. Only the HMC running on x86 hardware as an appliance will be withdrawn. IBM is keeping support for the vHMC on x86 as they do not have to do any testing of hardware.

From: Roberto José Etcheverry Romero<mailto:yggdrasil.raiker@xxxxxxxxx>
Sent: Thursday, July 4, 2019 9:45 AM
To: Midrange Systems Technical Discussion<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Timeline for EOS HMC x86

I'm still wrapping my head around this. The vHMC was a blessing for mid to
big customers that already had a vm server farm. But now we are back to
"buy my hardware or else". It's not exactly easy to have a secondary Power
server available to run the vHMC for POWER and even then, I'm betting it
only runs on p8+ machines (due to endian-ness) so no chance of giving a p7
machine another life. And the final point. Unless using the physicial POWER
HMC, you get into the chicken and egg situation where you have to very
carefully configure the LPARs to autostart and not be dependant on
anything, otherwise a full blackout will mean you lose your vHMC...
IF the ASMI/FSP had a barebones LPAR management interface, like ESXi's
interface (You might be using vCenter to manage your server farm, but you
can still connect to each host and start a VM), I would go with vHMC for
POWER. As it is, I don't see the point.

On Thu, Jul 4, 2019 at 6:33 AM Jack Kingsley <iseriesflorida@xxxxxxxxx>
wrote:

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.