Re: Informal voting proposal

On Nov 6, 2023, at 13:53, Kelly Choi wrote: >  > Hi all, > > As an open-source community, there will always be differences of opinion in > approaches and the way we think. It is imperative, however, that we view this > diversity as a source of strength rather than a hindrance. > > Recent

Re: [RFC PATCH] xen/arm: Rebranding dom0less feature

On Jul 8, 2023, at 03:29, Luca Fancellu wrote: >  Instead, the use case configurations should themselves be describable. >>> >>> Thanks Christopher, Daniel and all! >>> >>> So if I understand correctly, you are in favor if renaming Dom0less to >>> Hyperlaunch throughout the Xen

Re: [RFC PATCH] xen/arm: Rebranding dom0less feature

On Jul 7, 2023, at 21:17, Stefano Stabellini wrote: > > On Fri, 7 Jul 2023, Christopher Clark wrote: >> +CC openxt, Jason, Marek >> >> On Fri, Jul 7, 2023 at 2:06 PM Christopher Clark >> wrote: >> +CC members of the Hyperlaunch Working Group + participants on earlier >> Hyperlaunch

Re: [RFC PATCH] xen/arm: Rebranding dom0less feature

Hi Luca, On Jun 30, 2023, at 05:12, Luca Fancellu wrote: > > The "dom0less" feature was intended to be the feature where a domU > domain could be launched without the control domain (Dom0) > intervention, however the name seems to suggest that Dom0 cannot > be part of the configuration, while

Re: How to isolate vital part of a host with the Xen Hypervisor?

On Aug 21, 2022, at 1:36 AM, Jason Long wrote: > > Hello, > Is it possible to install the Xen Hypervisor for just isolate my host OS and > disable its Virtualization features (Install guest OS)? You can often disable hardware virtualization via a UEFI/BIOS setting. Even if hardware

Re: [PATCH] xen-pcifront: Handle missed Connected state

On Aug 29, 2022, at 11:16 AM, Jason Andryuk wrote: > > An HVM guest with linux stubdom and 2 PCI devices failed to start as > libxl timed out waiting for the PCI devices to be added. It happens > intermittently but with some regularity. libxl wrote the two xenstore > entries for the devices,

Re: PROPOSAL: Delete www-archive.xenproject.org

On May 12, 2022, at 11:55 AM, George Dunlap wrote: >  >> On Apr 14, 2022, at 4:49 PM, George Dunlap wrote: >> >> I’m pretty sure www-archive.xenproject.org is at least N-2 for websites; >> last updated nearly 9 years ago. As far as I can tell there’s nothing >> terribly interesting stored

[events] BigBlueButton enhancements

 LPC and LF have issued an RFQ that includes upstream usability enhancements for BBB and integration with Matrix chat. Some feature gaps (page 7, HTML5 client) may be familiar to Xen Summit participants. If Xen Summit has additional enhancement requests for 2022, these could be coordinated

Re: [PATCH v2 01/13] docs: Warn about incomplete vtpmmgr TPM 2.0 support

On May 6, 2021, at 10:00, Jason Andryuk wrote: > The vtpmmgr TPM 2.0 support is incomplete. Add a warning about that to > the documentation so others don't have to work through discovering it is > broken. > > Signed-off-by: Jason Andryuk > Acked-by: Andrew Cooper > --- >

Re: [openxt-dev] VirtIO-Argo initial development proposal

On Dec 17, 2020, at 07:13, Jean-Philippe Ouellet wrote: > On Wed, Dec 16, 2020 at 2:37 PM Christopher Clark > wrote: >> Hi all, >> >> I have written a page for the OpenXT wiki describing a proposal for >> initial development towards the VirtIO-Argo transport driver, and the >> related system

Re: [openxt-dev] Re: Follow up on libxl-fix-reboot.patch

(adding xen-devel & toolstack devs) On Dec 14, 2020, at 16:12, Jason Andryuk wrote: > > On Fri, Dec 11, 2020 at 3:56 PM Chris Rogers wrote: >> >> This is a follow up to a request during our roadmapping meeting to clarify >> the purpose of libxl-fix-reboot.patch on the current version of Xen

Re: [PATCH v2] xen: EXPERT clean-up and introduce UNSUPPORTED

 On Nov 20, 2020, at 05:09, Jan Beulich wrote: > On 19.11.2020 22:40, Stefano Stabellini wrote: >> On Thu, 19 Nov 2020, Jan Beulich wrote: >>> On 18.11.2020 22:00, Stefano Stabellini wrote: On Wed, 18 Nov 2020, Jan Beulich wrote: > On 18.11.2020 01:50, Stefano Stabellini wrote: >>

Re: [ANNOUNCE] Call for agenda items for 5 November 2020 Community Call @ 16:00 UTC

> On Nov 5, 2020, at 11:01, Jan Beulich wrote: > On 30.10.2020 15:47, George Dunlap wrote: >> Hi all, >> >> The proposed agenda is in >> https://cryptpad.fr/pad/#/2/pad/edit/k-0Aj+Sxb5SliLWrFRBwx49V/ and you can >> edit to add items. Alternatively, you can reply to this mail directly. >> >>

