How are you viewing the W10 VM on linux, via a VNC client or other streamed client? Does each monitor & vm have its own dedicated GPU?
My setup has 2 GPUs/monitors, one for windows VM, one for Linux VM (I can also use dual monitor for either VM by changing monitor input sources). But I also have separate keyboard & mouse for each VM.
If I want one k/m to work with both VMs, I've used barrier software -- and it works, plus I believe there are ways to lock/unlock the cursor onto a screen -- but i usually just use separate k/m so i don't have to worry about that.
nvidia gt710 - fully supported by macos and pre-dates uefi/vbios crap. even comes in passive/lowprofile models. you want the ddr3 model not the gddr5 one, i have this one currently for £47 (think i paid £34 used) - no displayport though. ebay has them starting at about £15, don't pay £70+ though as they're onboard graphics sort of level.
Solved!, For me at least
I'm using Mullvad vpn
In the mullvad gui app on my host OS I tried switching (local network sharing) in preferences to ON, it then connected to ethernet in the OS in the QEMU VM.
Exactly. On the same host, 1903 works but 1909 fails.
$ qemu-system-x86_64 --version
QEMU emulator version 4.2.0
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
ovmf seems to be version 1:202002-1
according to arch repo:
https://www.archlinux.org/packages/?sort=&q=ovmf&maintainer=&flagged=
BTW, I encountered the same problem with Ubuntu 20.04 preview as well.
Windows can be tricky because it like to hard-code the controller information in the Hardware Abstraction Layer (HAL). See this: https://www.virtualbox.org/wiki/Migrate_Windows
First check that the VM you're trying to use the new image with has the same controller setup (same IDE type or SATA, etc.) as the original machine. There's an old tool out there that can be installed on the running machine to make it more willing to deal with changes in hardware, but I can't find it.
It's probably that you did not allocate enough storage space, as you appear to have allocated 20GB but the minimum requirements are listed as 32GB.
I seems nobody has better suggestion then let me chime in with some rough solutions.
Usually you should not have any big issues setting up the guest.
The only stuff which comes to my mind is badly configured network interface (100mbit instead of 1/10 gbit), VM filesystems located on wrong disk (hdd instead of ssd, or even worse - nfs), filesystems on smb with big latency, wrong number of cpus for the workload or low amount of memory assigned.
Those are the most obvious fails. There is more but its hard to predict what you may be using.
Assumptions: - you know something is off and need proof.
You feel the performance is low but cant find the bottleneck
You can shuffle the workload between VMs, hosts
You can put controlled load on your guest.
You know how to perform standard linux performance checks (top, iostat, vmstat etc...)
Test the workload on VM and compare to non VM environment (laptop, desktop, host if possible). This will tell you if there is any big issue.
If approach #1 is not possible, try to move the workload to different machine. Preferably different VM solution. Compare with your initial setup.
Check standard metrics on host and on guest (top, iostat, vmstat, iptraf etc.) during load and test if there is a possibility to hit it even harder (if iostat shows 20MB/s average, can you load it even more? etc)
All above can be done much better if you have any monitoring solution (I suggest zabbix) which will give you any clues what is happening.
If you dont have one use the nmon http://nmon.sourceforge.net/pmwiki.php
Additionally check if the external components (DB, external soap web services, queues etc) are not having performance issues.
Unfortunately you did not provided much info so hopefully something from the stuff above will be helpful.
What's the full command that you're using?
Are you trying to just run qemu-system-x86_64 or virt-install? Or are you using virsh or virt-manager?
I personally haven't used edk2-x86_64-code.fd but have had great luck with the Clover EFI boot loader.
QEMU doe not lock the USB drive so it snapshots the USB volume - this means that file writes under E2B dont really write to the USB drive. This can cause strange problems. Use RMPrepUSB - F11 QEMU feature for correct QEMU emulation with file writes or...
Use Virtual Box + VMUB. MUCH faster!
http://www.easy2boot.com/testing-e2b/using-qemu-or-virtual-box/
I want to run Everything Search (I have looked into Linux alternatives but I have found them to be underwhelming). It is a simple and lightweight application that indexes all my media files and lets me search through them with ease and perform file manager-type operations on them. As you can see, the application's performance itself is probably not a concern, but my concern is sharing (mounting?) terabytes of files on my Linux host machine to the Windows virtual machine. I also want to consume and edit media content on the Windows virtual machine (image viewer/editor and video player/editor), ideally.
Basically, I just want to perform operations that an advanced file manager and a basic video player/editor and image viewer/editor on a Windows virtual machine on lots of data that is on the host machine. My primary concern is somehow retrieving the data from the host machine to perform operations on. I'm not sure how this will work--I don't want the data to be directly on the virtual machine (as much as possible) because that would be inefficient space-wise and also performance-wise, but I don't know if that's even possible.
I haven't tried Virtualbox with my particular use-case (only played around with it when I tried out Linux before switching to it) and based on what I've felt performance-wise and read, QEMU/KVM seems like it will at least be marginally better in terms of performance. The possibility of PCI passthrough even if I don't have the hardware or need for it alone is worth the switch.
Whilst I don't know how to fix this directly I'd know a possible workaround.
If your motherboard still has a PCIe slot free (a 1x slot is enough), put a USB 3.0 PCIe card (example) in it and pass it through to the VM like you did your GPU.
Then it's just plug&play with any USB device + if you get a USB hub switch (if you're fancy even an KVM switch). Then you can switch between those two systems on the fly using a single mouse and keyboard.
Only problem here could be that the card won't get it's own IOMMU group assigned but that depends on the motherboard