Skip to content

KVM leaves conversion XML and UEFI NVRAM files behind #14462

Open

Description

@andrijapanicsb

Migration testing found two cleanup problems:

  • After a cold import directly into NFS primary storage (forceconverttopool=true), the temporary <conversion-uuid>.xml file remains, including after the VM is expunged.
  • After a UEFI VM is expunged, its <vm-uuid>.fd firmware file remains on the KVM host.

The tested migrations and guest checks passed. These leftover files did not block the tests, but required manual cleanup.

Both cleanup gaps predate PR14256:

Expected behavior: remove unused conversion XML after successful import, without deleting the adopted disks; remove unused per-VM NVRAM after permanent expunge, not during stop/reboot or recoverable destroy.

Found while testing PR14256: #14256

Activity

  1. weizhouapache commented on Oct 22, 2026

    @weizhouapache
    Member

    @andrijapanicsb
    will you create a PR to fix it ?

    cc @nvazquez

  2. added this to the 24.0 milestone on Oct 28, 2026
  3. DaanHoogland commented on Oct 28, 2026

    @DaanHoogland
    Contributor

    not really a code cleanup issue but marked it as type:cleanup anyway as it can be considered a followup to (complete/wrap up) a feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions