Virtual-environments: Two different kinds of build agent are in use

[MatthewSteeples]

Description
There are (at least) 2 different kinds of build agent provided by hosted pipelines, and they seem to be configured differently but only very slightly. Most builds don't seem to produce a noticeable difference.

The way to tell which kind you're on is whether it's the agent name is fv-az8 or whether it beings WIN-. They look to be running different CPUs (although both are listed under the Dv2 page), and fv-az8 also emulates a CD drive (see attached Powershell outputs)

There are also differences in the way that the information output in the "Initialize job" step is rendered

Area for Triage:
Servers

Question, Bug, or Feature?:
Question

Virtual environments affected

• [ ] macOS 10.15
• [ ] Ubuntu 16.04 LTS
• [ ] Ubuntu 18.04 LTS
• [ ] Ubuntu 20.04 LTS
• [ ] Windows Server 2016 R2
• [X] Windows Server 2019

Expected behavior
The same build inputs will produce the same build outputs when the version of the agent remains the same

Actual behavior
The build results are different when run on different agents

Repro steps
I'm unable to reproduce the build running on different agents on demand (I'm assuming it's based on how busy the system is and what machines are available), but I've attached some logs demonstrating the output from each.

fv-az8 Powershell Info.txt
win Powershell Info.txt

fv-az8 Initialize Job.txt
win Initialize Job.txt

Question
Is this to be expected? Is it possible for the reason for this to be given?

Thanks

[miketimofeev]

Hi @MatthewSteeples!
Yes, this is expected, the difference is in the virtualization methods, but everything else is similar(the same VM image with the same software)

[miketimofeev]

I'm going to close the issue. Feel free to create a new one if you have more questions.
Thank you!