You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Curious Pandora <p4...@gmail.com> on 2022/03/24 01:13:23 UTC
Strange Virtual Router Problem
Hello all,
After dedicating a pod for system vms (might have nothing to do with the
problem )
the virtual routers stopped working.
The routers cannot launch since they are created with 174080kb of memory.
<memory unit='KiB'>174080</memory>
<currentMemory unit='KiB'>174080</currentMemory>
According to the logs from the management server indeed the creation
parameters include a maxram of 170MB.
[{"com.cloud.agent.api.StartCommand":{"vm":{"id":"1410","name":"r-1410-VM","state":"Starting","type":"DomainRouter","cpus":"1","minSpeed":"166","maxSpeed":"500","
178257920","maxRam":"(170.00 MB) 178257920","arch":"x86_64","os":"Debian
GNU/Linux 11 (64-bit)","platformEmulator":"Debian GNU/Linux 11
(64-bit)","bootArgs":" template=domP name=r-1410-VM
Checking the database i confirmed that:
1) The system offering for is the default "System Offering For Software
Router"
2) At ram_size column the correct value "256" is present
Cloudstack is at version: 4.16.1
--
p4nd0ra - the curious
Re: Strange Virtual Router Problem
Posted by Curious Pandora <p4...@gmail.com>.
Good catch.
vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor was set
to True and mem.overprovisioning.factor is at 1.5.
This particular new pod has only two clusters at the moment.
Thanks a lot
On Sun, Mar 27, 2022 at 12:46 PM Rafael Weingärtner <
rafaelweingartner@gmail.com> wrote:
> Are you using overprovisioning?
>
> Em sáb., 26 de mar. de 2022 21:30, Curious Pandora <p4...@gmail.com>
> escreveu:
>
> > After some further looking round and testing i am providing my findings.
> >
> > After monitoring all the database queries it is confirmed that the proper
> > sevice_offering is returned back to the job.
> > The values are correct and double checked.
> >
> > By increasing the ram_size in the database to 512 from 256 the router is
> > successfully launched with 375MB or ram.
> >
> > <memory unit='KiB'>349184</memory>
> > <currentMemory unit='KiB'>349184</currentMemory>
> >
> > The same behavior is observed in the consoleproxy and secondary storage
> vm.
> >
> > Console proxy offering is allocating 1GB of memory normally but only
> 715MB
> > are actually allocated
> > Secondary storage is allocating 512MB of memory normally but only 357MB
> > are actually allocated
> >
> > That probably indicates some problem with the code.
> >
> > On Thu, Mar 24, 2022 at 10:50 PM Curious Pandora <p4...@gmail.com>
> > wrote:
> >
> > > Yes. I already confirmed that.
> > >
> > > +---------------------+
> > > | service_offering_id |
> > > +---------------------+
> > > | 22 |
> > > +---------------------+
> > >
> > >
> > >
> >
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
> > > | id | cpu | speed | ram_size | nw_rate | mc_rate | ha_enabled |
> > > limit_cpu_use | host_tag | default_use | vm_type | sort_key |
> > > is_volatile | deployment_planner | dynamic_scaling_enabled |
> > >
> > >
> >
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
> > > | 22 | 1 | 500 | 256 | NULL | NULL | 1 |
> > > 0 | NULL | 1 | domainrouter | 0 | 0
> |
> > > NULL | 1 |
> > >
> > >
> >
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
> > >
> > >
> > > On Thu, Mar 24, 2022 at 10:39 AM Wei ZHOU <us...@gmail.com>
> wrote:
> > >
> > >> Hi,
> > >>
> > >> Can you check the database to see if the service offering is correct ?
> > >>
> > >> select service_offering_id from vm_instance where id=1410;
> > >> select * from service_offering where id=<service_offering_id>;
> > >>
> > >> -Wei
> > >>
> > >>
> > >>
> > >> On Thu, 24 Mar 2022 at 09:23, Curious Pandora <p4...@gmail.com>
> > wrote:
> > >>
> > >> > Hello all,
> > >> >
> > >> > After dedicating a pod for system vms (might have nothing to do with
> > the
> > >> > problem )
> > >> > the virtual routers stopped working.
> > >> >
> > >> > The routers cannot launch since they are created with 174080kb of
> > >> memory.
> > >> > <memory unit='KiB'>174080</memory>
> > >> > <currentMemory unit='KiB'>174080</currentMemory>
> > >> >
> > >> > According to the logs from the management server indeed the creation
> > >> > parameters include a maxram of 170MB.
> > >> >
> > >> >
> > >> >
> > >>
> >
> [{"com.cloud.agent.api.StartCommand":{"vm":{"id":"1410","name":"r-1410-VM","state":"Starting","type":"DomainRouter","cpus":"1","minSpeed":"166","maxSpeed":"500","
> > >> > 178257920","maxRam":"(170.00 MB)
> > 178257920","arch":"x86_64","os":"Debian
> > >> > GNU/Linux 11 (64-bit)","platformEmulator":"Debian GNU/Linux 11
> > >> > (64-bit)","bootArgs":" template=domP name=r-1410-VM
> > >> >
> > >> > Checking the database i confirmed that:
> > >> > 1) The system offering for is the default "System Offering For
> > Software
> > >> > Router"
> > >> > 2) At ram_size column the correct value "256" is present
> > >> >
> > >> > Cloudstack is at version: 4.16.1
> > >> >
> > >> > --
> > >> > p4nd0ra - the curious
> > >> >
> > >>
> > >
> > >
> > > --
> > > p4nd0ra - the curious
> > >
> >
> >
> > --
> > p4nd0ra - the curious
> >
>
--
p4nd0ra - the curious
Re: Strange Virtual Router Problem
Posted by Rafael Weingärtner <ra...@gmail.com>.
Are you using overprovisioning?
Em sáb., 26 de mar. de 2022 21:30, Curious Pandora <p4...@gmail.com>
escreveu:
> After some further looking round and testing i am providing my findings.
>
> After monitoring all the database queries it is confirmed that the proper
> sevice_offering is returned back to the job.
> The values are correct and double checked.
>
> By increasing the ram_size in the database to 512 from 256 the router is
> successfully launched with 375MB or ram.
>
> <memory unit='KiB'>349184</memory>
> <currentMemory unit='KiB'>349184</currentMemory>
>
> The same behavior is observed in the consoleproxy and secondary storage vm.
>
> Console proxy offering is allocating 1GB of memory normally but only 715MB
> are actually allocated
> Secondary storage is allocating 512MB of memory normally but only 357MB
> are actually allocated
>
> That probably indicates some problem with the code.
>
> On Thu, Mar 24, 2022 at 10:50 PM Curious Pandora <p4...@gmail.com>
> wrote:
>
> > Yes. I already confirmed that.
> >
> > +---------------------+
> > | service_offering_id |
> > +---------------------+
> > | 22 |
> > +---------------------+
> >
> >
> >
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
> > | id | cpu | speed | ram_size | nw_rate | mc_rate | ha_enabled |
> > limit_cpu_use | host_tag | default_use | vm_type | sort_key |
> > is_volatile | deployment_planner | dynamic_scaling_enabled |
> >
> >
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
> > | 22 | 1 | 500 | 256 | NULL | NULL | 1 |
> > 0 | NULL | 1 | domainrouter | 0 | 0 |
> > NULL | 1 |
> >
> >
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
> >
> >
> > On Thu, Mar 24, 2022 at 10:39 AM Wei ZHOU <us...@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> Can you check the database to see if the service offering is correct ?
> >>
> >> select service_offering_id from vm_instance where id=1410;
> >> select * from service_offering where id=<service_offering_id>;
> >>
> >> -Wei
> >>
> >>
> >>
> >> On Thu, 24 Mar 2022 at 09:23, Curious Pandora <p4...@gmail.com>
> wrote:
> >>
> >> > Hello all,
> >> >
> >> > After dedicating a pod for system vms (might have nothing to do with
> the
> >> > problem )
> >> > the virtual routers stopped working.
> >> >
> >> > The routers cannot launch since they are created with 174080kb of
> >> memory.
> >> > <memory unit='KiB'>174080</memory>
> >> > <currentMemory unit='KiB'>174080</currentMemory>
> >> >
> >> > According to the logs from the management server indeed the creation
> >> > parameters include a maxram of 170MB.
> >> >
> >> >
> >> >
> >>
> [{"com.cloud.agent.api.StartCommand":{"vm":{"id":"1410","name":"r-1410-VM","state":"Starting","type":"DomainRouter","cpus":"1","minSpeed":"166","maxSpeed":"500","
> >> > 178257920","maxRam":"(170.00 MB)
> 178257920","arch":"x86_64","os":"Debian
> >> > GNU/Linux 11 (64-bit)","platformEmulator":"Debian GNU/Linux 11
> >> > (64-bit)","bootArgs":" template=domP name=r-1410-VM
> >> >
> >> > Checking the database i confirmed that:
> >> > 1) The system offering for is the default "System Offering For
> Software
> >> > Router"
> >> > 2) At ram_size column the correct value "256" is present
> >> >
> >> > Cloudstack is at version: 4.16.1
> >> >
> >> > --
> >> > p4nd0ra - the curious
> >> >
> >>
> >
> >
> > --
> > p4nd0ra - the curious
> >
>
>
> --
> p4nd0ra - the curious
>
Re: Strange Virtual Router Problem
Posted by Curious Pandora <p4...@gmail.com>.
After some further looking round and testing i am providing my findings.
After monitoring all the database queries it is confirmed that the proper
sevice_offering is returned back to the job.
The values are correct and double checked.
By increasing the ram_size in the database to 512 from 256 the router is
successfully launched with 375MB or ram.
<memory unit='KiB'>349184</memory>
<currentMemory unit='KiB'>349184</currentMemory>
The same behavior is observed in the consoleproxy and secondary storage vm.
Console proxy offering is allocating 1GB of memory normally but only 715MB
are actually allocated
Secondary storage is allocating 512MB of memory normally but only 357MB
are actually allocated
That probably indicates some problem with the code.
On Thu, Mar 24, 2022 at 10:50 PM Curious Pandora <p4...@gmail.com> wrote:
> Yes. I already confirmed that.
>
> +---------------------+
> | service_offering_id |
> +---------------------+
> | 22 |
> +---------------------+
>
>
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
> | id | cpu | speed | ram_size | nw_rate | mc_rate | ha_enabled |
> limit_cpu_use | host_tag | default_use | vm_type | sort_key |
> is_volatile | deployment_planner | dynamic_scaling_enabled |
>
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
> | 22 | 1 | 500 | 256 | NULL | NULL | 1 |
> 0 | NULL | 1 | domainrouter | 0 | 0 |
> NULL | 1 |
>
> +----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
>
>
> On Thu, Mar 24, 2022 at 10:39 AM Wei ZHOU <us...@gmail.com> wrote:
>
>> Hi,
>>
>> Can you check the database to see if the service offering is correct ?
>>
>> select service_offering_id from vm_instance where id=1410;
>> select * from service_offering where id=<service_offering_id>;
>>
>> -Wei
>>
>>
>>
>> On Thu, 24 Mar 2022 at 09:23, Curious Pandora <p4...@gmail.com> wrote:
>>
>> > Hello all,
>> >
>> > After dedicating a pod for system vms (might have nothing to do with the
>> > problem )
>> > the virtual routers stopped working.
>> >
>> > The routers cannot launch since they are created with 174080kb of
>> memory.
>> > <memory unit='KiB'>174080</memory>
>> > <currentMemory unit='KiB'>174080</currentMemory>
>> >
>> > According to the logs from the management server indeed the creation
>> > parameters include a maxram of 170MB.
>> >
>> >
>> >
>> [{"com.cloud.agent.api.StartCommand":{"vm":{"id":"1410","name":"r-1410-VM","state":"Starting","type":"DomainRouter","cpus":"1","minSpeed":"166","maxSpeed":"500","
>> > 178257920","maxRam":"(170.00 MB) 178257920","arch":"x86_64","os":"Debian
>> > GNU/Linux 11 (64-bit)","platformEmulator":"Debian GNU/Linux 11
>> > (64-bit)","bootArgs":" template=domP name=r-1410-VM
>> >
>> > Checking the database i confirmed that:
>> > 1) The system offering for is the default "System Offering For Software
>> > Router"
>> > 2) At ram_size column the correct value "256" is present
>> >
>> > Cloudstack is at version: 4.16.1
>> >
>> > --
>> > p4nd0ra - the curious
>> >
>>
>
>
> --
> p4nd0ra - the curious
>
--
p4nd0ra - the curious
Re: Strange Virtual Router Problem
Posted by Curious Pandora <p4...@gmail.com>.
Yes. I already confirmed that.
+---------------------+
| service_offering_id |
+---------------------+
| 22 |
+---------------------+
+----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
| id | cpu | speed | ram_size | nw_rate | mc_rate | ha_enabled |
limit_cpu_use | host_tag | default_use | vm_type | sort_key |
is_volatile | deployment_planner | dynamic_scaling_enabled |
+----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
| 22 | 1 | 500 | 256 | NULL | NULL | 1 |
0 | NULL | 1 | domainrouter | 0 | 0 | NULL
| 1 |
+----+------+-------+----------+---------+---------+------------+---------------+----------+-------------+--------------+----------+-------------+--------------------+-------------------------+
On Thu, Mar 24, 2022 at 10:39 AM Wei ZHOU <us...@gmail.com> wrote:
> Hi,
>
> Can you check the database to see if the service offering is correct ?
>
> select service_offering_id from vm_instance where id=1410;
> select * from service_offering where id=<service_offering_id>;
>
> -Wei
>
>
>
> On Thu, 24 Mar 2022 at 09:23, Curious Pandora <p4...@gmail.com> wrote:
>
> > Hello all,
> >
> > After dedicating a pod for system vms (might have nothing to do with the
> > problem )
> > the virtual routers stopped working.
> >
> > The routers cannot launch since they are created with 174080kb of
> memory.
> > <memory unit='KiB'>174080</memory>
> > <currentMemory unit='KiB'>174080</currentMemory>
> >
> > According to the logs from the management server indeed the creation
> > parameters include a maxram of 170MB.
> >
> >
> >
> [{"com.cloud.agent.api.StartCommand":{"vm":{"id":"1410","name":"r-1410-VM","state":"Starting","type":"DomainRouter","cpus":"1","minSpeed":"166","maxSpeed":"500","
> > 178257920","maxRam":"(170.00 MB) 178257920","arch":"x86_64","os":"Debian
> > GNU/Linux 11 (64-bit)","platformEmulator":"Debian GNU/Linux 11
> > (64-bit)","bootArgs":" template=domP name=r-1410-VM
> >
> > Checking the database i confirmed that:
> > 1) The system offering for is the default "System Offering For Software
> > Router"
> > 2) At ram_size column the correct value "256" is present
> >
> > Cloudstack is at version: 4.16.1
> >
> > --
> > p4nd0ra - the curious
> >
>
--
p4nd0ra - the curious
Re: Strange Virtual Router Problem
Posted by Wei ZHOU <us...@gmail.com>.
Hi,
Can you check the database to see if the service offering is correct ?
select service_offering_id from vm_instance where id=1410;
select * from service_offering where id=<service_offering_id>;
-Wei
On Thu, 24 Mar 2022 at 09:23, Curious Pandora <p4...@gmail.com> wrote:
> Hello all,
>
> After dedicating a pod for system vms (might have nothing to do with the
> problem )
> the virtual routers stopped working.
>
> The routers cannot launch since they are created with 174080kb of memory.
> <memory unit='KiB'>174080</memory>
> <currentMemory unit='KiB'>174080</currentMemory>
>
> According to the logs from the management server indeed the creation
> parameters include a maxram of 170MB.
>
>
> [{"com.cloud.agent.api.StartCommand":{"vm":{"id":"1410","name":"r-1410-VM","state":"Starting","type":"DomainRouter","cpus":"1","minSpeed":"166","maxSpeed":"500","
> 178257920","maxRam":"(170.00 MB) 178257920","arch":"x86_64","os":"Debian
> GNU/Linux 11 (64-bit)","platformEmulator":"Debian GNU/Linux 11
> (64-bit)","bootArgs":" template=domP name=r-1410-VM
>
> Checking the database i confirmed that:
> 1) The system offering for is the default "System Offering For Software
> Router"
> 2) At ram_size column the correct value "256" is present
>
> Cloudstack is at version: 4.16.1
>
> --
> p4nd0ra - the curious
>