Live data from Hacker News

QEMU v4.0.0 released

qemu.org

141–150 of 168 posts

Re: QEMU v4.0.0 released

#141

It's pretty great and has been useful for many use cases for me, except too bad it lacks good 3D graphics support for modern gaming

You don't really need VMs for gaming, at least if you are ready to ditch a few broken games that don't work in Wine. For the most part they work very well these days.

Re: QEMU v4.0.0 released

#143

It's pretty great and has been useful for many use cases for me, except too bad it lacks good 3D graphics support for modern gaming

It all depends on how and if someone will implement a Windows driver for VirGL. Given how complex video drivers are nowadays, it looks like a pretty daunting task.

Intel has support for KVMGT, but AMD/NVIDIA won't support it. This would really be the correct approach to get support from the graphics manufacturers:

https://wiki.archlinux.org/index.php/Intel_GVT-g

Re: QEMU v4.0.0 released

#144
post #5

Last week, I intended to replace VirtualBox with QEMU for my personal use. The spartiate documentation made it really hard. I lack the competence to seriously contribute. The official documentation just explains the numerous parameters. It also points to tutorials (wikibook, etc), which unfortunately are very basic and out of sync. Even Arch Linux does not provide a good documentation (lack of clarity, some obsolete…

We need to spin up a lot of VMs of various Linux distributions for testing Flockport and we found the existing tooling too heavy and involved.

In the end we rolled our own solution that is much more lightweight, uses QEMU directly and provides better visibility, ease of use and even some potentially useful networking features. Here are a few screencasts [1].

This is mainly designed as a module for Flockport and we will preview this soon.

[1] https://www.youtube.com/watch?v=uEnk9m-egeA

Re: QEMU v4.0.0 released

#145
post #89

LTT [1] did a video recently about running macOS on a Linux host using QEMU. Anyone here tried that? If so, what's the experience like? Thanks [1]: https://www.youtube.com/watch?v=ATnpEOo3GJA

I am building a VFIO build this weekend. one of the goals is to power a macOS VM for work. if I remember I will update you on my experience.

I had success getting macOS running on QEMU with my existing PC, but its performance suffered without a dedicated GPU and CPU pinning, which my new build will be configured to handle

Re: QEMU v4.0.0 released

#146

Earlier quoted context omitted.

Thats sounds pretty interesting. Ive been running a hacked together windows VM gaming setup via qemu with vfio passthrough for the past 1.5 years on my local linux server. Im pretty pleased with it. Ive got it down to simply executing a small script and everything comes up. It could be even more automated using evdev potentially (recognizing mouse/keyboard events). I was thinking about expanding the setup to include…

I don't have any specific guides about my setup, but here are a few things that have been helpful to me: - Good starting point for setting up macOS under QEMU/KVM: https://github.com/kholia/OSX-KVM - DSDT/SSDT patching: https://www.tonymacx86.com/threads/ssdt-gpu-graphics-card-in... - AMD reset bug: https://www.reddit.com/r/VFIO/comments/5h351m/gpu_stuck_in_d... - Kernel extension that can help with some GPU issues:…

In case anyone runs across similar AMD GPU issues, the "disable_idle_d3=1" option in the second pastebin link (when used as a kernel parameter) should be prefixed as "vfio-pci.disable_idle_d3=1". Even then, it can still be hit-or-miss with some cards (it works most of the time for me, but some VM restarts still find that the GPU has entered D3 and won't come back without rebooting the host).

Re: QEMU v4.0.0 released

#147

Earlier quoted context omitted.

I don't have any specific guides about my setup, but here are a few things that have been helpful to me: - Good starting point for setting up macOS under QEMU/KVM: https://github.com/kholia/OSX-KVM - DSDT/SSDT patching: https://www.tonymacx86.com/threads/ssdt-gpu-graphics-card-in... - AMD reset bug: https://www.reddit.com/r/VFIO/comments/5h351m/gpu_stuck_in_d... - Kernel extension that can help with some GPU issues:…

In case anyone runs across similar AMD GPU issues, the "disable_idle_d3=1" option in the second pastebin link (when used as a kernel parameter) should be prefixed as "vfio-pci.disable_idle_d3=1". Even then, it can still be hit-or-miss with some cards (it works most of the time for me, but some VM restarts still find that the GPU has entered D3 and won't come back without rebooting the host).

is this a macOS guest specific issue? would I have similar issues on a Windows or Linux guest?

Re: QEMU v4.0.0 released

#148

Anybody here using QEMU? What is your use case?

Mainly playing with old operating systems, I'm a retrocomputing enthusiast. While years ago I would mainly use Virtual PC (I do miss its great GUI) and VMWare (and rarely bochs), qemu improved a lot and has (somewhat decent) support for so many more architectures. You can run Solaris for SPARC and Mac Os 9, for example.

"Solaris for SPARC"

Link?

Re: QEMU v4.0.0 released

#149
post #89

LTT [1] did a video recently about running macOS on a Linux host using QEMU. Anyone here tried that? If so, what's the experience like? Thanks [1]: https://www.youtube.com/watch?v=ATnpEOo3GJA

[deleted]

Re: QEMU v4.0.0 released

#150
post #147

Earlier quoted context omitted.

In case anyone runs across similar AMD GPU issues, the "disable_idle_d3=1" option in the second pastebin link (when used as a kernel parameter) should be prefixed as "vfio-pci.disable_idle_d3=1". Even then, it can still be hit-or-miss with some cards (it works most of the time for me, but some VM restarts still find that the GPU has entered D3 and won't come back without rebooting the host).

is this a macOS guest specific issue? would I have similar issues on a Windows or Linux guest?

I believe it happens for any guest OS (search for "amd reset bug"). Some people are using a workaround that involves removing the device (in the sysfs), suspending the host, and then rescanning, but for me, that's not much better than a host reboot, so when the AMD GPU occasionally does get stuck in D3 (preventing starting the VM after a VM reboot), I just reboot the host. It doesn't happen very often, and when it does, it's only when I'm in the process of rebooting the VM anyway.

Previously, I also attempted using a kernel patch that's been floating around (DECLARE_PCI_FIXUP_HEADER ... quirk_no_bus_reset), but it just gives me corrupt graphics when rebooting the VM.

Post reply on HN