Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-1660

VMs with `/dev/disk/by-path` can not migrate successfully

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 2.7.11
    • None
    • Guest
    • True
    • Hide
      MTV can not fix this, because the path depends on the exact PCI topology on the source side. But MTV is never accessing a running VM on the source side, and public APIs usually do not expose this level of detail. Thus after all we could only implement heuristics which are only partially helpful.
      Show
      MTV can not fix this, because the path depends on the exact PCI topology on the source side. But MTV is never accessing a running VM on the source side, and public APIs usually do not expose this level of detail. Thus after all we could only implement heuristics which are only partially helpful.
    • True

      From https://issues.redhat.com/browse/VIRTSTRAT-14?focusedId=25616512&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25616512

      Another problem that was reported as a blocker/bug would be that it appears that SUSE uses `/dev/disk/by-path` by default in their '/etc/fstab/' entry. This causes virt-v2v migrations to fail with errors as such:
      ~~~
      virt-v2v: error: mount: mount_stub: /dev/disk/by-path/pci-0000:03:00.0-scsi-0:0:0:0-part3: No such file or directory.
      ~~~
      

              yzamir@redhat.com Yaacov Zamir
              fdeutsch@redhat.com Fabian Deutsch
              Chenli Hu Chenli Hu
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: