[one-users] Errors, problems when "creating VM using OpenNebula 3.6.0 in Ubuntu 12.04 with iSCSI datastore"

Wed Dec 11 09:43:00 PST 2013

Hi,

OpenNebula 4.4 which has been just released has deprectated iSCSI. The main
reason is that the tgt iSCSI daemon is not very flexible and we recommend
using other storage mechanisms instead.

OpenNebula 3.6.0 should be definitetly upgraded to newer versions.

Regarding your specific problem, can you please detail what command and
image file did you use to create the image?

cheers,
Jaime

On Wed, Dec 4, 2013 at 7:25 AM, Qiubo Su (David Su) <qiubosu at gmail.com>wrote:

> Dear OpenNebula Community,
>
> 1) To create VM using OpenNebula 3.6.0 in Ubuntu 12.04 with iSCSI
> datastore, I create Front-end, NodeServer and iSCSIHost (an iSCSI target VM
> created within the NodeServer. The IP of iSCSIHost is 192.168.1.7).
>
> The required setup, configuration for Front-end, NodeServer and iSCSIHost
> looks fine.
>
> The host, image, vnet and datastore creation under NodeServer are ok
> (except of the VM creation in below 2) ), but when "oneimage show 0", can't
> see output of
>
> "SOURCE: iqn.2013-12.iSCSIHost:192.168.1.7.vg-one.lv-one-13
> PATH: /var/lib/images/win-xp.qcow2"
>
> while only can see "SOURCE: /var/lib/images/win-xp.qcow2".
>
> the opennebula 3.6.0 used was downloaded in more than one year ago. is it
> the correct version of opennebula to use?
>
> 2) the VM creation is failed and got "error executing image transfer
> script: error cloning NodeServer:/dev//var/lib/image/win-xp-2/qcow2-0".
> Below is the vm.log for this VM creation:
>
> Wed Dec  4 17:38:56 2013 [DiM][I]: New VM state is ACTIVE.
> Wed Dec  4 17:38:56 2013 [LCM][I]: New VM state is PROLOG.
> Wed Dec  4 17:38:56 2013 [TM][I]: Command execution fail:
> /var/lib/one/var/remotes/tm/iscsi/clone
> Front-end:/var/lib/image/win-xp-2.qcow2
> NodeServer:/var/lib/one/var//datastores/0/0/disk.0 0 101
> Wed Dec  4 17:38:56 2013 [TM][E]: clone: Command "    set -e
> Wed Dec  4 17:38:56 2013 [TM][I]:
> Wed Dec  4 17:38:56 2013 [TM][I]: # get size
> Wed Dec  4 17:38:56 2013 [TM][I]: SIZE=$(sudo lvs --noheadings -o lv_size
> "/dev//var/lib/image/win-xp-2/qcow2")
> Wed Dec  4 17:38:56 2013 [TM][I]:
> Wed Dec  4 17:38:56 2013 [TM][I]: # create lv
> Wed Dec  4 17:38:56 2013 [TM][I]: sudo lvcreate -L${SIZE}
> /var/lib/image/win-xp-2 -n qcow2-0
> Wed Dec  4 17:38:56 2013 [TM][I]:
> Wed Dec  4 17:38:56 2013 [TM][I]: # clone lv with dd
> Wed Dec  4 17:38:56 2013 [TM][I]: sudo dd
> if=/dev//var/lib/image/win-xp-2/qcow2
> of=/dev//var/lib/image/win-xp-2/qcow2-0 bs=64k
> Wed Dec  4 17:38:56 2013 [TM][I]:
> Wed Dec  4 17:38:56 2013 [TM][I]: # new iscsi target
> Wed Dec  4 17:38:56 2013 [TM][I]: TID=$(sudo tgtadm --lld iscsi --op show
> --mode target |             grep "Target" | tail -n 1 |             awk
> '{split($2,tmp,":"); print tmp[1]+1;}')
> Wed Dec  4 17:38:56 2013 [TM][I]:
> Wed Dec  4 17:38:56 2013 [TM][I]: sudo tgtadm --lld iscsi --op new --mode
> target --tid $TID  --targetname Front-end:/var/lib/image/win-xp-2.qcow2-0
> Wed Dec  4 17:38:56 2013 [TM][I]: sudo tgtadm --lld iscsi --op bind --mode
> target --tid $TID -I ALL
> Wed Dec  4 17:38:56 2013 [TM][I]: sudo tgtadm --lld iscsi --op new --mode
> logicalunit --tid $TID  --lun 1 --backing-store
> /dev//var/lib/image/win-xp-2/qcow2-0
> Wed Dec  4 17:38:56 2013 [TM][I]: sudo tgt-admin --dump |sudo tee
> /etc/tgt/targets.conf >& /dev/null" failed: ssh: Could not resolve hostname
> /var/lib/image/win-xp-2.qcow2: Name or service not known
> Wed Dec  4 17:38:56 2013 [TM][E]: Error cloning
> NodeServer:/dev//var/lib/image/win-xp-2/qcow2-0
> Wed Dec  4 17:38:56 2013 [TM][I]: ExitCode: 255
> Wed Dec  4 17:38:56 2013 [TM][E]: Error executing image transfer script:
> Error cloning NodeServer:/dev//var/lib/image/win-xp-2/qcow2-0
> Wed Dec  4 17:38:56 2013 [DiM][I]: New VM state is FAILED
>
> 3) the iSCSI INITIATOR is only installed in the NodeServer. the tgt (for
> tgt admin) is only installed in the iSCSIHost, so the /etc/tgt/targets.conf
> is only in the iSCSIHost.
>
> From the result, it doesn't look like the Front-end and NodeServer can
> well communicate with the iSCSIHost, can access the iSCSI storage partition
> created under the iSCSIHost target.
>
> It is much appreciated if anyone can help with the above.
>
> Thanks kindly,
> Q.S.
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>

-- 
Jaime Melis
C12G Labs - Flexible Enterprise Cloud Made Simple
http://www.c12g.com | jmelis at c12g.com

--

Confidentiality Warning: The information contained in this e-mail and
any accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person
and/or entity to whom it is addressed (i.e. those identified in the
"To" and "cc" box). They are the property of C12G Labs S.L..
Unauthorized distribution, review, use, disclosure, or copying of this
communication, or any part thereof, is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify us
immediately by e-mail at abuse at c12g.com and delete the e-mail and
attachments and any copy from your system. C12G's thanks you for your
cooperation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20131211/20eb5221/attachment-0002.htm>