On Fri, May 10, 2013 at 8:03 PM, Kashyap Chamarthy <kashyap.cv@xxxxxxxxx> wrote: > Also, > > I'm able to reproduce this consistently: When I create an L2 guest: > > -------------- > [.....] > > [ 463.655031] Dazed and confused, but trying to continue > [ 463.975563] Uhhuh. NMI received for unknown reason 20 on CPU 1. > [ 463.976040] Do you have a strange power saving mode enabled? > [ 463.976040] Dazed and confused, but trying to continue > 29 199M 29 58.7M 0 0 136k 0 0:25:02 0:07:20 0:17:42 > 153k > [ 465.136405] Uhhuh. NMI received for unknown reason 30 on CPU 1. > [ 465.137042] Do you have a strange power saving mode enabled? > [ 465.137042] Dazed and confused, but trying to continue > [ 466.645818] Uhhuh. NMI received for unknown reason 20 on CPU 1. > [ 466.646044] Do you have a strange power saving mode enabled? > [ 466.646044] Dazed and confused, but trying to continue > [ 466.907999] Uhhuh. NMI received for unknown reason 30 on CPU 1. > [ 466.908033] Do you have a strange power saving mode enabled? > > -------------- > > > > On Fri, May 10, 2013 at 6:30 PM, Kashyap Chamarthy <kashyap.cv@xxxxxxxxx> > wrote: >> >> Heya, >> >> This is on Intel Haswell. >> >> First, some version info: >> >> L0, L1 -- both of them have same versions of kernel, qemu: >> >> ===== >> $ rpm -q kernel --changelog | head -2 >> * Thu May 09 2013 Josh Boyer - 3.10.0-0.rc0.git23.1 >> - Linux v3.9-11789-ge0fd9af >> ===== >> >> ===== >> $ uname -r ; rpm -q qemu-kvm libvirt-daemon-kvm libguestfs >> 3.10.0-0.rc0.git23.1.fc20.x86_64 >> qemu-kvm-1.4.1-1.fc19.x86_64 >> libvirt-daemon-kvm-1.0.5-2.fc19.x86_64 >> libguestfs-1.21.35-1.fc19.x86_64 >> ===== >> >> Additionally, neither nmi_watchdog, nor hpet enabled on L0 & L1 kernels: >> ===== >> $ egrep -i 'nmi|hpet' /etc/grub2.cfg >> $ >> ===== >> >> KVM parameters on L0 : >> ===== >> $ cat /sys/module/kvm_intel/parameters/nested >> Y >> $ cat /sys/module/kvm_intel/parameters/enable_shadow_vmcs >> Y >> $ cat /sys/module/kvm_intel/parameters/enable_apicv >> N >> $ cat /sys/module/kvm_intel/parameters/ept >> Y >> ===== >> >> -> That's the stack trace I'm seeing, when I start the L2 guest: >> ------------------------------------------------ >> ....... >> [ 2.162235] Kernel panic - not syncing: VFS: Unable to mount root >> fs on unknown-block(0,0) >> [ 2.163080] Pid: 1, comm: swapper/0 Not tainted 3.8.11-200.fc18.x86_64 >> #1 >> [ 2.163080] Call Trace: >> [ 2.163080] [<ffffffff81649c19>] panic+0xc1/0x1d0 >> [ 2.163080] [<ffffffff81d010e0>] mount_block_root+0x1fa/0x2ac >> [ 2.163080] [<ffffffff81d011e9>] mount_root+0x57/0x5b >> [ 2.163080] [<ffffffff81d0132a>] prepare_namespace+0x13d/0x176 >> [ 2.163080] [<ffffffff81d00e1c>] kernel_init_freeable+0x1cf/0x1da >> [ 2.163080] [<ffffffff81d00610>] ? do_early_param+0x8c/0x8c >> [ 2.163080] [<ffffffff81637ca0>] ? rest_init+0x80/0x80 >> [ 2.163080] [<ffffffff81637cae>] kernel_init+0xe/0xf0 >> [ 2.163080] [<ffffffff8165bd6c>] ret_from_fork+0x7c/0xb0 >> [ 2.163080] [<ffffffff81637ca0>] ? rest_init+0x80/0x80 >> [ 2.163080] Uhhuh. NMI received for unknown reason 30 on CPU 0. >> [ 2.163080] Do you have a strange power saving mode enabled? >> [ 2.163080] Dazed and confused, but trying to continue >> [ 2.163080] Uhhuh. NMI received for unknown reason 20 on CPU 0. >> [ 2.163080] Do you have a strange power saving mode enabled? >> [ 2.163080] Dazed and confused, but trying to continue >> [ 2.163080] Uhhuh. NMI received for unknown reason 30 on CPU 0. >> ------------------------------------------------ >> >> I'm able to reproduce to reproduce this consistently. >> >> L1 QEMU command-line: >> ==================== >> $ ps -ef | grep -i qemu >> qemu 4962 1 21 15:41 ? 00:00:41 >> /usr/bin/qemu-system-x86_64 -machine accel=kvm -name regular-guest -S >> -machine pc-i440fx-1.4,accel=kvm,usb=off -cpu Haswell,+vmx -m 6144 >> -smp 4,sockets=4,cores=1,threads=1 -uuid >> 4ed9ac0b-7f72-dfcf-68b3-e6fe2ac588b2 -nographic -no-user-config >> -nodefaults -chardev >> >> socket,id=charmonitor,path=/var/lib/libvirt/qemu/regular-guest.monitor,server,nowait >> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc >> -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 >> -drive >> file=/home/test/vmimages/regular-guest.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none >> -device >> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 >> -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device >> >> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:80:c1:34,bus=pci.0,addr=0x3 >> -chardev pty,id=charserial0 -device >> isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 >> -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 >> >> L2 QEMU command-line: >> ==================== >> >> $ qemu 2042 1 0 May09 ? 00:05:03 >> /usr/bin/qemu-system-x86_64 -machine accel=kvm -name nested-guest -S >> -machine pc-i440fx-1.4,accel=kvm,usb=off -m 2048 -smp >> 2,sockets=2,cores=1,threads=1 -uuid >> 02ea8988-1054-b08b-bafe-cfbe9659976c -nographic -no-user-config >> -nodefaults -chardev >> >> socket,id=charmonitor,path=/var/lib/libvirt/qemu/nested-guest.monitor,server,nowait >> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc >> -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 >> -drive >> file=/home/test/vmimages/nested-guest.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none >> -device >> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 >> -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device >> >> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:65:c4:e6,bus=pci.0,addr=0x3 >> -chardev pty,id=charserial0 -device >> isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 >> -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 >> >> >> I attached the vmxcap script output. >> >> Before I debug further, anyone has hints here? >> >> Many thanks in advance. >> >> [1] Notes -- https://github.com/kashyapc/nested-virt-notes-intel-f18 >> Also, I'm able to reproduce this consistently: When I create an L2 guest: ========= ...... [ 463.655031] Dazed and confused, but trying to continue [ 463.975563] Uhhuh. NMI received for unknown reason 20 on CPU 1. [ 463.976040] Do you have a strange power saving mode enabled? [ 463.976040] Dazed and confused, but trying to continue 29 199M 29 58.7M 0 0 136k 0 0:25:02 0:07:20 0:17:42 153k [ 465.136405] Uhhuh. NMI received for unknown reason 30 on CPU 1. [ 465.137042] Do you have a strange power saving mode enabled? [ 465.137042] Dazed and confused, but trying to continue [ 466.645818] Uhhuh. NMI received for unknown reason 20 on CPU 1. [ 466.646044] Do you have a strange power saving mode enabled? [ 466.646044] Dazed and confused, but trying to continue [ 466.907999] Uhhuh. NMI received for unknown reason 30 on CPU 1. [ 466.908033] Do you have a strange power saving mode enabled? ========= Like I mentioned in my earlier email, I don't have NMI watchdog enabled. Am I doing something silly here? -- 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
