Currently, a blocked vCPU is put in its pCPU's pi blocking list. If
too many vCPUs are blocked on a given pCPU, it will incur that the list
grows too long. After a simple analysis, there are 32k domains and
128 vcpu per domain, thus about 4M vCPUs may be blocked in one pCPU's
PI blocking list. When
This patch adds a field, counter, in struct vmx_pi_blocking_vcpu to track
how many entries are on the pi blocking list. In order to analyze list
operation frequence and obtain the list length, add some relevant events
to xentrace and some associated code in xenalyze. As to xenalyze, for
removing fr
This number is used to calculate how many hvm vcpu on a pcpu on average.
This counting is x86 specific.
Signed-off-by: Chao Gao
---
xen/arch/x86/domain.c| 10 ++
xen/include/asm-x86/domain.h | 2 ++
2 files changed, 12 insertions(+)
diff --git a/xen/arch/x86/domain.c b/xen/arch
VT-d PI introduces a per-pCPU blocking list to track the blocked vCPU
on a given pCPU. Theoretically, there are 32K domain on single host,
128 vCPUs per domain. If all vCPUs are blocked on the same pCPU,
4M vCPUs are in the same list. Traversing this list consumes too
much time. More discussion can
On 24/05/2017 07:20, Jan Beulich wrote:
> I'm kind of disappointed that there was no visible attempt
> from Igor so far to help the situation.
Igor is out of the office at the moment, and besides, this thread of
problem is only 36h old at this point, which is a single working day in
this timezone.
>>> On 23.05.17 at 23:51, wrote:
> On 5/23/2017 4:46 PM, Boris Ostrovsky wrote:
>> On 05/23/2017 05:28 PM, Gary R Hook wrote:
>>> Signed-off-by: Gary R Hook
>>> ---
>>> xen/arch/x86/oprofile/nmi_int.c |4
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/xen/arch/x86/oprofile/n
On 05/24/2017 02:34 AM, Bart Van Assche wrote:
> Since the SCSI core zeroes driver-private command data, remove
> that code from the xen-scsifront driver.
>
> Signed-off-by: Bart Van Assche
> Cc: Juergen Gross
> Cc: xen-de...@lists.xenproject.org
> ---
> drivers/scsi/xen-scsifront.c | 1 -
> 1
>>> On 24.05.17 at 07:32, wrote:
>> -Original Message-
>> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of Hao,
>> Xudong
>> Sent: Tuesday, May 23, 2017 5:34 PM
>> To: Jan Beulich
>> Cc: Lars Kurth ; Julien Grall ;
>> George Dunlap ; Zhang, Haozhong
>> ; xen-devel@li
>>> On 24.05.17 at 00:25, wrote:
> On 05/23/2017 10:32 AM, Boris Ostrovsky wrote:
>> On 05/23/2017 10:05 AM, Jan Beulich wrote:
>>> Further changes may then
>>> be needed to the splitting of large pages (in p2m_next_level())
>>> depending on whether INVALID_MFN entries can make it there.
>> Let me
flight 109701 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/109701/
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. 109664
Tests which did n
flight 109697 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/109697/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 7 host-ping-check-xen fail REGR. vs. 109656
test-amd64-i386-lib
On 2017年05月24日 01:06, Anthony PERARD wrote:
> On Tue, May 23, 2017 at 08:16:25PM +0800, Lan Tianyu wrote:
>> On 2017年05月19日 20:04, Jan Beulich wrote:
>> On 19.05.17 at 13:16, wrote:
On Thu, May 18, 2017 at 01:32:59AM -0400, Lan Tianyu wrote:
> --- a/include/hw/i386/apic-msidef.h
>
Since the SCSI core zeroes driver-private command data, remove
that code from the xen-scsifront driver.
Signed-off-by: Bart Van Assche
Cc: Juergen Gross
Cc: xen-de...@lists.xenproject.org
---
drivers/scsi/xen-scsifront.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/scsi/xen-scsifr
When reading the priority value of a virtual interrupt, we were taking
the respective rank lock so far.
However for forwarded interrupts (Dom0 only so far) this may lead to a
deadlock with the following call chain:
- MMIO access to change the IRQ affinity, calling the ITARGETSR handler
- this handl
Target drivers must guarantee that struct se_cmd and struct se_tmr_req
exist as long as target_tmr_work() is in progress. Since the last
access by the LIO core is a call to .check_stop_free() and since the
Xen scsiback .check_stop_free() drops a reference to the TMF, it is
already guaranteed that t
This patch simplifies the implementation of the scsiback driver
but does not change its behavior.
Signed-off-by: Bart Van Assche
Cc: Juergen Gross
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: David Disseldorp
Cc: xen-de...@lists.xenproject.org
---
drivers/xen/xen-scsiback.c | 11 ---
scsiback_release_cmd() must not dereference se_cmd->se_tmr_req
because that memory is freed by target_free_cmd_mem() before
scsiback_release_cmd() is called. Fix this use-after-free by
inlining struct scsiback_tmr into struct vscsibk_pend.
Signed-off-by: Bart Van Assche
Cc: Juergen Gross
Cc: Chr
On 05/23/2017 10:32 AM, Boris Ostrovsky wrote:
> On 05/23/2017 10:05 AM, Jan Beulich wrote:
> On 23.05.17 at 15:40, wrote:
>>> And you haven't been able to reproduce this? I see this fail on two AMD
>>> systems (different processor families).
>> I didn't even have the time to try.
>>
>>> And t
On Mon, 15 May 2017, Punit Agrawal wrote:
> populate_physmap() calls alloc_heap_pages() per requested
> extent. alloc_heap_pages() invalidates the entire icache per
> extent. During domain creation, the icache invalidations can be deffered
> until all the extents have been allocated as there is no
On 05/23/2017 05:51 PM, Gary R Hook wrote:
> On 5/23/2017 4:46 PM, Boris Ostrovsky wrote:
>> On 05/23/2017 05:28 PM, Gary R Hook wrote:
>>> Signed-off-by: Gary R Hook
>>> ---
>>> xen/arch/x86/oprofile/nmi_int.c |4
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/xen/arch/x86/o
On 5/23/2017 4:46 PM, Boris Ostrovsky wrote:
On 05/23/2017 05:28 PM, Gary R Hook wrote:
Signed-off-by: Gary R Hook
---
xen/arch/x86/oprofile/nmi_int.c |4
1 file changed, 4 insertions(+)
diff --git a/xen/arch/x86/oprofile/nmi_int.c b/xen/arch/x86/oprofile/nmi_int.c
index 13534d4914
On 05/23/2017 05:28 PM, Gary R Hook wrote:
> Signed-off-by: Gary R Hook
> ---
> xen/arch/x86/oprofile/nmi_int.c |4
> 1 file changed, 4 insertions(+)
>
> diff --git a/xen/arch/x86/oprofile/nmi_int.c b/xen/arch/x86/oprofile/nmi_int.c
> index 13534d491405..5ad48c12e515 100644
> --- a/xen/a
On Mon, 15 May 2017, Punit Agrawal wrote:
> flush_page_to_ram() unconditionally drops the icache. In certain
> situations this leads to execessive icache flushes when
> flush_page_to_ram() ends up being repeatedly called in a loop.
>
> Introduce a parameter to allow callers of flush_page_to_ram()
get_host_initrd can return an invalid or null initrd. Do not set the
ramdisk option in the VM config file to an invalid value.
Signed-off-by: Stefano Stabellini
---
tests/busybox-pv | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tests/busybox-pv b/tests/busybox-pv
index
Ignore all cirros tests on ARM for now. Print a warning for PV tests,
which could work on ARM one day (HVM tests won't work any time soon,
given that there is no HVM builder type on ARM).
Do not exit 0 when we detect ARM in a test: it causes the whole raise to
exit. Return 0 instead.
Signed-off-b
We don't necessarely always want to guess and use the dom0 kernel and
initrd for tests. Introduce two options, TEST_KERNEL and TEST_INITRD,
that allow a user to manually specify which kernel and initrd to use.
Signed-off-by: Stefano Stabellini
---
defconfig | 8
lib/commo
Hi all,
this small patch series fixes a couple of issues with ./raise test and
makes tests work on ARM (actually just busybox-pv for now, the others
are disabled).
Stefano Stabellini (3):
raisin: introduce TEST_KERNEL and TEST_INITRD
raisin: check for invalid initrds
raisin/arm
Signed-off-by: Gary R Hook
---
xen/arch/x86/oprofile/nmi_int.c |4
1 file changed, 4 insertions(+)
diff --git a/xen/arch/x86/oprofile/nmi_int.c b/xen/arch/x86/oprofile/nmi_int.c
index 13534d491405..5ad48c12e515 100644
--- a/xen/arch/x86/oprofile/nmi_int.c
+++ b/xen/arch/x86/oprofile/nmi
This run is configured for baseline tests only.
flight 71417 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71417/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-amd64-libvirt 5 libvirt-buildfai
On Tue, 23 May 2017, Andrii Anisov wrote:
> Raisin is not functional as described [2]:
>
> root@salvator-x-domx:/raisin# ./raise test
> No config file found, copying default config
> [raisin] I don't know distro unknown. It might be missing packages.
> [raisin] I don't know distro
flight 109693 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/109693/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 107358
test-amd64-amd64-xl-q
On Tue, 23 May 2017, Julien Grall wrote:
> Both helpers access_ok and array_access_ok are not used on ARM. Remove
> them.
>
> Signed-off-by: Julien Grall
Reviewed-by: Stefano Stabellini
> ---
> xen/include/asm-arm/guest_access.h | 7 ---
> 1 file changed, 7 deletions(-)
>
> diff --git a/
On Tue, 23 May 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 23/05/17 00:48, Stefano Stabellini wrote:
> > On Fri, 19 May 2017, Stefano Stabellini wrote:
> > > On Thu, 11 May 2017, Andre Przywara wrote:
> > > > When LPIs get unmapped by a guest, they might still be in some LR of
> > > > some VCPU
In perl 5.14 in Massachusetts, this produces this message
/home/logs/logs/109694/test-amd64-amd64-examine Bad file descriptor at
./ts-examine-logs-save line 100.
Sadly this means there is no way to tell failure apart from end of
directory. This patch should be reverted when we have a fixed ver
flight 109700 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/109700/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 1c47fcd465a496fe1d1493f97da02cb6b07364f5
baseline version:
ovmf 3b2928b46987693caaaee
Roger Pau Monne writes ("[PATCH 5/7] osstest: introduce a FreeBSD build
script"):
> -my $path= "path_${part}dist";
> -logm("checking $k $path");
> -get_stashed($path, $r{$k});
> +if ("$part" eq "freebsd") {
> +foreach (qw(base kernel manifest image)) {
> +my $pa
On Tue, 23 May 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 22/05/17 23:19, Stefano Stabellini wrote:
> > On Tue, 16 May 2017, Julien Grall wrote:
> > > > @@ -436,8 +473,26 @@ static int __vgic_v3_rdistr_rd_mmio_write(struct
> > > > vcpu
> > > > *v, mmio_info_t *info,
> > > > switch ( gicr_
On Tue, 23 May 2017, Andre Przywara wrote:
> Hi,
>
> On 23/05/17 00:39, Stefano Stabellini wrote:
> > On Thu, 11 May 2017, Andre Przywara wrote:
> >> @@ -556,6 +583,93 @@ static int its_handle_mapd(struct virt_its *its,
> >> uint64_t *cmdptr)
> >> return ret;
> >> }
> >>
> >> +static int
On Tue, 23 May 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 22/05/17 23:32, Stefano Stabellini wrote:
> > On Thu, 11 May 2017, Andre Przywara wrote:
> > > +case VREG64(GITS_CWRITER):
> > > +if ( !vgic_reg64_check_access(info->dabt) ) goto bad_width;
> > > +
> > > +reg = its->
On Wed, 24 May 2017, Zhongze Liu wrote:
> Hi there,
>
> Thanks for your comments. They are all very insightful.
>
> Having read through the discussions so far, I can draw the
> following conclusions:
>
> 0. The syntax and semantics of the new config option should be more clearlly
> defined.
Hi there,
Thanks for your comments. They are all very insightful.
Having read through the discussions so far, I can draw the
following conclusions:
0. The syntax and semantics of the new config option should be more clearlly
defined. And this actually depends on the following:
1. If we're g
Hi,
On 17/05/17 18:45, Julien Grall wrote:
> Hi Andre,
>
> On 11/05/17 18:53, Andre Przywara wrote:
>> This introduces the ITS command handler for the CLEAR command, which
>> clears the pending state of an LPI.
>> This removes a not-yet injected, but already queued IRQ from a VCPU.
>> As read_itt
Hi,
On 16/05/17 14:03, Julien Grall wrote:
> Hi Andre,
>
> On 11/05/17 18:53, Andre Przywara wrote:
>> To let a guest know about the availability of virtual LPIs, set the
>> respective bits in the virtual GIC registers and let a guest control
>> the LPI enable bit.
>> Only report the LPI capabili
Hi,
On 17/05/17 17:17, Julien Grall wrote:
> Hi Andre,
>
> On 11/05/17 18:53, Andre Przywara wrote:
>> The INT command sets a given LPI identified by a DeviceID/EventID pair
>> as pending and thus triggers it to be injected.
>>
>> Signed-off-by: Andre Przywara
>> ---
>> xen/arch/arm/vgic-v3-its
Roger Pau Monne writes ("[PATCH 4/7] osstest: add a FreeBSD host install
recipe"):
> The installation is performed using the bsdinstall tool, which is
> part of the FreeBSD base system. The installer image is setup with
> the osstest ssh keys and sshd enabled by default, which allows the
> test ha
Roger Pau Monné writes ("Re: [Xen-devel] [OSSTEST PATCH 08/24] cs-hosts-list:
Support --suites"):
> I should add a --freebsd=... option.
Yes. Although currently my host examination uses only Linux and Xen.
Do you think there's any value in doing it with FreeBSD as well ?
Ian.
On Tue, May 23, 2017 at 08:16:25PM +0800, Lan Tianyu wrote:
> On 2017年05月19日 20:04, Jan Beulich wrote:
> On 19.05.17 at 13:16, wrote:
> >> On Thu, May 18, 2017 at 01:32:59AM -0400, Lan Tianyu wrote:
> >>> --- a/include/hw/i386/apic-msidef.h
> >>> +++ b/include/hw/i386/apic-msidef.h
> >>> @@ -
* Hardware:
Salvator-X board with Renesas R-Car H3 SoC (ARM64)
* Software:
XEN 4.9-rc6
System based on Renesas Yocto 2.19.0 BSP [1]
Linux kernel 4.9
* Guest operating systems:
The same system as dom0.
* Functionality tested:
xl create/restart/shutdown
Guest domain reboot from its console
PV NET
Both helpers access_ok and array_access_ok are not used on ARM. Remove
them.
Signed-off-by: Julien Grall
---
xen/include/asm-arm/guest_access.h | 7 ---
1 file changed, 7 deletions(-)
diff --git a/xen/include/asm-arm/guest_access.h
b/xen/include/asm-arm/guest_access.h
index 421bca5f36..251
Julien Grall writes ("Re: [Xen-devel] Xen 4.9 rc6"):
> On 23/05/17 10:24, M A Young wrote:
> > I had build problems with these two patches added (and before I added
> > them). It looks like at the stage in my build process where
> > make -j2 prefix=/usr tools
> > gets run it is running
> > make -C
On 05/23/17 17:02, Julien Grall wrote:
> Hi,
>
> On 23/05/17 15:12, Konrad Rzeszutek Wilk wrote:
The primary location for reporting bugs against the hypervisor and
associated bundled tools [...] is by posting to the xen-devel mailing
list (list info). Please tag your subject line wi
flight 109692 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/109692/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-xsm 13 saverestore-support-checkfail like 109637
test-armhf-armhf-libvirt 13 saveresto
Roger Pau Monne writes ("[PATCH 4/7] osstest: add a FreeBSD host install
recipe"):
> The installation is performed using the bsdinstall tool, which is
> part of the FreeBSD base system. The installer image is setup with
> the osstest ssh keys and sshd enabled by default, which allows the
> test ha
On 05/23/17 17:01, Jan Beulich wrote:
On 23.05.17 at 16:12, wrote:
>> On Thu, May 18, 2017 at 02:36:33PM +0200, Laszlo Ersek wrote:
>>> The situation is further hampered by the fact that Xen is (apparently)
>>> right at 4.9.0-rc5, so they likely won't commit Jan's hvmloader patch
>>> until Xe
flight 109690 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/109690/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-xsm 5 xen-build fail in 109679 REGR. vs. 109690
Tests which are fa
Dear John,
I would speak about XEN on ARM further.
Basically you need a passthrough in XEN terms in case you want a bus
initiator (i.e. DMA capable) device to be assigned to DomU.
For a passive device it's pretty enough to assign MMIO ranges and
interrupts using guest domain config. The pit
>>> On 23.05.17 at 16:12, wrote:
> The condition: if there is a space in the ring then wait for the producer
> to fill the ring also evaluates to true even if the ring if full. It
> leads to a deadlock where producer is waiting for consumer
> to consume the items and consumer is waiting for produc
On Mon, May 22, 2017 at 02:14:41PM -0700, Stefano Stabellini wrote:
> On Mon, 22 May 2017, Ian Jackson wrote:
> > Stefano Stabellini writes ("Re: Proposal to allow setting up shared memory
> > areas between VMs from xl config file"):
> > > In this scenario, she is going to write to the VM config f
This run is configured for baseline tests only.
flight 71414 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71414/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-amd64-libvirt 5 libvirt-buildfai
Hi,
On 23/05/17 15:12, Konrad Rzeszutek Wilk wrote:
The primary location for reporting bugs against the hypervisor and
associated bundled tools [...] is by posting to the xen-devel mailing
list (list info). Please tag your subject line with a '[BUG]' prefix.
Note that you do not need to be subsc
Roger Pau Monne writes ("[PATCH 3/7] osstest: fix regular expression used to
match buildjob in ts-build-check"):
> Current regular expression used to match the buildjob works correctly when the
> buildjob runvar has the buildjob format, but not when the format is
> _buildjob (the first match group
>>> On 23.05.17 at 16:12, wrote:
> On Thu, May 18, 2017 at 02:36:33PM +0200, Laszlo Ersek wrote:
>> The situation is further hampered by the fact that Xen is (apparently)
>> right at 4.9.0-rc5, so they likely won't commit Jan's hvmloader patch
>> until Xen 4.9 is out. This is a problem for a poten
Roger Pau Monne writes ("[PATCH 2/7] osstest: move known_hosts generation to
TestSupport"):
> This is equivalent to the already existing authorized_keys function, and
> generates the contents of the known_hosts file that should be installed on
> targets.
Acked-by: Ian Jackson
__
Roger Pau Monne writes ("[PATCH 1/7] osstest: make built_stash_file store a
path_ runvar for each file"):
> And introduce built_stash_debugfile in order the keep the previous behavior of
> built_stash_file.
Acked-by: Ian Jackson
___
Xen-devel mailing
Hi Stefano,
On 20/05/17 02:25, Stefano Stabellini wrote:
> On Thu, 11 May 2017, Andre Przywara wrote:
>> When LPIs get unmapped by a guest, they might still be in some LR of
>> some VCPU. Nevertheless we remove the corresponding pending_irq
>> (possibly freeing it), and detect this case (irq_to_pe
On 05/23/2017 10:05 AM, Jan Beulich wrote:
On 23.05.17 at 15:40, wrote:
>> And you haven't been able to reproduce this? I see this fail on two AMD
>> systems (different processor families).
> I didn't even have the time to try.
>
>> And this:
>>
>> --- a/xen/arch/x86/mm/p2m.c
>> +++ b/xen/arc
On Thu, May 18, 2017 at 12:01:18PM +0100, Ian Jackson wrote:
> Signed-off-by: Ian Jackson
> ---
> cs-hosts-list | 16
> 1 file changed, 16 insertions(+)
>
> diff --git a/cs-hosts-list b/cs-hosts-list
> index 92f44ee..9b82d51 100755
> --- a/cs-hosts-list
> +++ b/cs-hosts-list
> @
On Tue, May 23, 2017 at 02:54:16PM +0100, Ian Jackson wrote:
> Roger Pau Monné writes ("Re: [Xen-devel] [OSSTEST PATCH 06/24] cs-hosts-list:
> New utility"):
> > On Thu, May 18, 2017 at 12:01:16PM +0100, Ian Jackson wrote:
> > > +foreach my $flag (grep { length} split /\,/, $flags) {
> > > +$q
The condition: if there is a space in the ring then wait for the producer
to fill the ring also evaluates to true even if the ring if full. It
leads to a deadlock where producer is waiting for consumer
to consume the items and consumer is waiting for producer to fill the ring.
Fix for the issue: c
Adding Jan (autor of patch) and Julien (Xen release manager);
Pls see below.
On Thu, May 18, 2017 at 02:36:33PM +0200, Laszlo Ersek wrote:
> On 05/16/17 06:20, Gary Lin wrote:
> > On Mon, May 15, 2017 at 05:40:59PM -0700, Jordan Justen wrote:
> >> On 2017-05-12 01:40:34, Laszlo Ersek wrote:
> >>>
>>> On 23.05.17 at 15:40, wrote:
> And you haven't been able to reproduce this? I see this fail on two AMD
> systems (different processor families).
I didn't even have the time to try.
> And this:
>
> --- a/xen/arch/x86/mm/p2m.c
> +++ b/xen/arch/x86/mm/p2m.c
> @@ -560,7 +560,7 @@ int p2m_set_en
On Thu, May 18, 2017 at 12:01:13PM +0100, Ian Jackson wrote:
> This spuriously prints $!. It's still a poor message.
>
> Signed-off-by: Ian Jackson
> ---
> cs-flight-create | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/cs-flight-create b/cs-flight-create
> index a412
Roger Pau Monné writes ("Re: [Xen-devel] [OSSTEST PATCH 06/24] cs-hosts-list:
New utility"):
> On Thu, May 18, 2017 at 12:01:16PM +0100, Ian Jackson wrote:
> > +foreach my $flag (grep { length} split /\,/, $flags) {
> > +$qtxt.= < > + AND EXISTS (SELECT 1 FROM HOSTFLAGS f
> > +
Roger Pau Monné writes ("Re: [Xen-devel] [OSSTEST PATCH 05/24] tcmd: Work
around ssh bug with `ssh host ""'"):
> On Thu, May 18, 2017 at 12:01:15PM +0100, Ian Jackson wrote:
> > This runs an interactive shell session on the host, rathern than
> > running `sh -c ""' on it.
> >
> > Evidently ssh ch
Current regular expression used to match the buildjob works correctly when the
buildjob runvar has the buildjob format, but not when the format is
_buildjob (the first match group is empty in this case). Change it so
that it works for both formats.
Signed-off-by: Roger Pau Monné
---
ts-build-che
In order to generate the FreeBSD installer image and the install media.
The install sets are the vanilla ones generated by the 'ftp' release target.
The installer image is handcrafted based on the filesystem created by the
'bootonly' target, which is then populated with the ssh host keys, and setu
And introduce built_stash_debugfile in order the keep the previous behavior of
built_stash_file.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
---
Osstest/TestSupport.pm | 14 --
ts-kernel-build| 4 ++--
ts-xen-build | 8
3 files changed, 18 inserti
At the moment this flight only contains a build-amd64-freebsd and
build-amd64-freebsd-again jobs, because that's all osstest can do with FreeBSD
now.
This allows testing FreeBSD specific functionality without generating a
fully-fledged flight, that also includes the Linux jobs.
Signed-off-by: Rog
The installation is performed using the bsdinstall tool, which is part of the
FreeBSD base system. The installer image is setup with the osstest ssh keys and
sshd enabled by default, which allows the test harness to just ssh into the
box, create the install config file and launch the scripted insta
Hello,
This series introduces initial FreeBSD host support to osstest. The current
series allow installing a bare-metal host with FreeBSD and building FreeBSD on
it in order to generate new install media that can be fed into the installer
script.
This is still very limited, since no Xen testing i
This requires changes in several places in order to accommodate the FreeBSD
build, which although it's a build job, it doesn't have the same set of
dependencies as the current builds.
First, a new build recipe is added to sg-run-job, and accordingly sg-run-job is
also made aware about the differen
This is equivalent to the already existing authorized_keys function, and
generates the contents of the known_hosts file that should be installed on
targets.
Signed-off-by: Roger Pau Monné
---
Osstest/Debian.pm | 36 +---
Osstest/TestSupport.pm | 41 ++
Jan Beulich writes ("Re: [Xen-devel] [PATCH] XenBus: Don't wait for producer to
fill the ring if the ring"):
> On 23.05.17 at 14:42, wrote:
> > Thanks, and sorry to tetch.
[ much deleted because I really don't see much point me me arguing
this further ]
> While I can vaguely guess what you me
On 05/23/2017 09:17 AM, Jan Beulich wrote:
On 23.05.17 at 15:00, wrote:
>> (d1) Testing HVM environment:
>> (XEN) d1v0 Triple fault - invoking HVM shutdown action 1
>> (XEN) *** Dumping Dom1 vcpu#0 state: ***
>> (XEN) [ Xen-4.9-rc x86_64 debug=y Tainted: C ]
>> (XEN) CPU:11
On 23/05/17 14:35, Iurii Mykhalskyi wrote:
Hi Pranay,
As I say in my previous e-mail:
"I'm not familiar with QEMU, but in general case - you can't just take
image (for example RCAR-H3) and run it inside QEMU - a some things might
be different - uart, gic, timer, etc.
And i'm not sure about s
Hi Pranay,
As I say in my previous e-mail:
"I'm not familiar with QEMU, but in general case - you can't just take
image (for example RCAR-H3) and run it inside QEMU - a some things might be
different - uart, gic, timer, etc.
And i'm not sure about support of HW virtualization on QEMU - looks lik
Hello,
On 23/05/17 14:18, Jan Beulich wrote:
On 23.05.17 at 14:53, wrote:
Thanks for the reply. we are using renesas rcar h3 board. Does it supports?
A general rule is to provide as much as details on your mail so we can
provide the best feedback.
In this case, I don't fully understand wh
On Thu, May 18, 2017 at 12:01:11PM +0100, Ian Jackson wrote:
> Any flight eventually blessed `adhoc' is supposed to contain, in the
> db, accurate information corresponding to a real clean run. This is
> not appropriate for playing about.
>
> Using `play' usefully disables a number of safety catc
On Thu, May 18, 2017 at 12:01:16PM +0100, Ian Jackson wrote:
> No callers yet.
>
> Signed-off-by: Ian Jackson
> ---
> cs-hosts-list | 64
> +++
> 1 file changed, 64 insertions(+)
> create mode 100755 cs-hosts-list
>
> diff --git a/cs-hos
>>> On 23.05.17 at 14:53, wrote:
> Thanks for the reply. we are using renesas rcar h3 board. Does it supports?
I have no idea, I'm an x86 person.
Also please don't top-post.
Jan
> On Tuesday, May 23, 2017, Jan Beulich wrote:
>
>> >>> On 23.05.17 at 11:38, >
>> wrote:
>> > Is it possible to g
On Thu, May 18, 2017 at 12:01:15PM +0100, Ian Jackson wrote:
> This runs an interactive shell session on the host, rathern than
> running `sh -c ""' on it.
>
> Evidently ssh checks for the presence of a command line specification
> after (foolishly, but now historically unavoidably) concatenating
>>> On 23.05.17 at 15:00, wrote:
> (d1) Testing HVM environment:
> (XEN) d1v0 Triple fault - invoking HVM shutdown action 1
> (XEN) *** Dumping Dom1 vcpu#0 state: ***
> (XEN) [ Xen-4.9-rc x86_64 debug=y Tainted: C ]
> (XEN) CPU:11
> (XEN) RIP:0018:[<0010815c>]
> (XEN
>>> On 23.05.17 at 14:42, wrote:
> Jan Beulich writes ("Re: [Xen-devel] [PATCH] XenBus: Don't wait for producer
> to fill the ring if the ring"):
>> On 17.05.17 at 16:57, wrote:
>> > --- a/tools/firmware/hvmloader/xenbus.c
>> > +++ b/tools/firmware/hvmloader/xenbus.c
>> > @@ -141,7 +141,18 @@ st
On Mon, May 22, 2017 at 04:45:20PM +0100, Ian Jackson wrote:
> Due to an oversight, this was not plumbed into sg-run-job.
>
> Signed-off-by: Ian Jackson
Acked-by: Roger Pau Monné
Roger.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://list
On Mon, May 22, 2017 at 04:45:21PM +0100, Ian Jackson wrote:
> I ran a special report[1] to see what to expect and:
>
>Tests which did not succeed and are blocking,
>including tests which could not be run:
> test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR.
>
On 05/23/2017 04:07 AM, Jan Beulich wrote:
On 22.05.17 at 20:01, wrote:
>> On 05/10/2017 07:13 AM, Igor Druzhinin wrote:
>>> The same set of functions is used to set as well as to clean
>>> P2M entries, except that for clean operations INVALID_MFN (~0UL)
>>> is passed as a parameter. Unfortun
Thanks for the reply. we are using renesas rcar h3 board. Does it supports?
On Tuesday, May 23, 2017, Jan Beulich wrote:
> >>> On 23.05.17 at 11:38, >
> wrote:
> > Is it possible to give each channels of uart to different guests via pass
> > through mechanism?
>
> If each channel is represented
>>> On 27.04.17 at 16:35, wrote:
> +#define REGISTER_VPCI_INIT(f, p)\
> + static const struct vpci_register_init\
> + x##_entry __used_section(".data.vpci") = {\
> +.init = f,
>>> On 27.04.17 at 16:35, wrote:
> Add traps to each capability PCI_CAP_LIST_NEXT field in order to mask them on
> request.
>
> All capabilities from the device are fetched and stored in an internal list,
> that's later used in order to return the next capability to the guest. Note
> that this on
flight 109695 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/109695/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 3b2928b46987693caaaeefbb7b799d1e1de803c0
baseline version:
ovmf ac63e9392e7aa3791a4ea
1 - 100 of 130 matches
Mail list logo
