[Qemu-discuss] How to run qemu with -nographic and -monitor but still be able to send Ctrl+C to the guest?

2018-04-08 Thread Ciro Santilli
https://stackoverflow.com/questions/49716931/how-to-run-qemu-with-nographic-and-monitor-but-still-be-able-to-send-ctrlc-to I have just found out that if you run QEMU with `-monitor telnet::45454,server,nowait -nographic`, then Ctrl-C kills the QEMU VM instead of generating SIGINT on the guest: htt

[Qemu-discuss] qemu-img convert stuck

2018-04-08 Thread Benny Zlotnik
Hi, As part of copy operation initiated by rhev got stuck for more than a day and consumes plenty of CPU vdsm 13024 3117 99 Apr07 ?1-06:58:43 /usr/bin/qemu-img convert -p -t none -T none -f qcow2 /rhev/data-center/bb422fac-81c5-4fea-8782-3498bb5c8a59/26989331-2c39-4b34-a7ed-d7dd770364

Re: [Qemu-discuss] qemu-img convert stuck

2018-04-08 Thread Nir Soffer
On Sun, Apr 8, 2018 at 9:27 PM Benny Zlotnik wrote: > Hi, > > As part of copy operation initiated by rhev got stuck for more than a day > and consumes plenty of CPU > vdsm 13024 3117 99 Apr07 ?1-06:58:43 /usr/bin/qemu-img convert > -p -t none -T none -f qcow2 > > /rhev/data-center/bb

Re: [Qemu-discuss] qemu-img convert stuck

2018-04-08 Thread Benny Zlotnik
$ gdb -p 13024 -batch -ex "thread apply all bt" [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f98275cfaff in ppoll () from /lib64/libc.so.6 Thread 1 (Thread 0x7f983e30ab00 (LWP 13024)): #0 0x7f98275cfaff in ppoll () from /lib6

Re: [Qemu-discuss] [Qemu-block] qemu-img convert stuck

2018-04-08 Thread Stefan Hajnoczi
On Sun, Apr 08, 2018 at 10:35:16PM +0300, Benny Zlotnik wrote: What type of storage are the source and destination images? (e.g. source is a local qcow2 file on xfs, destination is a raw file on NFS) > $ gdb -p 13024 -batch -ex "thread apply all bt" > [Thread debugging using libthread_db enabled