ova conversion errors: where to search?
Hello, testing some VMware ova imports. In a test that I'm doing I get failure in conversion; in engine.log 2017-02-17 17:39:02,992+01 INFO [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback] (DefaultQuartzScheduler4) [59adde47] Conversion of VM from external environment failed: Job u'cdb31877-3ebb-400d-88da-1f645b1261ae' process failed exit-code: 1 where to find more details regarding reasons for failure? Other files on engine or should I see at host side? In case I have to import a windows VM ova, which iso should I attach near the "Attach VirtIO-Drivers" checkbox? Any "official" iso? I downloaded oVirt-toolsSetup-4.1-3.fc24.iso but I don't know if it is the right iso for this. Thanks, Gianluca
Hi, On Fri, 17 Feb 2017 17:54:28 +0100 Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, testing some VMware ova imports. In a test that I'm doing I get failure in conversion; in engine.log
2017-02-17 17:39:02,992+01 INFO [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback] (DefaultQuartzScheduler4) [59adde47] Conversion of VM from external environment failed: Job u'cdb31877-3ebb-400d-88da-1f645b1261ae' process failed exit-code: 1
where to find more details regarding reasons for failure? Other files on engine or should I see at host side?
There are two places you should look. One is vdsm.log on the host performing the import. And if you have oVirt 4.1 another place to look at is /var/log/vdsm/import where the import logs are stored.
In case I have to import a windows VM ova, which iso should I attach near the "Attach VirtIO-Drivers" checkbox? Any "official" iso? I downloaded oVirt-toolsSetup-4.1-3.fc24.iso but I don't know if it is the right iso for this.
Install virtio-win package somewhere. In it, inside /usr/share/virtio-win directory, you will find virtio-win-*.iso file.
Thanks, Gianluca
-- Tomáš Golembiovský <tgolembi@redhat.com>
also make sure that the ova have permission to vdsm:kvm (36:36) On Sat, Feb 18, 2017 at 1:42 AM, Tomáš Golembiovský <tgolembi@redhat.com> wrote:
Hi,
On Fri, 17 Feb 2017 17:54:28 +0100 Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, testing some VMware ova imports. In a test that I'm doing I get failure in conversion; in engine.log
2017-02-17 17:39:02,992+01 INFO [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback] (DefaultQuartzScheduler4) [59adde47] Conversion of VM from external environment failed: Job u'cdb31877-3ebb-400d-88da-1f645b1261ae' process failed exit-code: 1
where to find more details regarding reasons for failure? Other files on engine or should I see at host side?
There are two places you should look. One is vdsm.log on the host performing the import. And if you have oVirt 4.1 another place to look at is /var/log/vdsm/import where the import logs are stored.
In case I have to import a windows VM ova, which iso should I attach near the "Attach VirtIO-Drivers" checkbox? Any "official" iso? I downloaded oVirt-toolsSetup-4.1-3.fc24.iso but I don't know if it is the right iso for this.
Install virtio-win package somewhere. In it, inside /usr/share/virtio-win directory, you will find virtio-win-*.iso file.
Thanks, Gianluca
-- Tomáš Golembiovský <tgolembi@redhat.com> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Sat, Feb 18, 2017 at 12:42 AM, Tomáš Golembiovský <tgolembi@redhat.com> wrote:
where to find more details regarding reasons for failure? Other files on engine or should I see at host side?
There are two places you should look. One is vdsm.log on the host performing the import. And if you have oVirt 4.1 another place to look at is /var/log/vdsm/import where the import logs are stored.
Thanks. BTW: the permissions of the ova were ok. I see this text near the end of the file generated into /var/log/vdsm/import libguestfs: trace: v2v: vfs_type = "ext4" [ 8.6] Checking for sufficient free disk space in the guest [ 8.6] Estimating space required on target for each disk mpstats: mountpoint statvfs /dev/sda2 / (ext4): bsize=4096 blocks=3650143 bfree=3324165 bavail=3132985 estimate_target_size: fs_total_size = 14950985728 [13.9G] estimate_target_size: source_total_size = 19327352832 [18.0G] estimate_target_size: ratio = 0.774 estimate_target_size: fs_free = 13615779840 [12.7G] estimate_target_size: scaled_saving = 10532706254 [9.8G] estimate_target_size: sda: 8794646578 [8.2G] [ 8.6] Converting Ubuntu precise (12.04.5 LTS) to run on KVM virt-v2v: error: virt-v2v is unable to convert this guest type (linux/ubuntu) rm -rf '/var/tmp/ova.vUHL91' rm -rf '/var/tmp/null.LZo6Xr' libguestfs: trace: v2v: close libguestfs: closing guestfs handle 0x1b79170 (state 2) Can we take a sort of generic linux in case? I don't think there could be anything special in Ubuntu... or at least let the admin fix anything trying some resuce operation after the VM has been created.
In case I have to import a windows VM ova, which iso should I attach near the "Attach VirtIO-Drivers" checkbox? Any "official" iso? I downloaded oVirt-toolsSetup-4.1-3.fc24.iso but I don't know if it is the right iso for this.
Install virtio-win package somewhere. In it, inside /usr/share/virtio-win directory, you will find virtio-win-*.iso file.
Is virtio-win package still current? In case from where to download it? I read here: https://www.ovirt.org/develop/release-management/features/engine/windows-gue... and installied ovirt-guest-tools-iso package that gives: [g.cecchi@ovmsrv05 ~]$ ll /usr/share/ovirt-guest-tools-iso/ total 215316 -rw-r--r--. 1 root root 220481536 Jan 26 16:13 oVirt-toolsSetup_4.1-3.fc24.iso lrwxrwxrwx. 1 root root 31 Feb 20 16:13 ovirt-tools-setup.iso -> oVirt-toolsSetup_4.1-3.fc24.iso [g.cecchi@ovmsrv05 ~]$ and mounting as a loop device the iso I have inside it: -r--r--r--. 1 root root 290 Jan 12 17:59 default.ini -r--r--r--. 1 root root 667 Jan 12 17:59 default-logger.ini -r--r--r--. 1 root root 1006 Jan 12 17:59 ovirt-guest-agent.ini -r-xr-xr-x. 1 root root 11659498 Jan 12 17:59 OVirtGuestService.exe -r--r--r--. 1 root root 30836592 Jan 26 16:13 ovirt-guest-tools-setup.exe -r--r--r--. 1 root root 4216840 Aug 2 2016 vcredist_x86.exe dr-xr-xr-x. 2 root root 2048 Jan 26 16:12 vdagent_x64 dr-xr-xr-x. 2 root root 2048 Jan 26 16:12 vdagent_x86 dr-xr-xr-x. 15 root root 4096 Jan 26 16:12 virtio [g.cecchi@ovmsrv05 ~]$ ll /isomount/virtio/vioscsi/ total 18 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k12 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k12R2 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k16 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 2k8 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k8R2 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w10 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w7 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w8 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w8.1 [g.cecchi@ovmsrv05 ~]$ Gianluca
Adding Richard. On Mon, Feb 20, 2017 at 5:34 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sat, Feb 18, 2017 at 12:42 AM, Tomáš Golembiovský <tgolembi@redhat.com> wrote:
where to find more details regarding reasons for failure? Other files on engine or should I see at host side?
There are two places you should look. One is vdsm.log on the host performing the import. And if you have oVirt 4.1 another place to look at is /var/log/vdsm/import where the import logs are stored.
Thanks. BTW: the permissions of the ova were ok.
I see this text near the end of the file generated into /var/log/vdsm/import
libguestfs: trace: v2v: vfs_type = "ext4" [ 8.6] Checking for sufficient free disk space in the guest [ 8.6] Estimating space required on target for each disk mpstats: mountpoint statvfs /dev/sda2 / (ext4): bsize=4096 blocks=3650143 bfree=3324165 bavail=3132985 estimate_target_size: fs_total_size = 14950985728 [13.9G] estimate_target_size: source_total_size = 19327352832 [18.0G] estimate_target_size: ratio = 0.774 estimate_target_size: fs_free = 13615779840 <(361)%20577-9840> [12.7G] estimate_target_size: scaled_saving = 10532706254 [9.8G] estimate_target_size: sda: 8794646578 [8.2G] [ 8.6] Converting Ubuntu precise (12.04.5 LTS) to run on KVM virt-v2v: error: virt-v2v is unable to convert this guest type (linux/ubuntu) rm -rf '/var/tmp/ova.vUHL91' rm -rf '/var/tmp/null.LZo6Xr' libguestfs: trace: v2v: close libguestfs: closing guestfs handle 0x1b79170 (state 2)
Can we take a sort of generic linux in case? I don't think there could be anything special in Ubuntu... or at least let the admin fix anything trying some resuce operation after the VM has been created.
In case I have to import a windows VM ova, which iso should I attach near the "Attach VirtIO-Drivers" checkbox? Any "official" iso? I downloaded oVirt-toolsSetup-4.1-3.fc24.iso but I don't know if it is the right iso for this.
Install virtio-win package somewhere. In it, inside /usr/share/virtio-win directory, you will find virtio-win-*.iso file.
Is virtio-win package still current? In case from where to download it? I read here: https://www.ovirt.org/develop/release-management/features/ engine/windows-guest-tools/ and installied ovirt-guest-tools-iso package that gives:
[g.cecchi@ovmsrv05 ~]$ ll /usr/share/ovirt-guest-tools-iso/ total 215316 -rw-r--r--. 1 root root 220481536 Jan 26 16:13 oVirt-toolsSetup_4.1-3.fc24. iso lrwxrwxrwx. 1 root root 31 Feb 20 16:13 ovirt-tools-setup.iso -> oVirt-toolsSetup_4.1-3.fc24.iso [g.cecchi@ovmsrv05 ~]$
and mounting as a loop device the iso I have inside it:
-r--r--r--. 1 root root 290 Jan 12 17:59 default.ini -r--r--r--. 1 root root 667 Jan 12 17:59 default-logger.ini -r--r--r--. 1 root root 1006 Jan 12 17:59 ovirt-guest-agent.ini -r-xr-xr-x. 1 root root 11659498 Jan 12 17:59 OVirtGuestService.exe -r--r--r--. 1 root root 30836592 Jan 26 16:13 ovirt-guest-tools-setup.exe -r--r--r--. 1 root root 4216840 Aug 2 2016 vcredist_x86.exe dr-xr-xr-x. 2 root root 2048 Jan 26 16:12 vdagent_x64 dr-xr-xr-x. 2 root root 2048 Jan 26 16:12 vdagent_x86 dr-xr-xr-x. 15 root root 4096 Jan 26 16:12 virtio
[g.cecchi@ovmsrv05 ~]$ ll /isomount/virtio/vioscsi/ total 18 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k12 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k12R2 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k16 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 2k8 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k8R2 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w10 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w7 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w8 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w8.1 [g.cecchi@ovmsrv05 ~]$
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, 21 Feb 2017 10:09:49 +0200 Shahar Havivi <shavivi@redhat.com> wrote:
Adding Richard.
On Mon, Feb 20, 2017 at 5:34 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sat, Feb 18, 2017 at 12:42 AM, Tomáš Golembiovský <tgolembi@redhat.com> wrote:
where to find more details regarding reasons for failure? Other files on engine or should I see at host side?
There are two places you should look. One is vdsm.log on the host performing the import. And if you have oVirt 4.1 another place to look at is /var/log/vdsm/import where the import logs are stored.
Thanks. BTW: the permissions of the ova were ok.
I see this text near the end of the file generated into /var/log/vdsm/import
libguestfs: trace: v2v: vfs_type = "ext4" [ 8.6] Checking for sufficient free disk space in the guest [ 8.6] Estimating space required on target for each disk mpstats: mountpoint statvfs /dev/sda2 / (ext4): bsize=4096 blocks=3650143 bfree=3324165 bavail=3132985 estimate_target_size: fs_total_size = 14950985728 [13.9G] estimate_target_size: source_total_size = 19327352832 [18.0G] estimate_target_size: ratio = 0.774 estimate_target_size: fs_free = 13615779840 <(361)%20577-9840> [12.7G] estimate_target_size: scaled_saving = 10532706254 [9.8G] estimate_target_size: sda: 8794646578 [8.2G] [ 8.6] Converting Ubuntu precise (12.04.5 LTS) to run on KVM virt-v2v: error: virt-v2v is unable to convert this guest type (linux/ubuntu)
This is the core of the issue. Import of Debian based distributions is not yet available in virt-v2v, unless you want to package it yourself. Hopefully it should reach users with RHEL/CentOS 7.4 with libguestfs version 1.36.
rm -rf '/var/tmp/ova.vUHL91' rm -rf '/var/tmp/null.LZo6Xr' libguestfs: trace: v2v: close libguestfs: closing guestfs handle 0x1b79170 (state 2)
Can we take a sort of generic linux in case? I don't think there could be anything special in Ubuntu... or at least let the admin fix anything trying some resuce operation after the VM has been created.
Unfortunately that is not possible with virt-v2v.
In case I have to import a windows VM ova, which iso should I attach near the "Attach VirtIO-Drivers" checkbox? Any "official" iso? I downloaded oVirt-toolsSetup-4.1-3.fc24.iso but I don't know if it is the right iso for this.
Install virtio-win package somewhere. In it, inside /usr/share/virtio-win directory, you will find virtio-win-*.iso file.
Is virtio-win package still current?
Yes, it is. With 0.1.126 being the latest stable version.
In case from where to download it?
You should have this repo in the ovirt-*-dependencies.repo file installed as part of oVirt. [virtio-win-stable] name=virtio-win builds roughly matching what was shipped in latest RHEL baseurl=http://fedorapeople.org/groups/virt/virtio-win/repo/stable enabled=1 skip_if_unavailable=1 gpgcheck=0
I read here: https://www.ovirt.org/develop/release-management/features/ engine/windows-guest-tools/ and installied ovirt-guest-tools-iso package that gives:
[g.cecchi@ovmsrv05 ~]$ ll /usr/share/ovirt-guest-tools-iso/ total 215316 -rw-r--r--. 1 root root 220481536 Jan 26 16:13 oVirt-toolsSetup_4.1-3.fc24. iso lrwxrwxrwx. 1 root root 31 Feb 20 16:13 ovirt-tools-setup.iso -> oVirt-toolsSetup_4.1-3.fc24.iso
Right, I forgot. Sure, you can use ovirt-guest-tools ISO too. Tomas
[g.cecchi@ovmsrv05 ~]$
and mounting as a loop device the iso I have inside it:
-r--r--r--. 1 root root 290 Jan 12 17:59 default.ini -r--r--r--. 1 root root 667 Jan 12 17:59 default-logger.ini -r--r--r--. 1 root root 1006 Jan 12 17:59 ovirt-guest-agent.ini -r-xr-xr-x. 1 root root 11659498 Jan 12 17:59 OVirtGuestService.exe -r--r--r--. 1 root root 30836592 Jan 26 16:13 ovirt-guest-tools-setup.exe -r--r--r--. 1 root root 4216840 Aug 2 2016 vcredist_x86.exe dr-xr-xr-x. 2 root root 2048 Jan 26 16:12 vdagent_x64 dr-xr-xr-x. 2 root root 2048 Jan 26 16:12 vdagent_x86 dr-xr-xr-x. 15 root root 4096 Jan 26 16:12 virtio
[g.cecchi@ovmsrv05 ~]$ ll /isomount/virtio/vioscsi/ total 18 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k12 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k12R2 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k16 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 2k8 dr-xr-xr-x. 3 root root 2048 Jan 16 14:45 2k8R2 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w10 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w7 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w8 dr-xr-xr-x. 4 root root 2048 Jan 16 14:45 w8.1 [g.cecchi@ovmsrv05 ~]$
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Tomáš Golembiovský <tgolembi@redhat.com>
participants (3)
-
Gianluca Cecchi -
Shahar Havivi -
Tomáš Golembiovský