similar to: Re: [Qemu-devel] [PATCH] Remove hardcoded xen-platform device initialization

flight 10413 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10413/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 3 host-install(3) broken test-amd64-i386-win 8 guest-saverestore fail REGR. vs. 10201 test-i386-i386-win 8 guest-saverestore fail REGR. vs. 10201

Hi, the problem is as follows:(And then, others can't login mostly because of the os' busing and you can't do anything else.) [**@xentest ::三 12月 21::~]$ sudo xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1748 2 r----- 29396.3 xp-101 1 256

The xen_platform_pci xl configuration parameter currently has no effect on upstream QEMU; creation of the platform device is hardcoded. I have created a patch to QEMU to remove this hardcoded creation. This patch specifies the appropriate -device argument on the QEMU command line (and hence creates the device) only when xen_platform_pci is true. Signed-off-by: Paul Durrant

From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> When disk is a cdrom and the drive is empty the "params" node in xenstore might be missing completely: cope with it instead of segfaulting. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- hw/xen_disk.c | 16 +++++++++++----- 1 files changed, 11 insertions(+), 5 deletions(-) diff --git

Import "remove bgr" from qemu mainstream. git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6335 c046a42c-6fe2-441c-8c8c-71466251a162 Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- diff --git a/hw/musicpal.c b/hw/musicpal.c index d6bd9ec..44a5659 100644 --- a/hw/musicpal.c +++ b/hw/musicpal.c @@ -835,7 +835,7 @@ static void lcd_refresh(void *opaque)

flight 22184 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106 test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. 22106 Regressions which are regarded as

flight 21952 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/21952/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail REGR. vs. 20054 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop

flight 21930 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/21930/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail REGR. vs. 20054 Tests which are failing intermittently (not blocking): test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 7

flight 21993 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/21993/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail REGR. vs. 20054 Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 8

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded my server from squeeze to wheezy and then to jessie. Server is Intel S3200SHV m/b with Intel(R) Core(TM)2 Quad CPU. I'm pretty sure that before that it was running whatever came before squeeze, I forget the name. I was trying to get xen_pciback to work, so I

flight 17860 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17860/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-pvops 4 kernel-build fail REGR. vs. 17854 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 1 xen-build-check(1)

flight 5665 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5665/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 5640 build-amd64 4 xen-build fail REGR. vs. 5640 build-i386-oldkern 4 xen-build fail REGR. vs. 5640

From: Pranavkumar Sawargaonkar <pranavkumar@linaro.org> This patch adds initial platform stubs for APM X-Gene. Signed-off-by: Anup Patel <anup.patel@linaro.org> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org> Drop earlyprintk (split into earlier patch). Only build on ARM64. Drop empty init and reset hooks and enable 1:1 workaround. Signed-off-by: Ian

On Tue, Dec 15, 2015 at 4:13 AM, Stefano Stabellini <stefano.stabellini at eu.citrix.com> wrote: > On Mon, 14 Dec 2015, Andy Lutomirski wrote: >> On Mon, Dec 14, 2015 at 6:12 AM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Mon, Dec 14, 2015 at 02:00:05PM +0000, David Vrabel wrote: >> >> On 07/12/15 16:19, Stefano Stabellini wrote: >>

Intercepting this MSR is pointless - The swapgs instruction does not cause a vmexit, so the cached result of this is potentially stale after the next guest instruction. It is correctly saved and restored on vcpu context switch. Furthermore, 64bit Windows writes to this MSR on every thread context switch, so interception causes a substantial performance hit. From: Paul Durrant

Hi there, It is my understanding that blktap2 has been removed from the built of xen-hypervisor-{i386|amd64} because of the OpenSSL licensing and its incompatibility with the GPL, but apparently it is possible to not use OpenSSL at all. What is your thoughts about this? Could blktap2 support be added? Should it be packaged separately and be sent to non-free? Thomas -------- Original Message

---------- Wiadomo?? przekazana dalej ---------- Od: Stefano Stabellini <stefano.stabellini at eu.citrix.com> Data: 4 czerwca 2010 14:13 Temat: Re: [Xen-devel] Xen 4.0 in debian packages? Do: Thomas Goirand <thomas at goirand.fr> DW: "xen-devel at lists.xensource.com" <xen-devel at lists.xensource.com> On Thu, 3 Jun 2010, Thomas Goirand wrote: > ?ukasz Ole? wrote:

flight 8803 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8803/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 4 xen-install fail REGR. vs. 8769 test-amd64-i386-xl 4 xen-install fail REGR. vs. 8769 test-amd64-i386-pair 6 xen-install/dst_host fail REGR. vs. 8769

flight 14682 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/14682/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-winxpsp3 8 guest-saverestore fail REGR. vs. 14678 test-amd64-amd64-xl-qemut-winxpsp3 12 guest-localmigrate/x10 fail REGR. vs. 14678 test-amd64-amd64-xl-qemuu-win7-amd64

# HG changeset patch # User Paul Durrant <paul.durrant@citrix.com> # Date 1322574403 0 # Node ID 51692288a6e84c941f9e5049c73b7246bab97f70 # Parent e1e952982cf1d7a0c38a7822a8b5e78ba04b5ba5 Fix hvmloader xenbus segment array length. c/s acc408d667e1 had this one too short for handling a write. This incremental patch rectifies the problem. Signed-off-by: Paul Durrant