search for: 347feb68

...e. For me it does not. > Use virsh pool-dumpxml <pool> > to view the XML... Here's my XML which is directly taken from the manual. I only changed the host name to “freenas” and the device path. <pool type='iscsi'> <name>virtimages</name> <uuid>347feb68-7e11-4f2b-ba82-ada027296fb0</uuid> <capacity unit='bytes'>0</capacity> <allocation unit='bytes'>0</allocation> <available unit='bytes'>0</available> <source> <host name='freenas'/> <device path=...

...pool-dumpxml <pool> >> to view the XML... > > Here's my XML which is directly taken from the manual. I only > changed the host name to “freenas” and the device path. > > <pool type='iscsi'> > <name>virtimages</name> > <uuid>347feb68-7e11-4f2b-ba82-ada027296fb0</uuid> > <capacity unit='bytes'>0</capacity> > <allocation unit='bytes'>0</allocation> > <available unit='bytes'>0</available> > <source> > <host name='freenas'/...

...to view the XML... > > > > Here's my XML which is directly taken from the manual. I only > > changed the host name to “freenas” and the device path. > > > > <pool type='iscsi'> > > <name>virtimages</name> > > <uuid>347feb68-7e11-4f2b-ba82-ada027296fb0</uuid> > > <capacity unit='bytes'>0</capacity> > > <allocation unit='bytes'>0</allocation> > > <available unit='bytes'>0</available> > > <source> > > <hos...

Hi! I'm new to libvirt and face problems connecting to an iSCSI target. What I intend to do is to connect libvirt (I tried virt-manager and virsh) to an iSCSI target and then boot from the LUNs which contain the VMs. I followed the documentation¹ but got stuck at section 12.1.5.4.3. 1) virsh pool-define-as \ --name foo \ --type iscsi