<div dir="ltr"><div><div><div>Thank you Gianluca.  But that did not work for tying to import the ova&#39;s.<br><br># ls -l /tmp/graylog-2.1.2-1.ova <br>-rw-rw----. 1 vdsm kvm 1129371648 Jan 15 20:19 /tmp/graylog-2.1.2-1.ova<br><br></div>I also tried again with the qcow2 image.<br><br># ls -l /tmp/graylog-2.1.2-1.ova <br>-rw-rw----. 1 vdsm kvm 1129371648 Jan 15 20:19 /tmp/graylog-2.1.2-1.ova<br><br></div>I still get the same errors.<br><br></div>I am suspecting that I am converting the qcows image to the wrong location?  How do I know if I have the correct path? <div class="gmail-yj6qo gmail-ajU"><div id="gmail-:sb" class="gmail-ajR" tabindex="0"><img class="gmail-ajT" src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 21, 2017 at 8:20 AM, Gianluca Cecchi <span dir="ltr">&lt;<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><div class="gmail_extra"><div class="gmail_quote">On Sat, Jan 21, 2017 at 2:38 AM, Alex R <span dir="ltr">&lt;<a href="mailto:ar.digger@gmail.com" target="_blank">ar.digger@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br>1dae7037-73d5-4f11-b7da-c5d1a6<wbr>aa36b7<br><br># qemu-img convert -O raw /tmp/graylog-2.1.2-1.qcow2 /rhev/data-center/mnt/blockSD/<wbr>6643dec0-12b2-4764-9473-a86975<wbr>ef523d/images/1dae7037-73d5-<wbr>4f11-b7da-c5d1a6aa36b7/17a5753<wbr>5-77d1-4b3f-a0b4-a6f9b7717b4a<br><br>I then try to start the VM and get in both the vdsm.log and GUI:<br><br>2017-01-21T01:06:37.145854Z qemu-kvm: -drive file=/rhev/data-center/0000000<wbr>1-0001-0001-0001-0000000002ad/<wbr>6643dec0-12b2-4764-9473-<wbr>a86975ef523d/images/1dae7037-<wbr>73d5-4f11-b7da-c5d1a6aa36b7/<wbr>17a57535-77d1-4b3f-a0b4-<wbr>a6f9b7717b4a,format=raw,if=<wbr>none,id=drive-virtio-disk0,<wbr>serial=1dae7037-73d5-4f11-<wbr>b7da-c5d1a6aa36b7,cache=none,<wbr>werror=stop,rerror=stop,aio=<wbr>threads: Could not open &#39;/rhev/data-center/00000001-00<wbr>01-0001-0001-0000000002ad/6643<wbr>dec0-12b2-4764-9473-a86975ef52<wbr>3d/images/1dae7037-73d5-4f11-<wbr>b7da-c5d1a6aa36b7/17a57535-<wbr>77d1-4b3f-a0b4-a6f9b7717b4a&#39;: Permission denied<br>Thread-2666080::INFO::2017-01-<wbr>20 17:06:37,321::vm::1308::virt.v<wbr>m::(setDownStatus) vmId=`a1257117-e3f8-4896-9ab4-<wbr>1b010298f282`::Changed state to Down: internal error: qemu unexpectedly closed the monitor:<br>(process:23124): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported.<br></div></blockquote></div><br></div></span><div class="gmail_extra">Images should be owned by vdsm user and with group kvm and permission 660<br></div><div class="gmail_extra">Is your one ok?<br></div><div class="gmail_extra">HIH,<br></div><div class="gmail_extra">Gianluca<br></div></div>
</blockquote></div><br></div>