[Qemu-devel] [Bug 1717708] Re: QEMU aarch64 can't run Windows ARM64 iso's

[Laszlo Ersek \(Red Hat\)]

(1) See also <https://bugs.launchpad.net/qemu/+bug/1717708>.

(2) One idea is (a) letting Windows use VirtioGpuDxe's GOP (blt only)
until it calls ExitBootServices() -- which I have already confirmed to
work with an ARM64 Windows Server variant that I was legally given
access to --, and (b) once available, injecting a native ARM64 virtio-
gpu-pci driver into the installer image, which Windows could start using
right after ExitBootServices().

(3) BTW, Gerd recently posted

[Qemu-devel] [PATCH 0/4] ramfb: simple boot framebuffer, no legacy vga
http://lists.nongnu.org/archive/html/qemu-devel/2017-11/msg03299.html

which could be an alternative. (Albeit -- in my opinion! -- inferior to
(2).)

(4) In the above-referenced article at <https://docs.microsoft.com/en-us
/windows-hardware/drivers/bringup/uefi-requirements-that-apply-to-all-
windows-platforms>, Microsoft write, "Microsoft welcomes feedback and
comments from implementers on this set of requirements". That sounds
awesome: for a change, how about we stop reverse engineering Windows
boot (off of lawfully obtained media of course) and engage in a
conversation. Writing VirtioGpuDxe wasn't trivial, and I'm not amused at
the thought of (a) it being a waste, (b) struggling with more and more
hacks / custom devices & drivers until one set happens to work. We
should stop fabricating one-sided hacks for placating Windows.

(5) Can we please stop making references to leaked or otherwise
unlawfully obtained Windows media, and warez sites. In the upstream QEMU
bug tracker no less. Thanks.

** Bug watch added: bugzilla.tianocore.org/ #785
   https://bugzilla.tianocore.org/show_bug.cgi?id=785

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1717708

Title:
  QEMU aarch64 can't run Windows ARM64 iso's

Status in QEMU:
  New

Bug description:
  Hi,
  recently Windows ARM64 ISOs have been posted on the internet..
  just checked with latest QEMU 2.10 release from 
  https://qemu.weilnetz.de/w64/qemu-w64-setup-20170830.exe 
  "h:\qemu\qemu-system-aarch64.exe" -boot d -cdrom 
h:\iso\16353.1000.170825-1423.RS_PRERELEASE_CLIENTPRO_OEMRET_ARM64FRE_ES-ES.ISO 
-m 2048 -cpu cortex-a57 -smp 1 -machine virt
  seems no video output..
  checked various machine options for example versatilepb (says guest has not 
initialized the guest)..

  so don't know if it's a QEMU bug or lacking feature but can support
  running Windows ARM64 builds (would be nice if you can add a
  Snapdragon835 machine type which is which first machines will be
  running..)

  
  note running a Windows x64 ISO with similar parameters works (removing -cpu 
and -machine as not needed)

  thanks..

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1717708/+subscriptions