A machine won't be able to support more cores on a VM than the physical
processor. That should result in problems trying to deploy it. I'm guessing
the service offering is still valid since you could add a host later which has
a hex core or two cpus in it. As far as RAM goes, do you have over
This sounds like a great idea.
> From: chiradeep.vit...@citrix.com
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] Revert to VM disk Snapshot
> Date: Mon, 30 Sep 2013 21:53:35 +
>
> +1.
>
> On 9/30/13 2:31 PM, "SuichII, Christopher" wrote:
>
> >The storage subsystem API currentl
If you manually change the vm status in the database would it let you destroy
it then?
> Date: Thu, 3 Oct 2013 20:22:33 +0800
> Subject: Re: [URGENT] Unable to stop/start system VMs after upgrade to 4.2.0
> From: in...@sg.or.id
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
>
> Dea
Hello,
Is it possible to get edit permission? Username is dortiz.
Thanks, David Ortiz
> From: daan.hoogl...@gmail.com
> Date: Sat, 5 Oct 2013 11:08:19 +0200
> Subject: Re: Wiki access
> To: dev@cloudstack.apache.org
>
> Rajesh,
>
> You have access. So I don't
