[Bug 1859310] Re: libvirt probing fails due to assertion failure with KVM and 'none' machine type

2020-01-31 Thread Joey Adams
This was fixed in commit 8f54bbd0b4 "x86: Check for machine state object class before typecasting it". ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net

[Bug 1851972] Re: pc-q35-4.1 and AMD Navi 5700/XT incompatible

2020-01-31 Thread Joey Adams
Commit d1972be13f ("accel/kvm: Make "kernel_irqchip" default on") fixes the default mixup I described above. This isn't related to Marshall's issue as it involves qemu 3.0 vs 3.1, but at least it cleans up some confusion. -- You received this bug notification because you are a member of qemu- de

[Bug 1851972] Re: pc-q35-4.1 and AMD Navi 5700/XT incompatible

2020-01-12 Thread Joey Adams
Commit 11bc4a13 (Nov 13, 2019, merged after v4.2.0-rc5) moved the kernel-irqchip parameter to -accel, but I think the default was inadvertently changed to off. The documentation was changed to say the default is on, but the code change seems to have done the opposite. I found this when I tested m

[Bug 1859310] [NEW] libvirt probing fails due to assertion failure with KVM and 'none' machine type

2020-01-11 Thread Joey Adams
Public bug reported: Using libvirt on Ubuntu 19.10, I get the following error when I try to set to the latest qemu from git (commit dc65a5bdc9): error: internal error: Failed to start QEMU binary /usr/local/bin /qemu-system-x86_64 for probing: /home/joey/git/qemu/target/i386/kvm.c:2176:kvm_a