I've tried to provision a new kvm vm host through foreman using a
configured iscsi storage pool. But I receive the following error:
Unable to save
Failed to create Storage for Libirt instancedevhost15.local: Call to
function virNetworkCreateXML failed
When I use a local storage pool there is no issue creating the vm.
When I provision a host through virt-manager using the iscsi pool it
also works. My suspicion is that when selecting the iSCSI pool I can
not specify the UNIT/LUN that should be used for the host.
> Hello,
>
> I've tried to provision a new kvm vm host through foreman using a
> configured iscsi storage pool. But I receive the following error:
>
> Unable to save
> Failed to create Storage for Libirt instancedevhost15.local: Call to
> function virNetworkCreateXML failed
>
> When I use a local storage pool there is no issue creating the vm.
> When I provision a host through virt-manager using the iscsi pool it
> also works. My suspicion is that when selecting the iSCSI pool I can
> not specify the UNIT/LUN that should be used for the host.
>
> virsh # vol-list iSCSI
> Name Path
> -----------------------------------------
> unit:0:0:3 /dev/disk/by-path/ip-192.168.35.113:3260-iscsi-
> iqn.1986-03.com.sun:02:1fa832d5-0216-6d90-d428-cbc7266b7cd9-lun-3
>
> Is this something that should work, or is there currently no support
> for iSCSI pools?
>
First, sorry for the delay, as your email was blocked by google groups somehow.
In order to use iscsi, I'm guessing that we need to change a bit the
xml template we use in order to create the vm.
have a look at virt gem under the templates dir, afair, it should be a
line or two that needs to be modified, and you could compare it with
an existing machine which runs iscsi.
Thanks!
Ohad
···
On Tue, Jan 24, 2012 at 7:04 AM, Sachar de Vries wrote:
> Thanks,
>
> Sachar
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.
>
And used the path to store the vm on (from the vm XML file:
I think for this to work in foreman is that after selecting the Storage
Pool it should give the option to select the volume if it turns out to be a
iscsi storage pool. Let me know if you need more info.
One other thing I’ve noticed, and let me know if I should create a new
topic for this is that it looks like foreman keeps open the connection to
libvirt after checking say the amount of guests on a kvm host, and opens an
other connection if you do an other operation for that kvm host if you
check something else.
I appreciate that this is an old ticket, but was the issue ever fixed? I’ve only recently started using Foreman, but I’m having the same problem when trying to create a VM using Foreman 1.17. There is no visibility of individual iSCSI LUNs, only the pool.
