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 <p4nd...@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
>
