search for: maxrss

...Max Median Avg Stddev real 6 2283.69 2288.46 2285.74 2285.505 1.6470064 user 6 2145.2 2147.2 2146.18 2146.0567 0.68266146 sys 6 128.3 132.08 130.65 130.54833 1.256653 maxrss 6 179264 179264 179264 179264 0 ixrss 6 21407 21436 21420 21419.833 9.6211572 idrss 6 3628 3632 3630 3629.8333 1.3291601 isrss 6 252 252 252...

...uot; and its output on console wrt the time are real 0m3.713s user 0m1.968s sys 0m0.741s There many output with -v -x params enabled ... guestfsd: => internal_autosync (0x11a) took 0.05 secs libguestfs: trace: internal_autosync = 0 libguestfs: sending SIGTERM to process 11629 libguestfs: qemu maxrss 235720K libguestfs: trace: shutdown = 0 libguestfs: trace: close libguestfs: closing guestfs handle 0x562ae3df6c10 (state 0) libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsIDYj9s libguestfs: command: run: rm libguestfs: command: run: \ -rf /run/user/1000/libguestfs2SKM4...

...em like it would be terribly complicated. I've attached the code. My aim is to verify that I can use getrusage() to do (admittedly crude) instrumentation of which functions in my program are allocating lots of memory[1]. So I figure I can call getrusage() at various points and look at the ru_maxrss member. I'm confused because the results I'm getting don't make a great deal of sense. The attached program, when run 10 times one after the other, produces the following output; before: 0, after: 1300 before: 0, after: 0 before: 0, after: 0 before: 188, after: 188 bef...

...is reasonable, considering that debugging is enabled. > There many output with -v -x params enabled > > ... > guestfsd: => internal_autosync (0x11a) took 0.05 secs > libguestfs: trace: internal_autosync = 0 > libguestfs: sending SIGTERM to process 11629 > libguestfs: qemu maxrss 235720K > libguestfs: trace: shutdown = 0 > libguestfs: trace: close > libguestfs: closing guestfs handle 0x562ae3df6c10 (state 0) > libguestfs: command: run: rm > libguestfs: command: run: \ -rf /tmp/libguestfsIDYj9s > libguestfs: command: run: rm > libguestfs: command: run: \...

...) 2020-08-27 08:48:40 T libguestfs - 0 - appliance - Booting from ROM... 2020-08-27 08:48:40 T libguestfs - 0 - library - child_cleanup: 0xd5a840: child process died 2020-08-27 08:48:40 T libguestfs - 0 - library - sending SIGTERM to process 459 2020-08-27 08:48:40 T libguestfs - 0 - library - qemu maxrss 60136K 2020-08-27 08:48:40 T libguestfs - 0 - subprocess_quit 2020-08-27 08:48:40 T libguestfs - 0 - library - closing guestfs handle 0xd5a840 (state 0) 2020-08-27 08:48:40 T libguestfs - 0 - close 2020-08-27 08:48:40 T libguestfs - 0 - library - command: run: rm 2020-08-27 08:48:40 T libguestfs -...

...line parameter buffer is 0xe. [Parsed_scale_vaapi_2 @ 0xb005a40] Failed to render parameter buffer: 2 (resource allocation failed). Error while filtering: Input/output error Failed to inject frame into filter network: Input/output error Error while processing the decoded data for stream #0:0 bench: maxrss=106420kB [AVIOContext @ 0xaf40640] Statistics: 759514 bytes read, 0 seeks Conversion failed! Ow :( [full log attached] Note, i use libva1: libva-1.8.3 Can libva2 be installed in parallel with libva1 ? [1] - https://lists.cinelerra-gg.org/pipermail/cin/2019-May/000665.html -- You are receivin...

...- not syncing: Fatal exception in interrupt [ 110.721000] Rebooting in 1 seconds..libguestfs: error: appliance closed the connection unexpectedly, see earlier error messages libguestfs: child_cleanup: 0x55690ed44c60: child process died libguestfs: sending SIGTERM to process 31847 libguestfs: qemu maxrss 96256K libguestfs: error: guestfs_launch failed, see earlier error messages libguestfs: closing guestfs handle 0x55690ed44c60 (state 0) libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsIHeKLD libguestfs: command: run: rm libguestfs: command: run: \ -rf /run/user/1000/libg...

