Bugzilla Bug 137886

Reliably probably isn't the right word.
Many of the docs I've read put semi-colons at the end of each line in the vm
config, so that's what I've done on my test system.
get_domname() doesn't strip that semi-colon off, so making the is_running()
check fail whether the vm is actually running or not.
Changing the sed call to:
sed -ne 's/^[ \t]*name[ \t]*=[ \t]*"\([^"]*\)"[;]*/\1/p' $1
(adding a [;] after the last " and before the last *)
makes it work either way of defining config variables.

Thanks for your report and proposed fix.

get_domname() has been rewritten for xen-tools-3.0.2-r3 , which should hit the
tree in the next few days (at which point this bug will be resolved).

Fixed xen-tools-3.0.2-r3.

Andrew, while your re-write fixed the problem this bug was originally about,
you've unfortunately introduced a new one.
[[:alpha:]_] should be [[:alnum:]_], or you could use \w.
Numbers are legal in VM names.

Mike, according to bug #148628 the alpha->alnum fix was included in -r4

Please check to make sure you're using xen-tools-3.0.2-r4, and let me know so I
can properly close this bug.

(In reply to comment #4)
> Mike, according to bug #148628 the alpha->alnum fix was included in -r4
> 
> Please check to make sure you're using xen-tools-3.0.2-r4, and let me know so I
> can properly close this bug.

Ahh, yes, sorry. I'm testing 3.0.3, and as it fails to install the init scripts
I took the first one I saw in ${FILESDIR} which is different than
${FILESDIR}/3.0.2-r4.

Reopening so I can mark as fixed - stupid bugzilla :-)

Fixed in xen-tools-3.0.2-r4.