VMware v. Cirba: Four-Patent Cloud Virtualization Dispute Settled After 4+ Years
VMware, Inc. brought an infringement action against Cirba, Inc. in Delaware federal court asserting four patents spanning cloud aggregation, distributed resource allocation, and virtual container scheduling. After 1,577 days of litigation, the parties reached a settlement and stipulated to dismissal with prejudice — each side bearing its own costs.
VMware’s Four-Patent Virtualization Enforcement Action Ends in Settlement
On 25 February 2020, VMware, Inc. filed suit against Cirba, Inc. in the District of Delaware before Judge Gregory B. Williams, asserting infringement of four U.S. patents — US9379995B2, US10261842B2, US10025638B2, and US9766945B2 — covering technologies central to multi-cloud aggregation, distributed resource allocation, virtualized environment management, and container migration scheduling. The accused products place Cirba’s workload intelligence and cloud optimisation platform squarely within VMware’s core infrastructure IP portfolio.
The case closed on 20 June 2024 via a stipulated dismissal with prejudice after the parties confirmed they had settled. Under the stipulation, all claims and counterclaims — including any defences or invalidity challenges raised by Cirba — were dismissed with prejudice, meaning neither party can relitigate the same claims. Crucially, each party agreed to bear its own legal costs and attorneys’ fees, which suggests neither side extracted a clear fee-shifting concession, a common outcome in negotiated resolutions of this complexity.
At 1,577 days, the litigation spanned more than four years — notably long even for a multi-patent case in Delaware, a court accustomed to complex IP disputes. The extended duration likely reflects the breadth of the patent portfolio asserted, the technical complexity of virtualisation and cloud infrastructure claims, and the commercial stakes involved in a market where VMware and Cirba compete directly for enterprise cloud management customers. The financial terms of the settlement remain undisclosed, and it is unknown whether a licence or cross-licence was part of the resolution.
Filing to Dismissed with Prejudice in 1577 days
1,577 days — roughly 4.3 years, above the median for multi-patent district court disputes
Dismissed with prejudice: what the stipulated settlement means for both parties
Dismissal with prejudice ends all claims permanently
A dismissal with prejudice under a settlement stipulation extinguishes all asserted claims and counterclaims with finality. Neither party can re-file the same claims in federal court. This differs from a dismissal without prejudice, where a plaintiff could theoretically refile. The ‘with prejudice’ designation here gives Cirba certainty that it will not face these specific patent assertions again from VMware on these facts.
Res judicata effect appliesVMware preserves patents; confidential terms likely include licence or payment
VMware’s four asserted patents remain valid and enforceable — Cirba’s invalidity counterclaims were dismissed with prejudice alongside VMware’s infringement claims. While the settlement terms are confidential, the dismissal structure is consistent with Cirba agreeing to a licence or lump-sum resolution. VMware retains the ability to assert these patents against other cloud optimisation competitors who were not parties to this action.
Patents remain enforceableCirba exits with finality but faces unresolved competitive IP risk
Cirba avoided a court-imposed damages award or injunction, but surrendered its opportunity to invalidate VMware’s patents through litigation — a meaningful strategic concession. Any invalidity arguments developed over 4+ years of discovery were abandoned at settlement. Depending on undisclosed licence scope, Cirba may now operate under terms set by VMware rather than as a fully independent competitor in the cloud workload management market.
No public invalidity rulingSettlement preserves VMware’s IP moat in cloud resource management
For the broader cloud infrastructure sector, a confidential settlement — rather than a merits decision — leaves VMware’s patent positions fully intact and untested. Other vendors operating in multi-cloud aggregation, container scheduling, and distributed resource allocation should treat these four patents as live enforcement risks. The 1,577-day duration and the breadth of the portfolio signal that VMware is prepared to litigate virtualisation IP aggressively and at length.
Enforcement risk remains liveFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | VMware, Inc. | Company | Cloud infrastructure and virtualisation software company — holder of US9379995B2 and three further patentsSearch in Eureka ↗ |
| Defendant | Cirba, Inc. | Company | Cloud workload intelligence and optimisation platform provider accused of infringing VMware’s virtualisation patentsSearch in Eureka ↗ |
| Plaintiff counsel | Anne Shea Gaza | Attorney | Counsel for VMware, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Richard S.J. Hung | Attorney | Counsel for VMware, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Robert M. Vrana | Attorney | Counsel for VMware, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Samantha G. Wilson | Attorney | Counsel for VMware, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Yue Li | Attorney | Counsel for VMware, Inc.Search in Eureka ↗ |
| Plaintiff law firm | Young Conaway Stargatt & Taylor, LLP | Law Firm | Representing VMware, Inc.Search in Eureka ↗ |
| Defendant counsel | Adam Adler | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant counsel | Christine E. Lehman | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant counsel | Courtland L. Reichman | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant counsel | Jennifer Estremera | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant counsel | Kenneth Laurence Dorsney | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant counsel | Khue V. Hoang | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant counsel | Michael G. Flanigan | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant counsel | Michael J. Farnan | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant counsel | Wesley L. White | Attorney | Counsel for Cirba, Inc.Search in Eureka ↗ |
| Defendant law firm | Farnan LLP | Law Firm | Representing Cirba, Inc.Search in Eureka ↗ |
| Defendant law firm | Morris James LLP | Law Firm | Representing Cirba, Inc.Search in Eureka ↗ |
| Presiding judge | Judge Gregory B. Williams | Judge | Delaware District CourtSearch in Eureka ↗ |
Official order — verbatim text
The stipulated dismissal language — ‘dismiss with prejudice all claims and counterclaims asserted by both parties, as the parties have settled this matter’ — confirms a bilateral resolution: VMware’s infringement claims and Cirba’s defensive counterclaims (which likely included invalidity and non-infringement) are extinguished equally. The ‘each party bears its own costs’ clause is notable; it suggests neither side achieved a litigation posture strong enough to justify pressing for fee-shifting under 35 U.S.C. § 285. No merits ruling was issued, so no claim construction or validity determinations enter the public record.
US9379995B2 — Multi-cloud facility aggregation and virtualisation management
The four asserted patents span foundational layers of modern cloud and virtualisation infrastructure. US9379995B2 covers aggregation across multiple cloud computing facilities — relevant to any platform managing hybrid or multi-cloud deployments. US10261842B2 addresses resource allocation diagnosis on distributed systems using resource hierarchy, a core capability in workload optimisation engines. US10025638B2 covers the system and method for managing virtualised computing environments broadly, while US9766945B2 targets virtual resource scheduling for containers including migration logic — directly relevant to containerised workload platforms.
Strategically, this portfolio covers the full stack of enterprise cloud resource management: from infrastructure aggregation down to container-level scheduling. The application filing dates span 2012 to 2016, placing them squarely in the period when VMware was building its cloud management platform and containerisation was emerging as an enterprise paradigm. Any competitor offering workload intelligence, cloud cost optimisation, or container orchestration adjacent to VMware’s product line faces non-trivial exposure to one or more of these patents. The Broadcom acquisition of VMware in 2023 adds further weight — Broadcom has historically been an aggressive IP enforcer.
Should your team run an FTO against US9379995B2 and the VMware cloud portfolio?
If your organisation builds or sells multi-cloud management software, workload scheduling tools, container migration platforms, or distributed resource optimisation engines, these four VMware patents represent a material FTO risk. The claims cover not just specific implementations but the broader methods of aggregating cloud facilities, diagnosing resource allocation hierarchically, and scheduling container migrations. Products that perform any of these functions — even as a feature rather than a primary offering — may fall within claim scope.
PatSnap Eureka’s FTO Search Agent allows R&D and product teams to map their technical architecture against claim language across all four patents simultaneously, identify prior art that could support design-arounds, and benchmark against the claim constructions most likely to emerge in litigation. With VMware’s portfolio now under Broadcom’s ownership, proactive FTO analysis is especially advisable before launching new cloud management or container orchestration features into the enterprise market.
Run a freedom-to-operate analysis on US9379995B2 to assess your product’s exposure
Run FTO in Eureka →Similar Cloud Virtualisation and Resource Management Patent Cases in Delaware
Explore related patent infringement actions involving cloud infrastructure, virtualisation software, and container management technology litigated in the Delaware District Court.
Related patent case — similar technology
Comparable case in the same technology domain. Patent holder and defendant reached resolution after proceedings.
SettledRelated infringement action — same court
Comparable Multiple-cloud-computing-facility aggregation-adjacent infringement action. Patent enforcement dynamics analysed in depth.
Active · District CourtRelated invalidity challenge — appellate outcome
Combined invalidity and infringement action in the same technology space. Decided after substantive proceedings.
DecidedVMware, Inc.’s broader IP enforcement history
VMware, Inc.’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat this case signals for the cloud virtualisation IP landscape
VMware’s multi-patent enforcement posture in Delaware sets a clear precedent for how virtualisation IP disputes will play out commercially.
Four-patent assertion strategies amplify settlement leverage in complex tech disputes
By asserting four patents covering distinct but complementary layers of cloud infrastructure — aggregation, resource allocation, environment management, and container migration — VMware created a portfolio pressure that is far harder to design around than a single-patent claim. Companies operating in the virtualisation or cloud optimisation space should audit exposure across all four patents, not just the most prominent.
Delaware remains the preferred venue for enterprise software IP enforcement
This case reinforces Delaware’s role as the go-to jurisdiction for large-scale software patent litigation. Judge Williams presided for the full duration, providing the predictability sophisticated patent plaintiffs seek. For defendants, early invalidity motions or IPR petitions at the PTAB may offer a lower-cost path than enduring 4+ years of district court proceedings before settling.
Confidential settlement terms mask whether Cirba obtained a licence or paid damages
The public record is silent on financial terms, but the ‘each party bears own costs’ clause — rather than a fee award — typically signals a balanced negotiated resolution. Competitors evaluating their own exposure to VMware’s virtualisation portfolio should consider that Cirba’s settlement may have set an undisclosed royalty benchmark that VMware could reference in future enforcement actions.
Container migration and multi-cloud scheduling patents are high-value enforcement targets
US9766945B2 (container migration scheduling) and US9379995B2 (multi-cloud aggregation) represent technology areas experiencing rapid commercial adoption. As containerisation and Kubernetes-based infrastructure mature, these patents are likely to attract further assertion activity — either by VMware (now under Broadcom) or through portfolio transactions. R&D teams building in these spaces should run FTO analyses before product launch.
VMware v Cirba — key questions answered
VMware asserted four patents: US9379995B2 (multi-cloud aggregation), US10261842B2 (distributed resource allocation diagnosis), US10025638B2 (virtualised environment management), and US9766945B2 (virtual resource scheduling and container migration). All four remain valid and enforceable following the settlement dismissal.
The case was resolved by a stipulated dismissal with prejudice filed on 20 June 2024, following a private settlement between the parties. All claims and counterclaims were dismissed permanently. Each party agreed to bear its own costs and attorneys’ fees. Financial terms of the settlement were not disclosed publicly.
Dismissed with prejudice means the case is terminated permanently on the agreed terms. Neither party can refile the same claims in federal court. In a settlement context, it confirms the dispute is fully resolved and that Cirba’s invalidity counterclaims — potentially valuable for the industry — were also abandoned, leaving VMware’s patents unchallenged on the merits.
The case ran for 1,577 days — approximately 4.3 years — from filing on 25 February 2020 to closure on 20 June 2024. This duration is above typical for multi-patent district court cases and likely reflects the technical complexity of the virtualisation claims, the breadth of the portfolio asserted, and the commercial significance of the cloud workload management market.
Yes, indirectly. Because the case settled without a merits ruling, VMware’s four patents were never adjudicated for validity or claim scope. They remain fully enforceable against third parties. Other companies offering multi-cloud management, container scheduling, or distributed resource allocation tools should treat these patents as live enforcement risks and conduct freedom-to-operate analysis accordingly.
Map your exposure to VMware’s cloud virtualisation patent portfolio
With four patents surviving litigation untested on the merits, VMware’s cloud infrastructure IP remains a live enforcement risk. Run FTO analysis and monitor portfolio activity through PatSnap Eureka before your next product release.
PatSnap Eureka searches patents and litigation data to answer instantly.