Tested on 1-CPU and 2-CPU machines, the test:
20140305 13:41:28 Test: profile-5
build/dtrace -n ' int cnt_1ms, cnt_1s, cnt_fbt;
fbt::: {cnt_fbt++;}
tick-1ms { cnt_1ms++; }
tick-1s { cnt_1s++;
printf("tick-1ms=%d tick-1s=%d fbt=%d", cnt_1ms, cnt_1s, cnt_fbt);
}
tick-5s {
printf("the end: got %d + %d, fbt=%d\n", cnt_1ms, cnt_1s, cnt_fbt);
exit(0);
}
' >/tmp/test-root.profile-5.log 2>&1
makes one CPU spin at 100% (visible via virt-manager) and the whole machine is totally dead (no response via keyboard or ssh, no kernel messages on the console).
Is this expected? AIUI, this test is tracing every single function in the kernel, which does scream "don't do that".
Both the host and the guest (virtualized via KVM) are running Ubuntu 12.04. Host kernel: 3.5.0-45-generic, guest kernel: 3.2.0-59-virtual