From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg To: Ard Biesheuvel ,devel@edk2.groups.io From: "Sean" X-Originating-Location: Redmond, Washington, US (50.35.74.15) X-Originating-Platform: Windows Chrome 83 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Mon, 30 Mar 2020 10:00:59 -0700 References: In-Reply-To: Message-ID: <19211.1585587659874241589@groups.io> Content-Type: multipart/alternative; boundary="XwUMVVrTBWZMQwWP7JN7" --XwUMVVrTBWZMQwWP7JN7 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 30, 2020 at 02:36 AM, Ard Biesheuvel wrote: >=20 > It should be trivial to extend this to ARM, using TCG emulation. >=20 > One question though: what happens if the boot does not make it to the > shell, and crashes for some reason? The QEMU process will hang, so I'd > assume some kind of timeout should be applied? It has a 1 minute timeout and then the build will kill the process. The bootlog is uploaded in all cases so you can then look at the log. Here is an example where i didn't configure QEMU right: https://dev.azure.= com/tianocore/edk2-ci-play/_build/results?buildId=3D4942&view=3Dlogs&j=3D6f= b09fdb-58e7-5b12-0698-873f788bd2e9&t=3De63402bd-99b5-5ddd-38f9-868e9402ecc0 And the last lines in the bootlog.txt show MaxCpuCountInitialization: BootCpuCount=3D1 mMaxCpuCount=3D1 Q35BoardVerification: no TSEG (SMRAM) on host bridge DID=3D0x1237; only DI= D=3D0x29C0 (Q35) is supported ASSERT /home/vsts/work/1/s/OvmfPkg/PlatformPei/Platform.c(564): ((BOOLEAN)= (0=3D=3D1)) --XwUMVVrTBWZMQwWP7JN7 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 30, 2020 at 02:36 AM, Ard Biesheuvel wrote:
It should be trivial to extend this to ARM, using TCG emulatio= n.

One question though: what happens if the boot does not make i= t to the
shell, and crashes for some reason? The QEMU process will han= g, so I'd
assume some kind of timeout should be applied?
It has a 1 minute timeout and then the build will kill the process. &= nbsp;

The bootlog is uploaded in all cases so you can then look = at the log.  
Here is an example where i didn't configure QE= MU right: https://dev.azure.com/tianocore/edk2-ci-play/_build/resul= ts?buildId=3D4942&view=3Dlogs&j=3D6fb09fdb-58e7-5b12-0698-873f788bd= 2e9&t=3De63402bd-99b5-5ddd-38f9-868e9402ecc0

And the las= t lines in the bootlog.txt show

MaxCpuCountInitialization: BootCpuCount=3D1 mMaxCpuCount=3D1
Q35BoardVerification: no TSEG (SMRAM) on host bridge DID=3D0x1237; on= ly DID=3D0x29C0 (Q35) is supported
ASSERT /home/vsts/work/1/s/OvmfPkg/PlatformPei/Platform.c(564): ((BOO= LEAN)(0=3D=3D1))




--XwUMVVrTBWZMQwWP7JN7--