cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alessandro Caviglione <>
Subject Re: Strange instance boot issue
Date Mon, 08 Dec 2014 02:20:07 GMT
Ok... maybe I found the issue!!
Again... I'm learning CS in these month so you've to be patient with me! :)
But this thing is strange...
I configure some Compute offering setting CPU speed to 500 MHz and changing
vCPU number for each offer, all the offerings are with CPU CAP enabled.
Now, if I deploy a W2008R2 instance from a template or an ISO (yes....
W2012 is working fine! :-/) with 4vCPU (4*500 MHz = 2 GHz) I get the
issue... sloooooow boot time (about 15 mins).
If I deploy the same instance with 1 vCPU with 2000 MHz, the instance boot
in 7 sec!!

On Sun, Dec 7, 2014 at 1:49 AM, Alessandro Caviglione <> wrote:

> Hi guys,
> I'm sorry if I submit this problem, I honestly do not think it is a fault
> of CloudStack, but I do not know where to look anymore ...
> For several days (up to a week ago I did not have this problem) I have
> trouble creating templates and run instances.
> My infrastructure is composed of CS4.4.1 and 4 XenServer 6.2 hosts.
> I want to point out that the problem is not due to poor storage
> performance.
> When I create an instance from an ISO, the installation time is greatly
> increased.
> When restarting the instances, for example windows VMs, they remain in the
> boot about 30 minutes.
> The strange thing is that when instances are started, the performances are
> excellent!
> What's even more strange is that trying to install a new VM directly from
> XenServer, installation is fast and the boot issue when restart the VMs
> does not appear and also boot is very fast (about 20/30 sec.)
> In short, the problem seems to be only when the VMs are managed by
> CloudStack.
> I found this article and correct the BIOS of my server, even though I had
> never encountered this problem until a week ago. (
> Someone can give me some guidance?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message