Re: [RFC PATCH] xen: EXPERT clean-up

> On Nov 3, 2020, at 16:15, Stefano Stabellini wrote: > > On Tue, 3 Nov 2020, Rich Persaud wrote: >>> On Nov 3, 2020, at 14:37, Stefano Stabellini wrote: >>> >>> On Tue, 3 Nov 2020, Jan Beulich wrote: >>>>> On 02.11.2020 22:41, Stef

Re: [RFC PATCH] xen: EXPERT clean-up

On Nov 3, 2020, at 14:37, Stefano Stabellini wrote: > > On Tue, 3 Nov 2020, Jan Beulich wrote: >>> On 02.11.2020 22:41, Stefano Stabellini wrote: >>> On Mon, 2 Nov 2020, Jan Beulich wrote: On 31.10.2020 01:24, Stefano Stabellini wrote: > @@ -79,8 +79,8 @@ config SBSA_VUART_CONSOLE

Re: [Xen-devel] [PATCH V3 2/2] Xen/PCIback: Implement PCI flr/slot/bus reset with 'reset' SysFS attribute

On Oct 19, 2020, at 11:52, Håkon Alstadheim wrote: > >  > Den 19.10.2020 17:16, skrev Håkon Alstadheim: >> Den 19.10.2020 13:00, skrev George Dunlap: >>> >>>> On Jan 31, 2020, at 3:33 PM, Wei Liu wrote: >>>> >>>> On Fri, Jan 17, 2

Re: Xen 4.14.0 fails on Dell IoT Gateway without efi=no-rs

On Aug 20, 2020, at 07:24, George Dunlap wrote: >  >> On Thu, Aug 20, 2020 at 9:35 AM Jan Beulich wrote: > >> >> As far as making cases like this work by default, I'm afraid it'll >> need to be proposed to replace me as the maintainer of EFI code in >> Xen. I will remain on the position that

Re: Porting Xen to Jetson Nano

On Jul 28, 2020, at 13:19, Srinivas Bangalore wrote: > >  >> >> I struggled to find your comment inline as your e-mail client doesn't >> quote my answer. Please configure your e-mail client to use some form >> of quoting (the usual is '>'). >> >> [] Done! Sorry about that. > > Thanks this

Re: Saved notes for design sessions

> On Jul 16, 2020, at 07:55, George Dunlap wrote: > Hey all, > > PDFs of the saved shared notes for the design sessions can be found in this > zipfile: > > https://cryptpad.fr/file/#/2/file/LoJZpSq+vHKNoisVqdsPj3Z9/ > > The files are labeled with the start/end time and the room in which they

Re: [XEN RFC for-4.14] Re: use of "stat -"

On Jun 24, 2020, at 22:39, Jason Andryuk wrote: > > On Wed, Jun 24, 2020 at 12:19 PM Ian Jackson wrote: >> >> Jan Beulich writes ("Re: use of "stat -""): >>> [CAUTION - EXTERNAL EMAIL] DO NOT reply, click links, or open attachments >>> unless you have verified the sender and know the content

Re: [PATCH v1] tools: fix usage of strncpy

On Jun 8, 2020, at 10:12, Olaf Hering wrote: > > Am Mon, 8 Jun 2020 08:43:50 -0400 > schrieb Jason Andryuk : > >> I added a length check in this patch: > > gcc will not recognize such runtime checks and will (most likely) complain > about the strncpy usage anyway, just as it does now in >

Re: XenSummit 2020 *will* be held virtuaully in June!

 > > On May 7, 2020, at 18:50, George Dunlap wrote: > We’re still ironing out all the details, but it’s absolutely confirmed that > XenSummit 2020 will be held virtually in June. > > In addition, the new version of the Design Sessions website is now live: > >

Re: XenSummit 2020 *will* be held virtuaully in June!

On May 7, 2020, at 18:50, George Dunlap wrote: > > We’re still ironing out all the details, but it’s absolutely confirmed that > XenSummit 2020 will be held virtually in June. > > In addition, the new version of the Design Sessions website is now live: > >

Re: [Xen-devel] Moving Forward on XenSummit

On Mar 24, 2020, at 14:03, George Dunlap wrote: > > I wanted to let everyone know that the XenProject is moving forward with > plans to hold XenSummit this year, one way or another. > > There are two basic approaches the Advisory Board has been considering: > Postponing the even until later

Re: [Xen-devel] [PATCH 1/2] tools/helpers: Introduce cmp-fd-file-inode utility

On Feb 26, 2020, at 11:07, Jason Andryuk wrote: > >> On Wed, Feb 26, 2020 at 10:48 AM Ian Jackson wrote: >> Jason Andryuk writes ("[PATCH 1/2] tools/helpers: Introduce >> cmp-fd-file-inode utility"): >>> This is a C implementation of the perl code inside of locking.sh to >>> check that the

Re: [Xen-devel] [PATCH v3 0/9] Add hypervisor sysfs-like support

