Resolved, I'm using wrong device name in kgdboc parameters. Not a single error message in dmesg, sigh. On Thu, Apr 3, 2014 at 2:25 PM, Aaron Lewis <the.warl0ck.1989@xxxxxxxxx> wrote: > Hi, > > I'm trying to setup kgdb with KVM guest, so I downloaded kernel source > 3.8.8 from kernel.org, and compiled the kernel with the following > options enabled: > > # CONFIG_SERIAL_KGDB_NMI is not set > CONFIG_HAVE_ARCH_KGDB=y > CONFIG_KGDB=y > CONFIG_KGDB_SERIAL_CONSOLE=y > # CONFIG_KGDB_TESTS is not set > CONFIG_KGDB_LOW_LEVEL_TRAP=y > # CONFIG_KGDB_KDB is not set > > CONFIG_MAGIC_SYSRQ=y > > CONFIG_DEBUG_FS=y > CONFIG_DEBUG_KERNEL=y > CONFIG_DEBUG_INFO=y > > When I do 'echo g > /proc/sysrq-trigger', a 'sysrq HELP' message was > displayed on console, that means the debug event is not installed to > sysrq? > > I can see the kgdboc module in /sys/modules/ > > Anyone know how to fix that? > > P.S the guest is a centos 6.5 image, and booted directly from kernel bzImage > > -- > Best Regards, > Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/ > Finger Print: 9F67 391B B770 8FF6 99DC D92D 87F6 2602 1371 4D33 -- Best Regards, Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/ Finger Print: 9F67 391B B770 8FF6 99DC D92D 87F6 2602 1371 4D33 -- 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