|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [libvirt test] 80382: regressions - FAIL
flight 80382 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/80382/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt-qcow2 10 guest-start fail REGR. vs. 80121 test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs. 80121 test-amd64-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs. 80121 Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-raw 13 guest-saverestore fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass test-armhf-armhf-libvirt 14 guest-saverestore fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 14 guest-saverestore fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass version targeted for testing: libvirt 6221b8944e04c5cb02d3882833c11ce2319d88f7 baseline version: libvirt 6ec319b84f67d72bf59fe7e0fd41d88ee9c393c7 Last test of basis 80121 2016-02-03 04:26:28 Z 1 days Testing same since 80382 2016-02-04 04:29:24 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Dmitry Andreev <dandreev@xxxxxxxxxxxxx> Erik Skultety <eskultet@xxxxxxxxxx> Ján Tomko <jtomko@xxxxxxxxxx> Martin Kletzander <mkletzan@xxxxxxxxxx> Michal Privoznik <mprivozn@xxxxxxxxxx> Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx> Peter Krempa <pkrempa@xxxxxxxxxx> Roman Bogorodskiy <bogorodskiy@xxxxxxxxx> jobs: build-amd64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-xsm pass test-armhf-armhf-libvirt-xsm fail test-amd64-i386-libvirt-xsm pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt fail test-amd64-i386-libvirt pass test-amd64-amd64-libvirt-pair fail test-amd64-i386-libvirt-pair fail test-armhf-armhf-libvirt-qcow2 fail test-armhf-armhf-libvirt-raw fail test-amd64-amd64-libvirt-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 Not pushing. ------------------------------------------------------------ commit 6221b8944e04c5cb02d3882833c11ce2319d88f7 Author: Roman Bogorodskiy <bogorodskiy@xxxxxxxxx> Date: Sun Jan 3 05:25:35 2016 +0300 virsh: display if ZFS storage backend is enabled Make 'virsh -V' list ZFS storage backend if it's enabled. commit 82f17fbe68d3204932e72296fe07fd416aa8f9fc Author: Roman Bogorodskiy <bogorodskiy@xxxxxxxxx> Date: Thu Feb 4 03:13:10 2016 +0300 configure: zfs: enable on Linux ZFS-on-Linux implementation of ZFS starting with version 0.6.4 contains all the features we use. Additionally, as we support 'volmode' option handling that's not available on ZoL but is available on FreeBSD, there is no need to block ZFS storage driver on Linux anymore. So un-mark zfs storage driver as FreeBSD-only. commit c94f6d4dff41b97f603738b6e749900eb83d19b2 Author: Roman Bogorodskiy <bogorodskiy@xxxxxxxxx> Date: Thu Feb 4 03:03:12 2016 +0300 storage: zfs: flexible use of 'volmode' option There are slight differences in various ZFS implementations. Specifically, ZFS on FreeBSD requires to set value of 'volmode' option to 'dev' to expose volumes as raw disk device (that's what we need) rather than geom provides, for example. With ZFS on Linux, however, such option is not available and volumes exposed like we need by default. To make our implementation more flexible, only pass 'volmode' when it's supported. Support is checked by parsing usage information of the 'zfs get' command. commit 8cd1d546e67f77a72a026d502726a7a961dd43ed Author: Erik Skultety <eskultet@xxxxxxxxxx> Date: Tue Feb 2 14:13:15 2016 +0100 util: Export remoteSerializeTypedParameters internally via util Same as for deserializer, this method might get handy for admin one day. The major reason for this patch is to stay consistent with idea, i.e. when deserializer can be shared, why not serializer as well. The only problem to be solved was that the daemon side serializer uses a code snippet which handles sparse arrays returned by some APIs as well as removes any string parameters that can't be returned to older clients. This patch makes of the new virTypedParameterRemote datatype introduced by one of the pvious patches. commit 9afc115f7308199a7e678c3156832e826696629a Author: Erik Skultety <eskultet@xxxxxxxxxx> Date: Tue Feb 2 13:19:35 2016 +0100 util: Export remoteFreeTypedParameters internally via util Since the method is static to remote_driver, it can't even be used by our daemon. Other than that, it would be useful to be able to use it with admin as well. This patch uses the new virTypedParameterRemote datatype introduced in one of previous patches. commit 0472cef68538a155b18609bc0352467540cd24e0 Author: Erik Skultety <eskultet@xxxxxxxxxx> Date: Thu Jan 28 17:27:42 2016 +0100 util: Export remoteDeserializeTypedParameters internally via util Currently, the deserializer is hardcoded into remote_driver which makes it impossible for admin to use it. One way to achieve a shared implementation (besides moving the code to another module) would be pass @ret_params_val as a void pointer as opposed to the remote_typed_param pointer and add a new extra argument specifying which of those two protocols is being used and typecast the pointer at the function entry. An example from remote_protocol: struct remote_typed_param_value { int type; union { int i; u_int ui; int64_t l; uint64_t ul; double d; int b; remote_nonnull_string s; } remote_typed_param_value_u; }; typedef struct remote_typed_param_value remote_typed_param_value; struct remote_typed_param { remote_nonnull_string field; remote_typed_param_value value; }; That would leave us with a bunch of if-then-elses that needed to be used across the method. This patch takes the other approach using the new datatype introduced in one of earlier commits. commit 41a459947f58c302ff5cbad824fa1737fb3ec374 Author: Erik Skultety <eskultet@xxxxxxxxxx> Date: Tue Feb 2 15:33:30 2016 +0100 util: Introduce virTypedParameterRemote datatype Both admin and remote protocols define their own types (remote_typed_param vs admin_typed_param). Because of the naming convention, admin typed params wouldn't be able to reuse the serialization/deserialization methods, which are tailored for use by remote protocol, even if those method were exported properly. In that case, introduce a new internal data type structurally copying both admin and remote protocols which, eventually, would allow serializer and deserializer to be used in a more generic way. commit 1e93470df0dd0fff678914d53b7431af71f60d97 Author: Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx> Date: Mon Feb 1 12:33:45 2016 +0300 qemu: qemuDomainRename and virDomainObjListNumOfDomains ABBA deadlock fix A pretty nasty deadlock occurs while trying to rename a VM in parallel with virDomainObjListNumOfDomains. The short description of the problem is as follows: Thread #1: qemuDomainRename: ------> aquires domain lock by qemuDomObjFromDomain ---------> waits for domain list lock in any of the listed functions: - virDomainObjListFindByName - virDomainObjListRenameAddNew - virDomainObjListRenameRemove Thread #2: virDomainObjListNumOfDomains: ------> aquires domain list lock ---------> waits for domain lock in virDomainObjListCount Introduce generic virDomainObjListRename function for renaming domains. It aquires list lock in right order to avoid deadlock. Callback is used to make driver specific domain updates. Signed-off-by: Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx> Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> commit 92757d4d2d108cf612916928e733739d40a31942 Author: Martin Kletzander <mkletzan@xxxxxxxxxx> Date: Tue Feb 2 19:45:55 2016 +0100 systemd: Add virSystemdGetMachineNameByPID Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx> commit 9ba2646291266731d2933b54db3c825e19d44db6 Author: Martin Kletzander <mkletzan@xxxxxxxxxx> Date: Mon Feb 1 16:28:29 2016 +0100 Revert "systemd: Escape only needed characters for machined" This reverts commit 0e0149ce91d84f40b98acf4c4bb0da6e29b9c15c. That commit was added to comply with systemd rules that were changed in the meantime, so this patch is pointless. commit e1d7273f245b41578208705e395053f3be613142 Author: Ján Tomko <jtomko@xxxxxxxxxx> Date: Fri Jan 29 18:00:13 2016 +0100 Simplify virDomainParseMemory Do not store the return value of virDomainParseScaledValue, it was overwritten anyway. Delete the cleanup label, there is nothing to clean up. commit 598927a5bce5c47827f4d02b4596a564e7f8b28f Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Mon Jan 4 19:39:02 2016 +0100 conf: Split out logic to determine whether cpupin was provided commit 451b955d62a3e1a41ec7b3edeba39d965f8dbd81 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Thu Dec 17 16:04:23 2015 +0100 qemu: domain: Prepare qemuDomainDetectVcpuPids for reuse Free the old vcpupids array in case when this function is called again during the run of the VM. It will be later reused in the vCPU hotplug code. The function now returns the number of detected VCPUs. commit e97d1d20b174f3cf4bc7052d29000999db658de7 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Tue Dec 15 14:45:33 2015 +0100 qemu: Move and rename qemuProcessDetectVcpuPIDs to qemuDomainDetectVcpuPids Future patches will tweak and reuse the function in different places so move it separately first. commit a190744aa96d6abfb3a8b8946952134bc8b7f436 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Thu Dec 17 13:19:54 2015 +0100 qemu: cpu hotplug: Set vcpu state directly in the new structure Avoid using virDomainDefSetVcpus when we can set it directly in the structure. commit 9bf284daa9b4e28e70f77c434ce4d3a65e5f4acf Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Mon Dec 7 06:36:37 2015 +0100 conf: Add helper to retrieve bitmap of active vcpus for a definition In some cases it may be better to have a bitmap representing state of individual vcpus rather than iterating the definition. The new helper creates a bitmap representing the state from the domain definition. commit 58578f83bc65cdc687eb96f402a9f39dca672844 Author: Peter Krempa <pkrempa@xxxxxxxxxx> Date: Mon Dec 7 07:39:34 2015 +0100 cgroup: Clean up virCgroupGetPercpuStats Use 'ret' for return variable name, clarify use of 'param_idx' and avoid unnecessary 'success' label. No functional changes. Also document the function. commit 1794a0103ae4fa91d9c11617e7981471173e27ce Author: Martin Kletzander <mkletzan@xxxxxxxxxx> Date: Tue Feb 2 22:08:59 2016 +0100 qemu: Don't crash when create fails early Since commit 714080791778e3dfbd484ccb3953bffd820b8ba9 we are generating socket path later than before -- when starting a domain. That makes one particular inconsistent state of a chardev, which was not possible before, currently valid. However, SELinux security driver forgot to guard the main restoring function by a check for NULL-paths. So make it no-op for NULL paths, as in the DAC driver. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1300532 Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx> commit 1fe6d8bfa81c8243516e38e81c31645049cb54e2 Author: Erik Skultety <eskultet@xxxxxxxxxx> Date: Thu Jan 28 16:46:32 2016 +0100 cfg.mk: Adjust sc_prohibit_int_ijk to support 'exempt from syntax-check' There might be cases, like with typed params, where triggering this check isn't desirable. But including the whole module in the exception regex is not always to right way of doing things. By adding an option to manually disable this check on a specific occurrence, the module itself will still be checked against the rule. commit d2dabff3a03862c9560e79957dd8f04443193b4f Author: Dmitry Andreev <dandreev@xxxxxxxxxxxxx> Date: Sat Jan 23 19:08:45 2016 +0300 qemuDomainResume: allow to resume domain with guest panicked In case of guest panicked, preserved crashed domain has stopped CPUs. It's not possible to use tools like WinDbg for the problem investigation until we start CPUs back. commit 4a67b044fbe8f64ebb37a105bdebd3487cc2b707 Author: Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx> Date: Mon Feb 1 16:28:40 2016 +0300 qemu: return -1 on error paths in qemuDomainSaveImageStartVM Error paths after sending the event that domain is started written as if ret = -1 which is set at the beginning of the function. It's common idioma to keep 'ret' equal to -1 until the end of function where it is set to 0. But here we use ret to keep result of restore operation too and thus breaks the idioma and its users :) Let's use different variable to hold restore result. Signed-off-by: Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |