That said, "really low latency" is relative. Device assignment will give you excellent I/O performance in terms of sending data to/from the device, particularly for bulk DMA transfers. Where you (likely) still pay a penalty is in terms of interrupt delivery, as on most chips these are still routed through the host even in "passthrough" mode. Even so, you're looking at delays at the outside on the tens of microseconds scale, depending on which microarchitecture you're on and how well tuned the fiddly bits of your hypervisor (presumably KVM for most users) are. Some configurations will be much better behaved here. If your audio hardware goes into polling mode (or can be made to do so) when it is recording you can potentially avoid the interrupts entirely.
(source: I work on Google Compute Engine, in particular on virtualized networking, historically on performance. Virtual interrupt delivery latency is a topic near and dear to my heart, although I don't know a damned thing about audio gear and its tolerances there :)
What you need: Wine Wineasio (for Wine support in FL Studio or others) KXstudio
1. http://kxstudio.linuxaudio.org/index.php 2. https://www.youtube.com/watch?v=GBD-wsMiZCk 3. https://www.youtube.com/watch?v=PhfmGGPcwNc
I/O performance is a whole other story, dependent on many workload and hypervisor specific factors.
However, my main reason for needing Windows is for music recording and mixing via Cubase and other DAW software. This requires really low-latency access to my USB and PCI sound cards.
Does anyone have experience with running applications like this in a VM? Is it feasible?
I would be thrilled if I could finally move to Linux or FreeBSD entirely and just keep a Windows 7 VM, all sandboxed up with no Internet access, just for the music recording.