[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [qemu-upstream-unstable test] 17567: regressions - FAIL
flight 17567 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17567/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-win7-amd64 10 guest-saverestore.2 fail REGR. vs. 17276 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass test-amd64-i386-xend-qemuu-winxpsp3 16 leak-check/check fail never pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass version targeted for testing: qemuu e2155ddd22fe4378030cbbdbbb089a6fa2f3ad44 baseline version: qemuu f3903bbac78a81fcbce1350cdce860764a62783a ------------------------------------------------------------ People who touched revisions under test: Alex Bligh <alex@xxxxxxxxxxx> Felipe Franciosi <felipe@xxxxxxxxxxxx> Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Weidong Han <hanweidong@xxxxxxxxxx> Zhenguo Wang <wangzhenguo@xxxxxxxxxx> ------------------------------------------------------------ jobs: build-amd64 pass build-armhf pass build-i386 pass build-amd64-oldkern pass build-i386-oldkern pass build-amd64-pvops pass build-i386-pvops pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-i386-xend-qemuu-winxpsp3 fail test-amd64-amd64-xl-qemuu-winxpsp3 fail ------------------------------------------------------------ sg-report-flight on woking.cam.xci-test.com logs: /home/xc_osstest/logs images: /home/xc_osstest/images Logs, config files, etc. are available at http://www.chiark.greenend.org.uk/~xensrcts/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit e2155ddd22fe4378030cbbdbbb089a6fa2f3ad44 Author: Felipe Franciosi <felipe.franciosi@xxxxxxxxxx> Date: Fri Apr 5 15:47:59 2013 +0000 Allow xen guests to plug disks of 1 TiB or more The current xen backend driver implementation uses int64_t variables to store the size of the corresponding backend disk/file. It also uses an int64_t variable to store the block size of that image. When writing the number of sectors (file_size/block_size) to xenstore, however, it passes these values as 32 bit signed integers. This will cause an overflow for any disk of 1 TiB or more. This patch changes the xen backend driver to use a 64 bit integer write xenstore function. upstream-commit-id: 9246ce881128df2a69178779c1ef33c83df3c70d Signed-off-by: Felipe Franciosi <felipe@xxxxxxxxxxxx> Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> commit 2b4260da6d510def4067cc06c439c88a457d016e Author: Felipe Franciosi <felipe.franciosi@xxxxxxxxxx> Date: Fri Apr 5 15:37:32 2013 +0000 Introduce 64 bit integer write interface to xenstore The current implementation of xen_backend only provides 32 bit integer functions to write to xenstore. This patch adds two functions that allow writing 64 bit integers (one generic function and another for the backend only). This patch also fixes the size of the char arrays used to represent these integers as strings (originally 32 bytes, however no more than 12 bytes are needed for 32 bit integers and no more than 21 bytes are needed for 64 bit integers). upstream-commit-id: 10bb3c623478117aee5117c312736f10833decc2 Signed-off-by: Felipe Franciosi <felipe@xxxxxxxxxxxx> Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> commit 7714986a9896a3ba25612b7d4739365a9932041f Author: Alex Bligh <alex@xxxxxxxxxxx> Date: Fri Apr 5 15:45:15 2013 +0000 Xen PV backend: Disable use of O_DIRECT by default as it results in crashes. Due to what is almost certainly a kernel bug, writes with O_DIRECT may continue to reference the page after the write has been marked as completed, particularly in the case of TCP retransmit. In other scenarios, this "merely" risks data corruption on the write, but with Xen pages from domU are only transiently mapped into dom0's memory, resulting in kernel panics when they are subsequently accessed. This brings PV devices in line with emulated devices. Removing O_DIRECT is safe as barrier operations are now correctly passed through. See: http://lists.xen.org/archives/html/xen-devel/2012-12/msg01154.html for more details. upstream-commit-id: c1a88ad1f4ac994cd70695bf08141d161e21533e Signed-off-by: Alex Bligh <alex@xxxxxxxxxxx> Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> commit 2d9b78b602494464ccae7667e655c962db9c3a65 Author: Alex Bligh <alex@xxxxxxxxxxx> Date: Fri Apr 5 15:45:10 2013 +0000 Xen PV backend: Move call to bdrv_new from blk_init to blk_connect This commit delays the point at which bdrv_new (and hence blk_open on the underlying device) is called from blk_init to blk_connect. This ensures that in an inbound live migrate, the block device is not opened until it has been closed at the other end. This is in preparation for supporting devices with open/close consistency without using O_DIRECT. This commit does NOT itself change O_DIRECT semantics. upstream-commit-id: 86f425db3b1c4b6c4a2927eaec35627f9ab2e703 Signed-off-by: Alex Bligh <alex@xxxxxxxxxxx> Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> commit 6dec8e7a46ae33062c05abaeba73b47bbe9337b9 Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Date: Fri Apr 5 23:30:14 2013 +0000 Revert "xen: Disable use of O_DIRECT by default as it results in crashes." This reverts commit f3903bbac78a81fcbce1350cdce860764a62783a. commit 217ecf853bc888858a4dc36554bc5b430d3821ab Author: Hanweidong <hanweidong@xxxxxxxxxx> Date: Tue Apr 2 13:22:41 2013 +0000 xen-mapcache: pass the right size argument to test_bits Compute the correct size for test_bits(). qemu_get_ram_ptr() and qemu_safe_ram_ptr() will call xen_map_cache() with size is 0 if the requested address is in the RAM. Then xen_map_cache() will pass the size 0 to test_bits() for checking if the corresponding pfn was mapped in cache. But test_bits() will always return 1 when size is 0 without any bit testing. Actually, for this case, test_bits should check one bit. So this patch introduced a __test_bit_size which is greater than 0 and a multiple of XC_PAGE_SIZE, then test_bits can work correctly with __test_bit_size >> XC_PAGE_SHIFT as its size. upstream-commit-id: 044d4e1aae539bd4214175bd9591b3de7986cf18 Signed-off-by: Zhenguo Wang <wangzhenguo@xxxxxxxxxx> Signed-off-by: Weidong Han <hanweidong@xxxxxxxxxx> Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> commit 7cde9aa1a4d36eca1f2517ed38740e84b84a8667 Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Date: Tue Apr 2 13:23:40 2013 +0000 xen-mapcache: replace last_address_index with a last_entry pointer Replace last_address_index and last_address_vaddr with a single pointer to the last MapCacheEntry used. upstream-commit-id: e2deee3ea6136b6189e8cfd26379420b9a398d96 Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |