As another alternative you can just build a new VM with all the same hardware as the VSA and use the two boot disks that come with the VSA. Basically you are then building a new VM that is a VSA instead of importing. I'd only advise this if you are having trouble importing though.

To do so you would...

1. Create a new VM
2. Select Custom
3. Give it a name
4. Specify the datastore for it
5. For OS specify other linux 32 bit
6. 1 virtual processor
7. 1024 MB of RAM
8. Select a correct network for it
9. Use the LSI logic adapter
10. Use an existing virtual disk (browse to the fist boot disk of the VSA, probably "VSA.vmdk" and specify it as SCSI 0:0, and mark it as independent / persistent)
11. Finish the new VM wizard
12. Edit the new VSA
13. Add another disk (the other boot disk for the VSA, probably "VSA_1.vmdk" and specify it as SCSI 0:1, and mark it as independent / persistent)

From there it should be just like a new VSA that was imported. So you'll still want to add the third data disk @ SCSI 1:0 and reserve resources.... just follow the quick start guide from there.

Please, those who run into problems importing please DO post your experiences or work arounds here. If there is something we can do to the VSA to avoid particular issues we'll make those updates to future versions.

Adam C
Product Manager
LeftHand Networks