|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable test] 125817: trouble: blocked/broken/fail/pass
flight 125817 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/125817/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64 <job status> broken build-arm64-xsm <job status> broken build-arm64-pvops <job status> broken Regressions which are regarded as allowable (not blocking): build-arm64-pvops 2 hosts-allocate broken REGR. vs. 125691 build-arm64-xsm 2 hosts-allocate broken REGR. vs. 125691 build-arm64 2 hosts-allocate broken REGR. vs. 125691 Tests which did not succeed, but are not blocking: test-arm64-arm64-xl 1 build-check(1) blocked n/a test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a build-arm64-libvirt 1 build-check(1) blocked n/a test-arm64-arm64-examine 1 build-check(1) blocked n/a test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a test-arm64-arm64-xl-credit2 1 build-check(1) blocked n/a build-arm64 3 capture-logs broken blocked in 125691 build-arm64-pvops 3 capture-logs broken blocked in 125691 build-arm64-xsm 3 capture-logs broken blocked in 125691 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail like 125691 test-armhf-armhf-libvirt 14 saverestore-support-check fail like 125691 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 125691 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 125691 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 125691 test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 125691 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail like 125691 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail like 125691 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 125691 test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict 10 debian-hvm-install fail never pass test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 10 debian-hvm-install fail never pass test-amd64-i386-xl-pvshim 12 guest-start fail never pass test-amd64-i386-libvirt 13 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 13 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 13 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 13 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 14 saverestore-support-check fail never pass test-armhf-armhf-xl-multivcpu 14 saverestore-support-check fail never pass test-armhf-armhf-xl 13 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 13 migrate-support-check fail never pass test-armhf-armhf-xl 14 saverestore-support-check fail never pass test-armhf-armhf-xl-cubietruck 14 saverestore-support-check fail never pass test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass test-armhf-armhf-xl-vhd 12 migrate-support-check fail never pass test-armhf-armhf-xl-vhd 13 saverestore-support-check fail never pass test-armhf-armhf-xl-rtds 13 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 14 saverestore-support-check fail never pass test-armhf-armhf-xl-arndale 13 migrate-support-check fail never pass test-armhf-armhf-xl-arndale 14 saverestore-support-check fail never pass test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail never pass test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass test-amd64-amd64-xl-qemut-win10-i386 10 windows-install fail never pass test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass version targeted for testing: xen ed5f8d9ca47e69e30221c37ec812f2b38af19d83 baseline version: xen 1f7574763cbb2c85825b8cc4d81f386e767a476f Last test of basis 125691 2018-07-30 21:37:12 Z 10 days Failing since 125716 2018-08-01 03:36:29 Z 9 days 5 attempts Testing same since 125743 2018-08-02 10:13:53 Z 8 days 4 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Daniel Kiper <daniel.kiper@xxxxxxxxxx> Doug Goldstein <cardoe@xxxxxxxxxx> George Dunlap <george.dunlap@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Norbert Manthey <nmanthey@xxxxxxxxx> Roger Pau Monné <roger.pau@xxxxxxxxxx> Simon Gaiser <simon@xxxxxxxxxxxxxxxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm broken build-i386-xsm pass build-amd64-xtf pass build-amd64 pass build-arm64 broken build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt blocked build-armhf-libvirt pass build-i386-libvirt pass build-amd64-prev pass build-i386-prev pass build-amd64-pvops pass build-arm64-pvops broken build-armhf-pvops pass build-i386-pvops pass build-amd64-rumprun pass build-i386-rumprun pass test-xtf-amd64-amd64-1 pass test-xtf-amd64-amd64-2 pass test-xtf-amd64-amd64-3 pass test-xtf-amd64-amd64-4 pass test-xtf-amd64-amd64-5 pass test-amd64-amd64-xl pass test-arm64-arm64-xl blocked test-armhf-armhf-xl pass test-amd64-i386-xl pass test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-xsm pass test-arm64-arm64-libvirt-xsm blocked test-amd64-i386-libvirt-xsm pass test-amd64-amd64-xl-xsm pass test-arm64-arm64-xl-xsm blocked test-amd64-i386-xl-xsm pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-amd64-xl-pvhv2-amd pass test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 pass test-amd64-i386-xl-qemut-debianhvm-amd64 pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass test-amd64-amd64-rumprun-amd64 pass test-amd64-amd64-xl-qemut-win7-amd64 fail test-amd64-i386-xl-qemut-win7-amd64 fail test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-qemut-ws16-amd64 fail test-amd64-i386-xl-qemut-ws16-amd64 fail test-amd64-amd64-xl-qemuu-ws16-amd64 fail test-amd64-i386-xl-qemuu-ws16-amd64 fail test-armhf-armhf-xl-arndale pass test-amd64-amd64-xl-credit2 pass test-arm64-arm64-xl-credit2 blocked test-armhf-armhf-xl-credit2 pass test-armhf-armhf-xl-cubietruck pass test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict fail test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict fail test-amd64-amd64-examine pass test-arm64-arm64-examine blocked test-armhf-armhf-examine pass test-amd64-i386-examine pass test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumprun-i386 pass test-amd64-amd64-xl-qemut-win10-i386 fail test-amd64-i386-xl-qemut-win10-i386 fail test-amd64-amd64-xl-qemuu-win10-i386 fail test-amd64-i386-xl-qemuu-win10-i386 fail test-amd64-amd64-qemuu-nested-intel pass test-amd64-amd64-xl-pvhv2-intel pass test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt pass test-amd64-i386-libvirt pass test-amd64-amd64-livepatch pass test-amd64-i386-livepatch pass test-amd64-amd64-migrupgrade pass test-amd64-i386-migrupgrade pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub pass test-amd64-amd64-xl-pvshim pass test-amd64-i386-xl-pvshim fail test-amd64-amd64-pygrub pass test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw pass test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds pass test-armhf-armhf-xl-rtds pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow pass test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow pass test-amd64-amd64-xl-shadow pass test-amd64-i386-xl-shadow pass test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd pass ------------------------------------------------------------ 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 broken-job build-arm64 broken broken-job build-arm64-xsm broken broken-job build-arm64-pvops broken broken-step build-arm64-pvops hosts-allocate broken-step build-arm64-xsm hosts-allocate broken-step build-arm64 hosts-allocate broken-step build-arm64 capture-logs broken-step build-arm64-pvops capture-logs broken-step build-arm64-xsm capture-logs Not pushing. ------------------------------------------------------------ commit ed5f8d9ca47e69e30221c37ec812f2b38af19d83 Author: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Date: Tue Jul 31 22:19:05 2018 +0200 tools/gdbsx: use inttypes.h instead of custom macros Signed-off-by: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> [ wei: fix up patch ] Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 0c9821d5c870c35aa38df7bb5e2ff54da2169b5b Author: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Date: Tue Jul 31 04:30:42 2018 +0200 tools/gdbsx: fix 'g' packet response for 64bit guests gdb 8.0 fixed bounds checking for 'g' packet (commit 9dc193c3be85aafa60ceff57d3b0430af607b4ce "Check for truncated registers in process_g_packet"). This revealed that gdbsx did not properly formatted 'g' packet - segment registers and eflags are expected to be 32-bit fields in the response (according to gdb/features/i386/64bit-core.xml in gdb sources). Specific error is: Truncated register 26 in remote 'g' packet instead of silently truncating part of register. Additionally, it looks like segment registers of 64bit guests were never reported correctly, because of type mismatch. Signed-off-by: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 01dfa3378f915111c5fbc0f188f0cfd2658fe013 Author: Simon Gaiser <simon@xxxxxxxxxxxxxxxxxxxxxx> Date: Tue Jul 31 04:56:54 2018 +0200 xenstore-client: Add option for raw in-/output Parsing/generating the escape sequences used by xenstore-client is non trivial. So make scripting (for use in stubdom) easier by adding a raw option. [added man page entries, facor out expand_buffer] Signed-off-by: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit be541e53adf674f2b565ae7cef393da652449efa Author: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Date: Tue Jul 31 04:56:53 2018 +0200 docs: add xenstore-read and xenstore-write man pages Signed-off-by: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit deb0e164dee2ffb92846d3046452930e6fc3b384 Author: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Date: Tue Jul 31 05:15:32 2018 +0200 xenconsole: add option to avoid escape sequences in log Add --replace-escape option to xenconsoled, which replaces ESC with '.' in console output written to log file. This makes it slightly safer to do tail -f on a console output of untrusted guest. The pty output is unaffected by this option. Signed-off-by: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> [ wei: move variables into a narrower scope ] Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 98b92f26019bab403d3e5fa74dbec4bf8a541de4 Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Wed Aug 1 10:03:07 2018 +0100 xen: clean up altp2m op comment Delete trailing spaces and refer to XSM instead of an internal function in the public header. Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit 6aaa9fb308171ec58ddf4cf058ad5341f81a65cf Author: George Dunlap <george.dunlap@xxxxxxxxxx> Date: Tue Jul 31 15:17:21 2018 +0100 hvm/altp2m: Clarify the proper way to extend the altp2m interface The altp2m functionality was originally envisioned to be used in several different configurations, one of which was a single in-guest agent that had full operational control of altp2m. This required the single hypercall to be an HVMOP rather than a DOMCTL, since HVM guests are not allowed to make DOMCTLs. Access to this HVMOP is controlled by a per-domain HVM_PARAM, and defaults to 'off'. Exposing the altp2m functionality to the guest was controversial at the time, but was ultimately accepted. The fact that altp2m is an HVMOP rather than a DOMCTL has caused some problems, however, for those moving forward trying to extend the interface: Extending the interface even for the 'external' use case now means extending an HVMOP, which implicitly extends the surface of attack for the 'internal' use case as well. The result has been that every addition to this interface has also been controversial. Settle the controversy once and for all by documenting 1) the purpose of the altp2m interface, and 2) how to extend it. In particular: * Specify that the fully in-guest agent is a target use case * Specify that all extensions to altp2m functionality should be subops of the HVMOP hypercall * Specify that new subops should be enabled in ALTP2M_mixed mode by default, but that this mode has not been evaluated for safety. Hopefully this will allow the altp2m interface to be developed further without unnecessary controversy. Further discussion: As far as I can tell there are three possible solutions to this controversy. A. Remove the 'internal' functionality as a target by converting the current HVMOP into a DOMCTL. B. Have two hypercalls -- an HVMOP which contains functionality expected to be used by the 'internal' agent, and a DOMCTL for functionality which is expected to be used only be the 'external' agent. C. Agree to add all new subops to the current hypercall (HVMOP), even if we're not sure if they should be exposed to the guest. I think A is a terrible idea. Having a single in-guest agent is a reasonable design choice, and apparently it was even implemented at some point; we should make it straightforward for someone in the future to pick up the work if they want to. I think B is also a bad idea. The people extending it at the moment are primarily concerned with the 'external' use case. There is nobody around to represent whether new functionality should end up in the HVMOP or the DOMCTL, which means that by default it will end up in the DOMCTL. If it is discovered, afterwards, that the new operations *would* be safe and useful for the 'internal' use case, then we will either have to duplicate them inside the HVMOP (which would be terrible) or move the operation from the DOMCTL to the HVMOP (which would make coding an agent against several versions a mess). It just makes more sense to have all the altp2m operations in a single place, and a simple way to control whether they're available to the 'internal' use case or not. As such, I am proposing 'C'. Even within that, we have several options as far as what to do with the current interface: C1: Audit the current subops and make a blacklist of subops not suitable for exposure to the guest. Future subops should be on the blacklist unless they have been evaluated as safe for exposure. C2: Don't blacklist the current subops, but require that all future subops be blacklisted unless they have been evaluated as safe for exposure. C3: Don't blacklist current or future subops for the present; just document that they need to be evaluated (and some potentially blacklisted) before being exposed to a guest in a safety-critical environment. C1 would be ideal, but there's nobody at present to do the work. Given that, C3 has been seen as the best solution in discussion. Reviewed-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxx> commit 960d7b8ffbad12b065d72f1171780eb11f11ee91 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Jul 31 17:12:35 2018 +0200 x86/xstate: correct logging in handle_xsetbv() Correct a disagreement between text and logged value. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit b75bd296d7e8f444362e5e321d09825078875f11 Author: Norbert Manthey <nmanthey@xxxxxxxxx> Date: Tue Jul 31 17:11:36 2018 +0200 memory: fix label syntax When compiling this file with gcc, the compiler happily accepts the sequence of a label followed by an attribute. However, this sequence does not follow the gcc documentation. Hence, other compilers might stumble upon this statement. To be able to compile Xen with goto-cc (the compiler of the CPROVER tool suite), the missing semicolon is added in this commit. Reported-by: Elizabeth Polgreen <polgreen@xxxxxxxxx> Signed-off-by: Norbert Manthey <nmanthey@xxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 867a5e230d21866a35979ec68c5c82604096e018 Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Tue Jul 31 10:25:36 2018 +0200 iommu: remove unneeded return from iommu_hwdom_init Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit 93249f7fc17c1f3a2aa8bf9ea055aa326e93a4ae Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Tue Jul 31 10:25:06 2018 +0200 x86/efi: split compiler vs linker support So that an ELF binary with support for EFI services will be built when the compiler supports the MS ABI, regardless of the linker support for PE. Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Daniel Kiper <daniel.kiper@xxxxxxxxxx> Tested-by: Daniel Kiper <daniel.kiper@xxxxxxxxxx> commit 18cd4997d26b9df95dda87503e41c823279a07a0 Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Tue Jul 31 10:24:22 2018 +0200 x86/efi: move the logic to detect PE build support So that it can be used by other components apart from the efi specific code. By moving the detection code creating a dummy efi/disabled file can be avoided. This is required so that the conditional used to define the efi symbol in the linker script can be removed and instead the definition of the efi symbol can be guarded using the preprocessor. The motivation behind this change is to be able to build Xen using lld (the LLVM linker), that at least on version 6.0.0 doesn't work properly with a DEFINED being used in a conditional expression: ld -melf_x86_64_fbsd -T xen.lds -N prelink.o --build-id=sha1 \ /root/src/xen/xen/common/symbols-dummy.o -o /root/src/xen/xen/.xen-syms.0 ld: error: xen.lds:233: symbol not found: efi Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Daniel Kiper <daniel.kiper@xxxxxxxxxx> commit 38e53a33795a88f305f30f63b7f9548e446ba2ab Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Tue Jul 31 10:23:37 2018 +0200 xen/compiler: introduce a define for weak symbols And replace the open-coded versions already in tree. No functional change. Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reivewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> commit f93021754b34f65f61812491f0beefe3d46d8e7e Author: Doug Goldstein <cardoe@xxxxxxxxxx> Date: Sun Jul 29 16:53:16 2018 -0500 ci: enable builds with CentOS 7.x Add the CentOS 7.x images to be used for build testing. Signed-off-by: Doug Goldstein <cardoe@xxxxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 45205b65294fa7c8911e6632f25fcce86e457345 Author: Doug Goldstein <cardoe@xxxxxxxxxx> Date: Sun Jul 29 16:53:15 2018 -0500 automation: add CentOS 7.x image This image will always track the latest CentOS 7.x release. Add this container to containerize for easy access. Signed-off-by: Doug Goldstein <cardoe@xxxxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |