From: "Jan Beulich" <JBeulich@suse.com> To: xen-devel <xen-devel@lists.xenproject.org> Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, Olaf Hering <olaf@aepfle.de>, Wei Liu <wei.liu2@citrix.com> Subject: libxl assertion failure when creating any kind of guest Date: Wed, 22 May 2019 01:11:54 -0600 [thread overview] Message-ID: <5CE4F63A0200007800231313@prv1-mh.provo.novell.com> (raw) All, am I the only one to see xl: libxl.c:339: libxl_defbool_val: Assertion `!libxl_defbool_is_default(db)' failed. for any kind of (x86) guest being created, including simple XTF ones? I haven't taken a closer look at the code yet, but with this I wonder how even a smoke push could have occurred. I've re-based my tree yesterday (to 76ba8b14, which means in particular that 278c64519c ["libxl: fix libxl_domain_need_memory after 899433f149d"] is in place) after a couple of weeks of not having found the time to do so, so the range of possible candidate commits is rather long. In a mail on the 16th Jürgen had pointed out that 3802ecbaa9 causes this assertion to trigger _if_ another assertion this commit added gets removed again, but that assert() is still in place and did not trigger, so I assume the two issues are maybe related, but not identical. Which again leaves 899433f149 as the primary suspect. I've not been able to find any other recent mention of said assert() to trigger. This is the call stack, in case it helps: #0 0x00007ffff6f676d5 in raise () from /lib64/libc.so.6 #1 0x00007ffff6f68cb1 in abort () from /lib64/libc.so.6 #2 0x00007ffff6f605a0 in __assert_fail () from /lib64/libc.so.6 #3 0x00007ffff78ec132 in libxl_defbool_val (db=...) at libxl.c:339 #4 0x00007ffff78edd4a in libxl__domain_build_info_setdefault (gc=0x7fffffffdee0, b_info=0x7fffffffdb80) at libxl_create.c:143 #5 0x00007ffff7943e5f in libxl_domain_need_memory (ctx=0x641050, b_info_in=0x7fffffffe0b8, need_memkb=0x7fffffffdf40) at libxl_mem.c:478 #6 0x0000000000425e3c in freemem (domid=4294967295, b_info=0x7fffffffe0b8) at xl_vmcontrol.c:325 #7 0x00000000004274e7 in create_domain (dom_info=0x7fffffffe630) at xl_vmcontrol.c:881 #8 0x0000000000428367 in main_create (argc=3, argv=0x7fffffffe810) at xl_vmcontrol.c:1242 #9 0x000000000040b344 in main (argc=3, argv=0x7fffffffe810) at xl.c:413 Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com> To: "xen-devel" <xen-devel@lists.xenproject.org> Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, Olaf Hering <olaf@aepfle.de>, Wei Liu <wei.liu2@citrix.com> Subject: [Xen-devel] libxl assertion failure when creating any kind of guest Date: Wed, 22 May 2019 01:11:54 -0600 [thread overview] Message-ID: <5CE4F63A0200007800231313@prv1-mh.provo.novell.com> (raw) Message-ID: <20190522071154.EGQxd6DHkOJlWdXQ3Wyls_S_ijZwluAdK14AUrKKgqs@z> (raw) All, am I the only one to see xl: libxl.c:339: libxl_defbool_val: Assertion `!libxl_defbool_is_default(db)' failed. for any kind of (x86) guest being created, including simple XTF ones? I haven't taken a closer look at the code yet, but with this I wonder how even a smoke push could have occurred. I've re-based my tree yesterday (to 76ba8b14, which means in particular that 278c64519c ["libxl: fix libxl_domain_need_memory after 899433f149d"] is in place) after a couple of weeks of not having found the time to do so, so the range of possible candidate commits is rather long. In a mail on the 16th Jürgen had pointed out that 3802ecbaa9 causes this assertion to trigger _if_ another assertion this commit added gets removed again, but that assert() is still in place and did not trigger, so I assume the two issues are maybe related, but not identical. Which again leaves 899433f149 as the primary suspect. I've not been able to find any other recent mention of said assert() to trigger. This is the call stack, in case it helps: #0 0x00007ffff6f676d5 in raise () from /lib64/libc.so.6 #1 0x00007ffff6f68cb1 in abort () from /lib64/libc.so.6 #2 0x00007ffff6f605a0 in __assert_fail () from /lib64/libc.so.6 #3 0x00007ffff78ec132 in libxl_defbool_val (db=...) at libxl.c:339 #4 0x00007ffff78edd4a in libxl__domain_build_info_setdefault (gc=0x7fffffffdee0, b_info=0x7fffffffdb80) at libxl_create.c:143 #5 0x00007ffff7943e5f in libxl_domain_need_memory (ctx=0x641050, b_info_in=0x7fffffffe0b8, need_memkb=0x7fffffffdf40) at libxl_mem.c:478 #6 0x0000000000425e3c in freemem (domid=4294967295, b_info=0x7fffffffe0b8) at xl_vmcontrol.c:325 #7 0x00000000004274e7 in create_domain (dom_info=0x7fffffffe630) at xl_vmcontrol.c:881 #8 0x0000000000428367 in main_create (argc=3, argv=0x7fffffffe810) at xl_vmcontrol.c:1242 #9 0x000000000040b344 in main (argc=3, argv=0x7fffffffe810) at xl.c:413 Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-05-22 7:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-22 7:11 Jan Beulich [this message] 2019-05-22 7:11 ` [Xen-devel] libxl assertion failure when creating any kind of guest Jan Beulich 2019-05-22 7:25 ` Olaf Hering 2019-05-22 7:25 ` [Xen-devel] " Olaf Hering 2019-05-22 8:09 ` Wei Liu 2019-05-22 8:09 ` [Xen-devel] " Wei Liu 2019-05-22 8:40 ` Jan Beulich 2019-05-22 8:40 ` [Xen-devel] " Jan Beulich 2019-05-22 10:01 ` Wei Liu 2019-05-22 10:01 ` [Xen-devel] " Wei Liu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=5CE4F63A0200007800231313@prv1-mh.provo.novell.com \ --to=jbeulich@suse.com \ --cc=Ian.Jackson@eu.citrix.com \ --cc=olaf@aepfle.de \ --cc=wei.liu2@citrix.com \ --cc=xen-devel@lists.xenproject.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).