Virtamove v. Hewlett-Packard: Container IP Dismissed With Prejudice After 647 Days
Virtamove, Corp. asserted two patents covering container portability and application isolation technology — US7784058B2 and US7519814B2 — against Hewlett-Packard in the Eastern District of Texas. The case closed after 647 days with a joint stipulation of dismissal with prejudice, each party bearing its own costs.
Container Portability Patents Extinguished by Joint Dismissal in E.D. Texas
Virtamove, Corp. filed suit against Hewlett-Packard, Co. on February 9, 2024 in the Eastern District of Texas before Judge Rodney Gilstrap, asserting infringement of US7784058B2 and US7519814B2 — patents directed at container portability and application isolation in server environments. The accused product was IBM’s Cloud Kubernetes Service, suggesting the case was part of a broader coordinated enforcement campaign by Virtamove targeting containerisation infrastructure vendors.
The case closed on November 17, 2025 via a joint stipulation of dismissal with prejudice filed under Rule 41(a)(1)(A)(ii) of the Federal Rules of Civil Procedure. Dismissal with prejudice constitutes a final adjudication on the merits as a matter of law — Virtamove cannot re-file the same claims against Hewlett-Packard on these patents. The court also directed closure of the consolidated member case No. 2:24-cv-00064, confirming no live disputes remained in the consolidated series.
At 647 days, the case ran longer than many E.D. Texas patent disputes that settle early, suggesting substantive motion practice or protracted licensing negotiations preceded the resolution. The ‘each party bears its own costs’ structure is typical of negotiated settlements and does not indicate a plaintiff capitulation or a defendant walkaway — the financial terms of any underlying agreement remain confidential. What is publicly unknown is whether a licence was exchanged as consideration for the dismissal.
Filing to Dismissed with Prejudice in 647 days
647 days — above the E.D. Texas median for patent cases that resolve pre-trial
Dismissed with prejudice: what the joint stipulation means for both parties
Rule 41(a)(1)(A)(ii) — joint stipulation closes the case permanently
A dismissal under Rule 41(a)(1)(A)(ii) requires agreement from all parties who have appeared. Unlike a unilateral voluntary dismissal, both sides signed off — making this a negotiated exit. ‘With prejudice’ means the dismissal carries the legal force of a final judgment: Virtamove is permanently barred from asserting these same claims against HP on these patents in any future proceeding.
Permanent bar on re-filingVirtamove permanently surrenders claims against HP on these patents
By agreeing to dismissal with prejudice, Virtamove relinquishes all future enforcement rights against HP under US7784058B2 and US7519814B2 for the accused conduct. This is a meaningful concession — regardless of any confidential licence terms. The ‘each party bears costs’ structure suggests neither party extracted a publicly visible win, though undisclosed settlement consideration may have changed hands.
No re-assertion rights retainedHP secures permanent dismissal — re-litigation risk on these patents eliminated
For Hewlett-Packard, the with-prejudice dismissal is the strongest possible exit short of a full invalidity ruling. HP cannot be sued again by Virtamove on these patents for the same accused products and conduct. Baker Botts’ defence team secured this outcome without any public finding of liability. The closure of both lead and member consolidated cases confirms comprehensive resolution.
Clean exit, no liability findingPatents remain live — other container platform vendors still face exposure
Dismissal with prejudice protects only HP. US7784058B2 and US7519814B2 remain enforceable against all other parties. The consolidated case structure and accused IBM Kubernetes Service suggest Virtamove ran a multi-defendant campaign. Any cloud or container platform vendor that has not resolved its position against these patents should treat this dismissal as a signal, not a shield.
Third-party exposure persistsFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Virtamove, Corp. | Company | Patent assertion entity — holder of US7784058B2 and US7519814B2 covering container portabilitySearch in Eureka ↗ |
| Defendant | Hewlett-Parkard, Co. | Company | Hewlett-Packard, Co. — multinational enterprise IT infrastructure and cloud services providerSearch in Eureka ↗ |
| Plaintiff counsel | Amy Elizabeth Hayden | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Christian W. Conkle | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Daniel Benjamin Kolko | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jacob Buczko | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | James A. Milkey | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | James Shrin Tsuei | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jefferson Cummings | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jonathan Ma | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Linjun Xu | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Mackenzie Paladino | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Marc A. Fenster | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Neil Alan Rubin | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Qi Tong | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Reza Mirzaie | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff law firm | BC Law Group, PC | Law Firm | Representing Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Russ August & Kabat LLP (Los Angeles) | Law Firm | Representing Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Russ August Kabat LLP | Law Firm | Representing Virtamove, Corp.Search in Eureka ↗ |
| Defendant counsel | Bethany R. Salpietra | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Douglas Mark Kubehl | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Emily F. Deer | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Haleigh Ann Hashem | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Hien Khanh Lien | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Jennifer Haltom Doan | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Joshua Reed Thane | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Katharine Mary Burke | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Morgan Grissum Mayne | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant counsel | Samuel Kassa | Attorney | Counsel for Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant law firm | Baker Botts LLP | Law Firm | Representing Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant law firm | Baker Botts LLP (DC) | Law Firm | Representing Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant law firm | Baker Botts LLP (Dallas) | Law Firm | Representing Hewlett-Parkard, Co.Search in Eureka ↗ |
| Defendant law firm | Haltom & Doan LLP | Law Firm | Representing Hewlett-Parkard, Co.Search in Eureka ↗ |
| Presiding judge | Judge Rodney Gilstrap | Judge | Texas Eastern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The court’s order closely tracks the language of the joint stipulation, accepting and acknowledging the dismissal rather than independently adjudicating it — consistent with the ministerial role courts play under Rule 41(a)(1)(A)(ii). The explicit ‘with prejudice’ designation and the direction to close both the lead and consolidated member case confirm this is a comprehensive resolution. The denial of all pending relief as moot indicates substantive motions — potentially claim construction or summary judgment proceedings — were still open at the time of dismissal, suggesting the parties resolved before a merits ruling issued.
US7784058B2 & US7519814B2 — Container Portability and Application Isolation
US7784058B2 (application no. 10/946,536) and US7519814B2 (application no. 10/939,903) both originate from application filings that predate the mainstream container era, meaning their claims were drafted when application isolation concepts were framed in terms of operating system virtualisation rather than today’s Docker/Kubernetes paradigms. This temporal gap between claim drafting and accused technology is a double-edged sword: claims may read broadly onto modern implementations, but prior art density in the virtualisation space is also high.
Strategically, these patents sit at the intersection of OS-level containerisation and workload portability — precisely the technology underpinning cloud-native infrastructure from AWS EKS to Google GKE to IBM Kubernetes Service. Virtamove’s decision to assert them against major enterprise vendors in coordinated E.D. Texas actions suggests confidence in their enforceability. Any vendor shipping container orchestration, pod scheduling, or application isolation features as part of a managed cloud service should treat these patents as live enforcement risks until their expiry is confirmed.
Should your team run an FTO against US7784058B2 and US7519814B2?
If your organisation develops, ships, or operates containerisation platforms, Kubernetes distributions, or managed container services, both patents warrant active FTO analysis. The accused product in this case — IBM Cloud Kubernetes Service — is representative of a broad class of enterprise container infrastructure. Virtamove has demonstrated willingness to litigate in E.D. Texas, a plaintiff-friendly jurisdiction with predictable timelines. Waiting for a demand letter is a materially more expensive strategy than pre-emptive clearance.
PatSnap Eureka’s FTO Search Agent can map your product’s container and isolation architecture against the independent claims of US7784058B2 and US7519814B2, flag prior art that may inform invalidity arguments, and surface related patents in Virtamove’s portfolio that could represent further assertion risk. The platform also tracks prosecution history and any pending continuations that could extend the enforcement window beyond the original patent expiry dates.
Run a freedom-to-operate analysis on US7784058B2 to assess your product’s exposure
Run FTO in Eureka →Related container and virtualisation patent cases in E.D. Texas
Cases involving container portability, application isolation, and Kubernetes infrastructure patents litigated in the Eastern District of Texas before Judge Gilstrap.
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 IBM Cloud Kubernetes Service-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.
DecidedVirtamove, Corp.’s broader IP enforcement history
Virtamove, Corp.’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat this case signals for the container infrastructure IP landscape
Virtamove’s coordinated E.D. Texas campaign signals rising patent enforcement pressure on container and Kubernetes-era infrastructure vendors.
E.D. Texas remains the venue of choice for container platform patent assertions
Judge Gilstrap’s docket and E.D. Texas’s established patent procedures continue to attract assertion campaigns against enterprise infrastructure vendors. Container and Kubernetes IP is now firmly within scope. Any vendor with commercial containerisation products should assess exposure in this jurisdiction proactively, not reactively.
With-prejudice dismissal after 647 days suggests a negotiated resolution, not a capitulation
The timeline and cost-bearing structure are consistent with a licensing resolution reached after substantive claim construction or IPR risk crystallised. Neither party prevailed publicly. For other defendants in related Virtamove cases, this outcome suggests the plaintiff is willing to resolve commercially — but the terms remain opaque.
US7784058 claim scope: which container architectures face the highest infringement risk
The application isolation and portability claims in US7784058B2 were filed when container technology was nascent — claim language may read broadly onto modern Kubernetes pod and namespace architectures. Vendors running multi-tenant container orchestration at scale should map their implementations against the independent claims before any demand letter arrives.
Virtamove’s multi-defendant campaign: identifying who remains exposed
The court’s reference to consolidated member case No. 2:24-cv-00064 confirms Virtamove ran parallel actions. Mapping which defendants have resolved versus which remain active reveals where enforcement pressure is still live — and which technology overlaps with HP’s accused IBM Kubernetes Service deployment create analogous risk profiles.
Virtamove v Hewlett-Parkard — key questions answered
Dismissed with prejudice means Virtamove permanently relinquished its right to sue HP again on US7784058B2 and US7519814B2 for the same accused conduct. The dismissal carries the legal force of a final judgment on the merits, even though no court ruling on infringement or validity was issued. HP cannot be re-sued by Virtamove on these patents.
Virtamove asserted US7784058B2 (application no. 10/946,536) and US7519814B2 (application no. 10/939,903). Both patents relate to container portability and application isolation technology in server environments. The accused product referenced in the case is IBM Cloud Kubernetes Service.
E.D. Texas, and Judge Gilstrap’s docket in particular, is a frequently chosen venue by patent assertion entities due to established patent litigation procedures, predictable scheduling orders, and historically plaintiff-favourable outcomes. Virtamove appears to have run a coordinated multi-defendant campaign in this jurisdiction, as evidenced by the consolidated member case No. 2:24-cv-00064.
Yes. The with-prejudice dismissal only protects Hewlett-Packard. Both patents remain valid and enforceable against all other parties unless and until they are invalidated through IPR, ex parte reexamination, or a court ruling. Other container and Kubernetes platform vendors have no protection from this outcome.
When a court orders each party to bear its own costs, it neither awards attorneys’ fees to the defendant (which would signal an ‘exceptional case’ under 35 U.S.C. § 285) nor to the plaintiff. This neutral cost structure is typical of negotiated commercial resolutions and does not indicate which party received the better outcome — any licensing consideration would be confidential and off the public record.
Is your container platform exposed to Virtamove’s patent portfolio?
US7784058B2 and US7519814B2 remain enforceable against all parties outside this dismissal. Run a targeted FTO with PatSnap Eureka to map your container architecture against active claim scope before a demand letter arrives.
PatSnap Eureka searches patents and litigation data to answer instantly.