cros_vm_lib: add/fix some logging

1. Add a log message indicating the path of the VM disk image
   copy, so sheriffs can figure out which of the (possibly)
   multiple images is relevant.
2. Fix an existing log message, which claims that we are continuing,
   even though we are die-ing.
3. Add a comment about a dependency of cbuildbot_stages.py on this
   script.

BUG=chromium:311837
TEST=x86-generic-paladin trybot

Change-Id: I3512bf5a3f013945dd14efbdccc28c10a5ebba66
Reviewed-on: https://chromium-review.googlesource.com/175362
Tested-by: mukesh agrawal <quiche@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Queue: mukesh agrawal <quiche@chromium.org>
diff --git a/lib/cros_vm_lib.sh b/lib/cros_vm_lib.sh
index 254d437..824a6d5 100644
--- a/lib/cros_vm_lib.sh
+++ b/lib/cros_vm_lib.sh
@@ -87,11 +87,13 @@
 
     local vm_image="$1"
     if [ ${FLAGS_copy} -eq ${FLAGS_TRUE} ]; then
+      # This filename template must be kept in sync with cbuildbot_stages.py.
       local our_copy=$(mktemp "${vm_image}.copy.XXXXXXXXXX")
       if cp "${vm_image}" "${our_copy}"; then
+          info "Copied ${vm_image} to ${our_copy}."
           vm_image="${our_copy}"
       else
-          die "Copy failed. Continuing without copy."
+          die "Copy failed. Aborting."
       fi
     fi