[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959249#comment-13959249
 ] 

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'>
  <name>r-44-VM</name>
  <uuid>4a9056d0-1279-4b38-9579-16e8582eb780</uuid>
  <description>Debian GNU/Linux 7(64-bit)</description>
  <memory unit='KiB'>131072</memory>
  <currentMemory unit='KiB'>65536</currentMemory>
  <vcpu placement='static'>1</vcpu>

------------

#Storage
#Thu Apr 03 15:39:11 EDT 2014
guest.network.device=cloudbr0
workers=5
private.network.device=cloudbr0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
guid=ad414028-b816-39e0-879f-47626ec2e058
vm.memballoon.disable=true
public.network.device=cloudbr0
cluster=1
local.storage.uuid=65abf660-5f13-4b57-9424-372d5232145f
domr.scripts.dir=scripts/network/domr/kvm
host=199.195.215.83
LibvirtComputingResource.id=1


> Issue is Reproduceable - Suggest Re-open 
> -----------------------------------------
>
>                 Key: CLOUDSTACK-6334
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6334
>             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
(v6.2#6252)

Reply via email to