You are right Paolo, it is old: qemu-kvm-common-1.5.3-105.el7_2.4.x86_64 libvirt-daemon-driver-qemu-1.2.17-13.el7_2.4.x86_64 qemu-guest-agent-2.3.0-4.el7.x86_64 ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch qemu-img-1.5.3-105.el7_2.4.x86_64 qemu-kvm-1.5.3-105.el7_2.4.x86_64 These are the packages you have if you use Centos-7, and I guess also if you have Red Hat 7... -Mike "I have Centos-7" On Mon, Jun 6, 2016 at 4:56 PM, Mike Marshall <hubcap@xxxxxxxxxxxx> wrote: > Greetings... > > Please keep my email in the loop on this, I'm only subscribed > to fs-devel... > > Linux-next fails to boot properly for me, but Linux 4.7-rc2 from > Linus' tree boots fine. > > I got started bisecting next-20160603 last Friday, but didn't get done. > > git bisect start '64289ca' '7f9bef9' > > I picked 7f9bef9 as the good commit to start with because I knew > I needed 7f9bef9 or else my QEMU-KVM would crash. Before I started > the bisection, I verified that 7f9bef9 was indeed good by checking > out a branch from next-20160603 with 7f9bef9 as the HEAD and > building it: git checkout -b gas 7f9bef9 > > Today I got next-20160606 and checked to see if the same failure > occurred - it did. So I continued with the bisection of next-20160603. > > I arrived at 407aa3ff6f54ea2be7959639d664ae5183e2e9f8 as the bad commit. > > > 407aa3f is a rather complex commit... there is a problem with it, > but I'm not sure what to do next... both 7f9bef9 and 407aa3f are > related to ACPICA... > > -Mike -- 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
