kvm-guest-drivers-windows
qemu
kvm-guest-drivers-windows | qemu | |
---|---|---|
32 | 37 | |
1,843 | - | |
2.5% | - | |
9.3 | - | |
3 days ago | - | |
C | ||
BSD 3-clause "New" or "Revised" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kvm-guest-drivers-windows
-
Why are Apple Silicon VMs so different?
There's mature VirtIO drivers for just about everything already, under the virtio-win umbrella: https://github.com/virtio-win/kvm-guest-drivers-windows
My desktop PC is using libvirt+qemu (on an Arch host. I use Arch, btw) to PCI passthru my RTX 4090 GPU to a Windows guest. I installed the guest initially with emulated SATA for the main drive. Once Windows was up and running, I installed virtio-win and the guest is now using virtIO accelerated drivers for the network interface, main disk. I'm also sharing some filesystems using virtio-fs.
-
Help with my setup
So, I started configuring the PC with ubuntu desktop (since I need a GUI for my use case). Then I setup a windows KVM with this. In my use case, I want the windows VM to be always connected to a VPN (Mullvad) that has the toggle of LAN connections turned on. This is because I want to use sunshine on the KVM to stream my desktop to a firestick. This is how I have been configuring one PC till now for my family to be able to watch TV. The issue is that I cannot use sunshine or parsec cos there are no encoders in the VM, thus the performance sucks. (I could use software encoders, but I would use too much CPU for windows VM, which would make me unable to run a LLM (this was my plan) )
-
VirGL
Note also: it just got an experimental Windows driver!
[1]https://github.com/virtio-win/kvm-guest-drivers-windows/pull...
- [viogpu3d] Virtio GPU 3D acceleration for windows by max8rr8 · Pull Request #943 · virtio-win/kvm-guest-drivers-windows
- Virtio GPU 3D acceleration for windows
-
Libvirt/virtio: Limited resolution on Windows guests
virtio-GPU for Windows for now is just a basic display driver, without any kind of acceleration, so there shouldn't be any difference between using it and QXL, which is fully emulated and in it, if necessary, you can increase the VRAM to be able to use high resolutions, as explained here. Note: this link is just from a quick search, I tried this for myself some time ago but my intention was not to increase the resolution but just to find out if it was possible to have some kind of 3D acceleration, as it happens in VirtualBox, but is not possible yet.
- I Have passed through my gpu to windows VM in proxmox but not getting output via hdmi
-
Why is the virt-manager display so slow?
The only sorta-responsive display tech I've found is Virt with GL (3D) enabled. And if your physical box has 4k video you can forget about going anywhere near full screen with that guest VM.
-
Virtiofs slower than Samba file sharing?
I suggest you open a new issue in the repository describing this, or search if there is one open reporting the same. Also, keep in mind that as an early stage it might be a good idea to avoid copying important files using this, you could end up losing data unless you do an integrity check (recently I tried installing a game on the VM in a host directory and it didn't work. I'm thinking of an alternative or going back to using VirtualBox, since the shared folders worked very well for this purpose).
-
Windows Server 2019 - vioscsi Warning (129) - locking up data drive
The problem was really bad with latest virtio drivers, so I downgraded to version 204, as per: https://github.com/virtio-win/kvm-guest-drivers-windows/issues/623
qemu
-
QEMU AioContext removal and how it was done
https://gitlab.com/qemu-project/qemu/-/blob/master/hw/scsi/s...
QEMU's IOThreads allow the user to configure the threads and get something similar to thread per core architecture. But if 1 thread becomes a bottleneck, then some form of thread synchronization is needed again even with thread per core architecture. Some problems can be parallelized and they work well with thread per core.
-
Why are Apple Silicon VMs so different?
Add `ENV ERL_FLAGS="+JPperf true"` to your Dockerfile and it will build just fine cross platform. The flag just changes some things during build time and won’t affect runtime performance.
[1] https://gitlab.com/qemu-project/qemu/-/issues/1034
-
RISC-V Vector benchmark results
> I don't know how rdcycle works on qemu.
That's a good question! I had to look it up myself ...
Obviously qemu TCG isn't a cycle-accurate emulation. Using RDCYCLE / reading the corresponding CSR eventually calls https://gitlab.com/qemu-project/qemu/-/blob/69680740eafa1838... which calls cpu_get_host_ticks is basically an arch-independent wrapper around RDTSC.
So it just measures the time taken to run using RDTSC. Which I guess is what you would want (maybe?). It would measure the time taken to emulate the vector instruction in host instructions.
> This benchmark is more meant for developers to figure out how to vectorize algorithms effectively, as in which instructions to choose.
Absolutely, I'm not saying the qemu results would say anything very deep, but they're kind of interesting from the point of view of either optimizing qemu or if you have to use qemu because the hardware you want isn't available / isn't cheap enough.
-
The IMPOSSIBLE RISCV HACK: Vector Extension 0.7.1-draft w/ current Linux kernel! – René Rebe
I see the commits that started switch support from RVV 071 to 100 start here, https://gitlab.com/qemu-project/qemu/-/commit/9ec6622db30df1c00d863c1ffc33341f9e0a534d
-
I booted Linux 292,612 times
>> https://gitlab.com/qemu-project/qemu/-/issues/1696 ]
> Can I please just get the detail in mail instead of having to go look at random websites?
Maybe it's me but if I did boot boot linux 292.612 times to find a bug, you might as well click a link to a repository of a major open source project on a major git hosting service.
Is it really that weird to ask people online to check a website? Maybe I don't know the etiquette of these mail lists so this is a geniune question.
-
Rise: Accelerate the Development of Open Source Software for RISC-V
Capstone is used[1] by QEMU as disassembly engine in debug logs and in monitor mode debugger, by the way, so it's in the scope of the RISE effort.
[1] https://gitlab.com/qemu-project/qemu/-/blob/master/disas/cap...
-
Intel Arc 750 Crashes Host + Display Cable Workaround not needed anymore (Windows)
A user on the qemu bugtracker found a way to get the Intel Arc working across resets without crashing the host: Just don't passthrough the audio device of the GPU and everything works!
- Qemu 7.2.2: command line syntax in libvirt domain changed
- Anyone know if there's a way to disable ReBar on only one GPU?
-
[RFT] Allow QEMU to expose static REBAR capability
[1]https://gitlab.com/qemu-project/qemu/-/commit/3412d8ec9810b819f8b79e8e0c6b87217c876e32 [2]https://gitlab.com/alex.williamson/qemu/-/commit/9a6d1822a2bd55f5dee1aec1b6529ae57949d5ba.patch
What are some alternatives?
quickemu - Quickly create and run optimised Windows, macOS and Linux desktop virtual machines.
gcc
vgpu_unlock - Unlock vGPU functionality for consumer grade GPUs.
riscv-binutils-gdb - RISC-V backports for binutils-gdb. Development is done upstream at the FSF.
LookingGlass - An extremely low latency KVMFR (KVM FrameRelay) implementation for guests with VGA PCI Passthrough.
nbdkit
qemu-pinning - My QEMU fork with pinning (affinity) support and a few tweaks.
safeclib - safec libc extension with all C11 Annex K functions
dokany - User mode file system library for windows with FUSE Wrapper
lzbench - lzbench is an in-memory benchmark of open-source LZ77/LZSS/LZMA compressors
swtpm - Libtpms-based TPM emulator with socket, character device, and Linux CUSE interface.
CLK - A latency-hating emulator of: the Acorn Electron and Archimedes, Amstrad CPC, Apple II/II+/IIe and early Macintosh, Atari 2600 and ST, ColecoVision, Enterprise 64/128, Commodore Vic-20 and Amiga, MSX 1/2, Oric 1/Atmos, early PC compatibles, Sega Master System, Sinclair ZX80/81 and ZX Spectrum.