flight 158787 xen-unstable real [real]
flight 158808 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158787/
http://logs.test-lab.xenproject.org/osstest/logs/158808/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd6
flight 158805 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158805/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
On Thu, Jan 28, 2021 at 12:08:02PM +0100, Roger Pau Monné wrote:
> [...]
> Also, the qemu-ifup script doesn't seem to be part of the NetBSD
> scripts that are upstream, is this something carried by the NetBSD
> package?
Actually, the script is part of qemu-xen-traditional:
tools/qemu-xen-tradition
On Thu, Jan 28, 2021 at 11:39:03AM +, Ian Jackson wrote:
> [...]
> Taking a step back, I think this series is very close to going in, if
> not actually ready. Do you have a git branch version of this ?
Actually no. I'm not used to git, and I find it quite hard to use
(and is a large part of t
flight 158795 qemu-mainline real [real]
flight 158814 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158795/
http://logs.test-lab.xenproject.org/osstest/logs/158814/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
From: Tamas K Lengyel
Allow resetting the vmtrace buffer in response to a vm_event. This can be used
to optimize a use-case where detecting a looped vmtrace buffer is important.
Signed-off-by: Tamas K Lengyel
---
This is a last minute addition to the series "acquire_resource size and
external I
On 30.1.2021 3.42, Stefano Stabellini wrote:
On Wed, 27 Jan 2021, Stefano Stabellini wrote:
FYI I have just ordered a micro HDMI cable so I might be able to provide
more useful feedback in the following days.
What did you use to setup the graphic environment? Is it Ubuntu or
Raspbian? I am
flight 158796 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158796/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-dom0pvh-xl-intel 14 guest-start fail REGR. vs. 158387
test-amd64-amd64-dom0
On 29.1.2021 20.50, Julien Grall wrote:
Hi,
@Jukka, would it be possible to at least configure your client to quote
with '>'? This would make easier to understand who wrote what
(tabulation is not great for that).
If you are using gmail, then configuring it to send it as plain text
shoul
Hi,
On 30/01/2021 13:44, Jukka Kaartinen wrote:
On 30.1.2021 3.42, Stefano Stabellini wrote:
On Wed, 27 Jan 2021, Stefano Stabellini wrote:
FYI I have just ordered a micro HDMI cable so I might be able to provide
more useful feedback in the following days.
What did you use to setup the gra
Hi Jukka,
On 30/01/2021 13:53, Jukka Kaartinen wrote:
On 29.1.2021 20.50, Julien Grall wrote:
Hi,
@Jukka, would it be possible to at least configure your client to
quote with '>'? This would make easier to understand who wrote what
(tabulation is not great for that).
If you are using gma
From: Julien Grall
Xen is heavily relying on the DCE stage to remove unused code so the
linker doesn't throw an error because a function is not implemented
yet we defined a prototype for it.
On some GCC version (such as 9.4 provided by Debian sid), the compiler
will DCE stage will not managed to
On Fri, Jan 29, 2021 at 01:22:15PM +0100, Roger Pau Monne wrote:
> commit ef3a575baf53571dc405ee4028e26f50856898e7 upstream.
>
Now queued up, thanks.
greg k-h
flight 158802 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158802/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ws16-amd64 7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
On Fri, 2021-01-29 at 09:08 +0100, Anders Törnqvist wrote:
> On 1/26/21 11:31 PM, Dario Faggioli wrote:
> > Thanks again for letting us see these logs.
>
> Thanks for the attention to this :-)
>
> Any ideas for how to solve it?
>
So, you're up for testing patches, right?
How about applying thes
#define _GNU_SOURCE to get for asprintf() prototype on Linux.
Harmless on NetBSD.
Signed-off-by: Manuel Bouyer
---
tools/xenpmd/xenpmd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/xenpmd/xenpmd.c b/tools/xenpmd/xenpmd.c
index e432aad856..8e783181e1 100644
--- a/tools/xenpmd/xenpmd
On NetBSD, d_name is larger than 256, so file_name[284] may not be large
enough (and gcc emits a format-truncation error).
Use asprintf() instead of snprintf() on a static on-stack buffer.
Signed-off-by: Manuel Bouyer
Reviewed-by: Ian Jackson
---
tools/xenpmd/xenpmd.c | 8
1 file chan
On Fri, Jan 29, 2021 at 11:05:24PM +, Andrew Cooper wrote:
> On 29/01/2021 23:01, Manuel Bouyer wrote:
> > On Fri, Jan 29, 2021 at 10:51:14PM +, Andrew Cooper wrote:
> >> Given the freeze, and discussions on IRC, I have committed most of this
> >> series.
> > thanks
> >
> >> This particular
On Fri, Jan 29, 2021 at 11:28 PM Jürgen Groß wrote:
>
> On 29.01.21 21:12, Roman Shaposhnik wrote:
> > Hi!
> >
> > I'm trying to see how much mileage I can get out of
> > crash(1) 7.2.8 (based on gdb 7.6) when it comes to
> > analyzing crash dumps taken via xl dump-core (this
> > is all on x86_64
flight 158811 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158811/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 158787
test-amd64-amd64-xl-qemuu-ws16-amd64
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-dom0pvh-xl-intel
testid guest-start
Tree: linux
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.
Pass bridge name to qemu as command line option
When starting qemu, set an environnement variable XEN_DOMAIN_ID,
to be used by qemu helper scripts
The only functional difference of using the br parameter is that the
bridge name gets passed to the QEMU script.
NetBSD doesn't have the ioctl to rename
Document that on NetBSD, the tap interface will be configured by the
qemu-ifup script. Document the arguments, and XEN_DOMAIN_ID environnement
variable.
---
docs/man/xl-network-configuration.5.pod | 4
1 file changed, 4 insertions(+)
diff --git a/docs/man/xl-network-configuration.5.pod
b/do
On Fri, Jan 29, 2021 at 03:52:14PM +0100, Roger Pau Monné wrote:
>
> Right, but the default script provided will do bridging mode only, and
> even if you add 'script=vif-ip' to the network configuration line it
> won't do what you expect. Instead it will try to add the tap network
> interface to t
On Fri, Jan 29, 2021 at 03:16:52PM +0100, Jürgen Groß wrote:
> On 29.01.21 15:13, Michael Labriola wrote:
> > On Fri, Jan 29, 2021 at 12:26 AM Jürgen Groß wrote:
> > > If the buggy patch has been put into stable this Fixes: tag should
> > > result in the fix being put into the same stable branches
On Tue, Sep 29, 2020 at 05:27:48PM +0200, Jürgen Groß wrote:
> On 29.09.20 17:16, Marek Marczykowski-Górecki wrote:
> > On Tue, Sep 29, 2020 at 05:07:11PM +0200, Jürgen Groß wrote:
> > > On 29.09.20 16:27, Marek Marczykowski-Górecki wrote:
> > > > On Mon, Mar 23, 2020 at 01:09:49AM +0100, Marek Mar
flight 158816 qemu-mainline real [real]
flight 158836 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158816/
http://logs.test-lab.xenproject.org/osstest/logs/158836/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
flight 158818 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158818/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-dom0pvh-xl-intel 14 guest-start fail REGR. vs. 158387
test-amd64-amd64-dom0
On 30.01.21 19:53, Roman Shaposhnik wrote:
On Fri, Jan 29, 2021 at 11:28 PM Jürgen Groß wrote:
On 29.01.21 21:12, Roman Shaposhnik wrote:
Hi!
I'm trying to see how much mileage I can get out of
crash(1) 7.2.8 (based on gdb 7.6) when it comes to
analyzing crash dumps taken via xl dump-core (t
29 matches
Mail list logo