On Jan 21, 2020, at 03:45, Juergen Gross wrote: > > On the 2019 Xen developer summit there was agreement that the Xen > hypervisor should gain support for a hierarchical name-value store > similar to the Linux kernel's sysfs. Is there a short summary of the most recent use cases for this

Re: [Xen-devel] [PATCH v4 12/16] libxl: use vchan for QMP access with Linux stubdomain

On Jan 24, 2020, at 09:07, Jason Andryuk wrote: > > On Tue, Jan 21, 2020 at 6:46 PM Marek Marczykowski-Górecki > wrote: > + +sdss->qmp_proxy_spawn.timeout_ms = LIBXL_DEVICE_MODEL_START_TIMEOUT * 1000; +sdss->qmp_proxy_spawn.midproc_cb = libxl__spawn_record_pid;

Re: [Xen-devel] [PATCH v4 13/16] Regenerate autotools files

On Jan 21, 2020, at 15:58, Marek Marczykowski-Górecki wrote: > > On Wed, Jan 15, 2020 at 04:57:29PM -0500, Rich Persaud wrote: >>>> On Jan 14, 2020, at 21:42, Marek Marczykowski-Górecki >>>> wrote: >>> Since we have those generated files committed to

Re: [Xen-devel] [PATCH V3 2/2] Xen/PCIback: Implement PCI flr/slot/bus reset with 'reset' SysFS attribute

On Aug 26, 2019, at 17:08, Pasi Kärkkäinen wrote: > Hi, > >> On Mon, Oct 08, 2018 at 10:32:45AM -0400, Boris Ostrovsky wrote: >>> On 10/3/18 11:51 AM, Pasi Kärkkäinen wrote: >>> On Wed, Sep 19, 2018 at 11:05:26AM +0200, Roger Pau Monné wrote: On Tue, Sep 18, 2018 at 02:09:53PM -0400, Boris

Re: [Xen-devel] [PATCH] xen: xen-pciback: Reset MSI-X state when exposing a device

On Sep 26, 2019, at 06:17, Pasi Kärkkäinen wrote: > > Hello Stanislav, > >> On Fri, Sep 13, 2019 at 11:28:20PM +0800, Chao Gao wrote: >>> On Fri, Sep 13, 2019 at 10:02:24AM +, Spassov, Stanislav wrote: >>> On Thu, Dec 13, 2018 at 07:54, Chao Gao wrote: On Thu, Dec 13, 2018 at

Re: [Xen-devel] [PATCH v4 11/16] tools: add simple vchan-socket-proxy