Hi, I have a KVM host running ubuntu 18.04 with libguestfs-tools version 1.36.13-1ubuntu3.3 installed from the Ubuntu's repo and when I try to use virt-cat for example on a VM it fails with: libguestfs: error: appliance closed the connection unexpectedly. > libguestfs: error: guestfs_launch failed. After doing "export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1" and running the

...: Restarting system > [ 0.978966] reboot: machine restart > libguestfs: error: appliance closed the connection unexpectedly, see earlier error messages > libguestfs: child_cleanup: 0x563940429170: child process died > libguestfs: sending SIGTERM to process 11708 > libguestfs: qemu maxrss 167128K > libguestfs: error: guestfs_launch failed, see earlier error messages > libguestfs: trace: launch = -1 (error) > libguestfs: trace: close > libguestfs: closing guestfs handle 0x563940429170 (state 0) > libguestfs: command: run: rm > libguestfs: command: run: \ -rf /tmp/li...

...[ 0.978966] reboot: machine restart > > libguestfs: error: appliance closed the connection unexpectedly, see > earlier error messages > > libguestfs: child_cleanup: 0x563940429170: child process died > > libguestfs: sending SIGTERM to process 11708 > > libguestfs: qemu maxrss 167128K > > libguestfs: error: guestfs_launch failed, see earlier error messages > > libguestfs: trace: launch = -1 (error) > > libguestfs: trace: close > > libguestfs: closing guestfs handle 0x563940429170 (state 0) > > libguestfs: command: run: rm > > libguestf...

...ing: settle fsync /dev/sda commandrvf: stdout=n stderr=y flags=0x0 commandrvf: udevadm --debug settle -E /dev/sdb calling: settle guestfsd: main_loop: proc 282 (internal_autosync) took 0.01 secondslibguestfs: trace: internal_autosync = 0 libguestfs: sending SIGTERM to process 24148 libguestfs: qemu maxrss 213052K libguestfs: command: run: rm libguestfs: command: run: \ -rf /root/libguestfs-1.36.5/tmp/libguestfsNx5SCZ libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfst4FNb4 Regards, Alan

....9: debug: exiting worker thread nbd.9 nbdkit: nbd.10: debug: client closed input socket, closing connection nbdkit: nbd.10: debug: exiting worker thread nbd.10 nbdkit: nbd.11: debug: client closed input socket, closing connection nbdkit: nbd.11: debug: exiting worker thread nbd.11 libguestfs: qemu maxrss 166484K libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsYp1w4f libguestfs: command: run: rm libguestfs: command: run: \ -rf /run/user/1000/libguestfsUEHqc9 nbdkit: nbd[1]: debug: connection cleanup with final status 0 nbdkit: nbd[1]: debug: close nbdkit: nbd[1]: debug: s...

When converting from a single transaction to a linked list, I forgot to free the storage for each member of the list. Reported-by: Richard W.M. Jones <rjones at redhat.com> Fixes: 7f5bb9bf13f041ea7702bda557d9dd668bc3423a Signed-off-by: Eric Blake <eblake at redhat.com> --- I'm still not sure why 'make check' passes while 'make check-valgrind' fails for

...r-connection request lock nbdkit: python[1]: debug: flush nbdkit: python[1]: debug: release per-connection request lock nbdkit: python[1]: debug: release global request lock nbdkit: python[1]: debug: client sent disconnect command, closing connection nbdkit: python[1]: debug: close libguestfs: qemu maxrss 301548K libguestfs: trace: shutdown = 0 libguestfs: trace: close libguestfs: closing guestfs handle 0x559852bbbaf0 (state 0) libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsq6xGkY libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsnY8aXw nbdkit:...

...ing: settle commandrvf: stdout=n stderr=y flags=0x0 commandrvf: udevadm --debug settle -E /dev/sda calling: settle fsync /dev/sda guestfsd: main_loop: proc 282 (internal_autosync) took 3.51 seconds libguestfs: trace: internal_autosync = 0 libguestfs: sending SIGTERM to process 2940 libguestfs: qemu maxrss 316692K libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsjnSQmf libguestfs: command: run: rm libguestfs: command: run: \ -rf /run/user/1000/libguestfsHMk6Xd Any suggestion?