Red Hat v. VirtaMove (25-1706): Federal Circuit Appeal Voluntarily Dismissed
Red Hat, Inc. and VirtaMove, Corp. jointly dismissed their Federal Circuit infringement appeal covering two containerization patents — US7784058B2 and US7519814B2 — after 211 days, with each side bearing its own costs. The agreed dismissal under Fed. R. App. P. 42(b) leaves the merits unresolved on the appellate record.
Containerization patent appeal ends by mutual agreement at Federal Circuit
Red Hat, Inc. — one of the world’s leading open-source software companies — filed this appeal at the Court of Appeals for the Federal Circuit on 29 April 2025, challenging VirtaMove, Corp.’s assertion of two patents: US7784058B2, covering a computing system that employs user-mode critical system elements as shared libraries, and US7519814B2, relating to a system for containerisation of application sets. The underlying dispute centred on whether Red Hat’s platform technology infringed VirtaMove’s containerisation IP.
The appeal was closed on 26 November 2025, when the Federal Circuit ordered the proceeding dismissed pursuant to Fed. R. App. P. 42(b) — the rule governing voluntary dismissal of appellate proceedings by agreement of the parties. Critically, the court issued no ruling on the merits: no claim was affirmed, reversed, or vacated. The cost order — each side to bear its own — is consistent with a negotiated resolution rather than a contested procedural defeat.
At 211 days, the timeline is relatively compressed for a Federal Circuit appeal, suggesting the parties may have reached a commercial agreement relatively quickly after docketing. The public record does not disclose whether a settlement, licence, or other arrangement underlies the dismissal. What remains unknown is the status of the underlying district court proceedings and whether VirtaMove’s patents remain in active enforcement campaigns against other defendants in the containerisation sector.
Filing to Voluntary dismissal in 211 days
211 days from filing to dismissal — relatively swift resolution for a Federal Circuit appeal
Appeal dismissed by agreement: what Fed. R. App. P. 42(b) means for both sides
Fed. R. App. P. 42(b): dismissal by stipulation, not on the merits
Rule 42(b) permits parties to a Federal Circuit appeal to jointly move for voluntary dismissal at any time. Unlike a merits ruling, a 42(b) dismissal produces no precedent — the Federal Circuit issues no opinion on claim construction, obviousness, or infringement. The underlying patent rights are neither validated nor invalidated by this order. The only operative text is the cost allocation.
No merits adjudicationThe public record is silent on prejudice — what that means
The order does not specify whether the dismissal is with or without prejudice. Under Fed. R. App. P. 42(b), the default is typically without prejudice unless the parties stipulate otherwise. However, any res judicata or estoppel effect depends on the terms of any underlying agreement, which is not publicly disclosed. Practitioners should not assume either outcome without reviewing the full stipulation if it becomes available.
Prejudice terms undisclosedAppeal ends without a Federal Circuit ruling Red Hat could rely on
As the appellant, Red Hat secured no appellate ruling invalidating or narrowing VirtaMove’s patents. If the dismissal reflects a commercial settlement, Red Hat may have obtained a licence or covenant not to sue — but none of this is confirmed on the public record. Absent a merits win, Red Hat cannot cite this proceeding to resist future assertions of the same patents by VirtaMove.
No precedential protectionVirtaMove’s containerisation patents survive the Federal Circuit unchallenged
Because no merits ruling was issued, US7784058B2 and US7519814B2 remain on the register with no appellate-level invalidity finding. VirtaMove retains the option to assert these patents against other parties in the containerisation and enterprise Linux ecosystem. The agreed dismissal may, in practice, strengthen VirtaMove’s negotiating posture in future licensing discussions.
Patents remain enforceableFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Red Hat, Inc. | Company | Open-source software leader — appellant challenging US7784058B2 and US7519814B2Search in Eureka ↗ |
| Defendant | VIRTAMOVE, CORP. | Company | VirtaMove, Corp. — patent holder asserting containerisation and shared-library system IPSearch in Eureka ↗ |
| Plaintiff counsel | Brandon Brown | Attorney | Counsel for Red Hat, Inc.Search in Eureka ↗ |
| Plaintiff counsel | John C. O’Quinn | Attorney | Counsel for Red Hat, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Todd Friedman | Attorney | Counsel for Red Hat, Inc.Search in Eureka ↗ |
| Plaintiff counsel | William H. Burgess | Attorney | Counsel for Red Hat, Inc.Search in Eureka ↗ |
| Plaintiff counsel | Yimeng Dou | Attorney | Counsel for Red Hat, Inc.Search in Eureka ↗ |
| Plaintiff law firm | Kirkland & Ellis, LLP | Law Firm | Representing Red Hat, Inc.Search in Eureka ↗ |
| Defendant counsel | Christian Conkle | Attorney | Counsel for VIRTAMOVE, CORP.Search in Eureka ↗ |
| Defendant counsel | Daniel B. Kolko | Attorney | Counsel for VIRTAMOVE, CORP.Search in Eureka ↗ |
| Defendant counsel | James Milkey | Attorney | Counsel for VIRTAMOVE, CORP.Search in Eureka ↗ |
| Defendant counsel | Marc A. Fenster Counsel | Attorney | Counsel for VIRTAMOVE, CORP.Search in Eureka ↗ |
| Defendant counsel | Neil Rubin | Attorney | Counsel for VIRTAMOVE, CORP.Search in Eureka ↗ |
| Defendant counsel | Qi Tong | Attorney | Counsel for VIRTAMOVE, CORP.Search in Eureka ↗ |
| Defendant counsel | Reza Mirzaie | Attorney | Counsel for VIRTAMOVE, CORP.Search in Eureka ↗ |
| Defendant law firm | Russ August & Kabat LLP | Law Firm | Representing VIRTAMOVE, CORP.Search in Eureka ↗ |
| Presiding judge | Judge N/A | Judge | Court of Appeals for the Federal CircuitSearch in Eureka ↗ |
Official order — verbatim text
The Federal Circuit’s order reproduces the parties’ agreed terms verbatim and contains no judicial analysis of the merits. The operative language — ‘DISMISSED under Fed. R. App. P. 42(b)’ — confirms this is a consensual appellate dismissal, not a ruling on claim construction, validity, or infringement. The symmetric cost allocation (‘each side shall bear their own costs’) is the only substantive term on the public record, and it neither advantages nor disadvantages either party’s future patent enforcement position with respect to third parties.
US7784058B2 & US7519814B2 — containerisation and shared-library system patents
US7784058B2 (application no. US10/946536) protects a computing system architecture in which critical operating-system elements that would ordinarily run in kernel or privileged mode are instead implemented as user-mode shared libraries — a design approach relevant to lightweight virtualisation and container isolation. US7519814B2 (application no. US10/939903) covers a system specifically directed at containerising sets of applications, enabling multiple application environments to coexist on a single OS instance. Both patents sit at the foundation of modern container and virtualisation technology stacks.
Strategically, these patents are significant because containerisation is now core infrastructure for enterprise cloud deployments, DevOps pipelines, and edge computing. Any vendor offering container runtimes, application isolation layers, or OS-level virtualisation — including those building on Linux kernel namespaces or cgroups — could face exposure if their architecture overlaps with the claimed methods. VirtaMove’s willingness to pursue Red Hat, a dominant enterprise Linux player, signals that these patents are being actively enforced across the sector.
Should your product team run an FTO against US7784058B2 and US7519814B2?
If your organisation develops, ships, or integrates container runtimes, application virtualisation platforms, OS-level isolation technology, or shared-library operating environments, an FTO analysis against both VirtaMove patents is warranted. The Federal Circuit dismissal in Red Hat v. VirtaMove produced no invalidity finding, meaning the patents remain fully enforceable. Companies that assumed Red Hat’s appeal would yield a protective ruling are now exposed without that cover.
PatSnap Eureka’s FTO Search Agent can map the claim scope of US7784058B2 and US7519814B2 against your product architecture, surface relevant prior art that was not raised in the Red Hat proceedings, and flag design-around opportunities. Given VirtaMove’s active enforcement posture, an FTO report generated now — before a demand letter arrives — is materially more valuable than one commissioned reactively.
Run a freedom-to-operate analysis on US7784058B2 to assess your product’s exposure
Run FTO in Eureka →Similar Federal Circuit containerisation and virtualisation patent appeals
Cases involving containerisation, OS-level virtualisation, and shared-library system patents at the Federal Circuit — comparable in technology and appellate posture to Red Hat v. VirtaMove.
What this case signals for the containerisation IP landscape
A fast, mutually agreed Federal Circuit dismissal in a containerisation patent appeal carries specific implications for enterprise software IP strategy.
Agreed appellate dismissals often signal a licensing deal — monitor VirtaMove’s docket
When both parties agree to dismiss a Federal Circuit appeal within seven months, with each bearing own costs, a commercial resolution is the most likely explanation. Patent teams at container-platform vendors should monitor VirtaMove’s broader enforcement campaign, since these patents may resurface against other targets in the enterprise Linux and containerisation sector.
US7784058 and US7519814 carry no Federal Circuit invalidity finding — treat them as live risk
Neither patent was invalidated, narrowed, or even claim-construed at the appellate level. Any competitor operating in the containerisation or application-set virtualisation space who has not conducted an FTO analysis against these two patents should treat them as active exposure. The dismissal does not create a safe harbour for third parties.
Red v VIRTAMOVE — key questions answered
The dismissal under Fed. R. App. P. 42(b) means the parties jointly agreed to end the appeal without a merits ruling. The Federal Circuit issued no opinion on patent validity, claim construction, or infringement. Both US7784058B2 and US7519814B2 remain valid and enforceable, and no precedent was established that could benefit third parties facing similar VirtaMove assertions.
No. Neither patent was invalidated, narrowed, or subjected to claim construction by the Federal Circuit in case 25-1706. The proceeding was voluntarily dismissed by agreement before any merits adjudication. Both patents remain on the register and may be asserted against other defendants in the containerisation and enterprise software sector.
The public record does not disclose the reason. The agreed dismissal under Rule 42(b), resolved within 211 days of filing, is consistent with a negotiated commercial resolution — such as a licence or settlement — but no such agreement is publicly confirmed. The symmetric cost order suggests neither side extracted a concession that would typically accompany a unilateral dismissal.
US7784058B2 covers a computing system architecture where critical OS elements function as user-mode shared libraries rather than kernel-mode components — a technique relevant to container isolation. US7519814B2 covers a system for containerising sets of applications on a shared OS instance. Together, they address foundational concepts in modern container and virtualisation technology stacks.
No. Because the dismissal was on procedural rather than merits grounds, no invalidity or non-infringement finding was made that could benefit third parties. Other vendors in the containerisation, OS virtualisation, or enterprise Linux ecosystem who have not independently assessed their exposure to US7784058B2 and US7519814B2 should conduct their own FTO analysis — the Red Hat proceedings provide no safe harbour.
PatSnap Eureka searches patents and litigation data to answer instantly.