Re: [Xen-devel] [xen-unstable test] 12800: tolerable FAIL

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2012-05-08 at 10:25 +0100, xen.org wrote:
> flight 12800 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/12800/
> 
> Failures :-/ but no regressions.
> 
> Tests which are failing intermittently (not blocking):
>  test-amd64-i386-rhel6hvm-amd  7 redhat-install              fail pass in 
> 12797

        2012-05-08 07:11:44 Z executing ssh ... root@xxxxxxxxxxxx xl create 
/etc/xen/redhat.guest.osstest.cfg
        WARNING: ignoring "kernel" directive for HVM guest. Use 
"firmware_override" instead if you really want a non-default firmware
        xc: info: VIRTUAL MEMORY ARRANGEMENT:
          Loader:        0000000000100000->000000000019bca4
          TOTAL:         0000000000000000->000000002f800000
          ENTRY ADDRESS: 0000000000100000
        xc: info: PHYSICAL MEMORY ALLOCATION:
          4KB PAGES: 0x0000000000000200
          2MB PAGES: 0x000000000000017b
          1GB PAGES: 0x0000000000000000
        libxl: error: libxl.c:3115:libxl_sched_credit_domain_set: Cpu weight 
out of range, valid values are within range from 1 to 65535
        libxl: error: libxl_create.c:628:do_domain_create: cannot add disk 1 to 
domain: -3
        libxl: error: libxl_dm.c:1045:libxl__destroy_device_model: Couldn't 
find device model's pid: No such file or directory
        libxl: error: libxl.c:1094:libxl_domain_destroy: 
libxl__destroy_device_model failed for 2
        Parsing config file /etc/xen/redhat.guest.osstest.cfg

-3 is ERROR_FAIL from libxl_device_disk_add() and I don't see anything else in 
the logs.
Weird thing is I don't see any logs from libxl__device_disk_set_backend
which is unconditionally the first thing libxl_device_disk_add calls and
which always logs something with at least LIBXL__LOG_DEBUG -- which I
expected would go to /var/log/xen/xl-NAME.log but
http://www.chiark.greenend.org.uk/~xensrcts/logs/12800/test-amd64-i386-rhel6hvm-amd/potato-beetle---var-log-xen-xl-redhat.guest.osstest.log
 doesn't have anything. However I suspect that is the log of the previous boot 
of the guest -- in which case where is the log from this one?

Ignoring the missing logs, the only place I can see an ERROR_FAIL from
libxl_device_disk_add is the call to libxl__blktap_devpath, which is
unlogged (patch below).

Both 12797 (previous pass) and 12800 (this fail) seem to be testing the
same Xen version (8f1e0cc4a507), so I'm not sure what changed.

Ian.

8<--------------------------------------

# HG changeset patch
# User Ian Campbell <ian.campbell@xxxxxxxxxx>
# Date 1336483471 -3600
# Node ID 662621bcecd59b34acfda54a4c8d360389a40536
# Parent  5f72f4fd7f048c2e325c5070bb7adcc216b5772f
libxl: log failure from libxl__blktap_devpath in libxl_device_disk_add

Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

diff -r 5f72f4fd7f04 -r 662621bcecd5 tools/libxl/libxl.c
--- a/tools/libxl/libxl.c       Sun May 06 10:12:04 2012 +0100
+++ b/tools/libxl/libxl.c       Tue May 08 14:24:31 2012 +0100
@@ -1351,6 +1351,8 @@ int libxl_device_disk_add(libxl_ctx *ctx
         case LIBXL_DISK_BACKEND_TAP:
             dev = libxl__blktap_devpath(gc, disk->pdev_path, disk->format);
             if (!dev) {
+                LOG(ERROR, "failed to get blktap devpath for %p\n",
+                    disk->pdev_path);
                 rc = ERROR_FAIL;
                 goto out_free;
             }



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel