http://bugzilla.novell.com/show_bug.cgi?id=623470 http://bugzilla.novell.com/show_bug.cgi?id=623470#c3 James Fehlig <jfehlig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |koenig@linux.de --- Comment #3 from James Fehlig <jfehlig@novell.com> 2010-07-20 16:38:04 UTC --- (In reply to comment #2)
do you have any suggestion what's the best place to get more tracing info about what's going on ?
Try adding a 'set -x' to top of block-iscsi script then monitor /var/log/xen/xen-hotplug.log while starting your domU. We should then be able to see any failures in block-iscsi. I'm wondering whether the following is needed in the 'add' logic of block-iscsi: /sbin/iscsiadm -m discovery | sed "s/ .*//g" | while read line; do /sbin/iscsiadm -m discovery -t sendtargets -p $line; done >/dev/null An long-ago version of block-iscsi did not contain this line and its addition predates my involvement in this script - so I don't know why it was added. Nothing is being done with the output of sendtargets discovery. Does commenting this line help? Do you have any clue as to how this line improves the script? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.