bug 11428: remove the constraint based on customer's feedback, we will allow creating volume from a snapshot that was originally taken from root volume. Customers should be aware that when the volume is attached as a data volume, some partitions that were originally created as a root volume may not be recognized by the guest OS

This commit is contained in:
Kelven Yang 2012-01-17 16:10:20 -08:00
parent cf7469241f
commit 3612fc12c8
2 changed files with 6 additions and 2 deletions

View File

@ -1696,12 +1696,14 @@ public class StorageManagerImpl implements StorageManager, StorageService, Manag
//check snapshot permissions
_accountMgr.checkAccess(caller, null, true, snapshotCheck);
/*
// bug #11428. Operation not supported if vmware and snapshots parent volume = ROOT
if(snapshotCheck.getHypervisorType() == HypervisorType.VMware
&& _volumeDao.findByIdIncludingRemoved(snapshotCheck.getVolumeId()).getVolumeType() == Type.ROOT){
throw new UnsupportedServiceException("operation not supported, snapshot with id " + snapshotId + " is created from ROOT volume");
}
*/
}
// Verify that zone exists

View File

@ -1370,11 +1370,13 @@ public class UserVmManagerImpl implements UserVmManager, UserVmService, Manager
throw new InvalidParameterValueException("Snapshot id=" + snapshotId + " is not in " + Snapshot.Status.BackedUp + " state yet and can't be used for template creation");
}
/*
// bug #11428. Operation not supported if vmware and snapshots parent volume = ROOT
if(snapshot.getHypervisorType() == HypervisorType.VMware && snapshotVolume.getVolumeType() == Type.DATADISK){
throw new UnsupportedServiceException("operation not supported, snapshot with id " + snapshotId + " is created from Data Disk");
}
*/
hyperType = snapshot.getHypervisorType();
}