On Wed, Oct 19, 2011 at 10:02 AM, Jun Koi <junkoi2004@xxxxxxxxx> wrote: > On Wed, Oct 19, 2011 at 1:31 AM, Avi Kivity <avi@xxxxxxxxxx> wrote: >> On 10/18/2011 07:08 PM, John Stoffel wrote: >>> Avi> Also try out -no-kvm. >>> >>> This doesn't exist in my version of 'qemu' or should I really be doing >>> something else? I'm running: >>> >>> > qemu --version >>> QEMU PC emulator version 0.12.5 (Debian 0.12.5+dfsg-3squeeze1), >>> Copyright (c) 2003-2008 Fabrice Bellard >>> >>> Oh wait, I see, I should be doing: >>> >>> > kvm -no-acpi -no-hpet -cpu 486 -hda hda-caroline486.image -m 128 -vga std -vnc quad:4 >>> open /dev/kvm: Permission denied >>> Could not initialize KVM, will disable KVM support >>> >>> instead. And it looks like I don't have KVM support anyway when I run >>> as myself. >>> >>> John> Thanks, I'll give this a try tonight when I'm home again. >>> >>> Ok, so I ssh'd into home from work and now I can see it starting up, >>> but it's horribly slow. Heh. >> >> Ok, so tcg works? It's a kvm bug then. >> >> Please try with npt=0 (module parameter to kvm-amd), and also post a >> trace as per http://www.linux-kvm.org/page/Tracing. >> > > if i understand correctly, this tracing facility only supports Linux > guest, but not Windows guest? > hmm think again, since it seems there is no requirement on guest, i guess this supports all kind of guest OS. does this mean we can trace every instructions executed in both userspace & kernelspace of the guest? thanks, Jun -- 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
