On trying the import in ovirt after the completion of the conversion using -o rhev -os <ip>:/var/lib/exports/exports ..., I found an error in the vdsm.log:

Thread-199989::ERROR::2013-08-12 15:10:57,371::task::833::TaskManager.Task::(_setError) Task=`6fa2a23e-0194-4f67-b157-a3f831780d12`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 840, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 42, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 2891, in getVolumeInfo
    imgUUID=imgUUID, volUUID=volUUID).getInfo()
  File "/usr/share/vdsm/storage/fileSD.py", line 250, in produceVolume
    return fileVolume.FileVolume(repoPath, self.sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/fileVolume.py", line 71, in __init__
    volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/volume.py", line 128, in __init__
    self.validate()
  File "/usr/share/vdsm/storage/volume.py", line 140, in validate
    self.validateImagePath()
  File "/usr/share/vdsm/storage/fileVolume.py", line 522, in validateImagePath
    raise se.ImagePathError(imageDir)
ImagePathError: Image path does not exist or cannot be accessed/created: ('/rhev/data-center/6ff1a3cb-06b9-4a4f-a2ec-053cc45ac7c6/5eb89069-b750-4d32-b7d3-432fd77202d1/images/1e43cdf3-bf3b-4f28-a755-b5fb8a67543b',)


I have setenforce=0 with same result.
So the 5eb89069-b750-4d32-b7d3-432fd77202d1 is a valid ovirt domain number for the entire process in exports. The 1e43cdf3-bf3b-4f28-a755-b5fb8a67543b was the name of the dir created from the virt-v2v process.

The ovirt import gui provides this error:
Error while executing action: Cannot import VM. VM's Image does not exist.

I've tried with a qcow2 image, a raw image, vmdk (fails with unsupported format error).



On Mon, Aug 12, 2013 at 4:49 PM, Jim Kinney <jim.kinney@gmail.com> wrote:
I need to convert a vmdk to ovirt use. I have a qcow2 formatted image and it's corresponding xml. I'm trying to run virt-v2v to put things into the proper formats/places for ovirt but I need to use my proper credentials to access the qemu:///system space.

Where/how do I do this? man pages have no suggestions on virt-v2v. I have a user/passwd combo in saslauth that works for virsh.

virt-v2v -i libvirtxml -o libvirt -os export --vmtype server -n ovirtmgmt /var/lib/exports/exports/5eb89069-b750-4d32-b7d3-432fd77202d1/images/test/test.xml
virt-v2v: Failed to connect to qemu:///system: libvirt error code: 45, message: authentication failed: Failed to step SASL negotiation: -7 (SASL(-7): invalid parameter supplied: Unexpectedly missing a prompt result)

--
--
James P. Kinney III

Every time you stop a school, you will have to build a jail. What you gain at one end you lose at the other. It's like feeding a dog on his own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain

http://heretothereideas.blogspot.com/



--
--
James P. Kinney III

Every time you stop a school, you will have to build a jail. What you gain at one end you lose at the other. It's like feeding a dog on his own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain

http://heretothereideas.blogspot.com/