On Wed, Sep 8, 2010 at 1:55 AM, Blue Swirl <blauwirbel@xxxxxxxxx> wrote: > On Tue, Sep 7, 2010 at 2:43 AM, Amos Kong <kongjianjun@xxxxxxxxx> wrote: >> >> kvm upstream: 43e413f7db1a4a90671dda0b1d6c1f8cb30673ed KVM: Whitespace >> changes to remove differences wrt kvm-updates/2.6.37 >> qemu upstream: cb93bbdd7db92e50ff5e60a346b23df68acae46b Fix OpenBSD >> linker warning >> >> # ./x86_64-softmmu/qemu-system-x86_64 ~/win7-32.qcow2 -m 1024 -vnc :0 >> -usbdevice tablet -cpu qemu64 -snapshot -enable-kvm -bios pc-bios/bios.bin >> >> Guest hangs when I do general operation. >> It's fine when using upstream qemu-kvm. this problem only occurred >> one time when I debug by gdb, after execute 'continue', guest runs >> normally. >> >> debug msg of (qemu + kvm) >> (gdb) c >> Continuing. >> >> Program received signal SIGUSR2, User defined signal 2. > > This is normal, we use SIGUSR2 for AIO. By default, GDB stops and > prints a message about the signal. The same thing can happen with > SIGALRM. > > GDB command 'handle SIGUSR2 nostop noprint pass' lets the program > continue without stopping. If ignore this signal in gdb, guest could not break. Thanks -- 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
