sonic-buildimage/platform/vs/kvm-image.mk

# sonic kvm image

SONIC_KVM_IMAGE = sonic-vs.img.gz
$(SONIC_KVM_IMAGE)_INSTALLS += $(SYSTEMD_SONIC_GENERATOR)
$(SONIC_KVM_IMAGE)_MACHINE = vs
$(SONIC_KVM_IMAGE)_IMAGE_TYPE = kvm
ifeq ($(INSTALL_DEBUG_TOOLS),y)
$(SONIC_KVM_IMAGE)_DOCKERS += $(SONIC_INSTALL_DOCKER_DBG_IMAGES)
$(SONIC_KVM_IMAGE)_DOCKERS += $(filter-out $(patsubst %-$(DBG_IMAGE_MARK).gz,%.gz, $(SONIC_INSTALL_DOCKER_DBG_IMAGES)), $(SONIC_INSTALL_DOCKER_IMAGES))
else
$(SONIC_KVM_IMAGE)_DOCKERS = $(SONIC_INSTALL_DOCKER_IMAGES)
endif
$(SONIC_KVM_IMAGE)_FILES = $(ONIE_RECOVERY_IMAGE) $(ONIE_RECOVERY_KVM_4ASIC_IMAGE) $(ONIE_RECOVERY_KVM_6ASIC_IMAGE)
SONIC_INSTALLERS += $(SONIC_KVM_IMAGE)
[vs]: build sonic vs kvm image (#2269) Signed-off-by: Guohan Lu <gulv@microsoft.com> 2018-11-21 00:32:40 -06:00			`# sonic kvm image`

			`SONIC_KVM_IMAGE = sonic-vs.img.gz`
[build]: Move Systemd service start to systemd generator (#3172) - What I did Move the enabling of Systemd services from sonic_debian_extension to a new systemd generator - How I did it Create a new systemd generator to manually create symlinks to enable systemd services Add rules/Makefile to build generator Add services to be enabled to /etc/sonic/generated_services.conf to be read by the generator at boot time Signed-off-by: Lawrence Lee <t-lale@microsoft.com> 2019-07-29 17:52:15 -05:00			`$(SONIC_KVM_IMAGE)_INSTALLS += $(SYSTEMD_SONIC_GENERATOR)`
[vs]: build sonic vs kvm image (#2269) Signed-off-by: Guohan Lu <gulv@microsoft.com> 2018-11-21 00:32:40 -06:00			`$(SONIC_KVM_IMAGE)_MACHINE = vs`
			`$(SONIC_KVM_IMAGE)_IMAGE_TYPE = kvm`
Enable debug image build for kvm image. (#3203) 2019-07-22 16:30:13 -05:00			`ifeq ($(INSTALL_DEBUG_TOOLS),y)`
			`$(SONIC_KVM_IMAGE)_DOCKERS += $(SONIC_INSTALL_DOCKER_DBG_IMAGES)`
			`$(SONIC_KVM_IMAGE)_DOCKERS += $(filter-out $(patsubst %-$(DBG_IMAGE_MARK).gz,%.gz, $(SONIC_INSTALL_DOCKER_DBG_IMAGES)), $(SONIC_INSTALL_DOCKER_IMAGES))`
			`else`
			`$(SONIC_KVM_IMAGE)_DOCKERS = $(SONIC_INSTALL_DOCKER_IMAGES)`
			`endif`
[vs][multi-asic]: Add new platforms for multi-asic vs. (#8269) Why I did it End goal: To have azure pipeline job to run multi-asic VS tests. Intermediate goal: Require multi-asic KVM image so that the test can be run. The difference between single asic and multi-asic KVM image is asic.conf file which has different NUM_ASIC values. Idea behind the approach in this PR to attain the intermediate goal above: Ease of building multi-asic KVM image so that any user or azure pipeline can use a simple make command to generate single or multi-asic KVM images as required. Use a single onie installer image and multiple KVM images for single and multi-asic images. Current scenario: For VS platform, sonic-vs.bin is generated which is the onie installer image and sonic-vs.img.gz is generated which is the KVM iamge. Scenario to be achieved: sonic-vs.bin - which will include single asic platform, 4 asic platform and 6 asic platform. sonic-vs.img.gz - single asic KVM image sonic-4asic-vs.img.gz - 4 asic KVM image sonic-6asic-vs.img.gz - 6 asic KVM image In this PR, 2 new platforms are added for 4-asic and 6-asic VS. How I did it Create 4-asic and 6-asic device directories with the required files and hwsku files. Add onie-recovery image information in vs platform. How to verify it After this PR change, no build change. sonic-vs.bin onie installer image should include information of new multi-asic vs platforms. 2021-09-01 00:45:59 -05:00			`$(SONIC_KVM_IMAGE)_FILES = $(ONIE_RECOVERY_IMAGE) $(ONIE_RECOVERY_KVM_4ASIC_IMAGE) $(ONIE_RECOVERY_KVM_6ASIC_IMAGE)`
[vs]: build sonic vs kvm image (#2269) Signed-off-by: Guohan Lu <gulv@microsoft.com> 2018-11-21 00:32:40 -06:00			`SONIC_INSTALLERS += $(SONIC_KVM_IMAGE)`