Hi, > Here's why: I'd been used to Microsoft *not* cooperating usefully in > Windows-on-QEMU/KVM situations. But this instance was totally different. > In fact I'm still a bit shocked, in the positive sense. We got a fast > and helpful, to-the-point response. It's a first, considering my own > experience, and it has strongly changed my impression of Microsoft's > Windows team. I'd like us to acknowledge that in the commit message, if > possible.
And Microsoft saying this is tsc calibration code also gives us a workaround: When using 'qemu -cpu host,hv-frequencies=on' the windows installer iso boots just fine, most likely because cdboot.efi queries the hypervisor for the tsc frequency instead of running the calibration loop. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#104359): https://edk2.groups.io/g/devel/message/104359 Mute This Topic: https://groups.io/mt/98771399/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
