On Sat, 5 Nov 2016 17:34:25 -0400
"Derek Atkins" <derek(a)ihtfp.com> wrote:
After a bit more research I found this message in libguestfs that seems
to imply the issue is related to Fedora 23 in that dracut was moved from
/sbin to /usr/bin. Apparently this was fixed in libguestfs on January 28,
2016 by a change to convert_linux.ml . But apparently this change
isn't in the centos-7.2/ovirt-4.0.4 packages?
Yes you're right. That change was not back-ported to the version of
virt-v2v on CentOS 7.2. But if I understand things correctly it should
appear in CentOS 7.3. Is waiting for Centos 7.3 an option for you?
I just looked through my ovirt host and canot find
anywhere, so I have no idea how to actually apply this patch locally.
You can't just patch the code localy (it's not Python). You'd need to
recompile the virt-v2v binary.
Short term I suppose I can fix this by adding a symlink in the VM
repackage the OVA, but it would be nice to actually get this bugfix
propagated; it's been almost a year?
Adding Richard to the loop.
On Sat, November 5, 2016 5:02 pm, Derek Atkins wrote:
> I just tried using the OVA import feature in 4.0.4 to import an OVA file
> created from VMware-Workstation-12. I packaged the OVA, got it onto my
> ovirt host, and then go the Admin GUI and under the Virtual Machines tab
> clicked on Import. From there I chose Source: VMware Virtual Appliance
> (OVA), and selected the (local-to-the-host) path where I put the OVA
> file. After clicking Load it displayed the vm name in the window. I
> click on that and click the right arrow to and then Next. Then I select
> my storage domain to use and continue. It loads the VM and starts to
> process it internally with virt-v2v, but then it inexplicably fails.
> The only message in the GUI is:
> Failed to import Vm <vm name> to Data Center Default, Cluster Default
> I tried to look into /var/log/vdsm/vdsm.log looking for any errors. I
> found this:
> Thread-88166::ERROR::2016-11-05 16:36:09,219::v2v::674::root::(_run) Job
> eb7-63f3-46e8-abd5-5292dcc8809a' failed
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 669, in _run
> File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 696, in
> V2VProcessError: Job u'cdb1eeb7-63f3-46e8-abd5-5292dcc8809a' process
> failed exit
> -code: 1, stderr: virt-v2v: error: unable to rebuild initrd
> (/boot/initramfs-4.2.6-301.fc23.x86_64.img) because mkinitrd or dracut was
> not found in the guest
> If reporting bugs, run virt-v2v with debugging enabled and include the
> complete output:
> virt-v2v -v -x [...]
> I don't understand this error because /usr/bin/dracut certainly exists
> in the VM.
> Anyone have any suggestions on how to get around this?
> Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
> Member, MIT Student Information Processing Board (SIPB)
> URL: http://web.mit.edu/warlord/
> warlord(a)MIT.EDU PGP key available
> Users mailing list
Derek Atkins 617-623-3745
Computer and Internet Security Consultant
Users mailing list
Tomáš Golembiovský <tgolembi(a)redhat.com>