On Wed, 2014-10-29 at 17:36 -0400, Gedalya wrote:
> When booting domU's running amd64 jessie, I notice some memory problems
> with xl.
I ran it (actually, upstream staging-4.4) under valgrind and it reported
after a reboot:
==5722== 24 bytes in 1 blocks are definitely lost in loss record 35 of 72
==5722== at 0x4026B2D: malloc (vg_replace_malloc.c:299)
==5722== by 0x41739FF: strdup (strdup.c:43)
==5722== by 0x405F38E: libxl__device_disk_local_initiate_attach
(libxl.c:2681)
==5722== by 0x408D2A6: libxl__bootloader_run (libxl_bootloader.c:385)
==5722== by 0x406B50C: initiate_domain_create (libxl_create.c:807)
==5722== by 0x406B50C: do_domain_create (libxl_create.c:1354)
==5722== by 0x406B6AF: libxl_domain_create_new (libxl_create.c:1377)
==5722== by 0x8056182: create_domain (xl_cmdimpl.c:2254)
==5722== by 0x8059F27: main_create (xl_cmdimpl.c:4407)
==5722== by 0x804E119: main (xl.c:360)
==5722==
==5722== 28 bytes in 1 blocks are definitely lost in loss record 39 of 72
==5722== at 0x4026B2D: malloc (vg_replace_malloc.c:299)
==5722== by 0x4279EBB: read_message (xs.c:1143)
==5722== by 0x427A89B: read_thread (xs.c:1219)
==5722== by 0x40E7953: start_thread (pthread_create.c:304)
==5722== by 0x41CF95D: clone (clone.S:130)
And the bootloader one appears to increase with each reboot.
FTR I did:
valgrind --leak-check=full xl cr -F /etc/xen/d32-1
(-F runs xl in the foreground, so this won't return to a prompt).
Then in another window:
xl reboot d32-1
(equivalent to running init 6).
Ian.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
