Stefan Bader and I have continued trying to reproduce this. Here's what we've done:
- Tried to reproduce on various pieces of hardware available to us. - Requested the hardware information about the host machine from IS and tested on the most similar machine available to us (same generation Xeon CPU, but a different model). - Requested information about relevant software versions on the host machine (trusty with a 4.4.0-59 hwe kernel) and tried to reproduce using the same software versions. - Requested the libvirt configuration for the instance which exhibits the failures and tried using a similar configuration. So far we are still unable to reproduce the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682077 Title: nested KVM fails - KVM: entry failed, hardware error 0x0 Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Bug description: Hello, We just noticed that systemd's autopkgtests have started failing often on amd64 for all releases, when run in Canonical's scalingstack cloud. This is nested KVM I think. TEST RUN: Basic systemd setup + /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.10.0-19-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.unFR7V/rootdisk.img -initrd /boot/initrd.img-4.10.0-19-generic -machine accel=kvm -enable-kvm -cpu host -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' KVM: entry failed, hardware error 0x0 EAX=00000000 EBX=00000000 ECX=00000000 EDX=000206a1 ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000 EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0000 00000000 0000ffff 00009300 CS =f000 ffff0000 0000ffff 00009b00 SS =0000 00000000 0000ffff 00009300 DS =0000 00000000 0000ffff 00009300 FS =0000 00000000 0000ffff 00009300 GS =0000 00000000 0000ffff 00009300 LDT=0000 00000000 0000ffff 00008200 TR =0000 00000000 0000ffff 00008b00 GDT= 00000000 0000ffff IDT= 00000000 0000ffff CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000000 Code=d8 66 e8 d8 a2 ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 90 <ea> 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I have observed a failure on the compute node (region lgw01) Linux amemasu 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6 18:02:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and a pass of the exact same package on the compute node (region lcy01) Linux kissel 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Here's an example log- https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-2713/zesty/amd64/s/systemd/20170411_182221_b8bea@/log.gz I found bug #1329434 which looks more or less identical and was fixed for 3.13. Perhaps it regressed in 4.4? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
