# Requirements to adapt OpenNebula’s LVM datastore for local LV-based storage with SSH transfer support **URL:** \ **Category:** Integration Support\ **Created:** [November 24, 2025, 12:34pm UTC](https://forum.opennebula.io/t/requirements-to-adapt-opennebula-s-lvm-datastore-for-local-lv-based-storage-with-ssh-transfer-support/14320 "2025-11-24T12:34:20Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![TGM](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/tgm/32/7623_2.png) [@TGM](https://forum.opennebula.io/u/TGM)\ **Post date:** [November 24, 2025, 12:34pm UTC](https://forum.opennebula.io/t/requirements-to-adapt-opennebula-s-lvm-datastore-for-local-lv-based-storage-with-ssh-transfer-support/14320/1 "2025-11-24T12:34:20Z")
Hello, I’m looking for guidance on what’s required to modify OpenNebula’s LVM datastore driver so it can operate with **local storage instead of shared SAN**. Right now the LVM driver is designed for shared SAN volumes exposed are as documented in [SAN Datastore — OpenNebula 6.10.4 documentation](https://docs.opennebula.io/6.10/open_cluster_deployment/storage_setup/lvm_drivers.html) . What I want instead: - The Front-End connects to the target hypervisor via SSH - Copies the image to the HV over SSH - Creates the LV inside a predefined **`vg-one-`** volume group - Deploys the VM locally on that LV - Live or cold migration should still work between HVs (as long as each HV has its own **`vg-one-`** ) My question: **What are the actual technical requirements or components I need to modify?** Is it enough to extend the TM/LVM transfer scripts, or are there additional dependencies in the image manager, drivers, or migration hooks? I want to understand the full scope before I start patching anything. Thanks! ---
**Author:** ![brunorro](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/brunorro/32/7590_2.png) [@brunorro](https://forum.opennebula.io/u/brunorro)\ **Post date:** [November 24, 2025, 7:48pm UTC](https://forum.opennebula.io/t/requirements-to-adapt-opennebula-s-lvm-datastore-for-local-lv-based-storage-with-ssh-transfer-support/14320/2 "2025-11-24T19:48:35Z")
Hello, At a first glance, to work with local LVs the main problem is the migration: migrating a VM would mean migrating the LV to another hypervisor or replicating it with a `dd` or a similar command. I should check some more details, but this is the first thing that comes to my mind. Your idea is interesting and can be useful in some cases. Cheers! ---
**Author:** ![TGM](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/tgm/32/7623_2.png) [@TGM](https://forum.opennebula.io/u/TGM)\ **Post date:** [December 4, 2025, 1:47pm UTC](https://forum.opennebula.io/t/requirements-to-adapt-opennebula-s-lvm-datastore-for-local-lv-based-storage-with-ssh-transfer-support/14320/3 "2025-12-04T13:47:54Z")
Hello @brunorro , Any chance you had a look at this? I tried to do an alternative implementation, but indeed MV seems to be a pain to implement. ---
**Author:** ![brunorro](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/brunorro/32/7590_2.png) [@brunorro](https://forum.opennebula.io/u/brunorro)\ **Post date:** [December 9, 2025, 4:11pm UTC](https://forum.opennebula.io/t/requirements-to-adapt-opennebula-s-lvm-datastore-for-local-lv-based-storage-with-ssh-transfer-support/14320/4 "2025-12-09T16:11:07Z")
Hello, Sorry, I still didn’t have time to check it out ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/1/14d66f1130b9cd292905f575da9b68a9f574dd03.png) [@system](https://forum.opennebula.io/u/system)\ **Post date:** [January 8, 2026, 4:11pm UTC](https://forum.opennebula.io/t/requirements-to-adapt-opennebula-s-lvm-datastore-for-local-lv-based-storage-with-ssh-transfer-support/14320/5 "2026-01-08T16:11:39Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.