flight 65521 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65521/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-pair4 host-install/dst_host(4) broken REGR. vs. 59254
test-amd64-i386-xl-qe
On 08/12/15 17:34, Andrew Cooper wrote:
> On 08/12/15 16:02, Juergen Gross wrote:
>> On 08/12/15 16:04, Andrew Cooper wrote:
>>> On 08/12/15 14:44, Juergen Gross wrote:
I'm just playing a little bit with xenstore in an own domain.
I've come across some questions I'd like to have some
On Tue, 2015-12-08 at 10:29 +, Ian Campbell wrote:
> On Tue, 2015-12-08 at 08:06 +, Hu, Robert wrote:
> > >
> > [...]
>
> Please trim your quotes.
>
> > For your failure, as Kevin mentioned in other mail, we will find someone
> > to look into.
> > Would you find out the detailed log of '
flight 65554 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65554/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-winxpsp3 3 host-install(3) broken REGR. vs. 64765
build-armhf
Add pci = [ '$VF_BDF1', '$VF_BDF2', '$VF_BDF3'] in
hvm guest configuration file. After the guest boot up,
detach the VFs in sequence by
"xl pci-detach $DOMID $VF_BDF1"
"xl pci-detach $DOMID $VF_BDF2"
"xl pci-detach $DOMID $VF_BDF3"
and reattach the VFs in sequence by
"xl pci-attach $DOMID $VF_B
This run is configured for baseline tests only.
flight 38466 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38466/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemuu-rhe
On 12/08/15 at 10:57pm, Daniel Kiper wrote:
> Provide just print_crashkernel_region_size() stub. This way
> we can properly build kexec utility on ppc arch even
> if the functionality is not available on it.
The functionality is available by reading device tree nodes in procfs..
>
> Signed-off-b
On 12/08/15 at 10:57pm, Daniel Kiper wrote:
> Provide just print_crashkernel_region_size() stub. This way
> we can properly build kexec utility on ppc64 arch even
> if the functionality is not available on it.
Ditto as ppc, you can read procfs file to get the values..
>
> Signed-off-by: Daniel K
On 12/08/15 at 10:57pm, Daniel Kiper wrote:
> Provide just print_crashkernel_region_size() stub. This way
> we can properly build kexec utility on cris arch even
> if the functionality is not available on it.
>
> Signed-off-by: Daniel Kiper
> ---
> kexec/arch/cris/kexec-cris.c |5 +
> 1
This run is configured for baseline tests only.
flight 38467 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38467/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 5ac96e3a28dd26eabee421919f67fa7c443a47f1
baseline version:
ovm
flight 6 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/6/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 3 host-install(3) broken REGR. vs. 649
Add pci = [ '$VF_BDF1', '$VF_BDF2', '$VF_BDF3'] in
hvm guest configuration file. After the guest boot up,
detach the VFs in sequence by "xl pci-detach $DOMID $VF_BDF",
reattach the VFs by "xl pci-attach $VF_BDF" in sequence.
An error message will be reported like this:
"libxl: error: libxl_qmp.c:28
flight 65557 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65557/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 653
On Tue, Dec 08, 2015 at 04:34:13PM +, Andrew Cooper wrote:
> On 08/12/15 16:02, Juergen Gross wrote:
> > On 08/12/15 16:04, Andrew Cooper wrote:
> >> On 08/12/15 14:44, Juergen Gross wrote:
> >>> I'm just playing a little bit with xenstore in an own domain.
...
> >>> c) In order to be as flexib
Make st_* statistics per ring and the VBD sysfs would iterate over all the
rings.
Note: xenvbd_sysfs_delif() is called in xen_blkbk_remove() before all rings
are torn down, so it's safe.
This patch was based on konrad/xen.git/for-jens-4.5.
Signed-off-by: Bob Liu
---
drivers/block/xen-blkback/b
flight 65543 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65543/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 5ac96e3a28dd26eabee421919f67fa7c443a47f1
baseline version:
ovmf 84c7452165816ed26cd5bdeb5666d4dc002
flight 65522 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65522/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 4 host-install/dst_host(4) broken REGR. vs. 60684
test-amd64
Provide just print_crashkernel_region_size() stub. This way
we can properly build kexec utility on ppc64 arch even
if the functionality is not available on it.
Signed-off-by: Daniel Kiper
---
kexec/arch/ppc64/crashdump-ppc64.c |5 +
1 file changed, 5 insertions(+)
diff --git a/kexec/arc
Crash kernel region size is available via sysfs on Linux running on
bare metal. However, this does not work when Linux runs as Xen dom0.
In this case Xen crash kernel region size should be established using
__HYPERVISOR_kexec_op hypercall (Linux kernel kexec functionality does
not make a lot of sen
Follow similar x86 patch.
Signed-off-by: Daniel Kiper
---
kexec/arch/ia64/crashdump-ia64.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/kexec/arch/ia64/crashdump-ia64.c b/kexec/arch/ia64/crashdump-ia64.c
index 726c9f4..07de42a 100644
--- a/kexec/arch/ia64/crashdump-ia64.c
++
Provide just print_crashkernel_region_size() stub. This way
we can properly build kexec utility on cris arch even
if the functionality is not available on it.
Signed-off-by: Daniel Kiper
---
kexec/arch/cris/kexec-cris.c |5 +
1 file changed, 5 insertions(+)
diff --git a/kexec/arch/cris/
Here print_crashkernel_region_size() function is available on all archs (even
if the functionality is not implemented on some). So, we can safely use it in
arch independent code and export the functionality to the user space.
Signed-off-by: Daniel Kiper
---
kexec/kexec.8 |3 +++
kexec/kexec.
Signed-off-by: Daniel Kiper
---
kexec/kexec.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kexec/kexec.c b/kexec/kexec.c
index f0bd527..20dd93d 100644
--- a/kexec/kexec.c
+++ b/kexec/kexec.c
@@ -969,7 +969,7 @@ void usage(void)
" prese
Provide just print_crashkernel_region_size() stub. This way
we can properly build kexec utility on ppc arch even
if the functionality is not available on it.
Signed-off-by: Daniel Kiper
---
kexec/arch/ppc/crashdump-powerpc.c |4
1 file changed, 4 insertions(+)
diff --git a/kexec/arch/p
Follow similar x86 patch.
Signed-off-by: Daniel Kiper
---
kexec/arch/s390/kexec-s390.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/kexec/arch/s390/kexec-s390.c b/kexec/arch/s390/kexec-s390.c
index 074575e..212a64f 100644
--- a/kexec/arch/s390/kexec-s390.c
+++ b/kexec/arch/s
Follow similar x86 patch.
Signed-off-by: Daniel Kiper
---
kexec/arch/mips/crashdump-mips.c |9 +
1 file changed, 9 insertions(+)
diff --git a/kexec/arch/mips/crashdump-mips.c b/kexec/arch/mips/crashdump-mips.c
index dc68cb4..450fa13 100644
--- a/kexec/arch/mips/crashdump-mips.c
+++
Provide just print_crashkernel_region_size() stub. This way
we can properly build kexec utility on m68k arch even
if the functionality is not available on it.
Signed-off-by: Daniel Kiper
---
kexec/arch/m68k/kexec-m68k.c |5 +
1 file changed, 5 insertions(+)
diff --git a/kexec/arch/m68k/
Crash kernel region size is available via sysfs on Linux running on
bare metal. However, this does not work when Linux runs as Xen dom0.
In this case Xen crash kernel region size should be established using
__HYPERVISOR_kexec_op hypercall (Linux kernel kexec functionality does
not make a lot of sen
Signed-off-by: Daniel Kiper
---
purgatory/Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/purgatory/Makefile b/purgatory/Makefile
index 2b5c061..caea7ea 100644
--- a/purgatory/Makefile
+++ b/purgatory/Makefile
@@ -33,7 +33,7 @@ PURGATORY_SRCS+=$($(ARCH)_PURGATORY_S
Follow similar x86 patch.
Signed-off-by: Daniel Kiper
---
kexec/arch/arm/crashdump-arm.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/kexec/arch/arm/crashdump-arm.c b/kexec/arch/arm/crashdump-arm.c
index b523e5f..b3e93ad 100644
--- a/kexec/arch/arm/crashdump-arm.c
+++ b/kexe
Signed-off-by: Daniel Kiper
---
kexec/crashdump.h |1 -
1 file changed, 1 deletion(-)
diff --git a/kexec/crashdump.h b/kexec/crashdump.h
index 95f1f0c..320767b 100644
--- a/kexec/crashdump.h
+++ b/kexec/crashdump.h
@@ -1,7 +1,6 @@
#ifndef CRASHDUMP_H
#define CRASHDUMP_H
-int get_crashker
Follow similar x86 patch.
Signed-off-by: Daniel Kiper
---
kexec/arch/sh/crashdump-sh.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/kexec/arch/sh/crashdump-sh.c b/kexec/arch/sh/crashdump-sh.c
index 9e6af6b..6556eb1 100644
--- a/kexec/arch/sh/crashdump-sh.c
+++ b/kexec/arch/s
On Tue, 8 Dec 2015, Boris Ostrovsky wrote:
> On 12/08/2015 04:02 PM, Thomas Gleixner wrote:
> > > > --- a/arch/x86/kernel/rtc.c
> > > > +++ b/arch/x86/kernel/rtc.c
> > > > @@ -200,6 +200,9 @@ static __init int add_rtc_cmos(void)
> > > > }
> > > > #endif
> > > > + if (xen_pv_domain()
On 12/08/2015 04:02 PM, Thomas Gleixner wrote:
On Fri, 4 Dec 2015, David Vrabel wrote:
On 04/12/15 14:06, David Vrabel wrote:
On 03/12/15 10:43, David Vrabel wrote:
Adding the rtc platform device when there are no legacy irqs (no
legacy PIC) causes a conflict with other devices that end up usi
flight 65542 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65542/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-amd64-pvgrub 3 host-install(3) broken in 65498 pass in 65542
test-amd64-amd64-xl-qemuu-debianh
On Fri, 4 Dec 2015, David Vrabel wrote:
> On 04/12/15 14:06, David Vrabel wrote:
> > On 03/12/15 10:43, David Vrabel wrote:
> >> Adding the rtc platform device when there are no legacy irqs (no
> >> legacy PIC) causes a conflict with other devices that end up using the
> >> same irq number.
> >
>
The block-attach command now returns 1 when fails. Update first test
case to expect return value 1 instead of 255.
The parser now doesn't generate output for default values. Remove them
from expected output.
The "discard=" variant is never not supported, so delete two test cases
with that variant
flight 65572 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65572/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 13
On 11/30/15 8:45 AM, Jan Beulich wrote:
On 24.11.15 at 18:51, wrote:
>> --- a/xen/Makefile
>> +++ b/xen/Makefile
>> @@ -26,6 +26,9 @@ default: build
>> .PHONY: dist
>> dist: install
>>
>> +.PHONY: build
>> +build:: $(BASEDIR)/include/config/auto.conf
>> +
>> .PHONY: build install uninsta
On Tue, Dec 08, 2015 at 12:51:25PM +, Julien Grall wrote:
> Hi Konrad,
>
> On 07/12/15 15:01, Konrad Rzeszutek Wilk wrote:
> > On Mon, Dec 07, 2015 at 02:21:46PM +, Julien Grall wrote:
> >> Thank you, the changes look good to me. What about patch #2?
> >
> > Oh, I thought you said you wou
On 12/07/2015 08:52 PM, Haozhong Zhang wrote:
On 12/07/15 13:14, Boris Ostrovsky wrote:
On 12/06/2015 03:58 PM, Haozhong Zhang wrote:
This patch makes the pvclock return the scaled host TSC and
corresponding scaling parameters to HVM domains if guest TSC is not
emulated and TSC scaling is enabl
flight 65540 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65540/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-prev 3 host-install(3) broken REGR. vs. 65114
build-i386-xsm
On 12/07/2015 08:08 PM, Haozhong Zhang wrote:
On 12/07/15 12:53, Boris Ostrovsky wrote:
On 12/06/2015 03:58 PM, Haozhong Zhang wrote:
When the TSC mode of a HVM container is TSC_MODE_DEFAULT or
TSC_MODE_PVRDTSCP and no TSC emulation is used, the existing
tsc_get_info() uses the host TSC frequen
> > Correct, it was just providing the rom to the driver. Is there already
> > a way to allow pci-front to pass this, or does it require a patch? I
> > do not know the code base very well, nor do I have much experience
> > with how PCI operates, I was pretty excited to get this far :)
>
> I am not
On 08/12/15 17:59, Doug Goldstein wrote:
> On 12/8/15 8:25 AM, Jan Beulich wrote:
> On 08.12.15 at 15:16, wrote:
>>> On 12/8/15 1:32 AM, Jan Beulich wrote:
>>> On 07.12.15 at 22:27, wrote:
> On 12/3/15 2:57 AM, Jan Beulich wrote:
> On 03.12.15 at 01:34, wrote:
>>> On 12/1
branch xen-unstable
xenbranch xen-unstable
job build-i386-xsm
testid xen-build
Tree: ovmf https://github.com/tianocore/edk2.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: ovmf https://gi
On 12/8/15 8:25 AM, Jan Beulich wrote:
On 08.12.15 at 15:16, wrote:
>> On 12/8/15 1:32 AM, Jan Beulich wrote:
>> On 07.12.15 at 22:27, wrote:
On 12/3/15 2:57 AM, Jan Beulich wrote:
On 03.12.15 at 01:34, wrote:
>> On 12/1/15 5:22 AM, Jan Beulich wrote:
>> On 30.
flight 65569 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65569/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 11 guest-start fail REGR. vs. 65561
Tests which di
On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
> save_domain was already constructing an error code; it just wasn't
> being used.
>
> Signed-off-by: George Dunlap
Acked-by: Ian Campbell
> ---
> CC: Ian Campbell
> CC: Ian Jackson
> CC: Wei Liu
> ---
> tools/libxl/xl_cmdimpl.c | 3
On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
> Add return codes for pci-detach, pci-attach, pci-asssignable-add, and
> pci-assignable-remove.
>
> Returning error codes makes it easier for shell scripts to tell if a
> command has failed or succeeded.
>
> Signed-off-by: George Dunlap
>
On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
> This makes xl more useful in scripts.
>
> The strange thing about this is that the internal cd_insert function
> *already* returned something appropriate, and cd-eject was using it,
> but cd-insert wasnt.
Missing an apostrophe in wasnt.
>
On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
> Bring set_memory_target into line with set_memory_max (which does
> return an error code.
>
> Signed-off-by: George Dunlap
> ---
> CC: Ian Campbell
> CC: Ian Jackson
> CC: Wei Liu
> CC: Konrad Wilk
> ---
> tools/libxl/xl_cmdimpl.c | 1
On 08/12/15 17:19, Ian Campbell wrote:
> On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
>> libxl_set_memory_target seems to have the following return values:
>>
>> * 1 on failure, if the failure happens because of a xenstore error *or*
>> invalid target
>>
>> * -1 if the setmaxmem hypercal
On Wed, 2015-12-02 at 16:30 +0100, Juergen Gross wrote:
> On 02/12/15 16:28, Ian Campbell wrote:
> > On Wed, 2015-12-02 at 12:36 +, Andrew Cooper wrote:
> > > On 02/12/15 07:42, Juergen Gross wrote:
> > > > diff --git a/tools/libxc/xc_sr_save_x86_hvm.c
> > > > b/tools/libxc/xc_sr_save_x86_hvm.c
On Mon, 2015-12-07 at 13:09 +, Andrew Cooper wrote:
> Error messages along the lines of:
>
> xc: error: panic: xc_dom_core.c:207: failed to open file: No such file
> or
> directory: Internal error
>
> are of very little use.
>
> Include the filename in the error messages, so the user d
On Tue, 2015-12-08 at 15:14 +, Ian Jackson wrote:
> Sander Eikelenboom writes ("[PATCH] Fix regression in xendomains
> initscript: test for privcmd char device"):
> > Since commit:
> > "xendomains initscript: test for privcmd char device"
> > (1367e9e5ba4d1612e303123ec0bbf961100fcfa1)
> > due t
On Tue, 2015-12-08 at 12:26 +, George Dunlap wrote:
> On Tue, Dec 1, 2015 at 12:09 PM, George Dunlap
> wrote:
> > We have several outstanding patch series which add devices that have
> > two levels: a controller and individual devices attached to that
> > controller.
> >
> > In the interest o
On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
> libxl_set_memory_target seems to have the following return values:
>
> * 1 on failure, if the failure happens because of a xenstore error *or*
> invalid target
>
> * -1 if the setmaxmem hypercall
>
> * -errno if the set_pod_target hyperca
On Tue, 2015-12-01 at 11:53 +, George Dunlap wrote:
> Return proper error codes on failure so that scripts can tell whether
> the command completed properly or not.
>
> Also while we're at it, normalize init and dispose of
> libxl_device_disk structures. This means calling init and dispose in
On Mon, 2015-12-07 at 17:48 +0100, Roger Pau Monne wrote:
> Allow the usage of the VCPUOP_initialise, VCPUOP_up, VCPUOP_down,
> VCPUOP_is_up, VCPUOP_get_physid and VCPUOP_send_nmi hypercalls from HVM
> guests.
>
> This patch introduces a new structure (vcpu_hvm_context) that should be
> used
> in
On Wed, 2015-12-02 at 15:22 +, Paul Durrant wrote:
> > -Original Message-
> > From: Ian Campbell [mailto:ian.campb...@citrix.com]
> > Sent: 02 December 2015 15:21
> > To: Paul Durrant; xen-de...@lists.xenproject.org
> > Cc: Ian Jackson; Stefano Stabellini; Wei Liu
> > Subject: Re: [PATC
On 08/12/15 16:02, Juergen Gross wrote:
> On 08/12/15 16:04, Andrew Cooper wrote:
>> On 08/12/15 14:44, Juergen Gross wrote:
>>> I'm just playing a little bit with xenstore in an own domain.
>>>
>>> I've come across some questions I'd like to have some answers to before
>>> presenting official patc
Daniel P. Berrange wrote:
> On Mon, Dec 07, 2015 at 10:59:32PM -0700, Jim Fehlig wrote:
>> On 12/07/2015 11:52 AM, Daniel P. Berrange wrote:
>>> On Mon, Dec 07, 2015 at 09:42:21AM -0700, Jim Fehlig wrote:
In commit d2e5538b1, the libxl driver was changed to copy interface
names autogenera
On 08/12/15 16:04, Andrew Cooper wrote:
> On 08/12/15 14:44, Juergen Gross wrote:
>> I'm just playing a little bit with xenstore in an own domain.
>>
>> I've come across some questions I'd like to have some answers to before
>> presenting official patches to make this an easy configurable option:
>
flight 65561 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65561/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 13
Since commit:
"xendomains initscript: test for privcmd char device"
(1367e9e5ba4d1612e303123ec0bbf961100fcfa1)
due to incorrect negation the xendomains initscript bails out
early when both: "/dev/xen/privcmd" and "/proc/xen/privcmd"
are present in dom0.
Signed-off-by: Sander Eikelenboom
---
tool
flight 38464 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38464/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-amd64-weekly-netinst-pygrub 9 debian-di-install fail REGR. vs.
38405
Sander Eikelenboom writes ("[PATCH] Fix regression in xendomains initscript:
test for privcmd char device"):
> Since commit:
> "xendomains initscript: test for privcmd char device"
> (1367e9e5ba4d1612e303123ec0bbf961100fcfa1)
> due to incorrect negation the xendomains initscript bails out
> early
On 08/12/15 14:55, Geoffrey McRae wrote:
>
> On 09/12/15 01:51, Andrew Cooper wrote:
>> On 08/12/15 14:37, Geoffrey McRae wrote:
>>> Hi All,
>>>
>>> This is just a heads up on the steps involved in getting a HD4550
>>> working with the ATI driver as a pv guest on a Dom0 with no IOMMU
>>> support. T
On 08/12/15 14:44, Juergen Gross wrote:
> I'm just playing a little bit with xenstore in an own domain.
>
> I've come across some questions I'd like to have some answers to before
> presenting official patches to make this an easy configurable option:
>
> a) As this would need a boot time configura
On Tue, 2015-12-08 at 14:54 +, Anthony PERARD wrote:
> On Tue, Dec 08, 2015 at 10:23:49AM +, Ian Campbell wrote:
> > On Fri, 2015-11-20 at 14:55 +, Anthony PERARD wrote:
> >
> > I think this will also add a devstack job to most other flights? That's
> > a
> > good thing, I think.
>
>
On 09/12/15 01:51, Andrew Cooper wrote:
On 08/12/15 14:37, Geoffrey McRae wrote:
Hi All,
This is just a heads up on the steps involved in getting a HD4550
working with the ATI driver as a pv guest on a Dom0 with no IOMMU
support. The main issue with making this work was providing a way for
the
On Tue, Dec 08, 2015 at 10:23:49AM +, Ian Campbell wrote:
> On Fri, 2015-11-20 at 14:55 +, Anthony PERARD wrote:
>
> I think this will also add a devstack job to most other flights? That's a
> good thing, I think.
That was not my intention. It's true that the more test, the better, but on
On 08/12/15 14:37, Geoffrey McRae wrote:
> Hi All,
>
> This is just a heads up on the steps involved in getting a HD4550
> working with the ATI driver as a pv guest on a Dom0 with no IOMMU
> support. The main issue with making this work was providing a way for
> the guest to read the vga bios.
>
>
I'm just playing a little bit with xenstore in an own domain.
I've come across some questions I'd like to have some answers to before
presenting official patches to make this an easy configurable option:
a) As this would need a boot time configuration item I'd like to add
e.g. /etc/xen/server.
On 08/12/15 12:54, Jan Beulich wrote:
On 08.12.15 at 12:37, wrote:
>> On 08/12/15 08:28, Jan Beulich wrote:
>> On 07.12.15 at 17:48, wrote:
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -1842,7 +1842,7 @@ static const char * hvm_efer_valid(const struct vcpu
Hi All,
This is just a heads up on the steps involved in getting a HD4550
working with the ATI driver as a pv guest on a Dom0 with no IOMMU
support. The main issue with making this work was providing a way for
the guest to read the vga bios.
[2.127078] [drm] Initialized drm 1.1.0 2006081
On Tue, 2015-12-08 at 14:19 +, Ian Jackson wrote:
> If OSSTEST_TASK is not set, we construct a from the username
> and the nodename, and look for a such a static task. If OSSTEST_TASK
> /is/ set would require it to contain ` '.
>
> In this patch, permit OSSTEST_TASK to be set simply to the
Ian Campbell writes ("[PATCH OSSTEST v2] standalone: Log things we are running
via with_logging"):
> Turning on set -x generally in this script is too verbose, so run the
> command in a subshell which sets -x.
>
> Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
(I will pick this up into my
>>> On 08.12.15 at 15:16, wrote:
> On 12/8/15 1:32 AM, Jan Beulich wrote:
> On 07.12.15 at 22:27, wrote:
>>> On 12/3/15 2:57 AM, Jan Beulich wrote:
>>> On 03.12.15 at 01:34, wrote:
> On 12/1/15 5:22 AM, Jan Beulich wrote:
> On 30.11.15 at 18:53, wrote:
>>> On 11/30/15 8:
Ian Campbell writes ("Re: [OSSTEST PATCH 15/16] mg-schema-test-database: Safety
catch in JobDB database open"):
> On Mon, 2015-12-07 at 17:27 +, Ian Jackson wrote:
> > +# mg-schema-test-database creates a task
> > +# xdbref/DBNAME with username ${Username}@
>
> Was there intended to
Ian Campbell writes ("Re: [OSSTEST PATCH 13/16] mg-schema-test-database: Change
username for back-to-main-db xref"):
> On Mon, 2015-12-07 at 17:27 +, Ian Jackson wrote:
> > Currently this is purely cosmetic, but it is going to be useful to
> > distinguish the two cases:
> > * This is a test D
If OSSTEST_TASK is not set, we construct a from the username
and the nodename, and look for a such a static task. If OSSTEST_TASK
/is/ set would require it to contain ` '.
In this patch, permit OSSTEST_TASK to be set simply to the .
This is much more convenient and doesn't involve manually look
On 12/8/15 1:32 AM, Jan Beulich wrote:
On 07.12.15 at 22:27, wrote:
>> On 12/3/15 2:57 AM, Jan Beulich wrote:
>> On 03.12.15 at 01:34, wrote:
On 12/1/15 5:22 AM, Jan Beulich wrote:
On 30.11.15 at 18:53, wrote:
>> On 11/30/15 8:36 AM, Jan Beulich wrote:
>> On 24
The tables are almost identical and therefore there is little reason to
keep both sets.
PVH needs 3 extra hypercalls:
* mmuext_op. PVH uses MMUEXT_TLB_FLUSH_MULTI and MMUEXT_INVLPG_MULTI to
optimize TLB flushing. Since HVMlite guests may decide to use them as
well we can allow these two comman
flight 65523 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65523/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken REGR. vs. 63340
build-amd64-xsm
After update dom0 kernel to 3.19, all vcpus act normal. Thanks very much.
2015-12-07 21:02 GMT+08:00 Jan Beulich :
> >>> On 07.12.15 at 13:56, wrote:
> > On 07/12/15 12:39, Big Strong wrote:
> >> I set the xen.efi directly boot without grub2 to be able to list all
> >> the cpu cores.
> >> Howeve
>>> On 08.12.15 at 12:37, wrote:
> On 08/12/15 08:28, Jan Beulich wrote:
> On 07.12.15 at 17:48, wrote:
>>> --- a/xen/arch/x86/hvm/hvm.c
>>> +++ b/xen/arch/x86/hvm/hvm.c
>>> @@ -1842,7 +1842,7 @@ static const char * hvm_efer_valid(const struct vcpu
> *v, uint64_t value,
>>> {
>>>
Hi Konrad,
On 07/12/15 15:01, Konrad Rzeszutek Wilk wrote:
> On Mon, Dec 07, 2015 at 02:21:46PM +, Julien Grall wrote:
>> Thank you, the changes look good to me. What about patch #2?
>
> Oh, I thought you said you would rebase it - so I had been waiting
> for that.
>
> Should have communicat
Hi Royger,
On 01/12/15 15:30, Roger Pau Monné wrote:
> Just a couple of cosmetic comments below. Unless anyone else has real
> comments I don't think you need to resend.
Well, I'm considering those kind of comestic comments as minor. They are
not necessary and doesn't improve the readability of t
On Tue, Dec 08, 2015 at 12:11:34PM +, Ian Campbell wrote:
> On Tue, 2015-12-08 at 13:00 +0100, Samuel Thibault wrote:
> > Marek Marczykowski-Górecki, on Tue 08 Dec 2015 12:46:31 +0100, wrote:
> > > > > http://xenbits.xen.org/gitweb/?p=mini-os.git;a=commit;h=7c8f3483906
> > > > > 52a67e
> > > >
Hi Konrad,
The rebase of my patch is not correct. It now contains an unused variable and
missing one change.
I will post the rebase of the two patches.
On 01/12/15 18:52, Konrad Rzeszutek Wilk wrote:
> +static unsigned long blkif_ring_get_request(struct blkfront_ring_info *rinfo,
> +
On Tue, Dec 1, 2015 at 12:09 PM, George Dunlap
wrote:
> We have several outstanding patch series which add devices that have
> two levels: a controller and individual devices attached to that
> controller.
>
> In the interest of consistency, this patch introduces a section that
> sketches out a te
On Tue, Dec 1, 2015 at 11:53 AM, George Dunlap
wrote:
> Return proper error codes on failure so that scripts can tell whether
> the command completed properly or not.
>
> Also while we're at it, normalize init and dispose of
> libxl_device_disk structures. This means calling init and dispose in
>
On Tue, 2015-12-08 at 13:00 +0100, Samuel Thibault wrote:
> Marek Marczykowski-Górecki, on Tue 08 Dec 2015 12:46:31 +0100, wrote:
> > > > http://xenbits.xen.org/gitweb/?p=mini-os.git;a=commit;h=7c8f3483906
> > > > 52a67e
> > > > 9356eec9cd2b0f76a9c7c72
> > > >
> > > > With that commit reverted, is
On Mon, 2015-12-07 at 17:24 +, Wei Liu wrote:
> Signed-off-by: Wei Liu
> ---
> mg-hosts | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/mg-hosts b/mg-hosts
> index a911099..0d02c56 100755
> --- a/mg-hosts
> +++ b/mg-hosts
> @@ -24,6 +24,13 @@
> # of osstest. W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xen Security Advisory CVE-2015-8341 / XSA-160
version 3
libxl leak of pv kernel and initrd on error
UPDATES IN VERSION 3
Public release.
ISSUE DESCRIPTION
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xen Security Advisory CVE-2015-8339,CVE-2015-8340 / XSA-159
version 4
XENMEM_exchange error handling issues
UPDATES IN VERSION 4
Public release.
ISSUE DESCRIPTION
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xen Security Advisory CVE-2015-8338 / XSA-158
version 3
long running memory operations on ARM
UPDATES IN VERSION 3
Public release.
ISSUE DESCRIPTION
=
C
Marek Marczykowski-Górecki, on Tue 08 Dec 2015 12:46:31 +0100, wrote:
> > > http://xenbits.xen.org/gitweb/?p=mini-os.git;a=commit;h=7c8f348390652a67e
> > > 9356eec9cd2b0f76a9c7c72
> > >
> > > With that commit reverted, issue vanishes.
> > >
> > > I guess it's because before this commit, there was
1 - 100 of 132 matches
Mail list logo
