Hi James, I was able to see the full log output in the file you attached, no need to use pastebin now. Also good to know they have a line limit......
One thing I noticed in the log file, after a image capture the node should get reloaded automatically. It didn't happen in this case, for some reason the state of the computer did not get changed. I recommend to. Go to: manage computers select Select All computers make sure computer utilities is selected hit submit Make sure computenode1 is set to available. >> The wiki states "You must add the image to an image group using the VCL >> website after the image capture process is complete. Reservations for the >> image cannot be made until this is done. To add the image to an image >> group, browse to the VCL website and select Manage Images > Edit Image >> Grouping." What's meant to happen after this step? >> On your new image, yes it will need to be mapped correctly. The reason for this mapping is that VCL supports the ability to run different types of images under the same VCL instance, kvm, vmware, virtual box, bare metal and standalone lab machines, and hopefully in the future openstack, cloudstack on so on. This image to computer mapping is the method to correctly have images land on the correct subset of computer resources in your VCL infrastructure. By default, we have made a couple of initial mappings for you, allVMimages is mapped to All VM computers. allimages is mapped to allComputers Once you add you new image to the allVMimages then you should be able to test it out either through the computer reload or through making a new reservation. Aaron -- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
