search for: libvirtqemu

On 2013–12–21 John Ferlan wrote: > On 12/17/2013 07:13 PM, Marco wrote: > > 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

...run into one other issue that's discussed in a bz (https://bugzilla.redhat.com/show_bug.cgi?id=957295) where libiscsi had a bug where it wasn't handling the name string built up by libvirt properly. I don't remember all the details of what was happening, but you'd see messages from libvirtqemu indicating something like: " could not open disk image iscsi://freenas:3260/iqn.2013-11.freenas%3Avmpool:" This was for the case for when the iSCSI target was directly added to the guest though, but that's just a subset of the pool changes. Still the whole issue occurred in late O...

...ink to the bug report, it looks interesting. I will read it the next days when I have some time. > libiscsi had a bug where it wasn't handling the name string built up by > libvirt properly. I don't remember all the details of what was > happening, but you'd see messages from libvirtqemu indicating something > like: > > " could not open disk image > iscsi://freenas:3260/iqn.2013-11.freenas%3Avmpool:" > > This was for the case for when the iSCSI target was directly added to > the guest though, but that's just a subset of the pool changes. The di...