When we tried to make a new VM on the VMware ESX using SC VMM we wanted to use dynamic disk VMs, but we could only select fixed-sized disks.

Using its GUI, we tried to add standard ISO images of operating systems that would serve as image sources in our SC VMM image library. But it's not obvious how to do this, so we simply manually copied and moved images into the required folder.

We wanted to use an ISO image to initially install a guest VM onto Hyper-V. We setup the guest and chose Novell's SLES 10.2 (64-bit) as the operating system to run on the Hyper-V host. We chose the ISO image we had manually added to the library. We didn't want to copy the ISO image so we chose: 'Share image file instead of copying it'. But when we did that we got an inarticulate error message, telling us in a roundabout way that the machine requesting the image did not have proper access rights. Eventually, the problems were solved with a change in file/folder permissions. But it was no mean feat to get the Library function to work.

Moving things around

When we initially attempted to migrate VMs between Hyper-V hosts we got an error message advising us of processor incompatibility issues. The only way to perform a cross-CPU migration with SC-VMM is to shut the VM down, copy the image file, then restart it elsewhere. Why would you want to use this function in a shutdown VM, when this action is no different than taking a snapshot and reloading it as a VM? This means additional downtime is required to complete a very simple and ostensibly common act of migration.