I am trying to take one of virtual appliances available on https://www.graylog.org/download. I have the tried to import the VMware OVA through the ovirt GUI but it fails with "Failed to load VM configuration from OVA file: /tmp/graylog-2.1.2-1.ova". /tmp/graylog-2.1.2-1.ova is the location of the file on the webclient. So I try to use the openstack image. From my ovirt host: # unzip graylog-2.1.2-1.qcow2.gz # qemu-img info /tmp/graylog-2.1.2-1.qcow2 image: /tmp/graylog-2.1.2-1.qcow2 file format: qcow2 virtual size: 5.9G (6291456000 bytes) disk size: 5.8G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false I create a VM in ovirt named graylog with a disk sized at 25 GB I locate the the disk id that the VM graylog has in the ovirt GUI. 1dae7037-73d5-4f11-b7da-c5d1a6aa36b7 # qemu-img convert -O raw /tmp/graylog-2.1.2-1.qcow2 /rhev/data-center/mnt/blockSD/6643dec0-12b2-4764-9473-a86975ef523d/images/1dae7037-73d5-4f11-b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-a6f9b7717b4a I then try to start the VM and get in both the vdsm.log and GUI: 2017-01-21T01:06:37.145854Z qemu-kvm: -drive file=/rhev/data-center/00000001-0001-0001-0001-0000000002ad/6643dec0-12b2-4764-9473-a86975ef523d/images/1dae7037-73d5-4f11-b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-a6f9b7717b4a,format=raw,if=none,id=drive-virtio-disk0,serial=1dae7037-73d5-4f11-b7da-c5d1a6aa36b7,cache=none,werror=stop,rerror=stop,aio=threads: Could not open '/rhev/data-center/00000001-0001-0001-0001-0000000002ad/6643dec0-12b2-4764-9473-a86975ef523d/images/1dae7037-73d5-4f11-b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-a6f9b7717b4a': Permission denied Thread-2666080::INFO::2017-01-20 17:06:37,321::vm::1308::virt.vm::(setDownStatus) vmId=`a1257117-e3f8-4896-9ab4-1b010298f282`::Changed state to Down: internal error: qemu unexpectedly closed the monitor: (process:23124): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported. Thanks in advance. -Alex
On Sat, Jan 21, 2017 at 2:38 AM, Alex R <ar.digger@gmail.com> wrote:
1dae7037-73d5-4f11-b7da-c5d1a6aa36b7
# qemu-img convert -O raw /tmp/graylog-2.1.2-1.qcow2 /rhev/data-center/mnt/blockSD/6643dec0-12b2-4764-9473- a86975ef523d/images/1dae7037-73d5-4f11-b7da-c5d1a6aa36b7/ 17a57535-77d1-4b3f-a0b4-a6f9b7717b4a
I then try to start the VM and get in both the vdsm.log and GUI:
2017-01-21T01:06:37.145854Z qemu-kvm: -drive file=/rhev/data-center/ 00000001-0001-0001-0001-0000000002ad/6643dec0-12b2- 4764-9473-a86975ef523d/images/1dae7037-73d5-4f11-b7da- c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-a6f9b7717b4a,format= raw,if=none,id=drive-virtio-disk0,serial=1dae7037-73d5- 4f11-b7da-c5d1a6aa36b7,cache=none,werror=stop,rerror=stop,aio=threads: Could not open '/rhev/data-center/00000001-0001-0001-0001-0000000002ad/ 6643dec0-12b2-4764-9473-a86975ef523d/images/1dae7037- 73d5-4f11-b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-a6f9b7717b4a': Permission denied Thread-2666080::INFO::2017-01-20 17:06:37,321::vm::1308::virt.vm::(setDownStatus) vmId=`a1257117-e3f8-4896-9ab4-1b010298f282`::Changed state to Down: internal error: qemu unexpectedly closed the monitor: (process:23124): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported.
Images should be owned by vdsm user and with group kvm and permission 660 Is your one ok? HIH, Gianluca
Thank you Gianluca. But that did not work for tying to import the ova's. # ls -l /tmp/graylog-2.1.2-1.ova -rw-rw----. 1 vdsm kvm 1129371648 Jan 15 20:19 /tmp/graylog-2.1.2-1.ova I also tried again with the qcow2 image. # ls -l /tmp/graylog-2.1.2-1.ova -rw-rw----. 1 vdsm kvm 1129371648 Jan 15 20:19 /tmp/graylog-2.1.2-1.ova I still get the same errors. I am suspecting that I am converting the qcows image to the wrong location? How do I know if I have the correct path? On Sat, Jan 21, 2017 at 8:20 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sat, Jan 21, 2017 at 2:38 AM, Alex R <ar.digger@gmail.com> wrote:
1dae7037-73d5-4f11-b7da-c5d1a6aa36b7
# qemu-img convert -O raw /tmp/graylog-2.1.2-1.qcow2 /rhev/data-center/mnt/blockSD/6643dec0-12b2-4764-9473-a86975 ef523d/images/1dae7037-73d5-4f11-b7da-c5d1a6aa36b7/17a5753 5-77d1-4b3f-a0b4-a6f9b7717b4a
I then try to start the VM and get in both the vdsm.log and GUI:
2017-01-21T01:06:37.145854Z qemu-kvm: -drive file=/rhev/data-center/00000001-0001-0001-0001-0000000002ad/ 6643dec0-12b2-4764-9473-a86975ef523d/images/1dae7037- 73d5-4f11-b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4- a6f9b7717b4a,format=raw,if=none,id=drive-virtio-disk0, serial=1dae7037-73d5-4f11-b7da-c5d1a6aa36b7,cache=none, werror=stop,rerror=stop,aio=threads: Could not open '/rhev/data-center/00000001-0001-0001-0001-0000000002ad/6643 dec0-12b2-4764-9473-a86975ef523d/images/1dae7037-73d5-4f11- b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-a6f9b7717b4a': Permission denied Thread-2666080::INFO::2017-01-20 17:06:37,321::vm::1308::virt.vm::(setDownStatus) vmId=`a1257117-e3f8-4896-9ab4-1b010298f282`::Changed state to Down: internal error: qemu unexpectedly closed the monitor: (process:23124): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported.
Images should be owned by vdsm user and with group kvm and permission 660 Is your one ok? HIH, Gianluca
Hi, On Sat, 21 Jan 2017 10:11:59 -0800 Alex R <ar.digger@gmail.com> wrote:
Thank you Gianluca. But that did not work for tying to import the ova's.
# ls -l /tmp/graylog-2.1.2-1.ova -rw-rw----. 1 vdsm kvm 1129371648 Jan 15 20:19 /tmp/graylog-2.1.2-1.ova
I've looked at the OVA and you're probably hitting this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1371843 but without the vdsm.log it is just a guess. Anyway, this bug should be fixed in oVirt 4.1.0/4.0.7 and with recent version of virt-v2v installed. BUT, you probably still won't be able to import the OVA since it's based on Ubuntu. Unfortunately virt-v2v with support of Debian based distributions is not yet readily available. I'm afraid trying to import the QCOW2 image directly is your best option. BTW oVirt 4.0 has support for uploading disk images via the web interface. That way you can avoid the magic with disk IDs and conversions. Best regards, Tomas
I also tried again with the qcow2 image.
# ls -l /tmp/graylog-2.1.2-1.ova -rw-rw----. 1 vdsm kvm 1129371648 Jan 15 20:19 /tmp/graylog-2.1.2-1.ova
I still get the same errors.
I am suspecting that I am converting the qcows image to the wrong location? How do I know if I have the correct path?
On Sat, Jan 21, 2017 at 8:20 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sat, Jan 21, 2017 at 2:38 AM, Alex R <ar.digger@gmail.com> wrote:
1dae7037-73d5-4f11-b7da-c5d1a6aa36b7
# qemu-img convert -O raw /tmp/graylog-2.1.2-1.qcow2 /rhev/data-center/mnt/blockSD/6643dec0-12b2-4764-9473-a86975 ef523d/images/1dae7037-73d5-4f11-b7da-c5d1a6aa36b7/17a5753 5-77d1-4b3f-a0b4-a6f9b7717b4a
I then try to start the VM and get in both the vdsm.log and GUI:
2017-01-21T01:06:37.145854Z qemu-kvm: -drive file=/rhev/data-center/00000001-0001-0001-0001-0000000002ad/ 6643dec0-12b2-4764-9473-a86975ef523d/images/1dae7037- 73d5-4f11-b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4- a6f9b7717b4a,format=raw,if=none,id=drive-virtio-disk0, serial=1dae7037-73d5-4f11-b7da-c5d1a6aa36b7,cache=none, werror=stop,rerror=stop,aio=threads: Could not open '/rhev/data-center/00000001-0001-0001-0001-0000000002ad/6643 dec0-12b2-4764-9473-a86975ef523d/images/1dae7037-73d5-4f11- b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-a6f9b7717b4a': Permission denied Thread-2666080::INFO::2017-01-20 17:06:37,321::vm::1308::virt.vm::(setDownStatus) vmId=`a1257117-e3f8-4896-9ab4-1b010298f282`::Changed state to Down: internal error: qemu unexpectedly closed the monitor: (process:23124): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported.
Images should be owned by vdsm user and with group kvm and permission 660 Is your one ok? HIH, Gianluca
-- Tomáš Golembiovský <tgolembi@redhat.com>
participants (3)
-
Alex R -
Gianluca Cecchi -
Tomáš Golembiovský