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(a)gmail.com>
wrote:
On Sat, Jan 21, 2017 at 2:38 AM, Alex R <ar.digger(a)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