The Register Home Page

back to article Nine in 10 VMware customers eye the exit as licensing bills bite

Nine out of ten respondents to a survey of VMware customers say higher licensing costs were prompting them to consider alternatives. Unisphere Research surveyed 269 executives, managers, and professionals at VMware user organizations between December 2025 and February 2026. The study, commissioned by third-party support provider …

  1. Anonymous Coward
    Anonymous Coward

    I'm shocked, shocked I tell you.

    1. Anonymous Coward
      Anonymous Coward

      By 2029 Broadcom will have bought Oracle out of Chapter 11 Bankrupcy and will be on a rinse and repeat cycle.

  2. Anonymous Coward
    Anonymous Coward

    We've already migrated one site from VMware to Hyper-V, another is due for a hardware refresh early next year and that will also move away.

    1. druck Silver badge

      Hyper-V? You really thing Microsoft is going to treat you any better over the longer term?

  3. MattieD

    Giving up revenue

    I was - and still am - genuinely surprised that Broadcom wants rid of all it's SME customers.

    Ok, individually they're not bringing in massive amounts of money, but we're probably talking of tens, if not hundreds, of thousands of customers worldwide who are (or rather, were) quite happy to throw thousands of dollarpounds each at Broadcom for licences. All that adds up to a serious amount of money.

    I would have thought that the money-obsessives MBA bellends at Broadcom would want to extract every penny possible (those yachts don't come cheap, you know), and the costs for developing the lower tiers of the platforms can't have been that much when compared to the revenue it brings in.

    Like everyone else we've spoke to in our industry we're going to move over to Hyper-V. Not because it gives us any additional features or benefits, but because Broadcom will be massively increasing our licencing costs (and Hyper-V comes as part of our Microsoft licencing agreement so there's no additional costs). We've yet to get our renewal yet, but we've heard of several instances where the increase was 800% or more.

    1. Anonymous Coward
      Anonymous Coward

      Re: Giving up revenue

      Not surprised at all. My company is going in a similar direction.

      Many small companies consume more resources than they pay for.

      It is a mistake for Broadcom because they need to train people in their products, but in general, medium term, you can't give the same service.

      But of course Broadcom just squeezed a decade or two of profits in a couple of years. Strip mining, recover the investment, and sell or keep in a diminished capacity.

      1. This post has been deleted by its author

      2. Doctor Syntax Silver badge

        Re: Giving up revenue

        Medium term? What medium term?

        1. spireite Silver badge
          Mushroom

          Re: Giving up revenue

          To be fair, to communicate with VMware soon will require a medium because it will be dead.

    2. NewModelArmy

      Re: Giving up revenue

      .....but because Broadcom will be massively increasing our licencing costs (and Hyper-V comes as part of our Microsoft licencing agreement so there's no additional costs)....

      So far.....

      It will not take long before Microsoft cotton onto the Broadcom attitude in that, where are you going to go otherwise, or there is more money to be made.

      1. AtomicDog

        Re: Giving up revenue

        ...or the competition authorities finally slap them down for their continued MO of using product bundling to unfairly extend a monopoly in one product into adjacent areas...

    3. Doctor Syntax Silver badge

      Re: Giving up revenue

      "we've heard of several instances where the increase was 800% or more."

      With hikes of that magnitude they make their money screwing the big customers. Cut costs as much as possible. By the time the biggest and, presumably, lies agile customers have gone, pull down the shutters and count the profit.

      "Hyper-V comes as part of our Microsoft licencing agreement so there's no additional costs" Yet.

    4. spireite Silver badge

      Re: Giving up revenue

      Actually, what Broadcom has done - by hiking prices - has benefitted their smaller customers, and SME customers.

      When the prices hiked, said customers looked at the price, looked at the alternatives and likely found two things.

      1. They never realised how much VMWare was costing them pre-Broadcom hikes, because someone just signed the POs without reviewing. They then realised it wasn't value for money on their old costs, let alone 'new' renewal costs.

      2.Finances aside, they realised that they were underutilising it anyway.. The price rises just shone a light on it.

  4. BassX

    We're in the process of moving away from VMware. Used to love the product, but Broadcom is actively working to gain every short-term penny they can. Long term I can see VMware disappearing totally, even the customers who are sticking with them for the time being aren't going to tolerate 300-1000% price increases forever. But that's a "someone else's problem" situation for current execs who'll cash in and check out before that happens.

  5. williamyf Silver badge

    Migrating is not so easy

    1.) VMware had (and still has) a lot of goodies on vSphere that were (and some still are) not on competing products. If your Virtualization strategy depended on any of these, migrating is hard.

    2.) Take point #1 and multiply by 20x if you have (private/public/hybrid) VMware Cloud Foundation.

    3.) If you were a single-virtualization or single-(private)cloud vendor based shop, you probably want to migrate to a multivendor stack as part of THIS migration, so that, if one of your new vendors goes rogue (just like VMware/Broadcom did) you are not trapped again. This complicates even more the migrations, as, you will need to handle a multivendor environment, and more so, for a while you will have to juggle 3 (or more) vendors (WMware + at least other 2)

    4.) For ages, before the Broadcom acquisition VMware was a model citizen. And for many years in the early era of virtualization, VMware was THE ONLY CREDIBLE virtualization/(private)cloud option. Which means everyone certified agaist them. HW vendors (mostly for the type 1 hypervisor), OS vendors, ISVs, commisioned bespoke SW, you name it . Before the migration, you need to make sure all your workloads are certified on your alternatives. This is 4x valid for purposes of regulation, certification, compliance, and (cyber) insurance

    Is a very complex issue. For many an organization is not as simple as "I migrated the VMs in my homelab in an afternon so how hard can it be?". And the timelines are heavily compressed so that adds even more risk, complication and stress to the whole thing...

    ---

    *** Suerte a todos y Feliz dia!

    1. Doctor Syntax Silver badge

      Re: Migrating is not so easy

      "If your Virtualization strategy depended on any of these, migrating is hard."

      Broadcom PoV: that's their problem.

    2. Anonymous Coward
      Anonymous Coward

      Re: Migrating is not so easy

      Pretty much all of this, cost of license is a fraction of the overall migration cost.

      The real cost is getting a handle of all your apps, checking they have owners and proper support (lost count of the number of apps where the vendor has gone bust or they don't have install media), if they can be moved to cloud or better still decommissioned and minimum moved to supported OS (I am sure most of us have apps running on unsupported OS), making sure they are certified on your new platform (how many vendors have heard of alternatives to ESX), dual hardware, migration downtime, etc

      However the good news is that you should end up with fewer apps, a good handle on your apps which should hopefully now be fully supported and modernised and running refreshed hardware.

  6. Pascal Monett Silver badge
    WTF?

    Brilliant move, Broadcom

    Investing so much money in a top-tier product with thousands of satisfied customers just so you can treat it like a sex doll, extract unreasonable amounts of money from it (aka fucking it dry) and turning all those paying customers away.

    Honestly, I would really like to hear what your Board's plan was for this acquisition in the first place. You had no product in this market, therefore there was no competition argument. You are not creating a new product to compete with it. You're basically just killing it off.

    Why invest so much just to kill the product ? What was VMWare doing to you that justified this action ?

    1. Sproggit Silver badge

      Re: Brilliant move, Broadcom

      If you look at history, the actions of Broadcom's board with respect to VMWare make perfect sense.

      They previously used the exact same playbook with e.g. CA Technologies and with Symantec Enterprise Security. Their playbooks to date all seem to include some version of a "Product Bundling Simplification", which stops users from buying individual product elements and instead forces users in to larger, comprehensive suites. They argue the suite is more feature rich, but having to pay for features you don't use is of little benefit to most customers.

      They have also altered billing metrics to extract higher revenues from top-tier clients, while actively shedding less profitable mid-market or small-business accounts. There is a clear and consistent calculus visible in their actions, where they seem to be considering "revenue earned" against "cost of generating revenue". The line is not visible, but there is clearly a threshold in there somewhere below which Broadcom simply aren't interested in moving product. It's all about keeping their operating overheads lower by allowing them to employ the absolute minimum number of staff.

      They also "pull fast ones" when it comes to the billing approach - for example by shifting from a "per CPU" metric [per physical CPU] to a "per Core" metric, which generated massively more revenue from customers who were using e.g. Threadripper machines with high core counts as a way of consolidating their costs.

      The reason I think this is set to continue is thanks to the results:-

      https://www.networkworld.com/article/4053783/broadcoms-vmware-strategy-pays-off-financially-but-customers-not-as-keen-as-wall-street.html

      Prior to the exodus, Broadcom saw their VMWare strategy raise the operating margin to 77%. That's pretty much unheard-of territory, even for a mercenary software provider.

      Unfortunately, for customers, the other thing that Broadcom have been doing is through their selection of acquisition targets... When they went after and obtained VMWare, it was the undeniable market leader, with a deep and wide moat around the core business. That made it much harder for competitors to take market share, which left customers with fewer choices and it gave Broadcom the captive market they wanted to act in the way that they do.

      It's worth noting that the "VMWare Story" is not Broadcom's first Rodeo. It's very much a "Rinse & Repeat" iteration of something that has worked before. Unless or until their are either stopped [unlikely] or their strategy bites them in the rear and turns an expensive acquisition in to a big financial mistake, they are just going to keep doing this.

      They have become predatory corporate raiders in the tech world.

      Avoid at all costs.

      1. Anonymous Coward
        Anonymous Coward

        Re: Brilliant move, Broadcom

        Living the (Corporate) American Dream !

    2. Doctor Syntax Silver badge

      Re: Brilliant move, Broadcom

      "Honestly, I would really like to hear what your Board's plan was for this acquisition in the first place."

      You don't need to hear it. You just summarised it in the first paragraph. The key bit was "extract unreasonable amounts of money".

  7. billdehaan Silver badge

    Everything old is new again

    I worked with a multinational whose IT and IS departments were almost comically inept. It was quite common for them to show up at an employee's desk for a service call with replacement parts for a laptop, only to be shocked to see that employee had a desktop computer. They'd then say they couldn't service the computer because they'd stopped buying replacement parts for desktops because "everyone has a laptop". The actual percentage of laptops in the company was about 15%, mostly IT, VIPs and management. Naturally, IT considered it was the employee's responsibility to tell them what computer they had. After all, it's not like IT departments are going to inventory what computers are in the company, are they?

    The standard response was "it's a good thing we're not a technology company, or this would be embarrassing". It was, in fact a technology company, or at least it was considered itself one.

    Naturally, when AWS and the like appeared, IT salivated over it, because it would solve all these problems of them not knowing what was deployed anywhere. They quoted deliriously low operating costs to replace costly desktops with centralized servers, and management bought into it completely.

    Before I left the company, a department needed to certify a build machine. In order to meet auditing standards, the software had to be built on a known baseline that had run and passed a validation suite. The suite was automated, and it only took about a day to run. However, an external auditor had to sign off on it, which took several weeks, and cost a huge amount of money. Any change to the system required re-certification. And since the system was running Windows 10, the operating system changed pretty much every Tuesday when IT applied patches. How could they maintain a certified server?

    My recommendation was to make a VM image of Windows 10 and the development tools, disable networking so it was air gapped, certify the image, and have users use that image to do their final builds was rejected by IT as too complicated for end users. They proposed setting up an AWS zone of a dedicated machines that would be air gapped from the internet, and everyone could remote into it, none of that silly local VM package management I was proposing. Management agreed that this was a much better solution than mine.

    Besides, my solution would have cost $5K for a server machine, plus the licencing cost for Windows and other tools in the image for 35 users, so the total cost would be almost $8K. That would strain the department budget, because they'd not allocated anything for this, it was coming out of overhead.

    How much will the AWS solution be, by the way? Well, the upfront cost of licencing would be $2K (sigh of relief from management), setting up the zone would another $2K (worried faces from managers), and then about $1500 a month after that. So $22K for the first year, but only $18K for every year after that.

    So the anticipated five year project would be cost just under $100K in IS fees, compared to the "outrageous" one time $8K cost of my proposal.

    My last day at the company was the day that the IS director told management that he was refusing to allow the purchase of the $5K server I'd proposed, and they had to go with AWS, as per corporate direction.

    Two years later, I ran into a friend who still works there. He told me that the company is scrapping the AWS virtualization project almost entirely. The anticipated savings of $20M over five years apparently never materialized, and in fact it cost them almost $10M more in increases. Much to management's surprise, of course.

    When I mentioned that I'd told them that at the beginning, he drily said "Why would they listen to you? You had nothing to base that on other than decades of experience costing out projects like that in the past".

    I'm not really surprised to see the same reaction industry wide. VMs are a great solution for a lot of problems, but they aren't the silver bullet to solve all problems, like a lot of management seem to believe.

    1. Anonymous Coward
      Anonymous Coward

      Re: Everything old is new again

      This was explained to me in a way I could understand.

      Every budget is a little pot of gold.

      Each has an owner.

      They each want to keep as much gold as possible

      1. billdehaan Silver badge

        Re: Everything old is new again

        Oh, it absolutely is. There was a Dilbert cartoon about the PHB rejecting a proposal that would save the company $2M a year for a one-time expense of $20K, because the $2M would be company wide profit, but the $20K came out of his budget. I've seen that happen in a dozen companies or more.

        One company was paying $10 a minute for connect charges, and spending on average an hour a day on it, so $300/week, $1200/month, so between $10K and $15K a year for the service. The proprietary modem device was about $500. The next generation modem was $2K, but it ran 8 times faster at the same connect charge rate. So for $1500 more, the connect charges would be dropped to between $2K and $3K.

        You'd think spending $1,500 to save $8K to$12K a year would be a no-brainer, but no. The manager shut it down with the explanation that the modem was capital equipment, which came out of his budget, while the connect charges were overhead, which didn't come out of his budget. So he spent between $8K-$12K a year, recurring (for at least five years), to save his budget $1500.

        Yes, we ran it up the flagpole to senior management. Their reaction was "that sounds like a really good idea that would save a lot of money. Discuss it with your manager" (the one who'd already said no) "and if he agrees with it, we'll go forward". He didn't, so they didn't.

    2. Doctor Syntax Silver badge

      Re: Everything old is new again

      Why would they listen to you? You had nothing to base that on other than decades of experience costing out projects like that in the past".

      Alternatively they didn't listen to you because you earned much less than the IS director and your opinion was, therefore, that less valuable. If a reassuringly expensive consultant had told them the same thing as you did it might well have been adopted.

      1. billdehaan Silver badge
        Happy

        Re: Everything old is new again

        As a contractor, I routinely earned more than my management chain.

        Often, when I subbed for a manager for whatever reason (parental leave, medical leave, LOA, in rehab, whatever), senior management would discover I'd done a better job, and offer me a position in management, sometimes higher than the current boss' position. I wasn't interested because I wanted to remain technical, but also, I found I was already making far more as a coder contracting than I would have made as a full time manager or senior manager.

        But in general terms, you're right about advice be considered based on what it cost. I once did a competitive vendor evaluation that the company then distributed to the various vendors. These were the criteria we used to rank vendors, here is where you placed in each category, here are the areas you excelled, here are the areas you were weak, here are reasons you were disqualified, that sort of thing. The 3rd, 4th, and 5th place vendors were all thankful for the advice. The 3rd place vendor actually flew up an exec and a tech from California to Toronto to take me out to dinner and pick my brains, basically asking "what did we need to do to win".

        The 2nd place vendor, however, wanted nothing to do with my evaluation. They said the company was foolish for not hiring them, that they were the biggest name in the industry (and at the time, they arguably were), and that they didn't need to waste time looking at some "low level coder's idea of why our award winning company isn't up to his standards".

        A year later, they'd plunged from something like 80% of the market to under 15%, and they were losing clients by the day. In a panic, they hired a high priced consultancy firm (like Gartner Group for the specific industry). That firm spent two months doing an analysis. The vendor was charged somewhere between $50K and $100K for the analysis, which recommended... exactly what I'd said a year earlier, for free.

        Oh, they said it better, of course. I'd just typed up 8 pages of text and stapled it together. Theirs was almost 100 pages, in a leather bound binder, filled with lots of colourful graphics. It was really professional looking. And it went into much more detail than I had. I'd only looked at the tech side; they'd also looked at market trends and other issues.

        But ultimately, they made almost exactly the same recommendations I had. The three differences between us were that (1) it was now a year later, so the vendor had nowhere near as much time to course correct, (2) I have the advice for free, the firm charged $75K-ish, and (c) the vendor not only ignored my advice, they mocked it, while taking the exact same advice seriously when they were charged for it.

        If I'm charitable, I'd say that one of the reasons they took them seriously while not taking me seriously was that when I told them, they were at the top of the market, and a year later, they'd crashed and burned (as I'd predicted), so my "doomsday scenario" wasn't fearmongering any more, but history they'd lived through.

        But no, I'm not that charitable.

        1. Sproggit Silver badge

          Possible Lucky Escape

          I have two experiences of trying to approach a selection process in the way you described the competitive tender process.

          One was indeed for a competitive tender, to migrate an organization with about 2,500 employees from a legacy, proprietary network across to one based on open standards, Ethernet and Cat-5 premises cabling [so: a while ago!] that went back to the main backbone via a hub-and-spoke model with 62.5um multimode. The other was an attempt to hire in to a critical role for a Team Lead, where I was looking for someone with deep technical skills, management and decision-making ability but also that rather difficult-to-define "leadership" quality.

          The technical tender had quite a lot of criteria, which we weighted and scored using a loose approximation of the Kepner-Tregoe "Decision Analysis" methodology. The hiring process was based on an all-day workshop with all candidates together and a series of scenarios - all based on real-world experience - that had them interacting and solving problems as well as interviewing with key stakeholders.

          The effort to do both of these exercises was immense: nobody asked me to put in the hard yards, but I was the key stakeholder in both cases and wanted to do everything in my power to get to the right decision. As each exercise drew to natural conclusions, the work that I'd done naturally created the sort of SWOT feedback/analysis that you describe here, so I prepped up a series of letters and prepared to send the feedback to the companies and candidates that had been involved in the exercises [exercises performed in two different companies, maybe 5 years apart].

          I was prevented from sending out content on both occasions. HR blocked my attempt to give feedback to the candidates and a more senior manager blocked the technical feedback. In both cases their justification was a concern that by communicating *anything* beyond, "sorry, but you have not been successful on this occasion" that I would unwittingly open the company to a lawsuit. In the case of the HR block, I had enough seniority and a good enough relationship with our HR Team that I was able to get time with the chief recruitment officer and ask them to walk me through their decision to help me understand their point of view. They explained that in their view, hiring decisions ultimately come down to one of subjective opinion, gut instinct [if you've ever read that missive on hiring by Steve Jobs, you'll have the essence of HR's concern]. Their point was that because the decision implicitly included subjectivity, providing feedback - no matter how clinical or objective - would be to open the company to a lawsuit alleging discrimination, bias, or a flawed selection process. Their position was [and to my knowledge remains to this day] the view that no candidate for a job should ever be given feedback on why they were unsuccessful.

          For the record, I respect and admire what you did and I think you did the right thing. If we had been so nervous of giving feedback because we felt an unsuccessful candidate might sue, the strongest possible grounds for that would have been because we made a subjective, biased and clearly flawed decision. I started out with the view that if I wasn't confident enough to stand behind the hiring decision I made, I should not have sent out an offer letter. I was vetoed, I guess, because we live in litigious times.

          To be balanced, I've also seen the same responses you described... I once had accountability for a Team that performed "Third Party Oversight" of technical suppliers - companies like telecommunications providers that gave us site-to-site leased lines. We took a new supplier through a TPO review and based on the nature of their contract, our internal controls stipulated that we should conduct a deep, on-site review every 24 months and a simpler, email Q&A review in the alternate years. After our first visit I got a call from their CIO to ask if we would mind terribly giving them the "full review" on an annual basis - *because they found it so useful*. Sadly, these are the exceptions, not the norm.

          But kudos to you for delivering such a powerful set of analysis. Until you've run something like that yourself, it's hard to grasp just how grueling it can be, or how the hardest parts can be working to remain fair and impartial to all participants over what can turn out to be an extended period of time.

          If more people and companies acted with your diligence, we'd have far fewer cowboys and fly-by-night outfits in this industry.

          1. billdehaan Silver badge

            Re: Possible Lucky Escape

            To be fair, I have to give credit to my team and my team lead for that. We had a four phase evaluation process, and there were numerous subsystems, like networking, security, legal compliance, user representative, software, hardware, etc. I was the software guy.

            In the first phase, every team had to agree that the vendor's offering could do what we needed. As my team lead put it, "nobody can say yes to a vendor, but any of us can say no".

            The vendor the user thought was the clear cut winner would be cut if legal said it didn't meet Canadian compliance standards (many vendors were American or European). I could say a vendor was the best, but if the security team rejected them, that was it. I cut a few out for not meeting the software requirements. Only about 20% of the vendors made it to the second round.

            The second phase was trimming the remaining vendors down to five, so the team did an analysis of all the collected data, and prioritized the vendors that stood out.

            Phase three was longer, and more difficult. It meant installing, and testing, each vendor's offering in a local environment. The users still ran the main system, but they could kick the tires of the vendor's offering as well. It didn't have access to our real data, but we could test real world problems with it. That's when the warts started to show, and several vendors bailed out at that point.

            In the end, there were five vendors standing. That's where the scoring came in. Each subsystem had defined their own criteria. I'd defined 8 criteria, the networking guy had only defined 4, the legal guy had over 30, of course, etc. Based on that, we selected two front runners, who would install their products and run live for a month (in parallel with the legacy system, of course).

            My analysis writeup for phase three was internal, but the vendors knew the process, and a couple asked for a copy. I was given permission to give tailored subsets out. I had to strip out all confidential information, of course, and vendor A only got the scoring for his product, with all references to competitive vendors being anonymized, with the exception of cases where the vendor was the only one to exhibit a positive or negative. "Vendor A's XYZ feature in their API was found to make development of widgets for $FUNCTION a one day job, making it a standout", that sort of thing.

            There weren't any legal issues regarding confidentiality. Our choosing process, and the criteria used, had been made public in the tender. Copies of it were given to all of the bidders ahead of time. This project would be in the tens of millions of dollars over the years, and we wanted to cull the number of bidders up front. And since there was a considerable cost to the bidders, we wanted to make sure that no one who was disqualified would have any grounds for a (potentially legal) complaint that the disqualification wasn't warranted.

  8. Sproggit Silver badge

    For EU Customers...

    ... it might be worth taking a look at Proxmox. It's a FOSS project, based on Debian platforms. It integrates clustering, high availability, software-defined networking, storage management, backup and restore, a distributed firewall and live migration.

    It's been around since 2005, it's written in a combination of Rust and Perl... and the company behind it is based in the EU.

    There are lots of other solutions, of course. But perhaps one advantage of picking a locally-optimum destination solution and then migrating all existing VMWare implementations over is that you start to build experience of the migration process: the round-the-edges customizations start to fall in to patterns for which you will build or have solutions.

    But if there's one thing I've learned from doing similar migrations in the past [like for example migrating from the then BEA Weblogic to IBM WebSphere AS or between Oracle RDMBS and first UDB, then MySQL and finally on to MariaDB] it's the value of sticking as close to "international standards" as you possibly can. The temptation to leverage bespoke local features is high - often they solve real business problems. The downside is they effectively cripple your portability and lock you to a specific platform.

    The closer you can stick to a single, simple approach, the better. And the closer that single approach sticks to industry standards, the better.

    1. Anonymous Coward
      Anonymous Coward

      Re: For EU Customers...

      "it might be worth taking a look at Proxmox."

      We have extensive FC SAN where VMware hosts share the VMFS formated storage LUNs. Last time I looked, there wasn't any such supported solution from Proxmox. Have things improved?

      1. Doctor Syntax Silver badge

        Re: For EU Customers...

        When the situation is A does B in way C the correct question isn't "does D also do B in way C?" It's "does D have a solution for what we use B to do?"

        It makes the difference between being locked in and being flexible.

    2. Oneman2Many Bronze badge

      Re: For EU Customers...

      Proxmox is fine for homelabs. There is virtually no 3rd party support, missing a ton of features compared to VMWave, immature management, very few COTS companies support it (that shouldn't be a big issue, it uses KVM/VirtIO), you can't easily buy support and where you can it makes it as expensive as anything else and no enterprise is going to use critical infrastructure without support.

      Though as you say there are plenty of other options available.

      1. Sproggit Silver badge

        Re: For EU Customers...

        You picked up on the key point I wanted to convey: that there are options out there. Just because VMWare holds such a huge market share does *not* mean that other offerings lack the functionality needed by most users.

        As to enterprise suitability... I see your point and I agree that it's worth underlining the need for diligence. Proxmox do offer commercial, enterprise support tiers, up to and including global, 24x7 support options, but I don't have experience of the quality or level of service that provides.

        I hope we'd agree that as companies scale in size, so their need to conduct due diligence - and their ability to do so effectively - tend to move along in the same rough formation over time. Medium-to-large enterprise customers - say anything from the low thousands of employees upwards - really ought to have the budget and/or in-house resources to conduct the sort of diligence you advocate. And the really big enterprise players probably have the resources to offer their own in-house expertise, especially if virtualization is a key part of their technology architecture.

  9. spireite Silver badge

    At this rate....

    VMWare will be regressing to VapourWare

  10. rwbthatisme

    vDisaSphere indeed 2027 is most probably when I will say goodbye to to vmWare, off to hyper-v

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon