Thanks Anshul, just what i wanted to know :)
-thinktwo
2015-04-28 12:16 GMT+02:00 Anshul Gangwar :
> These restrictions are not there due to Hypervisor limitations. These
> limitations are due to way this feature is implemented in CloudStack.
> If we allow those operation then they may work fine
These restrictions are not there due to Hypervisor limitations. These
limitations are due to way this feature is implemented in CloudStack.
If we allow those operation then they may work fine but in long run they may
lead to corruption of VM etc. So to avoid those situation these restrictions
ar
Thanks Anshul,
I did a quick test with adding vCPU and NIC in XenCenter after creating a
snapshot through CloudStack. I also tried reverting the VM to the snapshots
afterwards with the vCPU and NIC still added, and it worked OK.
This made curious about what the background and details for this pat
Hi Jan-Arve,
In which order have you tried adding vCPUs and NICs?
i.e. After creating VM snapshot or before creating snapshot.
And have you deleted VM snapshots before adding vCPUs and NICs?
Regards,
Anshul
On 24-Apr-2015, at 5:58 pm, Jan-Arve Nygård
mailto:jan.arve.nyg...@gmail.com>> wrote:
H
