On 17.12.20 08:49, Jan Beulich wrote:
On 16.12.2020 18:52, Dario Faggioli wrote:
On Wed, 2020-12-09 at 17:09 +0100, Juergen Gross wrote:
When moving a domain between cpupools with different scheduling
granularity the sched_units of the domain need to be adjusted.
Do that by allocating new
On 16.12.2020 18:52, Dario Faggioli wrote:
> On Wed, 2020-12-09 at 17:09 +0100, Juergen Gross wrote:
>> When moving a domain between cpupools with different scheduling
>> granularity the sched_units of the domain need to be adjusted.
>>
>> Do that by allocating new sched_units and throwing away
On 17.12.2020 02:51, boris.ostrov...@oracle.com wrote:
>
> On 11/17/20 3:12 AM, Jan Beulich wrote:
>> On 16.11.2020 22:57, Cheyenne Wills wrote:
>>> Running Xen with XSA-351 is causing Solaris 11 systems to panic during
>>> boot. The panic screen is showing the failure to be coming from
>>>
flight 157597 xen-4.13-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157597/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs.
157135
Tests
flight 157621 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157621/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
flight 157594 xen-4.12-testing real [real]
flight 157623 xen-4.12-testing real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/157594/
http://logs.test-lab.xenproject.org/osstest/logs/157623/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could
On Wed, 16 Dec 2020, Andrew Cooper wrote:
> On 16/12/2020 14:14, Jason Andryuk wrote:
> > On Tue, Dec 15, 2020 at 5:22 PM Chris Rogers wrote:
> >> Hopefully I can provide a little more context. Here is a link to the
> >> patch:
> >>
> >>
On Tue, 15 Dec 2020, Stefano Stabellini wrote:
> Hi all,
>
> I am building Xen tools for ARM32 using qemu-user. I am getting the
> following error building tools/flask. Everything else works fine. It is
> worth noting that make -j1 works fine, it is only make -j4 that fails.
>
> I played with
On 11/17/20 3:12 AM, Jan Beulich wrote:
> On 16.11.2020 22:57, Cheyenne Wills wrote:
>> Running Xen with XSA-351 is causing Solaris 11 systems to panic during
>> boot. The panic screen is showing the failure to be coming from
>> "unix:rdmsr". The panic occurs with existing guests (booting off
flight 157573 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157573/
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
flight 157568 xen-unstable real [real]
flight 157614 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/157568/
http://logs.test-lab.xenproject.org/osstest/logs/157614/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
flight 157611 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157611/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
flight 157569 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157569/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-vhd 19 guest-start/debian.repeat fail REGR. vs. 152631
flight 157571 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157571/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 157345
The pull request you sent on Tue, 15 Dec 2020 13:26:06 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.11-rc1-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7acfd4274e26e05a4f12ad31bf331fef11ebc6a3
Thank you!
--
Deet-doot-dot,
On Tue, 15 Dec 2020, Elliott Mitchell wrote:
> On Tue, Dec 15, 2020 at 08:36:34AM -0800, Stefano Stabellini wrote:
> > On Mon, 14 Dec 2020, Elliott Mitchell wrote:
> > > The available examples seem geared towards Linux DomUs. I'm looking at a
> > > FreeBSD installation image and it appears to
Am 16.12.2020 um 15:55 hat Sergio Lopez geschrieben:
> On Wed, Dec 16, 2020 at 01:35:14PM +0100, Kevin Wolf wrote:
> > Am 15.12.2020 um 18:23 hat Sergio Lopez geschrieben:
> > > On Tue, Dec 15, 2020 at 04:01:19PM +0100, Kevin Wolf wrote:
> > > > Am 15.12.2020 um 14:15 hat Sergio Lopez geschrieben:
flight 157609 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157609/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 157560
Tests which
flight 157593 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157593/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 151777
build-arm64-libvirt
On Wed, Dec 16, 2020 at 10:43:57AM +, Wei Liu wrote:
> Paul, are you able to cook up a patch today? If not I will revert the
> offending patch(es).
>
I've reverted the offending 8 patches for now.
Wei.
On Wed, Dec 16, 2020 at 10:56:05AM -0600, Josh Poimboeuf wrote:
> On Wed, Dec 16, 2020 at 09:40:59AM +0100, Peter Zijlstra wrote:
> > > Could we make it easier by caching the shared
> > > per-alt-group CFI state somewhere along the way?
> >
> > Yes, but when I tried it grew the code required.
On Wed, 2020-12-09 at 17:09 +0100, Juergen Gross wrote:
> When moving a domain between cpupools with different scheduling
> granularity the sched_units of the domain need to be adjusted.
>
> Do that by allocating new sched_units and throwing away the old ones
> in sched_move_domain().
>
>
On 16.12.20 17:36, Jan Beulich wrote:
On 16.12.2020 17:24, Jürgen Groß wrote:
On 16.12.20 17:16, Jan Beulich wrote:
On 09.12.2020 17:09, Juergen Gross wrote:
In order to better support resource allocation and locking for dynamic
hypfs nodes add enter() and exit() callbacks to struct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory CVE-2020-29570 / XSA-358
version 5
FIFO event channels control block related ordering
UPDATES IN VERSION 5
"Unstable" patch updated (needed
On Wed, Dec 16, 2020 at 09:40:59AM +0100, Peter Zijlstra wrote:
> > So much algorithm.
>
> :-)
>
> It's not really hard, but it has a few pesky details (as always).
It really hurt my brain to look at it.
> > Could we make it easier by caching the shared
> > per-alt-group CFI state somewhere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory CVE-2020-29481 / XSA-322
version 5
Xenstore: new domains inheriting existing node permissions
UPDATES IN VERSION 5
Fix deployment info to refer to
On 16.12.2020 17:24, Jürgen Groß wrote:
> On 16.12.20 17:16, Jan Beulich wrote:
>> On 09.12.2020 17:09, Juergen Gross wrote:
>>> In order to better support resource allocation and locking for dynamic
>>> hypfs nodes add enter() and exit() callbacks to struct hypfs_funcs.
>>>
>>> The enter()
On 16.12.2020 17:17, Jürgen Groß wrote:
> On 16.12.20 17:08, Jan Beulich wrote:
>> On 09.12.2020 17:09, Juergen Gross wrote:
>>> --- a/xen/include/xen/guest_access.h
>>> +++ b/xen/include/xen/guest_access.h
>>> @@ -26,6 +26,11 @@
>>> type *_x = (hnd).p; \
>>>
On 16.12.20 17:16, Jan Beulich wrote:
On 09.12.2020 17:09, Juergen Gross wrote:
In order to better support resource allocation and locking for dynamic
hypfs nodes add enter() and exit() callbacks to struct hypfs_funcs.
The enter() callback is called when entering a node during hypfs user
On 16.12.20 17:08, Jan Beulich wrote:
On 09.12.2020 17:09, Juergen Gross wrote:
--- a/xen/include/xen/guest_access.h
+++ b/xen/include/xen/guest_access.h
@@ -26,6 +26,11 @@
type *_x = (hnd).p; \
(XEN_GUEST_HANDLE_PARAM(type)) { _x }; \
})
+/* Same for
On 09.12.2020 17:09, Juergen Gross wrote:
> In order to better support resource allocation and locking for dynamic
> hypfs nodes add enter() and exit() callbacks to struct hypfs_funcs.
>
> The enter() callback is called when entering a node during hypfs user
> actions (traversing, reading or
On 09.12.2020 17:09, Juergen Gross wrote:
> --- a/xen/include/xen/guest_access.h
> +++ b/xen/include/xen/guest_access.h
> @@ -26,6 +26,11 @@
> type *_x = (hnd).p; \
> (XEN_GUEST_HANDLE_PARAM(type)) { _x }; \
> })
> +/* Same for casting to a const type. */
>
flight 157606 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157606/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 157560
Tests which
On 16.12.20 15:08, Jason Andryuk wrote:
commit bfda93aee0ec ("xen: Kconfig: nest Xen guest options")
accidentally re-added X86_64 as a dependency to XEN_512GB. It was
originally removed in commit a13f2ef168cb ("x86/xen: remove 32-bit Xen
PV guest support"). Remove it again.
Fixes:
On Wed, Dec 16, 2020 at 01:35:14PM +0100, Kevin Wolf wrote:
> Am 15.12.2020 um 18:23 hat Sergio Lopez geschrieben:
> > On Tue, Dec 15, 2020 at 04:01:19PM +0100, Kevin Wolf wrote:
> > > Am 15.12.2020 um 14:15 hat Sergio Lopez geschrieben:
> > > > On Tue, Dec 15, 2020 at 01:12:33PM +0100, Kevin Wolf
On 16/12/2020 14:14, Jason Andryuk wrote:
> On Tue, Dec 15, 2020 at 5:22 PM Chris Rogers wrote:
>> Hopefully I can provide a little more context. Here is a link to the patch:
>>
>> https://github.com/OpenXT/xenclient-oe/blob/master/recipes-extended/xen/files/libxl-fix-reboot.patch
>>
>> The
On Tue, Dec 15, 2020 at 5:22 PM Chris Rogers wrote:
>
> Hopefully I can provide a little more context. Here is a link to the patch:
>
> https://github.com/OpenXT/xenclient-oe/blob/master/recipes-extended/xen/files/libxl-fix-reboot.patch
>
> The patch is a bit mis-named. It does not implement
>
commit bfda93aee0ec ("xen: Kconfig: nest Xen guest options")
accidentally re-added X86_64 as a dependency to XEN_512GB. It was
originally removed in commit a13f2ef168cb ("x86/xen: remove 32-bit Xen
PV guest support"). Remove it again.
Fixes: bfda93aee0ec ("xen: Kconfig: nest Xen guest options")
On 16.12.2020 13:19, Liwei wrote:
> On Wed, 16 Dec 2020 at 16:12, Jan Beulich wrote:
>> On 15.12.2020 20:08, Liwei wrote:
>>> Hi list,
>>> This is a reply to the thread of the same title (linked here:
>>> https://www.mail-archive.com/xen-devel@lists.xenproject.org/msg84916.html
>>> ) which I
flight 157566 xen-4.11-testing real [real]
flight 157605 xen-4.11-testing real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/157566/
http://logs.test-lab.xenproject.org/osstest/logs/157605/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
Am 15.12.2020 um 18:23 hat Sergio Lopez geschrieben:
> On Tue, Dec 15, 2020 at 04:01:19PM +0100, Kevin Wolf wrote:
> > Am 15.12.2020 um 14:15 hat Sergio Lopez geschrieben:
> > > On Tue, Dec 15, 2020 at 01:12:33PM +0100, Kevin Wolf wrote:
> > > > Am 14.12.2020 um 18:05 hat Sergio Lopez geschrieben:
Hi Jan,
Response inline...
Liwei
On Wed, 16 Dec 2020 at 16:12, Jan Beulich wrote:
>
> On 15.12.2020 20:08, Liwei wrote:
> > Hi list,
> > This is a reply to the thread of the same title (linked here:
> > https://www.mail-archive.com/xen-devel@lists.xenproject.org/msg84916.html
> > )
flight 157600 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157600/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 157560
Tests which
On 16.12.20 12:22, Andrew Cooper wrote:
On 16/12/2020 06:06, Jürgen Groß wrote:
On 15.12.20 19:09, Andrew Cooper wrote:
Additionally, something in core.c should check for unknown flags and
reject them them with EINVAL. It was buggy that this wasn't done
before, and really needs to be
On 16/12/2020 06:06, Jürgen Groß wrote:
> On 15.12.20 19:09, Andrew Cooper wrote:
>>
>> Additionally, something in core.c should check for unknown flags and
>> reject them them with EINVAL. It was buggy that this wasn't done
>> before, and really needs to be implemented before we start having
Paul, are you able to cook up a patch today? If not I will revert the
offending patch(es).
Wei.
On Wed, Dec 16, 2020 at 10:17:29AM +, Andrew Cooper wrote:
> On 16/12/2020 02:27, osstest service owner wrote:
> > branch xen-unstable-smoke
> > xenbranch xen-unstable-smoke
> > job
On 16/12/2020 02:27, osstest service owner wrote:
> branch xen-unstable-smoke
> xenbranch xen-unstable-smoke
> job build-amd64-libvirt
> testid libvirt-build
>
> Tree: libvirt git://xenbits.xen.org/libvirt.git
> Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git
> Tree: qemu
flight 157565 xen-4.10-testing real [real]
flight 157601 xen-4.10-testing real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/157565/
http://logs.test-lab.xenproject.org/osstest/logs/157601/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
flight 157602 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157602/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 904148ecb4a59d4c8375d8e8d38117b8605e10ac
baseline version:
xen
On Tue, Dec 15, 2020 at 06:38:02PM -0600, Josh Poimboeuf wrote:
> On Tue, Dec 15, 2020 at 03:54:08PM +0100, Peter Zijlstra wrote:
> > The problem is that a single instance of unwind information (ORC) must
> > capture and correctly unwind all alternatives. Since the trivially
> > correct mandate is
flight 157598 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/157598/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 157560
Tests which
On 15.12.20 21:59, Andrew Cooper wrote:
On 15/12/2020 11:10, Juergen Gross wrote:
In case a process waits for any Xenstore action in the xenbus driver
it should be interruptible by signals.
Signed-off-by: Juergen Gross
---
V2:
- don't special case SIGKILL as libxenstore is handling -EINTR
On 15.12.2020 20:08, Liwei wrote:
> Hi list,
> This is a reply to the thread of the same title (linked here:
> https://www.mail-archive.com/xen-devel@lists.xenproject.org/msg84916.html
> ) which I could not reply to because I receive this list by digest.
>
> I'm unclear if this is exactly
53 matches
Mail list logo