cloudstack

Author SHA1 Message Date

Author	SHA1	Message	Date
Koushik Das	4809d91c51	CLOUDSTACK-5993: Cloud agent fails to start on 32-bit system vms (cpvm and ssvm) created with 4GB RAM offering Capped the max heap size of the JVM at 2600M for 32-bit system VMs. For 64-bit, existing logic works fine. (cherry picked from commit `1ae02009b5`) Signed-off-by: Animesh Chaturvedi <animesh@apache.org>	2014-02-02 16:06:14 -08:00
Hugo Trippaers	6c26104282	Move the system vm to a separate maven project. All (almost) files belonging to the systemvm aer now centralize in the systemvm directory. The code for the separate functions is still in the services directory. This will make the code easier to understand and makes it clear that the systemvm is a separate item. It alos means that it can be excluded from the build entirely by not adding the systemvm profile, this will speed up the compiles somewhat.	2013-09-20 18:31:02 +08:00

Koushik Das

4809d91c51

CLOUDSTACK-5993: Cloud agent fails to start on 32-bit system vms (cpvm and ssvm) created with 4GB RAM offering

Capped the max heap size of the JVM at 2600M for 32-bit system VMs. For 64-bit, existing logic works fine.
(cherry picked from commit 1ae02009b5)

Signed-off-by: Animesh Chaturvedi <animesh@apache.org>

2014-02-02 16:06:14 -08:00

Hugo Trippaers

6c26104282

Move the system vm to a separate maven project.

All (almost) files belonging to the systemvm aer now centralize in the systemvm directory. The code for the separate functions is still in the services directory. This will make the code easier to understand and makes it clear that the systemvm is a separate item. It alos means that it can be excluded from the build entirely by not adding the systemvm profile, this will speed up the compiles somewhat.

2013-09-20 18:31:02 +08:00

2 Commits