On Jun 24, 2015, at 9:50 AM, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > On 23/06/2015 00:08, John Nielsen wrote: >>>> I’m resurrecting an old thread since I haven’t heard anything in a >>>> while. Has anyone looked in to the KVM+apicv bug documented above as >>>> well as here: >>>> >>>> https://bugs.launchpad.net/qemu/+bug/1329956 ? >>>> >>>> If appropriate, where should I go to file a KVM bug (since this isn’t >>>> really Qemu’s problem)? >>> >>> Hi John, does this happen with the latest upstream kernel version ? >> >> I know for sure it happens with 4.0.4 and I’m not aware of any newer changes that would affect it.-- >> To unsubscribe from this list: send the line "unsubscribe kvm" in > > Can you reproduce it with 10.1? > > I did this: > > 1) download > http://download.pcbsd.org/iso/10.1-RELEASE/amd64/PCBSD10.1.2-x64-trueos-server.raw.xz > and unpack it > > 2) run it with "qemu-kvm -drive > if=virtio,PCBSD10.1.2-x64-trueos-server.raw -smp 2" > > 3) login as root/pcbsd, type "reboot" > > I would like to know if I'm doing anything wrong. My machine is a Xeon > E5 v3 (Haswell). My SeaBIOS build doesn't have the atkbd0 bug, but just > to rule that out, can you send me your Seabios binary > (/usr/share/qemu/bios*.bin) as well? Interesting. Using the same PC-BSD image I am able to reproduce on a server running slightly older software but I can not reproduce running bleeding edge. I verified enable_apicv=Y on both. In both cases I ran qemu-kvm -drive if=virtio,file=PCBSD10.1.2-x64-trueos-server.raw -smp 2 -vnc 0.0.0.0:0 Specifically: Breaks (VM hangs during boot after pressing ctrl-alt-del): kernel 3.12.22 qemu-kvm-1.7.0-3.el6.x86_64 seabios-1.7.3.1-1.el6.noarch Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz Works (VM reboots normally): kernel 4.0.4 qemu-kvm-2.3.0-6.el7.centos.x86_64 seabios-bin-1.8.1-1.el7.centos.noarch Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz Unfortunately I no longer have the test environment I used a few days ago to reproduce this issue so I can’t verify the software versions that were in use. It’s possible I was mistaken about the kernel version (I thought it was 4.0.4). Perhaps it really is fixed in the newer kernel? In any case, this is great news! I would be interested in identifying the patch(es) that fixed the issue to make back-porting them easier, but I won’t have time to do a binary search anytime soon. Thanks for looking in to this again. If anyone else is interested in identifying what specifically fixed the issue please let me know if I can do anything to help. JN -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
