[PVE-User] libiscsi storages limitations

Dmitry Petuhov mityapetuhov at gmail.com
Sun Aug 21 19:32:43 CEST 2016

21.08.2016 17:59, Alexandre DERUMIER wrote:
>>> - offline volume clone/move, because we cannot pass initiator name to qemu-img; 
> qemu-img is able to use libiscsi, so it's work. (qemu-img convert ... -O iscsi:....)
Partly. qemu-img can use only hardcoded initiator name "iqn.2008-11.org.linux-kvm". So it must be enabled on target too. It is not always possible.

> > - backups, because we cannot pass initiator name to vma; backup use qemu, so it's works
Hmmm. That's strange. I have error below if try to backup machine with libiscsi storage. But maybe that's because of scsi passthrough. I'll try to test virtio-blk instead of virtio-scsi and to disable passthrough for iscsi..

Backup log:
INFO: starting new backup job: vzdump 115 --storage localINFO: Starting Backup of VM 115 (qemu)INFO: status = runningINFO: update VM 115: -lock backupINFO: VM Name: lotusINFO: exclude disk 'scsi1' (backup=no)Activating 'vm-115-disk-1'INFO: backup mode: snapshotINFO: ionice priority: 7INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-115-2016_08_20-23_11_20.vma'INFO: started backup task 'a857303e-e44a-4e2a-9556-66fca8f6c3ed'INFO: status: 0% (1048576/17181966336), sparse 0% (1044480), duration 0, 1/0 MB/sERROR: job failed with err -5 - Input/output errorINFO: aborting backup jobERROR: Backup of VM 115 failed - job failed with err -5 - Input/output errorINFO: Backup job finished with errorsTASK ERROR: job errors------------------------------------

More information about the pve-user mailing list