Description: this session will focus on discussing the current state and
key challenges of Nested Virtualization in Xen.
---
I'm going to reference this message to the mailing list in the related
Gitlab epic:
https://gitlab.com/groups/xen-project/-/epics/25
References: George Dunlap's two part
The description of the design session was:
PVH: limitations, requirements & future considerations
A general discussion on PVH from both guest and Dom0 perspectives, covering:
Trade-offs and key limitations
Required work for PCI passthrough and SR-IOV support
Dom0 feasibility: kern
On Wed, Jun 19, 2024 at 12:27 PM Christian König
wrote:
>
> Am 18.06.24 um 16:12 schrieb Demi Marie Obenour:
> > On Tue, Jun 18, 2024 at 08:33:38AM +0200, Christian König wrote:
> > > Am 18.06.24 um 02:57 schrieb Demi Marie Obenour:
> > >> On Mon, Jun 17, 2024 at 10:46:13PM +0200, Marek Marczykows
Am 18.06.24 um 16:12 schrieb Demi Marie Obenour:
On Tue, Jun 18, 2024 at 08:33:38AM +0200, Christian König wrote:
> Am 18.06.24 um 02:57 schrieb Demi Marie Obenour:
>> On Mon, Jun 17, 2024 at 10:46:13PM +0200, Marek Marczykowski-Górecki
>> wrote:
>>> On Mon, Jun 17, 2024 at 09:46:29AM +0200, Roge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Jun 18, 2024 at 04:43:50PM +0200, Roger Pau Monné wrote:
> On Mon, Jun 17, 2024 at 08:57:14PM -0400, Demi Marie Obenour wrote:
> > Given the recent progress on PVH dom0, is it reasonable to assume that
> > PVH dom0 will be ready in time for R
On Mon, Jun 17, 2024 at 08:57:14PM -0400, Demi Marie Obenour wrote:
> Given the recent progress on PVH dom0, is it reasonable to assume that
> PVH dom0 will be ready in time for R4.3, and that therefore Qubes OS
> doesn't need to worry about this problem on x86?
PVH dom0 will only be ready (whatev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Jun 18, 2024 at 08:33:38AM +0200, Christian König wrote:
> Am 18.06.24 um 02:57 schrieb Demi Marie Obenour:
> > On Mon, Jun 17, 2024 at 10:46:13PM +0200, Marek Marczykowski-Górecki
> > wrote:
> > > On Mon, Jun 17, 2024 at 09:46:29AM +0200, Ro
Am 18.06.24 um 02:57 schrieb Demi Marie Obenour:
On Mon, Jun 17, 2024 at 10:46:13PM +0200, Marek Marczykowski-Górecki
wrote:
> On Mon, Jun 17, 2024 at 09:46:29AM +0200, Roger Pau Monné wrote:
>> On Sun, Jun 16, 2024 at 08:38:19PM -0400, Demi Marie Obenour wrote:
>>> In both cases, the device phy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Jun 17, 2024 at 10:46:13PM +0200, Marek Marczykowski-Górecki wrote:
> On Mon, Jun 17, 2024 at 09:46:29AM +0200, Roger Pau Monné wrote:
> > On Sun, Jun 16, 2024 at 08:38:19PM -0400, Demi Marie Obenour wrote:
> > > In both cases, the device phy
On Mon, Jun 17, 2024 at 09:46:29AM +0200, Roger Pau Monné wrote:
> On Sun, Jun 16, 2024 at 08:38:19PM -0400, Demi Marie Obenour wrote:
> > In both cases, the device physical
> > addresses are identical to dom0’s physical addresses.
>
> Yes, but a PV dom0 physical address space can be very scattere
On Mon, Jun 17, 2024 at 05:39:23PM +0200, Jan Beulich wrote:
> On 17.06.2024 17:17, Demi Marie Obenour wrote:
> > On Mon, Jun 17, 2024 at 11:07:54AM +0200, Jan Beulich wrote:
> >> On 14.06.2024 18:44, Demi Marie Obenour wrote:
> >>> On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
> >>>
On 17.06.2024 17:17, Demi Marie Obenour wrote:
> On Mon, Jun 17, 2024 at 11:07:54AM +0200, Jan Beulich wrote:
>> On 14.06.2024 18:44, Demi Marie Obenour wrote:
>>> On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
On 14.06.2024 09:21, Roger Pau Monné wrote:
> I'm not sure it's p
On Mon, Jun 17, 2024 at 11:07:54AM +0200, Jan Beulich wrote:
> On 14.06.2024 18:44, Demi Marie Obenour wrote:
> > On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
> >> On 14.06.2024 09:21, Roger Pau Monné wrote:
> >>> I'm not sure it's possible to ensure that when using system RAM such
On Mon, Jun 17, 2024 at 09:46:29AM +0200, Roger Pau Monné wrote:
> On Sun, Jun 16, 2024 at 08:38:19PM -0400, Demi Marie Obenour wrote:
> > On Fri, Jun 14, 2024 at 10:39:37AM +0200, Roger Pau Monné wrote:
> > > On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
> > > > On 14.06.2024 09:21,
On 17.06.2024 02:38, Demi Marie Obenour wrote:
> On Fri, Jun 14, 2024 at 10:39:37AM +0200, Roger Pau Monné wrote:
>> On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
>>> On 14.06.2024 09:21, Roger Pau Monné wrote:
On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
> O
On 14.06.2024 18:44, Demi Marie Obenour wrote:
> On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
>> On 14.06.2024 09:21, Roger Pau Monné wrote:
>>> I'm not sure it's possible to ensure that when using system RAM such
>>> memory comes from the guest rather than the host, as it would lik
On 14.06.2024 18:35, Demi Marie Obenour wrote:
> On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
>> On 13.06.2024 20:43, Demi Marie Obenour wrote:
>>> 2. Add support for `XEN_DOMCTL_memory_mapping` to use system RAM, not
>>>just IOMEM. Mappings made with `XEN_DOMCTL_memory_mapping
On Sun, Jun 16, 2024 at 08:38:19PM -0400, Demi Marie Obenour wrote:
> On Fri, Jun 14, 2024 at 10:39:37AM +0200, Roger Pau Monné wrote:
> > On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
> > > On 14.06.2024 09:21, Roger Pau Monné wrote:
> > > > On Fri, Jun 14, 2024 at 08:38:51AM +0200,
On Fri, Jun 14, 2024 at 10:39:37AM +0200, Roger Pau Monné wrote:
> On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
> > On 14.06.2024 09:21, Roger Pau Monné wrote:
> > > On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
> > >> On 13.06.2024 20:43, Demi Marie Obenour wrote:
>
On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
> On 13.06.2024 20:43, Demi Marie Obenour wrote:
> > GPU acceleration requires that pageable host memory be able to be mapped
> > into a guest.
>
> I'm sure it was explained in the session, which sadly I couldn't attend.
> I've been aski
On Fri, Jun 14, 2024 at 09:21:56AM +0200, Roger Pau Monné wrote:
> On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
> > On 13.06.2024 20:43, Demi Marie Obenour wrote:
> > > GPU acceleration requires that pageable host memory be able to be mapped
> > > into a guest.
> >
> > I'm sure it
On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
> On 14.06.2024 09:21, Roger Pau Monné wrote:
> > On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
> >> On 13.06.2024 20:43, Demi Marie Obenour wrote:
> >>> GPU acceleration requires that pageable host memory be able to be map
On Fri, Jun 14, 2024 at 10:12:40AM +0200, Jan Beulich wrote:
> On 14.06.2024 09:21, Roger Pau Monné wrote:
> > On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
> >> On 13.06.2024 20:43, Demi Marie Obenour wrote:
> >>> GPU acceleration requires that pageable host memory be able to be map
On 14.06.2024 09:21, Roger Pau Monné wrote:
> On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
>> On 13.06.2024 20:43, Demi Marie Obenour wrote:
>>> GPU acceleration requires that pageable host memory be able to be mapped
>>> into a guest.
>>
>> I'm sure it was explained in the session,
On Fri, Jun 14, 2024 at 08:38:51AM +0200, Jan Beulich wrote:
> On 13.06.2024 20:43, Demi Marie Obenour wrote:
> > GPU acceleration requires that pageable host memory be able to be mapped
> > into a guest.
>
> I'm sure it was explained in the session, which sadly I couldn't attend.
> I've been aski
On 13.06.2024 20:43, Demi Marie Obenour wrote:
> GPU acceleration requires that pageable host memory be able to be mapped
> into a guest.
I'm sure it was explained in the session, which sadly I couldn't attend.
I've been asking Ray and Xenia the same before, but I'm afraid it still
hasn't become c
GPU acceleration requires that pageable host memory be able to be mapped
into a guest. This requires changes to all of the Xen hypervisor, Linux
kernel, and userspace device model.
### Goals
- Allow any userspace pages to be mapped into a guest.
- Support deprivileged operation: this API must
Notes from the design session on guest unaware migration:
Migration is often needed for e.g. host maintenance. When this is done, we
(XenServer) see two classes of issues with guests:
- Guest kernel crashes (relatively rare). Often detectable by the
toolstack and thus reported to the admin, dist
Notes from the design session: possible improvements to our documented
committing process
Description about the intended discussion:
> Various typically smaller changes have difficulty getting acks from all
> relevant maintainers. It is often quite reasonable to not wait long with
> such, and
Slides used for scene setting -
https://github.com/xapi-project/xen-api/discussions/5080.
Example code in Github -
https://github.com/xapi-project/xen-api/tree/master/ocaml/xapi-storage/python/examples
Notes taken in the session
Since scene setting slides wer
Stefano: 2min summary: gitlab as CI infrastucture, not as code hosting, tickets
etc;
we have several improvements for gitlab CI, including tests on hw
there are a bunch of build jobs, and also some run tests, most on qemu, but
some on hw
I'd like to give commiters and other notable communit
Hi,
Here is what I managed to capture, unfortunately some parts slipped by
me.
Julien: remove directmap, avoid speculative reading it
series sent 6 months ago - enough to remove directmap, but not perfect
resolving virtual adresses requires mapping/unmapping page tables -
significant perf h
Hi,
These are the raw notes for this design session from the Xen Summit:
https://design-sessions.xenproject.org/uid/discussion/disc_JEWVIhuv2TRAo2AXAZnP/view
Dependencies haven't been updated in quite some time:
* Toolchain
* system libraries, and other runtime deps
E.g. when to drop Python2.
Design Session - Hyperlaunch
Wednesday 26th May, at the Xen Design and Developer Summit 2021
Session Hosts: Christopher Clark & Daniel Smith
tl;dr:
- use cases for Hyperlaunch include supporting bare metal apps
- latency is a critical requirement for workloads
- de
Hi Everyone,
Attached are the notes from the Design Session on VirtuIO Cross-Project BoF
(Birds of a Feather) for Xen and Guest OS (Linux, Windows, FreeBSD)
developers.
Thanks,
Deb
Deb Giles
Event Manager
The Linux Foundation
+1.503.807.1876 (Time Zone: Central Time)
*Schedule a Meeting with M
# Design Session Notes - "How best to upstream Bareflank's implementation
of the Xen VMM into the Xen Project"
## Design Session Description
Assured Information Security, Inc. has been working on a new implementation
of the Xen VMM (i.e., just the root component of the Xen hy
Dear Community member,
if you didn’t make it to the developer summit, you can find material related to
the summit in the following locations
Slides:
https://www.slideshare.net/search/slideshow?searchfrom=header&q=XPDDS19
YouTube playlist of recordings
https://www.youtube.com/user/XenProjectSof
Hi all,
I collated all the design session descriptions and all the notes I could find
on xen-devel@
at https://wiki.xenproject.org/wiki/Design_Sessions_2019
I may be missing a few from day 1, as we lost some of the session in the system
when we improvised the schedule to pack more sessions in
> 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 cross-com
On Mon, Jul 15, 2019 at 02:27:27PM +0100, George Dunlap wrote:
> Or use Android's build system?
I never worked with AOSP's sources, but after reading
https://elinux.org/Android_Build_System
the build system seems quite helpful.
If we can do the following to build libxl, I think we could live with
Below are the raw notes. General agreements seem to be:
* Removing external builds from xen build system is an advantage for the
main users (developers, distros / packagers)
* Out-of-tree build is useful for lots of circumstances; symlink trick
used to work around its lack causes lots of problems
41 matches
Mail list logo
