Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

[SUCCESS] Virtualize Windows 10 for ARM on M1 with Alexander Graf's qemu hypervisor patch

Gnattu said:
But only a very small portion requires a D3D driver. Most of them will work if we have a proper fake GPU to allow basic resolution settings etc.
Click to expand...

As i said, there is a default D3D adapter/driver, which makes most of the apps (mostly games, mind you?) run - albeit very slow.
If you pass NULL as pAdapter to D3D12CreateDevice(...) it will return the first available adapter/device with a proper D3D driver, which in case you have a GPU with no supported D3D driver, happens to be the WARP adapter/device.
 
Gerdi said:
As i said, there is a default D3D adapter/driver, which makes most of the apps (mostly games, mind you?) run - albeit very slow.
If you pass NULL as pAdapter to D3D12CreateDevice(...) it will return the first available adapter/device with a proper D3D driver, which in case you have a GPU with no supported D3D driver, happens to be the WARP adapter/device.
Click to expand...
What I mean is that most application do not require D3D at all to function.
 
Microsoft totally lets the enterprise download an ARM version of their latest version and my enterprise key works on it. Just so people are aware licensing wise it is possible even for non OEM just not for the average user.

arm.PNG
 
ha1o2surfer said:
Microsoft totally lets the enterprise download an ARM version of their latest version and my enterprise key works on it. Just so people are aware licensing wise it is possible even for non OEM just not for the average user.

View attachment 1684301
Click to expand...

and the exact file name of the ISO would be

SW_DVD9_Win_Pro_10_20H2_64ARM_English_Pro_Ent_EDU_N_MLF_-2_X22-41558.ISO

correct? could you provide a checksum for the ISO? thnx!
 
I'm running low on storage. Can anyone tell me how to uninstall qemu and everything else in this walkthrough completely please?
 
Gnattu said:
What I mean is that most application do not require D3D at all to function.
Click to expand...

Well, even the GUI is using D3D and the DXGI swap chain for different effects - but i assume thats fast enough under SW rasterization.
Otherwise yes, most applications outside games do not need D3D.
 
If you are a Windows Insider, you can enter your credentials and switch to DEV channel and update the VM to a Fe Build of Windows. Those are the most recent builds.
 
I think there is an issue in nvme qemu driver, at least on macos/m1/hvf host and windows guest as we use it here. Sometimes I get corrupted files after shutdown/startup cycle, it also invokes disk check on boot pretty often. I am not doing anything that can specifically cause this.
 
netkas said:
I think there is an issue in nvme qemu driver, at least on macos/m1/hvf host and windows guest as we use it here. Sometimes I get corrupted files after shutdown/startup cycle, it also invokes disk check on boot pretty often. I am not doing anything that can specifically cause this.
Click to expand...

yup, same here...
 
Gerdi said:
I use a Surface Pro X as my daily driver (aside from my MacBook Pro) and there are very few issues with 32 bit x86 apps. Of course drivers as well as most kernel mode stuff could be an issue.
There are apps which are not compatible with Windows 10 in general, but most apps of the last 20 years and even some older do run flawless. I was surprised that even some fairly old apps, like the original Unreal game (from 1998 - the first game which used the unreal engine) does indeed run with Direct3D acceleration.

You can run OpenGL apps up to OpenGL 3.2. There is lots on development going on at the moment - you are possibly not quite up-to-date regarding Windows ARM?
There is no issue with RetroArch or Dolphin even before the availability of OpenGL 3.2 as they support Direct3d12 as backend - as do many other emulators like SNES9x, PCSX, Mame, PPSSPP - which are available in a native ARM64 version under Windows.
Click to expand...

Ah, yeah, I can see it now. Microsoft just recently released an OpenCL/OpenGL compatibility layer that translates OpenGL calls to Direct3D 12 essentially.

I sold my Surface Pro X a long while ago after realizing that it was not going to fit my workflow as expected. Microsoft foregoing Azure Data Studio and SQL Management Studio being a big part of that.

RetroArch is not stable with D3D for me. Many cores will crash because a lot of them still depend on OpenGL (for instance, Beetle PSX or DuckStation). And OpenGL didn't work right at all. PPSSPP is much the same way. D3D12 would crash a lot. Dolphin is better, but it's not D3D 12. And Vulkan is non-existent so the Pro X ended up not being that much better than an old Intel iGPU to me.

Not sure if the situation is much better now than it was before, but that was what happened when I tried to use it last year, and I just gave up.
 
tdar said:
@billp I see that you have sound working on Windows, Can you tell me what driver you used?
Click to expand...
not a billp, but i have tried this, from first post, windows detects and installs driver automatically

-device intel-hda -device hda-duplex
 
  • Like
Reactions: bill-p
netkas said:
not a billp, but i have tried this, from first post, windows detects and installs driver automatically

-device intel-hda -device hda-duplex
Click to expand...
Seems that it works for some people and not for others. I've looked at all the screenshots here on the thread, and only Bill's have working audio. I'm using the GUI wrapper, so I can't see my startup commands.
 
That's what I have as well. I launch everything through the terminal. It's likely the wrapper isn't including that line.
 
netkas said:
I think there is an issue in nvme qemu driver, at least on macos/m1/hvf host and windows guest as we use it here. Sometimes I get corrupted files after shutdown/startup cycle, it also invokes disk check on boot pretty often. I am not doing anything that can specifically cause this.
Click to expand...
There is a known bug in QEMU's NVME implementation - it does not reinitialize correctly after the simulated PCIe reset.

EDIT: this could probably be avoided by switching the device type to either SCSI or virtio. I have not bothered to try this on my M1 Air, but I work with QEMU a lot...
 
bill-p said:
So, here is how I got my Linux setup to work. A bit different from what you guys are doing, I'm guessing. I didn't have to pass in kernel/initrd:

Code: 
#!/bin/bash
./qemu-system-aarch64 \
-M virt,highmem=off \
-accel hvf \
-m 4G \
-smp 2 \
-cpu max \
-drive file=storage.img,index=0,media=disk \
-serial stdio \
-netdev type=user,id=net0 \
-device virtio-gpu-pci -vga none \
-device nec-usb-xhci \
-device usb-kbd \
-device usb-tablet \
-device intel-hda -device hda-duplex \
-device virtio-net-pci,netdev=net0,romfile="" \
-bios QEMU_EFI.fd

Make sure there's a storage.img. I used qemu-img to create it.
If you need to install using the live CD, just add this (make sure to remove it after you're done with installation):

Code: 
-device file=PATH_TO_LIVE_CD,index=2,media=cdrom

Boots every time. Though... you may lose the cursor if/when you get into the UI.

To fix that, either set "SWcursor" to "true" in xorg.conf (you may have to recreate this in Recovery if you're on a newer version of Ubuntu). Or... add this:

Code: 
-display default,show-cursor=on

^ what that does is basically just "unhide" your mouse cursor when it enters the window. Would be useful in case it gets hard to see where you're pointing to. But I'd recommend doing "SWcursor" fix if you have the time to spare.

And yeah, V2 is far better. There are some other stuffs that can still be patched (like hidpi support, for instance), but it is... pretty much just what I'll want out of an eventual Parallels/VMWare release anyways. It has been useful and super stable!
Click to expand...
Even with the V2 patches, I am still getting 100% CPU utilization with both Ubuntu and Fedora in idle state. Windows VM works fine.

@bill-p Do you have the same issue? I was planning to use the background always-running linux VM with docker engine + docker-sync for local development.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back