4 ms·
> you're using a supported and exact version of the hypervisor and associated tools Having exact versions is not a problem (any version of RHEL guests are supp
by bonzini 3y ago
> you're using a supported and exact version of the hypervisor and associated tools
Having exact versions is not a problem (any version of RHEL guests are supported on any RHEL hosts past and future, almost). Plus Windows, ESX, Amazon and Google clouds, and a few more.
Rather, the problem is having _up to date_ versions; with RHEL you can often ask the customer to reproduce on an up to date host if possible, with other distros the support machinery isn't there and you need someone to talk to at the cloud provider, so that they can debug stuff that breaks only in their environment and can't be reproduced. Otherwise you cannot guarantee the level of support that you mention. Very few cloud provider can provide that, I am not even sure that IBM's cloud made the short list.
- XorNot 3y agoIsn't long term support Red Hat's thing? The ask isn't to support some random system, it's for RH to put out an official image and distro they support on cloud providers and bake the licensing costs into the hourly runtime fees. This is exactly how you consume Windows on AWS and it's a huge incentive to do it that way because it takes licences management out of consideration.
- bonzini 3y agoThe cloud provider is also running software, the cloud doesn't run on magic dust. Red Hat doesn't supports RHEL on your blood if they don't believe they can trust you to help supporting RHEL, the way their customers expect. The easiest way is to run RHEL as the bare metal OS but it's not the only way. > This is exactly how you consume Windows on AWS and it's a huge incentive to do it that way because it takes licences management out of consideration. It's also how you consume RHEL on AWS, GCE or Azure.
- bonzini 3y agoBlood -> cloud of course.