I do not recommend libvirt compute resource for production deployments, it is meant more for development scenarios. With that, I need you to share the XML request that goes into libvirt, there is some kind of parsing error there.
I’m not the original poster, but I recently encountered this same problem when I tried, for the first time, to provision a host from a QCOW2 image on my KVM/QEMU compute resource from Satellite 6.10.1. (Which uses foreman-188.8.131.52-3.el7sat.noarch.)
I enabled debug logging on my KVM/QEMU server and will upload the relevant section of its /var/log/libvirt/libvirtd.log along with my satellite’s /var/log/foreman/production.log, shortly. But from me looking at it, it appears that it does not like the XML having a blank owner section: <owner></owner>
In my satellite’s Hosts —> Create Host —> Virtual Machine tab, there is no “owner” setting.
Oops, I get a Sorry, new users can not upload attachments message when I try to upload my log files. Their sizes (libvirtd.log is 823 kB and production.log is 32 kB) are likely too big for me to copy & paste into a comment.
Please instruct me on how to get them to you, @lzap . Thanks!
Just FYI, I took the XML appearing in the log file and tried to use it via the virsh vol-create command on my KVM/QEMU server. It considered both the blank owner and group entries as “malformed elements”.
It also errored on my format type being “raw”, stating: error: this function is not supported by the connection driver: backing storage not supported for raw volumes.
Making those changes, I was able to get it to work. So the question becomes how to get Satellite to not leave the owner and group elements blank.
Am I understanding that correctly? I don’t think I am, because I would think that we just need to change whatever it is in Satellite that puts together the request to Ruby Fog to not leave the owner and group values blank.