ACRN Project Technical Community Meeting Minutes - 7/31/2019
Meeting Minutes Archive: https://drive.google.com/drive/u/2/folders/111m6iU3PjSZebOOKzLagYPUWMvseGLeU
ACRN Project TCM - 31th July 2019
Download foil from ACRN Presentation->ACRN_TCM->WW31’19
Q1: What’s the life cycle of GOP from power on to Windows desktop showing up?
A1: VM setup -> OVMF loading -> OVMF loads GOP -> OVMF displays on GOP -> OVMF boots Windows -> Windows display through GOP framebuffer -> Windows load GFX driver -> Windows desktop show up.
Q2: What’s the relationship between VideoBIOS and GOP?
A2: Video BIOS is for legacy BIOS and GOP is for UEFI BIOS.
Q3: What’s the overall boot flow sequence of SOS, GVT-g, OVMF, UOS?
A3: SOS booting -> SOS loading GVT-g -> VM setup by hypervisor -> vGPU created by GVT-g -> OVMF loaded in VM -> OVMF loads UOS bootloader -> UOS booting.
Q4: Can current GOP driver design support pass-throughed GPU device besides GVT-g?
A4: No. We may support it in the future if there’s such requirement.
Q5: What’s development environment of GOP driver? In OVMF?
A5: GOP driver is inside of OVMF (actually in EDK2). And it supports development in both Windows and Linux environment.
Q6: Can GOP driver support other Guest OS beyond Windows?
A6: Yes. GOP driver is OS independent.
Q7: Can GOP driver feature co-exist with KVM’s QEMU’s video driver? Any conflict between GOP’s local display and VNC remote display after GOP driver changes upstreamed?
A7: The driver binary can exist in the OVMF of KVM qemu. But they cannot work at the same time. KVM qemu must set up to use either GVT-g’s vGPU or, the Qemu’s emulated video.
Tel: +86-21-6116 7445
MP: +86-1364 1793 689