flight 101584 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101584/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs.
101000
flight 101590 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101590/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 101563
Regressions which
On 10/22/2016 1:27 AM, Wei Liu wrote:
On Wed, Oct 12, 2016 at 03:58:24PM +0800, Lan Tianyu wrote:
Dumping timer info may run for a long time on the huge machine with
a lot of physical cpus. To avoid triggering NMI watchdog, add
process_pending_softirqs() in the loop of dumping timer info.
__serial_rx() runs in either irq handler or timer handler and non-irq
keyhandler should not run in these contexts. So always force non-irq
keyhandler to run in tasklet when receive a debugkey from serial port
Signed-off-by: Lan Tianyu
---
xen/drivers/char/console.c | 2 +-
This run is configured for baseline tests only.
flight 67922 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67922/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 3e14edf82031845233f3825ac9239609c0ee98fc
baseline
On Fri, Oct 21, 2016 at 10:11 PM, Meng Xu wrote:
> Bug scenario:
> While a VCPU is running on a core, it may misses its deadline.
> Then repl_timer_handler() will update the VCPU period and deadline.
> The VCPU may have high priority with the new deadline and
Bug scenario:
While a VCPU is running on a core, it may misses its deadline.
Then repl_timer_handler() will update the VCPU period and deadline.
The VCPU may have high priority with the new deadline and repl_timer_handler()
decides to keep the VCPU running on the core, but with new period and
We should clear the __RTDS_depleted bit once a VCPU budget is replenished.
Because repl_timer_handler may be called after rt_schedule
but before rt_context_saved, the VCPU may be not on CPU or on queue
when the VCPU is the middle of context switch
Signed-off-by: Meng Xu
---
On Mon, 5 Sep 2016, Kyle Temkin wrote:
> From: "Kyle J. Temkin"
>
> Several Tegra hardware devices-- and the Tegra device tree-- expect
> the presence of a Tegra Legacy Interrupt Controller (LIC) in the hardware
> domain. Accordingly, we'll need to expose (most of) the
flight 101591 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101591/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 3e14edf82031845233f3825ac9239609c0ee98fc
baseline version:
ovmf
On Fri, 16 Sep 2016, Konrad Rzeszutek Wilk wrote:
> On Mon, Sep 05, 2016 at 06:14:00AM -0400, Kyle Temkin wrote:
> > From: "Kyle J. Temkin"
> >
> > The addition of new IRQ-related platform hooks now allow platforms to
> > perform platform-specific interrupt logic; allowing
Thanks for the patch! I would like to see it in Xen 4.9.
On Fri, 16 Sep 2016, Konrad Rzeszutek Wilk wrote:
> On Mon, Sep 05, 2016 at 06:13:59AM -0400, Kyle Temkin wrote:
> > From: "Kyle J. Temkin"
> >
> > Tegra devices have a legacy interrupt controller (lic, or ictlr)
On Mon, 5 Sep 2016, Kyle Temkin wrote:
> From: "Kyle J. Temkin"
>
> Some common platforms (e.g. Tegra) have non-traditional IRQ controllers
> that must be programmed in addition to their primary GICs-- and which
> can come in unusual topologies. Device trees for targets
Sorry for the late review, I promise I'll be faster next time :-)
On Mon, 5 Sep 2016, Kyle Temkin wrote:
> From: "Kyle J. Temkin"
>
> Currently, we don't copy in the interrupt parent from the host device
> tree; and instead let Xen automatically figure it out when
On Tue, 13 Sep 2016, Konrad Rzeszutek Wilk wrote:
> On Mon, Sep 05, 2016 at 06:13:56AM -0400, Kyle Temkin wrote:
> > From: "Kyle J. Temkin"
> >
> > Tegra boards feature a NS16550-compatible serial mapped into the MMIO
> > space. Add support for its use both as a
* Hardware:
Intel(R) Xeon(R) CPU E3-1220L V2 @ 2.30GHz
Sandisk SSD
32G Ram
* Software:
Debian Stretch/testing is dom0
* Guest operating systems:
Guests Ubuntu 14.04 LTS Debian Stretch/Sid
Ubuntu 16.10 with latest 4.8 kernel crashes
* Functionality tested:
xl
creating booting
pygrub
On Fri, Oct 21, 2016 at 1:36 PM, Dario Faggioli
wrote:
>
> On Wed, 2016-10-19 at 11:13 -0400, Meng Xu wrote:
> > The bug is introduced in Xen 4.7 when we converted RTDS scheduler
> > from quantum-driven model to event-driven model.
> > We assumed rt_schedule() is always
On Fri, 21 Oct 2016, Wei Liu wrote:
> On Thu, Oct 20, 2016 at 01:38:35PM -0700, Stefano Stabellini wrote:
> > On Thu, 20 Oct 2016, Andrew Cooper wrote:
> > > On 20/10/16 21:04, Stefano Stabellini wrote:
> > > > On Thu, 20 Oct 2016, Andrew Cooper wrote:
> > > >> On 20/10/16 20:09, Stefano
On Fri, 21 Oct 2016, Wei Liu wrote:
> On Thu, Oct 20, 2016 at 09:05:26PM +0100, Andrew Cooper wrote:
> > On 20/10/16 21:04, Stefano Stabellini wrote:
> > > On Thu, 20 Oct 2016, Andrew Cooper wrote:
> > >> On 20/10/16 20:09, Stefano Stabellini wrote:
> > >>> On Thu, 20 Oct 2016, Juergen Gross
From: Olaf Hering
Using 'vdev=sd[a-o]' will create an emulated LSI controller, which can
be used by the emulated BIOS to boot from disk. If the HVM domU has also
PV driver the disk may appear twice in the guest. To avoid this an
unplug of the emulated hardware is needed, similar
PAGE_SIZE is undefined on ARM64. Use XC_PAGE_SIZE instead, which is
always 4096 even when page granularity is 64K.
For this to actually work with 64K pages, more changes are required.
Signed-off-by: Stefano Stabellini
Reviewed-by: Juergen Gross
/xen-20161021-tag
for you to fetch changes up to 35132016dc1c27de2b1354b161df6cc22f3ac5bf:
xen_platform: SUSE xenlinux unplug for emulated PCI (2016-10-21 12:11:38
-0700)
Xen 2016/10/21
From: Olaf Hering
Implement SUSE specific unplug protocol for emulated PCI devices
in PVonHVM guests. Its a simple 'outl(1, (ioaddr + 4));'.
This protocol was implemented and used since Xen 3.0.4.
It is used in all SUSE/SLES/openSUSE releases up to SLES11SP3 and
openSUSE 12.3.
In
flight 101592 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101592/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl
On Fri, 21 Oct 2016, Olaf Hering wrote:
> Implement SUSE specific unplug protocol for emulated PCI devices
> in PVonHVM guests. Its a simple 'outl(1, (ioaddr + 4));'.
> This protocol was implemented and used since Xen 3.0.4.
> It is used in all SUSE/SLES/openSUSE releases up to SLES11SP3 and
>
On Fri, 21 Oct 2016, Olaf Hering wrote:
> Using 'vdev=sd[a-o]' will create an emulated LSI controller, which can
> be used by the emulated BIOS to boot from disk. If the HVM domU has also
> PV driver the disk may appear twice in the guest. To avoid this an
> unplug of the emulated hardware is
flight 101574 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101574/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-qcow2 12 saverestore-support-check fail REGR. vs.
101443
This run is configured for baseline tests only.
flight 67921 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67921/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf a750b4ae24ce072f7c5ced1b89c18f9cc23debc8
baseline
flight 101576 linux-3.10 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101576/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 6 xen-boot fail REGR. vs. 100648
On Wed, 2016-10-19 at 11:13 -0400, Meng Xu wrote:
> The bug is introduced in Xen 4.7 when we converted RTDS scheduler
> from quantum-driven model to event-driven model.
> We assumed rt_schedule() is always called for a VCPU
> before the VCPUs budget replenished handler.
>
No, we didn't.
Or at
On Wed, Oct 12, 2016 at 03:58:24PM +0800, Lan Tianyu wrote:
> Dumping timer info may run for a long time on the huge machine with
> a lot of physical cpus. To avoid triggering NMI watchdog, add
> process_pending_softirqs() in the loop of dumping timer info.
>
> Reviewed-by: Konrad Rzeszutek Wilk
On Fri, 2016-10-21 at 18:17 +0100, Wei Liu wrote:
> Clang complains nr_dom_vcpus may be used uninitialized after
> 4a6070ea9.
>
> The real issue is vinfo can be NULL and nr_dom_vcpus remains
> uninitialized if previous call fails.
>
If it were me doing this, I'd just have initialized
Clang complains nr_dom_vcpus may be used uninitialized after
4a6070ea9.
The real issue is vinfo can be NULL and nr_dom_vcpus remains
uninitialized if previous call fails.
Instead of initializing nr_dom_vcpus to 0, check if vinfo is NULL before
calling the free function, because that function
On Fri, Oct 21, 2016 at 05:47:52PM +0100, Andrew Cooper wrote:
> On 21/10/16 17:38, Wei Liu wrote:
> > On Fri, Oct 21, 2016 at 03:45:02PM +, osstest service owner wrote:
> >> flight 101571 xen-unstable real [real]
> >> http://logs.test-lab.xenproject.org/osstest/logs/101571/
> >>
> >>
On 21/10/16 17:38, Wei Liu wrote:
> On Fri, Oct 21, 2016 at 03:45:02PM +, osstest service owner wrote:
>> flight 101571 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/101571/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including
On Fri, Oct 21, 2016 at 03:45:02PM +, osstest service owner wrote:
> flight 101571 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/101571/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>
flight 101582 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101582/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf a750b4ae24ce072f7c5ced1b89c18f9cc23debc8
baseline version:
ovmf
flight 101583 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101583/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl
On Thu, Oct 20, 2016 at 9:19 AM, Andrew Cooper
wrote:
> On 20/10/16 15:15, Wei Liu wrote:
>> On Thu, Oct 20, 2016 at 06:44:26AM -0700, Kyle Huey wrote:
>>> rr (http://rr-project.org/), a Linux userspace record-and-replay reverse-
>>> execution debugger, would like to
On Thu, Oct 20, 2016 at 7:40 AM, Boris Ostrovsky
wrote:
> On 10/20/2016 10:11 AM, Andrew Cooper wrote:
>> On 20/10/16 14:55, Kyle Huey wrote:
> That said, rr currently does not work in Xen guests due to some PMU
> issues that we haven't tracked down yet.
flight 101571 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101571/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 101563
From: Christian Borntraeger
Date: Fri, 21 Oct 2016 17:08:54 +0200
> On 10/21/2016 04:57 PM, David Miller wrote:
>> From: Christian Borntraeger
>> Date: Fri, 21 Oct 2016 13:58:53 +0200
>>
>>> For spinning loops people did often use barrier() or
On 10/21/2016 04:57 PM, David Miller wrote:
> From: Christian Borntraeger
> Date: Fri, 21 Oct 2016 13:58:53 +0200
>
>> For spinning loops people did often use barrier() or cpu_relax().
>> For most architectures cpu_relax and barrier are the same, but on
>> some
flight 101570 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101570/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs.
101000
On Fri, Oct 21, 2016 at 03:49:30PM +0200, Dario Faggioli wrote:
> During NUMA automatic placement, the information
> of how many vCPUs can run on what NUMA nodes is used,
> in order to spread the load as evenly as possible.
>
> Such information is derived from vCPU hard and soft
> affinity, but
During NUMA automatic placement, the information
of how many vCPUs can run on what NUMA nodes is used,
in order to spread the load as evenly as possible.
Such information is derived from vCPU hard and soft
affinity, but that is not enough. In fact, affinity
can be set to be a superset of the
Hello,
Eric Shelton, on Fri 21 Oct 2016 09:01:43 -0400, wrote:
> ERROR: PCI region size must be pow2 type=0x8, size=0xdf08
> u32 u = pci_read_long(d, reg);
> if (u != 0x)
> - d->rom_base_addr = u;
> +{
> + d->rom_base_addr = u;
>
On Wed, 2016-10-19 at 10:48 -0400, Meng Xu wrote:
> Correct the mistakes in the example command
> Correct a simple typo.
>
> Signed-off-by: Meng Xu
>
Acked-by: Dario Faggioli
Regards,
Dario
--
<> (Raistlin Majere)
I am running Xen 4.6.3 (with Marek's recent patches at
https://lists.xen.org/archives/html/xen-devel/2016-10/msg01122.html)
and Linux 4.4.14.
qemu-traditional (running in a stubdom) exits due to an error when I
try doing passthrough of a PCI device that includes an
option/expansion ROM.
On Fri, 2016-10-21 at 11:29 +0100, Wei Liu wrote:
> On Fri, Oct 21, 2016 at 11:56:14AM +0200, Dario Faggioli wrote:
> > diff --git a/tools/libxl/libxl_numa.c b/tools/libxl/libxl_numa.c
> > index 33289d5..f2a719d 100644
> > --- a/tools/libxl/libxl_numa.c
> > +++ b/tools/libxl/libxl_numa.c
> > @@
This run is configured for baseline tests only.
flight 67920 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67920/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 55d05ae145145dafdd77a7c6f5c0b3677096cbde
baseline
On 21/10/16 14:05, Peter Zijlstra wrote:
> On Fri, Oct 21, 2016 at 01:58:55PM +0200, Christian Borntraeger wrote:
>> stop_machine can take a very long time if the hypervisor does
>> overcommitment for guest CPUs. When waiting for "the one", lets
>> give up our CPU by using the new cpu_relax_yield.
Using 'vdev=sd[a-o]' will create an emulated LSI controller, which can
be used by the emulated BIOS to boot from disk. If the HVM domU has also
PV driver the disk may appear twice in the guest. To avoid this an
unplug of the emulated hardware is needed, similar to what is done for
IDE and NIC
Update unplug in Xen HVM guests to cover more cases.
Please review.
changes in v3:
- adapt to API changes from 49137bf ("block-backend: remove blk_flush_all")
changes in v2:
- fix issues reported by checkpatch
Olaf Hering (2):
xen_platform: unplug also SCSI disks
xen_platform: SUSE
Implement SUSE specific unplug protocol for emulated PCI devices
in PVonHVM guests. Its a simple 'outl(1, (ioaddr + 4));'.
This protocol was implemented and used since Xen 3.0.4.
It is used in all SUSE/SLES/openSUSE releases up to SLES11SP3 and
openSUSE 12.3.
In addition old (pre-2011) VMDP
flight 67919 distros-debian-jessie real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67919/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-i386-jessie-netboot-pvgrub 10 guest-start fail REGR. vs. 67877
Tests
flight 101577 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101577/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 101572
build-amd64
On 14/10/16 20:05, Boris Ostrovsky wrote:
> Signed-off-by: Boris Ostrovsky
Reviewed-by: Juergen Gross
Juergen
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
On Fri, Oct 21, 2016 at 12:50:58PM +0200, Juergen Gross wrote:
> On 21/10/16 12:29, Wei Liu wrote:
> > On Fri, Oct 21, 2016 at 11:56:14AM +0200, Dario Faggioli wrote:
> >> During NUMA automatic placement, the information
> >> of how many vCPUs can run on what NUMA nodes is used,
> >> in order to
flight 101575 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101575/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl
On 21/10/16 11:56, Dario Faggioli wrote:
> During NUMA automatic placement, the information
> of how many vCPUs can run on what NUMA nodes is used,
> in order to spread the load as evenly as possible.
>
> Such information is derived from vCPU hard and soft
> affinity, but that is not enough. In
On 21/10/16 12:29, Wei Liu wrote:
> On Fri, Oct 21, 2016 at 11:56:14AM +0200, Dario Faggioli wrote:
>> During NUMA automatic placement, the information
>> of how many vCPUs can run on what NUMA nodes is used,
>> in order to spread the load as evenly as possible.
>>
>> Such information is derived
flight 101573 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101573/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-qcow2 12 saverestore-support-check fail REGR. vs.
101477
flight 101572 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101572/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 55d05ae145145dafdd77a7c6f5c0b3677096cbde
baseline version:
ovmf
On Fri, Oct 21, 2016 at 11:56:14AM +0200, Dario Faggioli wrote:
> During NUMA automatic placement, the information
> of how many vCPUs can run on what NUMA nodes is used,
> in order to spread the load as evenly as possible.
>
> Such information is derived from vCPU hard and soft
> affinity, but
During NUMA automatic placement, the information
of how many vCPUs can run on what NUMA nodes is used,
in order to spread the load as evenly as possible.
Such information is derived from vCPU hard and soft
affinity, but that is not enough. In fact, affinity
can be set to be a superset of the
Hi all
Xen 4.8 rc3 is tagged. You can check that out from xen.git:
git://xenbits.xen.org/xen.git 4.8.0-rc3
For you convenience, please find tarball and signature at:
https://downloads.xenproject.org/release/xen/4.8.0-rc3/
Please send bug reports and test reports to
On Thu, Oct 20, 2016 at 01:38:35PM -0700, Stefano Stabellini wrote:
> On Thu, 20 Oct 2016, Andrew Cooper wrote:
> > On 20/10/16 21:04, Stefano Stabellini wrote:
> > > On Thu, 20 Oct 2016, Andrew Cooper wrote:
> > >> On 20/10/16 20:09, Stefano Stabellini wrote:
> > >>> On Thu, 20 Oct 2016, Juergen
On Thu, Oct 20, 2016 at 09:05:26PM +0100, Andrew Cooper wrote:
> On 20/10/16 21:04, Stefano Stabellini wrote:
> > On Thu, 20 Oct 2016, Andrew Cooper wrote:
> >> On 20/10/16 20:09, Stefano Stabellini wrote:
> >>> On Thu, 20 Oct 2016, Juergen Gross wrote:
> On 19/10/16 21:21,
Sorry I haven't got on this thread yet, but want you know it's on my list
(hopefully will respond next week).
> -Original Message-
> From: Xuquan (Quan Xu) [mailto:xuqu...@huawei.com]
> Sent: Monday, October 17, 2016 5:28 PM
> To: Xuquan (Quan Xu); Tian, Kevin; Jan Beulich
> Cc: Andrew
flight 101568 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/101568/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-xsm 13 saverestore-support-check fail REGR. vs. 101443
71 matches
Mail list logo