Skip to content
vJailbreak

Archived Releases

v0.1.2

What’s Changed

Known Issues

  • If the VM to be migrated has an LV spanning multiple physical devices used as boot volume unless both are mounted simultaneously to the OS-VM, vJailbreak cannot detect whether it is bootable, or not. (issue link)
  • If a user turns on a VM on VCenter after migration and tries to migrate it again, the migration object will not be created. In this case, the user should delete the VM from PCD/Openstack before trying the migration again. This error will be pushed up the stack for visibility.

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.1…16.01

v0.1.3

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.2…v0.1.3

v0.1.4

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.3…v0.1.4

v0.1.5

What’s Changed

New Contributors

  • @damian-pf9
  • @anmolsachan
  • @bhavin192

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.4…v0.1.5

v0.1.6

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.5…v0.1.6

v0.1.7

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.6…v0.1.7

v0.1.8

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.6…v0.1.8

v0.1.9

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.8…v0.1.9

v0.1.10

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.9…v0.1.10

v0.1.11

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.10…v0.1.11

v0.1.12

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.11…v0.1.12

v0.1.13

What’s Changed

Usability Enhancements and Stability Improvements

  • Rolling Conversion (Beta Availability)
    The Rolling Conversion feature is now available as a beta release.

  • Pre-Packaged vJailbreak Image
    A new vJailbreak image is now available, containing all required components pre-installed. This enhancement eliminates the need for internet access during installation, making it suitable for restricted network environments.

  • Support for Custom VirtIO Drivers
    Users may now upload VirtIO drivers to a designated path. If present, these drivers will be utilized during the migration process. If absent, the system will default to downloading the necessary drivers from the internet, providing flexibility based on deployment conditions. https://github.com/platform9/vjailbreak/blob/main/docs/src/content/docs/guides/virtio_doc.md

  • Resolution of Pod Eviction Due to Disk Pressure
    An issue causing pod eviction under disk pressure conditions has been resolved. This fix improves the reliability and stability of workloads during extended migration operations.

  • Enhanced Debug Logging
    Debug logs have been improved to provide more comprehensive and structured output

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.12…v0.1.13

v0.1.14

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.13…v0.1.14

v0.1.15

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.14…v0.1.15

v0.2.0

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.1.15…v0.2.0

v0.2.1

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.2.0…v0.2.1

v0.3.0

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.2.1…v0.3.0

v0.3.1

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.0…v0.3.1

v0.3.2

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.1…v0.3.2

v0.3.3

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.2…v0.3.3

v0.3.4

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.3…v0.3.4

v0.3.5

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.4…v0.3.5

v0.3.6

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.5…v0.3.6

v0.3.7

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.6…v0.3.7

v0.3.8

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.7…v0.3.8

title: v0.4.0 description: Release Notes for v0.4.0

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.3.8…v0.4.0

title: v0.4.1 description: Release Notes for v0.4.1

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.4.0…v0.4.1

Upgrade Guide: v0.4.0 → v0.4.1

Users upgrading from v0.4.0 to v0.4.1 need to follow the steps below:

Step 1: Update v0.4.0 Container Images

In your existing v0.4.0 setup, update the deployment images to pull the latest v0.4.0 containers and set imagePullPolicy to Always using the following command:

Terminal window
kubectl patch deployment migration-controller-manager -n migration-system --type='json' \
-p='[{"op":"replace","path":"/spec/template/spec/containers/0/imagePullPolicy","value":"Always"}]' && \
kubectl patch deployment migration-vpwned-sdk -n migration-system --type='json' \
-p='[{"op":"replace","path":"/spec/template/spec/containers/0/imagePullPolicy","value":"Always"}]' && \
kubectl patch deployment vjailbreak-ui -n migration-system --type='json' \
-p='[{"op":"replace","path":"/spec/template/spec/containers/0/imagePullPolicy","value":"Always"}]'
Step 2: Restart Deployments

Restart the deployments to ensure the updated images are pulled and running:

Terminal window
kubectl rollout restart deployment -n migration-system
Step 3: Follow Upgrade Steps from the public documentation

v0.4.2

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.4.1…v0.4.2

v0.4.3

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.4.2…v0.4.3

Release Notes & Known Issues

  • Static IP and interface name preservation is not supported when the target network has DHCP disabled.
  • For Windows VMs, static IP configurations are automatically converted to DHCP. However, the original source IP is retained on the destination VM to maintain network connectivity.
  • The VMware Tools removal script may leave behind some residual artifacts. Refer to the documentation for more details.
  • Agent scaling is not supported for vJailbreak VMs operating on L2 networks.

v0.4.4

What’s Changed

New Contributors

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.4.3…v0.4.4

Highlights

  • VMware Tools Removal: The removal script now removes all residual files and folders. A small number of registry entries may remain depending on the Windows version, but these are harmless and can be removed manually if needed.
  • Migration Profiles: Pre-defined key-value pairs can now be applied to a migrated VM’s root volume in OpenStack. Profiles are supported for both Windows and Linux guests.
  • L2 Network Scaling Support: Scaling of agents in L2 network (Simple Networking) is now supported.
  • Persistent Network Interface for Windows (2016+): Static network configurations including interface name, IP, MAC, and gateway are now preserved across migration for Windows Server 2016 and above.
  • FC Support for Storage Area Migration (SAM): Fibre Channel support has been added for SAM workflows, verified with NetApp FC targets.

Known Limitations

  • Windows 2012 and Earlier — Persist Network: The persistent network interface option is not supported on Windows 2012 and below. IP and MAC addresses are preserved, but the interface name and gateway may get lost, and the NIC configuration becomes dynamic after migration.
  • Migration Profiles — Upgrade Path: The two default profiles (Windows and Linux) are auto-created on fresh installations only. Users upgrading from lower versions to v0.4.4 will need to create these profiles manually.
  • VMware Tools Registry Entries: Depending on the Windows version, a small number of VMware Tools registry entries (listed in public docs) may not be removed by the uninstall script. These are harmless but can be removed manually if desired.
  • FC SAM — Verified Target: FC support for SAM has been verified against NetApp FC targets. Compatibility with other FC storage vendors is not yet validated.

v0.4.5

What’s Changed

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.4.4…v0.4.5

v0.4.6

What’s Changed

Highlights

Hot Add Proxy: Hot-Add Proxy is an advanced data copy method that attaches source VM disks directly to a dedicated Proxy VM and streams the data over NBD (Network Block Device) to the destination. Instead of copying data over the NFC protocol from ESXi. This feature is currently in beta, will be stabilized in the coming releases.

Migration Reliability:

  • VMs with no network interfaces can now be migrated successfully.
  • Multi-attach volume types are now supported for migration.

Enhanced UX:

  • All IP addresses (assigned and preserved) are now shown on the Migration Details page in the UI.
  • Controller logs (migration controller manager) are visible in the UI irrespective of any migrations triggered.
  • A debug bundle collection button makes log and resource gathering easier for troubleshooting. All CRs related to that migration are now gathered for easier debugging.

Known Limitations

  • Migrations of VMs with grub version lower than 2 might face issues while booting post migration.

Full Changelog: https://github.com/platform9/vjailbreak/compare/v0.4.5…v0.4.6