VDMs in the cloud
One of the most requested and fastest growing use cases for VLAB VDMs is cloud-based deployments, typically supporting large-scale test regressions. For this reason, VDMs have been designed from the very beginning to support the features that matter in the cloud.
Select the cloud service to suit your needs
Cloud services such as Amazon AWS allows the user to choose from a wide range of target hardware architectures to run their application software/workloads. Options are plentiful and include single or multicore CPUs, different RAM and memory configurations, inclusion of dedicated GPUs etc.
VLAB VDMs are created with HiperSim technology that can run multi-threaded and operate on single, or multiple CPU Cores when available. This gives the user the flexibility to choose optimum performance when and if required.
VLAB VDMs, built for regression testing
There are some features that simply make testing large scale regressions in an automated fashion that much simpler. Take for example Python scripting for configuration, powerful CLI for simple launch, run and execute, checkpoint save and restore to allow tests to focus on the code being tested, or something as simple as IO capture for verification and analysis.
VDM launch – Short and sharp
In this video you can see a VLAB ARMv8a VDM launched from the console of an Amazon AWS EC2 instance. In this case the VDM gets up and running, booting Linux in under 10 seconds, before exiting. As part of the CLI the user has requested VLAB to ‘print stats’ which shows information on the number of instructions executed, per CPU core stats, even comparison to Real Time performance.
VDM checkpoint save and restore
In this video you can see a VLAB ARMv8a VDM launched from the console of an Amazon AWS EC2 instance. After running for a short period of time, the VDM is interrupted and a checkpoint is saved. Following on from this the user launches from the CLI the same VDM, restoring from a checkpoint file. On close inspection, you can see that the simulation clock is exactly the same from the exit of the first VDM to the entry of the second.