I tried to start a VM from the OVM manager and it produced the following:
12:31:32,015: Starting operation 'Virtual Machine Start' on object 'd3bcd3595f354eb18c6298ae55679f10 (mldbovm4s)'
Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.JobFailureException: OVMAPI_5001E Job: 1,375,151,489,392/1375151489391/Start Virtual Machine mldbovm4s, failed. The job has a Job Failure Event: 1,375,151,493,342/Job Error: Server Async Command Failed/(07/30/2013 12:31:33:428 PM)
Async operation failed on server: DCOVM4S.
Server error message: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000da667039e9298f71/VirtualMachines/d3bcd3595f354eb18c6298ae55679f10/vm.cfg'] failed (1): stderr: Error: Disk isn't accessible
stdout: Using config file "/OVS/Repositories/0004fb0000030000da667039e9298f71/VirtualMachines/d3bcd3595f354eb18c6298ae55679f10/vm.cfg".
I tried to run xm create from the command line and it produced the same error.
I did a quick google and there are a lot of discussion around selinux but selinux is not modified and is left as disabled.
Well, the implication is, that the vdisk image is not present, where it is stated in the guest config file vm.cfg. Issue a
cat /OVS/Repositories/0004fb0000030000da667039e9298f71/VirtualMachines/d3bcd3595f354eb18c6298ae55679f10/vm.cfg and see where it expects the vdisk to be and check if it's really there.