[qemu-mainline bisection] complete build-arm64-libvirt

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

branch xen-unstable
xenbranch xen-unstable
job build-arm64-libvirt
testid libvirt-build

Tree: libvirt git://xenbits.xen.org/libvirt.git
Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemuu git://git.qemu.org/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
Tree: xen git://xenbits.xen.org/xen.git

*** Found and reproduced problem changeset ***

  Bug is in tree:  xen git://xenbits.xen.org/xen.git
  Bug introduced:  66dd1c62b2a3c707bd5c55750d10a8223fbd577f
  Bug not present: f732240fd3bac25116151db5ddeb7203b62e85ce
  Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/172257/


  commit 66dd1c62b2a3c707bd5c55750d10a8223fbd577f
  Author: Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
  Date:   Fri Jul 15 22:20:24 2022 +0300
  
      libxl: Add support for Virtio disk configuration
      
      This patch adds basic support for configuring and assisting virtio-mmio
      based virtio-disk backend (emulator) which is intended to run out of
      Qemu and could be run in any domain.
      Although the Virtio block device is quite different from traditional
      Xen PV block device (vbd) from the toolstack's point of view:
       - as the frontend is virtio-blk which is not a Xenbus driver, nothing
         written to Xenstore are fetched by the frontend currently ("vdev"
         is not passed to the frontend). But this might need to be revised
         in future, so frontend data might be written to Xenstore in order to
         support hotplugging virtio devices or passing the backend domain id
         on arch where the device-tree is not available.
       - the ring-ref/event-channel are not used for the backend<->frontend
         communication, the proposed IPC for Virtio is IOREQ/DM
      it is still a "block device" and ought to be integrated in existing
      "disk" handling. So, re-use (and adapt) "disk" parsing/configuration
      logic to deal with Virtio devices as well.
      
      For the immediate purpose and an ability to extend that support for
      other use-cases in future (Qemu, virtio-pci, etc) perform the following
      actions:
      - Add new disk backend type (LIBXL_DISK_BACKEND_STANDALONE) and reflect
        that in the configuration
      - Introduce new disk "specification" and "transport" fields to struct
        libxl_device_disk. Both are written to the Xenstore. The transport
        field is only used for the specification "virtio" and it assumes
        only "mmio" value for now.
      - Introduce new "specification" option with "xen" communication
        protocol being default value.
      - Add new device kind (LIBXL__DEVICE_KIND_VIRTIO_DISK) as current
        one (LIBXL__DEVICE_KIND_VBD) doesn't fit into Virtio disk model
      
      An example of domain configuration for Virtio disk:
      disk = [ 'phy:/dev/mmcblk0p3, xvda1, backendtype=standalone, 
specification=virtio']
      
      Nothing has changed for default Xen disk configuration.
      
      Please note, this patch is not enough for virtio-disk to work
      on Xen (Arm), as for every Virtio device (including disk) we need
      to allocate Virtio MMIO params (IRQ and memory region) and pass
      them to the backend, also update Guest device-tree. The subsequent
      patch will add these missing bits. For the current patch,
      the default "irq" and "base" are just written to the Xenstore.
      This is not an ideal splitting, but this way we avoid breaking
      the bisectability.
      
      Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
      Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
      Acked-by: George Dunlap <george.dunlap@xxxxxxxxxx>
      Tested-by: Jiamei Xie <jiamei.xie@xxxxxxx>


For bisection revision-tuple graph see:
   
http://logs.test-lab.xenproject.org/osstest/results/bisect/qemu-mainline/build-arm64-libvirt.libvirt-build.html
Revision IDs in each graph node refer, respectively, to the Trees above.

----------------------------------------
Running cs-bisection-step 
--graph-out=/home/logs/results/bisect/qemu-mainline/build-arm64-libvirt.libvirt-build
 --summary-out=tmp/172257.bisection-summary --basis-template=172123 
--blessings=real,real-bisect,real-retry qemu-mainline build-arm64-libvirt 
libvirt-build
Searching for failure / basis pass:
 172241 fail [host=laxton1] / 172123 ok.
Failure / basis pass flights: 172241 / 172123
Tree: libvirt git://xenbits.xen.org/libvirt.git
Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemuu git://git.qemu.org/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
444260d45ec2a84e8f8c192b3539a3cd5591d009 
c669f22f1a47897e8d1d595d6b8a59a572f9158c 
46de2eec93bffa0706e6229c0da2919763c8eb04 
6d6aee437e37fced0c49be97e08c30da873690fc
Basis pass 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
f732240fd3bac25116151db5ddeb7203b62e85ce
Generating revisions with ./adhoc-revtuple-generator  
git://xenbits.xen.org/libvirt.git#2c846fa6bcc11929c9fb857a22430fb9945654ad-2c846fa6bcc11929c9fb857a22430fb9945654ad
 
https://gitlab.com/keycodemap/keycodemapdb.git#27acf0ef828bf719b2053ba398b195829413dbdd-27acf0ef828bf719b2053ba398b195829413dbdd
 
git://xenbits.xen.org/osstest/ovmf.git#0dc9b78a46813d61533b2bb0f7ef897a06a273be-444260d45ec2a84e8f8c192b3539a3cd5591d009
 
git://git.qemu.org/qemu.git#2480f3bbd03814b0651a1f74959f5c6631ee5819-c669f22f1a4\
 7897e8d1d595d6b8a59a572f9158c 
git://xenbits.xen.org/osstest/seabios.git#46de2eec93bffa0706e6229c0da2919763c8eb04-46de2eec93bffa0706e6229c0da2919763c8eb04
 
git://xenbits.xen.org/xen.git#f732240fd3bac25116151db5ddeb7203b62e85ce-6d6aee437e37fced0c49be97e08c30da873690fc
Loaded 64808 nodes in revision graph
Searching for test results:
 172123 pass 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
f732240fd3bac25116151db5ddeb7203b62e85ce
 172148 fail irrelevant
 172164 fail irrelevant
 172197 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
444260d45ec2a84e8f8c192b3539a3cd5591d009 
09ed077d7fae5f825e18ff9a2004dcdd1b165edb 
46de2eec93bffa0706e6229c0da2919763c8eb04 
1f7543c039f6b9eb182f0395965b9d414ac774c4
 172235 pass 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
f732240fd3bac25116151db5ddeb7203b62e85ce
 172237 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
444260d45ec2a84e8f8c192b3539a3cd5591d009 
09ed077d7fae5f825e18ff9a2004dcdd1b165edb 
46de2eec93bffa0706e6229c0da2919763c8eb04 
1f7543c039f6b9eb182f0395965b9d414ac774c4
 172217 fail irrelevant
 172239 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
444260d45ec2a84e8f8c192b3539a3cd5591d009 
ed021daf2d6c19499ae406055156dc19c073228f 
46de2eec93bffa0706e6229c0da2919763c8eb04 
7c5b25c3038abc2dc8353f56ed67d2c4fcd43d79
 172240 fail irrelevant
 172243 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
68b01ef0b3c182d207bff01dd3e20d287668c855
 172244 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
8a3b89e4307da260675483bb86fc06cc62ed7c08
 172245 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
ca45d3cb4586372909f350e54482246f994e1bc7
 172248 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
66dd1c62b2a3c707bd5c55750d10a8223fbd577f
 172249 pass 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
f732240fd3bac25116151db5ddeb7203b62e85ce
 172241 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
444260d45ec2a84e8f8c192b3539a3cd5591d009 
c669f22f1a47897e8d1d595d6b8a59a572f9158c 
46de2eec93bffa0706e6229c0da2919763c8eb04 
6d6aee437e37fced0c49be97e08c30da873690fc
 172251 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
66dd1c62b2a3c707bd5c55750d10a8223fbd577f
 172253 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
444260d45ec2a84e8f8c192b3539a3cd5591d009 
c669f22f1a47897e8d1d595d6b8a59a572f9158c 
46de2eec93bffa0706e6229c0da2919763c8eb04 
6d6aee437e37fced0c49be97e08c30da873690fc
 172256 pass 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
f732240fd3bac25116151db5ddeb7203b62e85ce
 172257 fail 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
66dd1c62b2a3c707bd5c55750d10a8223fbd577f
Searching for interesting versions
 Result found: flight 172123 (pass), for basis pass
 Result found: flight 172241 (fail), for basis failure
 Repro found: flight 172249 (pass), for basis pass
 Repro found: flight 172253 (fail), for basis failure
 0 revisions at 2c846fa6bcc11929c9fb857a22430fb9945654ad 
27acf0ef828bf719b2053ba398b195829413dbdd 
0dc9b78a46813d61533b2bb0f7ef897a06a273be 
2480f3bbd03814b0651a1f74959f5c6631ee5819 
46de2eec93bffa0706e6229c0da2919763c8eb04 
f732240fd3bac25116151db5ddeb7203b62e85ce
No revisions left to test, checking graph state.
 Result found: flight 172123 (pass), for last pass
 Result found: flight 172248 (fail), for first failure
 Repro found: flight 172249 (pass), for last pass
 Repro found: flight 172251 (fail), for first failure
 Repro found: flight 172256 (pass), for last pass
 Repro found: flight 172257 (fail), for first failure

*** Found and reproduced problem changeset ***

  Bug is in tree:  xen git://xenbits.xen.org/xen.git
  Bug introduced:  66dd1c62b2a3c707bd5c55750d10a8223fbd577f
  Bug not present: f732240fd3bac25116151db5ddeb7203b62e85ce
  Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/172257/


  commit 66dd1c62b2a3c707bd5c55750d10a8223fbd577f
  Author: Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
  Date:   Fri Jul 15 22:20:24 2022 +0300
  
      libxl: Add support for Virtio disk configuration
      
      This patch adds basic support for configuring and assisting virtio-mmio
      based virtio-disk backend (emulator) which is intended to run out of
      Qemu and could be run in any domain.
      Although the Virtio block device is quite different from traditional
      Xen PV block device (vbd) from the toolstack's point of view:
       - as the frontend is virtio-blk which is not a Xenbus driver, nothing
         written to Xenstore are fetched by the frontend currently ("vdev"
         is not passed to the frontend). But this might need to be revised
         in future, so frontend data might be written to Xenstore in order to
         support hotplugging virtio devices or passing the backend domain id
         on arch where the device-tree is not available.
       - the ring-ref/event-channel are not used for the backend<->frontend
         communication, the proposed IPC for Virtio is IOREQ/DM
      it is still a "block device" and ought to be integrated in existing
      "disk" handling. So, re-use (and adapt) "disk" parsing/configuration
      logic to deal with Virtio devices as well.
      
      For the immediate purpose and an ability to extend that support for
      other use-cases in future (Qemu, virtio-pci, etc) perform the following
      actions:
      - Add new disk backend type (LIBXL_DISK_BACKEND_STANDALONE) and reflect
        that in the configuration
      - Introduce new disk "specification" and "transport" fields to struct
        libxl_device_disk. Both are written to the Xenstore. The transport
        field is only used for the specification "virtio" and it assumes
        only "mmio" value for now.
      - Introduce new "specification" option with "xen" communication
        protocol being default value.
      - Add new device kind (LIBXL__DEVICE_KIND_VIRTIO_DISK) as current
        one (LIBXL__DEVICE_KIND_VBD) doesn't fit into Virtio disk model
      
      An example of domain configuration for Virtio disk:
      disk = [ 'phy:/dev/mmcblk0p3, xvda1, backendtype=standalone, 
specification=virtio']
      
      Nothing has changed for default Xen disk configuration.
      
      Please note, this patch is not enough for virtio-disk to work
      on Xen (Arm), as for every Virtio device (including disk) we need
      to allocate Virtio MMIO params (IRQ and memory region) and pass
      them to the backend, also update Guest device-tree. The subsequent
      patch will add these missing bits. For the current patch,
      the default "irq" and "base" are just written to the Xenstore.
      This is not an ideal splitting, but this way we avoid breaking
      the bisectability.
      
      Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
      Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
      Acked-by: George Dunlap <george.dunlap@xxxxxxxxxx>
      Tested-by: Jiamei Xie <jiamei.xie@xxxxxxx>

Revision graph left in 
/home/logs/results/bisect/qemu-mainline/build-arm64-libvirt.libvirt-build.{dot,ps,png,html,svg}.
----------------------------------------
172257: tolerable ALL FAIL

flight 172257 qemu-mainline real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/172257/

Failures :-/ but no regressions.

Tests which did not succeed,
including tests which could not be run:
 build-arm64-libvirt           6 libvirt-build           fail baseline untested


jobs:
 build-arm64-libvirt                                          fail    


------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary