cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prieur Leary (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6334) Issue is Reproduceable - Suggest Re-open
Date Thu, 03 Apr 2014 21:31:17 GMT


Prieur Leary commented on CLOUDSTACK-6334:

Check below for dumpxml output of the virtual router that is actually currently running fine
(I can console in and MS sees its status as good).

It does seem logical that is a memory issue, and I have tried overprovisioning of 2 and 4.
Interesting that the dumpxml from virsh reads the same no matter what. I even created a custom
System Offering with 512MB memory in an effort to work around the problem.

I also verified the vm.memballon.disable=true setting and copied the agent properties below.
And yes, I did start/stop the agent.

Thanks for all your help!.

<domain type='kvm' id='25'>
  <description>Debian GNU/Linux 7(64-bit)</description>
  <memory unit='KiB'>131072</memory>
  <currentMemory unit='KiB'>65536</currentMemory>
  <vcpu placement='static'>1</vcpu>


#Thu Apr 03 15:39:11 EDT 2014

> Issue is Reproduceable - Suggest Re-open 
> -----------------------------------------
>                 Key: CLOUDSTACK-6334
>                 URL:
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.3.0
>         Environment: CentOS - KVM
>            Reporter: Prieur Leary
>             Fix For: 4.2.0
> This is issue is reproducable when setting the cluster property mem.overprovisioning.factor
greater than 1.
> If the virtual router is started or re-started and the variable is set greater than one,
the Virtual Router VM is created on the host, but never boots.

This message was sent by Atlassian JIRA

View raw message