On Jan 14, 2020, at 21:42, Marek Marczykowski-Górecki wrote: > > diff --git a/tools/libvchan/Makefile b/tools/libvchan/Makefile > index 7892750..1c845ca 100644 > --- a/tools/libvchan/Makefile > +++ b/tools/libvchan/Makefile > @@ -13,6 +13,7 @@ LIBVCHAN_PIC_OBJS = $(patsubst

Re: [Xen-devel] [PATCH v4 13/16] Regenerate autotools files

> On Jan 14, 2020, at 21:42, Marek Marczykowski-Górecki > wrote: > Since we have those generated files committed to the repo (why?!), > update them after changing configure.ac. Is there any reason not to remove the generated configure files? A developer using generated files on system B

Re: [Xen-devel] [PATCH net-next] xen-netback: get rid of old udev related code

> On Dec 16, 2019, at 03:31, Jürgen Groß wrote: > > On 16.12.19 09:18, Durrant, Paul wrote: >>> -Original Message- >>> From: Jürgen Groß >>> Sent: 16 December 2019 08:10 >>> To: Durrant, Paul ; David Miller >>> >>> Cc: xen-devel@lists.xenproject.org; wei@kernel.org; linux- >>>

[Xen-devel] Making save/restore optional in toolstack, for edge/embedded derivatives

Linux stubdom patches currently require qemu in dom0 for consoles [1], due to the upstream toolstack need for save/restore. Until a long-term solution is available (multiple console support in xenconsoled), would tools maintainers consider a patch that made save/restore build-time configurable

Re: [Xen-devel] [MirageOS-devel] [PATCH v2 4/6] Add Code Review Guide

On Nov 28, 2019, at 09:05, Lars Kurth wrote: > > On 28/11/2019, 07:37, "Jan Beulich" wrote: > >>On 28.11.2019 14:06, Lars Kurth wrote: >> I can certainly add something on the timing , along the lines of >> * For complex series, consider the time it takes to do reviews (maybe with a >>

Re: [Xen-devel] [PATCH v2 4/6] Add Code Review Guide

On Nov 28, 2019, at 05:12, Jan Beulich wrote: > > On 28.11.2019 01:54, Stefano Stabellini wrote: >>> On Thu, 26 Sep 2019, Lars Kurth wrote: >>> From: Lars Kurth >>> >>> This document highlights what reviewers such as maintainers and committers >>> look >>> for when reviewing code. It sets

Re: [Xen-devel] UEFI support on Dell boxes (was: Re: Status of 4.13)

On Nov 27, 2019, at 04:16, Jan Beulich wrote: > > On 26.11.2019 22:20, Rich Persaud wrote: >> As an intermediate step, could we have an umbrella opt-in >> Kconfig option (CONFIG_EFI_NONSPEC_COMPATIBILITY?) that >> enables multiple EFI options for maximu

Re: [Xen-devel] UEFI support on Dell boxes (was: Re: Status of 4.13)

On Nov 26, 2019, at 15:23, Andrew Cooper wrote: > On 26/11/2019 20:12, Roman Shaposhnik wrote: >>> On Tue, Nov 26, 2019 at 10:32 AM Marek Marczykowski-Górecki >>> wrote: >>> On Tue, Nov 26, 2019 at 09:56:25AM -0800, Roman Shaposhnik wrote: Hi Marek, after applying Jan's patch I'm making

Re: [Xen-devel] Status of 4.13

On Nov 21, 2019, at 17:11, Marek Marczykowski-Górecki wrote: > > On Thu, Nov 21, 2019 at 11:39:14AM -0800, Roman Shaposhnik wrote: >>> On Thu, Nov 21, 2019 at 9:38 AM Andrew Cooper >>> wrote: >>> On 21/11/2019 17:31, Roman Shaposhnik wrote: >> On Wed, Nov 20, 2019 at 10:06 PM Jürgen

Re: [Xen-devel] Likely regression in efi=no-rs option

this is clearly a regression from RC1 (just verified). > > Thanks, > Roman. > >>>> On Sat, Nov 16, 2019 at 12:47 PM Rich Persaud wrote: >> I don't know if there's a change in efi=no-rs behavior, but some EFI fixes >> were merged on 10/25, which (on some machines

Re: [Xen-devel] Likely regression in efi=no-rs option

I don't know if there's a change in efi=no-rs behavior, but some EFI fixes were merged on 10/25, which (on some machines) have reduced the need to disable UEFI runtime services to work around non-spec UEFI firmware. This should increase hardware compatibility with Xen. Of course, there could

[Xen-devel] Virtualization videos from Platform Security Summit 2019

Xen, OpenXT, QubesOS and embedded developers may be interested in these videos. The first (IBM ppc Ultravisor with extended Q) is related to past discussions of minimal L0 Xen in firmware, similar to HP/Bromium nesting-optimized hypervisor. The second is related to kexec and TrenchBoot,

Re: [Xen-devel] [RFC] Documentation formats, licenses and file system structure

On Oct 17, 2019, at 12:55, Stefano Stabellini wrote: > > On Thu, 17 Oct 2019, Rich Persaud wrote: >>> On Oct 17, 2019, at 12:32, Stefano Stabellini >>> wrote: >>> >>> On Thu, 17 Oct 2019, Lars Kurth wrote: >>>> On 16/10/2019, 17:3

Re: [Xen-devel] [RFC] Documentation formats, licenses and file system structure

On Oct 17, 2019, at 12:32, Stefano Stabellini wrote: > > On Thu, 17 Oct 2019, Lars Kurth wrote: >> On 16/10/2019, 17:35, "Rich Persaud" wrote: >> >>>> On Oct 15, 2019, at 08:27, Lars Kurth wrote: >>> ... >>> >>> My point

Re: [Xen-devel] [RFC] Documentation formats, licenses and file system structure

> On Oct 15, 2019, at 08:27, Lars Kurth wrote: > Hi Rich, > >>>> On 15 Oct 2019, at 02:58, Rich Persaud wrote: >>>>> On Oct 11, 2019, at 07:11, Lars Kurth wrote: >>> On 11/10/2019, 02:24, "Stefano Stabellini" wrote: >>>>

Re: [Xen-devel] [RFC] Documentation formats, licenses and file system structure

> On Oct 11, 2019, at 07:11, Lars Kurth wrote: > > On 11/10/2019, 02:24, "Stefano Stabellini" wrote: > >>On Thu, 10 Oct 2019, Lars Kurth wrote: >> * Would we ever include API docs generated from GPLv2 code? E.g. for safety >> use-cases? >> @Stefano, @Artem: I guess this one is for you.

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

On Sep 5, 2019, at 12:12, Lars Kurth wrote: > > > We can defer the xenstoreless name service topic to the October monthly > > call. > > > > For today's call, can we discuss the previously posted high-level design > > for unification of the domB RFC with dom0less, as "domB mode" for > >

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

> On Sep 5, 2019, at 04:36, Lars Kurth wrote: > > On 05/09/2019, 09:33, "Juergen Gross" wrote: > >>On 05.09.19 10:14, Andrew Cooper wrote: >>> On 05/09/2019 08:49, Lars Kurth wrote: >>>> On 05/09/2019, 08:41, "Rich Persaud" wro

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

> On Sep 5, 2019, at 03:19, Jan Beulich wrote: > >> On 05.09.2019 04:32, Rich Persaud wrote: >> Agenda item: Domain name service for nested virt and disaggregation >> >> (text based on draft by Daniel Smith, who will speak to this agenda item) >> >>

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

Agenda item: Domain name service for nested virt and disaggregation (text based on draft by Daniel Smith, who will speak to this agenda item) If a future, minimal "L0 Xen" hypervisor can be optimized for nested virtualization in greenfield deployments (i.e. no requirement to maintain

Re: [Xen-devel] More questions about Xen memory layout/usage, access to guest memory

> On Aug 22, 2019, at 09:51, Andrew Cooper wrote: > >> On 22/08/2019 03:06, Johnson, Ethan wrote: >> >> For HVM, obviously anything that can't be virtualized natively by the >> hardware needs to be emulated by Xen/QEMU (since the guest kernel isn't >> expected to be cooperative to issue PV

Re: [Xen-devel] [RFC] Code of Conduct

On Aug 16, 2019, at 07:19, George Dunlap wrote: > > On 8/15/19 6:23 PM, Rich Persaud wrote: >>> On Aug 9, 2019, at 13:48, Lars Kurth wrote: >>> >>> Hi all, >> >> Hi Lars, >> >>> >>> Following the discussion we h

Re: [Xen-devel] [win-pv-devel] [RFC] Code of Conduct

> On Aug 15, 2019, at 14:46, Lars Kurth wrote: >> On 15 Aug 2019, at 19:27, Rich Persaud wrote: >> On Aug 15, 2019, at 14:01, Lars Kurth wrote: >> >>> Hi Rich, >>> >>> thanks for the feedback. I am going to >>> >>> On

Re: [Xen-devel] [RFC] Code of Conduct

On Aug 15, 2019, at 14:01, Lars Kurth wrote: > > Hi Rich, > > thanks for the feedback. I am going to > > On 15/08/2019, 18:23, "Rich Persaud" wrote: > > > On Aug 9, 2019, at 13:48, Lars Kurth wrote: > > > > Hi all, >

Re: [Xen-devel] [RFC] Code of Conduct

> On Aug 9, 2019, at 13:48, Lars Kurth wrote: > > Hi all, Hi Lars, > > Following the discussion we had at the Developer Summit (see > https://wiki.xenproject.org/wiki/Design_Sessions_2019#Community_Issues_.2F_Improvements_-_Communication.2C_Code_of_Conduct.2C_etc. > for notes) I put

[Xen-devel] Xen Summit 2019 Design Session - Nested Virtualization

Session notes attached in markdown and PDF format, please revise as needed.Rich xen-summit-2019-nested-virt-design-session.pdf Description: Adobe PDF document # Nested Virtualization Design Session Xen Design and Developer Summit, [11 July

Re: [Xen-devel] Design session notes: Build system gripe session

> On Jul 15, 2019, at 09:27, George Dunlap wrote: > ... > https://hackmd.io/mAGT5bU9T6-aXJVj88deYw > ... > > 3. meta virtualization build system (yocto) needs to pull simlink > tricks, xen's build system stomp on that Are more details available on this item? This script can be used to

Re: [Xen-devel] Terminology for "guest" - Was: [PATCH] docs/sphinx: Introduction

On Aug 8, 2019, at 06:49, Jan Beulich wrote: > >> On 08.08.2019 11:13, Julien Grall wrote: >> Hi Jan, >> >>> On 08/08/2019 10:04, Jan Beulich wrote: On 08.08.2019 10:43, Andrew Cooper wrote: > On 08/08/2019 07:22, Jan Beulich wrote: >> On 07.08.2019 21:41, Andrew Cooper wrote:

Re: [Xen-devel] [PATCH] tests/cpu-policy: fix format-overflow warning by null terminating strings

> On Jul 31, 2019, at 04:11, Jan Beulich wrote: > >> On 31.07.2019 02:22, Dario Faggioli wrote: >> Jan's example above, seem to compile **without any warnings** for me as >> well. If I add a main(), I can even get the code above to print the >> content of the array. >> >> And yet, building the

Re: [Xen-devel] [PATCH] Adding Intel TXT maintainter

> On Jul 29, 2019, at 10:45, Jan Beulich wrote: > >> On 29.07.2019 16:39, Lukasz Hawrylko wrote: >> Support for Intel TXT has orphaned status right now because >> no active maintainter is listed. Adding myself as active maintainter, >> so it could be reverted to supported state. > > Which you

Re: [Xen-devel] [PATCH] docs/sphinx: todo/wishlist

> On Jul 22, 2019, at 15:20, Andrew Cooper wrote: > > a.k.a. (at least in this form) Andrew's "work which might be offloadable to > someone else" list. > > Signed-off-by: Andrew Cooper > --- > CC: George Dunlap > CC: Ian Jackson > CC: Jan Beulich > CC: Stefano Stabellini > CC: Tim Deegan

Re: [Xen-devel] [PATCH] tboot: remove maintainers and declare orphaned

(cc Intel and tboot-devel) Hi Roger, Thanks for your interest in documenting the status of maintenance for Intel TXT support in Xen. Intel TXT and Xen are deployed in production today by OpenXT and QubesOS for boot integrity. Xen was a pioneering adopter of DRTM, almost a decade ago, but

Re: [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx

> On Jul 19, 2019, at 15:31, Roman Shaposhnik wrote: > > Hi! > > we're using Xen on Advantech ARK-2250 Embedded Box PC: > > https://www.elmark.com.pl/web/uploaded/karty_produktow/advantech/ark-2250l/ark-2250l_instrukcja-uzytkownika.pdf Roman, Good to see Xen being used on fanless

Re: [Xen-devel] preparations for 4.12.1

> On Jul 23, 2019, at 17:05, Roman Shaposhnik wrote: > >> On Tue, Jul 23, 2019 at 2:00 PM Pasi Kärkkäinen wrote: >> >> Hi, >> >>> On Fri, Jul 19, 2019 at 02:23:44PM +, Jan Beulich wrote: >>> All, >>> >>> the release is due in early August. Please point out backports you >>> find missing

Re: [Xen-devel] [RFC] xen: Add .astylerc for automated style-formatting

On Jul 19, 2019, at 09:31, Julien Grall wrote: >> On 19/07/2019 14:24, Julien Grall wrote: >> Hi Tamas, >>> On 19/07/2019 14:14, Tamas K Lengyel wrote: On Fri, Jul 19, 2019 at 7:11 AM Julien Grall wrote: Hi Tamas, > On 19/07/2019 14:00, Tamas K Lengyel wrote: >> On

Re: [Xen-devel] [RFC] xen: Add .astylerc for automated style-formatting

> On Jul 18, 2019, at 10:43, Tamas K Lengyel wrote: > > Using astyle (http://astyle.sourceforge.net) can greatly reduce the overhead > of > manually checking and applying style-fixes to source-code. The included > .astylerc is the closest approximation of the established Xen style (including >

Re: [Xen-devel] [PATCH] golang/xenlight: Fixing compilation for go 1.11

> On Apr 25, 2019, at 07:41, George Dunlap wrote: > > On 4/25/19 12:40 PM, Jan Beulich wrote: > On 18.04.19 at 15:11, wrote: On 4/18/19 2:52 AM, Daniel P. Smith wrote: This deals with two casting issues for compiling under go 1.11: - explicitly cast to *C.xentoollog_logger

Re: [Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items

> On Jun 26, 2019, at 06:45, Lars Kurth wrote: > > > > On 25/06/2019, 21:27, "Rich Persaud" wrote: > >> On Jun 25, 2019, at 16:17, Julien Grall wrote: >> >> Hi Rich, >> >> On 6/25/19 8:38 PM, Rich Persaud wrote: >>&g

Re: [Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items

> On Jun 25, 2019, at 16:17, Julien Grall wrote: > > Hi Rich, > > On 6/25/19 8:38 PM, Rich Persaud wrote: >>> On Jun 25, 2019, at 12:36, Lars Kurth wrote: >>> >>> Hi all: >>> please add your agenda items. I had only ONE series which wa

Re: [Xen-devel] Xen Project Community Call June 27th (instead of July 4th): @15:00 UTC Call for agenda items

> On Jun 25, 2019, at 12:36, Lars Kurth wrote: > > Hi all: > please add your agenda items. I had only ONE series which was highlighted as > needing attention from others. Is this seriously the only one? Proposed agenda item: in the absence of Jira tickets, would it be useful to have a list

Re: [Xen-devel] Migrating key developer docs to xen.git sphinx docs and refreshing them in the process

> On Jun 25, 2019, at 12:34, Lars Kurth wrote: > > On 25/06/2019, 14:47, "Andrew Cooper" wrote: > >> On 25/06/2019 13:15, Lars Kurth wrote: >> On 25/06/2019, 10:03, "Julien Grall" wrote: >> > The point here is that we can be flexible and creative about the way to > maintain the

Re: [Xen-devel] [PATCH v2 0/3] mwait support for AMD processors

> On Mar 28, 2019, at 11:04, Woods, Brian wrote: > > This patch series add support and enablement for mwait on AMD Naples > and Rome processors. Newer AMD processors support mwait, but only for > c1, and for c2 halt is used. The mwait-idle driver is modified to be > able to use both mwait and

Re: [Xen-devel] Anyone using blktap2?

> On May 13, 2019, at 11:34, Wei Liu wrote: > > Hello > > Seeing that you were the last people who changed blktap2 in a meaningful > way: do you use it at all? As discussed F2F in a Xen Summit 2017 design session: OpenXT and Citrix XenServer use blktap. VHD encryption support was recently

Re: [Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against

> On May 9, 2019, at 21:28, Lars Kurth wrote: > > Hi all, > > following a discussion with committers about Guest testing in OSSTEST, it > surfaced that we have not updated what distros we test in OSSTEST for a very > long time. All agreed that we should regularly review what we test against:

Re: [Xen-devel] [VOTE] tagging for operational messages sent to xen-devel@ (was Re: Xen 4.13 Development Update)

> On May 1, 2019, at 14:37, Lars Kurth wrote: > > Rich, > as nobody replied to the mail, I am inclined to dismiss the proposal of ANN > for now > Lars What do you think about the suggestion to apply a tag ("ANNOUNCE"?) for emails that are mirrored to xen-devel from the -announce mailing list?

Re: [Xen-devel] [VOTE] tagging for operational messages sent to xen-devel@ (was Re: Xen 4.13 Development Update)

> On Apr 25, 2019, at 12:36, Lars Kurth wrote: > > Alright, > > there was a lengthy discussion on this topic on IRC - log attached. The > consensus appears to be to use Canonical messages with a CAPITALISED tag. > E.g. "[TAG] Xen 4.13 Development Update". > > The options which seemed to have

Re: [Xen-devel] [PATCH 1/2] libxl: Add virtio vga interface support for qemu

> On Apr 10, 2019, at 20:02, Chris Patterson wrote: > > For anyone looking at this... while I have tested and verified that > both virtio-gpu and VirGL work, it's not without some hiccup. > > I have been running Ubuntu 19.04 with this config for a few days and I > have had a couple VM freezes.

Re: [Xen-devel] XSA-283: Post-mortem

On Feb 25, 2019, at 10:14, George Dunlap wrote: > > This is an attempt to do a 'post-mortem' on XSA-283, to find out how > the error came about, and consider what changes we could make to code > / processes to prevent such errors from happening in the future. The > Security Team hopes to make

Re: [Xen-devel] [PATCH v5 00/15] Argo: hypervisor-mediated interdomain communication

> On Feb 4, 2019, at 05:07, Roger Pau Monné wrote: > >> On Sun, Feb 03, 2019 at 10:04:29AM -0800, Christopher Clark wrote: >> On Thu, Jan 31, 2019 at 5:39 AM Roger Pau Monné >> wrote: >> >> On Wed, Jan 30, 2019 at 08:05:30PM -0800, Christopher Clark wrote: >>

Re: [Xen-devel] [PATCH v5 00/15] Argo: hypervisor-mediated interdomain communication

> On Feb 4, 2019, at 13:22, Stefano Stabellini wrote: > > On Mon, 4 Feb 2019, Roger Pau Monné wrote: >>> Yes, v7 was sent to address Jan and Julien's review comments in parallel >>> with our ongoing discussion on v5 macros. v7 also provided a checkpoint >>> for Argo testers to maximize test

[Xen-devel] Macro supply chains

Synopsys, which owns both Coverity and Black Duck, wrote about software supply-chain integrity for a library with almost two million downloads per week: "EventStream, a highly popular JavaScript library, was compromised with the addition of a third-party dependency, flatmap-stream, containing

Re: [Xen-devel] Xen (both x86 and Arm) Community Call: Feb 13 - 16:00 - 17:00 UTC - Call for Agenda Items

> On Feb 11, 2019, at 05:05, Lars Kurth wrote: > > Hi all, > > we have the community call for February coming up this Wednesday. My sincere > apologies, that I have not asked for agenda items last week. A current agenda > (primarily a skeleton) is available at >

Re: [Xen-devel] [PATCH v8 for-4.12 10/17] argo: implement the notify op

On Feb 7, 2019, at 04:04, Julien Grall wrote: > > Hi, > >> On 2/7/19 6:32 AM, Christopher Clark wrote: >>> On Wed, Feb 6, 2019 at 10:28 AM Julien Grall wrote: >>> >>> Hi, >>> On 2/6/19 8:55 AM, Christopher Clark wrote: +/* + * XEN_ARGO_OP_notify + * + * Asks Xen for

Re: [Xen-devel] [PATCH v8 for-4.12 00/17] Argo: hypervisor-mediated interdomain communication

On Feb 6, 2019, at 08:57, Jan Beulich wrote: On 06.02.19 at 14:53, wrote: >> On 06/02/2019 14:45, Jan Beulich wrote: >> On 06.02.19 at 09:54, wrote: Version eight of this series: Note: This version may not address the currently open discussion on the ARM hypercall

Re: [Xen-devel] [PATCH v3 04/15] argo: init, destroy and soft-reset, with enable command line opt

> On Jan 14, 2019, at 06:32, Roger Pau Monné wrote: > > On Mon, Jan 14, 2019 at 9:32 AM Christopher Clark > wrote: >> >> I've written a document about the locking to add to the tree with the >> series, and a copy is at github here: >> >>

Re: [Xen-devel] Xen (both x86 and Arm) Community Call: Jan 9 - 16:00 - 17:00 UTC - Call for Agenda Items

On Jan 9, 2019, at 10:46, Lars Kurth wrote: > > Quick note: the meeting is in 15 minutes - the agenda is at > https://docs.google.com/document/d/1Ufv9XcQO0zIAVeFbFCAHAeEIB9Ap4Y4srAm4vI8I01I/edit > On the topic of 4.12, I would like to propose moving the merge date by one week, since about

Re: [Xen-devel] x86 Community Call: Nov 14 - 15:00 - 16:00 UTC - Call reminder

> On Nov 14, 2018, at 04:56, Lars Kurth wrote: > > Hi all, > > the agenda is as follows: > https://docs.google.com/document/d/1RxW-iwcFFuKzNjjEqLEtiwFVHgAUlk35c0EtTkRE1k4/edit > * Follow up on previous actions > * PVH resource Mapping: Rian Quinn (AIS) > * TMEM (Jan) If there is time on

Re: [Xen-devel] x86 Community Call: Wed Oct 10, 14:00 - 15:00 UTC - Call for agenda items

Lars, This NIST document ("A Methodology for Determining Forensic Data Requirements for Detecting Hypervisor Attacks" [1]) appears to be focused on the application of LibVMI in some contexts. It is a NIST Interagency or Internal Report (NISTIR) document with a narrower scope than other NIST

Re: [Xen-devel] x86 Community Call - Wed Sept 12, 14:00 - 15:00 UTC - Call for agenda items

> On Sep 6, 2018, at 11:35, Lars Kurth wrote: > > Dear community members, > > please send me agenda items for next week’s community call by next > Monday. "Argo" (formerly v4v) inter-VM communication mechanism for Xen 4.12, discussed at Xen Summit 2018 design session and PSEC 2018, design

Re: [Xen-devel] [PATCH v3 5/5] x86: use PDEP for PTE flags insertion when available

On Aug 17, 2018, at 03:24, Jan Beulich wrote: > > This replaces 5 instructions by a single one, further reducing code size, > cache, and TLB footprint (in particular on systems supporting BMI2). This link claims that BMI2 may be less performant/consistent on AMD Ryzen than Intel:

Re: [Xen-devel] [OSSTEST PATCH] production-config: Temporarily drop arm64

On Aug 15, 2018, at 05:29, Julien Grall wrote: > > Hi, > >> On 08/15/2018 12:25 AM, Rich Persaud wrote: >>> On Aug 14, 2018, at 18:46, Julien Grall wrote: >>> >>> Hi Rich, >>> >>>>> On 08/14/2018 11:42 PM, Rich

Re: [Xen-devel] [OSSTEST PATCH] production-config: Temporarily drop arm64

On Aug 14, 2018, at 18:46, Julien Grall wrote: > > Hi Rich, > >> On 08/14/2018 11:42 PM, Rich Persaud wrote: >>> On Aug 13, 2018, at 10:57, Ian Jackson wrote: >>> >>> Both our arm64 boxes are out of commission and repairing them is >>&g

Re: [Xen-devel] [OSSTEST PATCH] production-config: Temporarily drop arm64

On Aug 13, 2018, at 10:57, Ian Jackson wrote: > > Both our arm64 boxes are out of commission and repairing them is > taking too long. Apologies if this is already documented elsewhere - does OSStest use Qemu for arm64 testing? Rich ___ Xen-devel

Re: [Xen-devel] Xen 4.12 Development Update

> On Jul 27, 2018, at 12:19, Juergen Gross wrote: > > This email only tracks big items for xen.git tree. Please reply for items you > would like to see in 4.12 so that people have an idea what is going on and > prioritise accordingly. Two additional items: 1. Linux stub domains, series posted

Re: [Xen-devel] Xen for Automotive - white paper on virtualization

Thanks to everyone who contributed to the AGL virtualization white paper and to Michele Paolino for stewarding it from concept to final publication. I’ve added it to the Xen wiki: https://wiki.xenproject.org/wiki/Automotive_Whitepapers Rich___

Re: [Xen-devel] [Notes for xen summit 2018 design session] Process changes: is the 6 monthly release Cadence too short, Security Process, ...

On Jul 5, 2018, at 22:54, Tamas K Lengyel wrote: > >> On Thu, Jul 5, 2018 at 12:52 PM George Dunlap >> wrote: >> >>> Again, there was a sense that some of the issues we are seeing could be solved if we had better CI capability: in other words, some of the issues we were

Re: [Xen-devel] Xen Project Security Whitepaper v1 is ready for community review

> On May 18, 2018, at 06:13, Lars Kurth wrote: > > Dear Community Members, > > just under 3 months ago, we started a community consultation titled "Xen > Security Process Consultation: is there a case to change anything?" (see >

Re: [Xen-devel] Xen and safety certification, Minutes of the meeting on Apr 4th

> On May 10, 2018, at 15:51, Stefano Stabellini wrote: > > On Thu, 10 May 2018, Praveen Kumar wrote: >>> Yeah, you are right. It looks like turning Dom0 into a DomU is not good >>> enough. Maybe for this option to be viable we would actually have to >>> terminate (or

Re: [Xen-devel] reboot driver domain, vifX.Y = NO-CARRIER?

> On May 1, 2018, at 08:53, Jason Cooper wrote: > > add the link to xen-users thread of me talking to myself. :-)) > >> On Tue, May 01, 2018 at 12:37:51PM +, Jason Cooper wrote: >> When I was first digging into this, I started a thread on xen-users [1], >> I've

Re: [Xen-devel] Community call: PCI Emulation - Future Direction (Wed, May 2nd, UTC 16:00-17:00 / BST 17:00-18:00)

> On Apr 24, 2018, at 05:19, Lars Kurth wrote: > > Hi all, > as agreed please find attached the meeting invite > Regards > Lars > > ## Agenda (provisional) > I copied what was discussed on this thread so far >

  1   2   >