The next install question is how to install on AMR in 1.0.
The challenge is that arm and the rest of the embedded world is kind of a zoo. In the i386 and amd64 worlds, microsoft kept things orderly by simplifying saying if a device (motherboard) didn't meet a set of specification it wouldn't boot windows. Their market dominance was enough to keep the PC world somewhat homogenous.
Things are slightly different in the ARM ecosystem. To deal with the differences among devices, developers came up with the Device Tree. ( https://en.wikipedia.org/wiki/Device_tree ) The challange for distibutions, like omv, is that each device must have a kernel custom compiled with a device specific device tree.
This means one of two solutions (there are probably more I haven't thought of):
1: A custom image for each device or class of device.
2. A second recommend install method where the user installs debian for their device and then install OVM via apt-get.
I think, what I would recommend, is that we defer the decision for another release and continue to call arm 'testing' until 1.1. I have found a bunch of little arm related issues that might take a while to fix... which are not show stoppers for i386 or amd64.
FWIW, I am currently testing OMV on Xycel NSA325, Raspberry PI, and Beagle Bone with a Qnap TS-212P on order while working with upstream kirkwood developers to get fully functioning kernels for kirkwood processors which run most of the 1 and 2 drive NAS devices on the market.
It pretty much works on any arm device that has wheezy available.