V/r,
Daniel P. Smith
Apertus Solutions, LLC
On 4/16/25 10:06, Jan Beulich wrote:
On 16.04.2025 16:00, Daniel P. Smith wrote:
V/r,
Daniel P. Smith
Apertus Solutions, LLC
On 4/16/25 09:33, Jan Beulich wrote:
On 16.04.2025 15:02, Daniel P. Smith wrote:
On 4/10/25 16:56, Jason Andryuk wrote
On 16.04.2025 16:00, Daniel P. Smith wrote:
>
>
> V/r,
> Daniel P. Smith
> Apertus Solutions, LLC
>
> On 4/16/25 09:33, Jan Beulich wrote:
>> On 16.04.2025 15:02, Daniel P. Smith wrote:
>>> On 4/10/25 16:56, Jason Andryuk wrote:
On 2025-04-10 11:01, Jan Beulich wrote:
> On 10.04.2025 15
V/r,
Daniel P. Smith
Apertus Solutions, LLC
On 4/16/25 09:33, Jan Beulich wrote:
On 16.04.2025 15:02, Daniel P. Smith wrote:
On 4/10/25 16:56, Jason Andryuk wrote:
On 2025-04-10 11:01, Jan Beulich wrote:
On 10.04.2025 15:09, Daniel P. Smith wrote:
On 4/9/25 02:24, Jan Beulich wrote:
On 0
On 16.04.2025 15:02, Daniel P. Smith wrote:
> On 4/10/25 16:56, Jason Andryuk wrote:
>> On 2025-04-10 11:01, Jan Beulich wrote:
>>> On 10.04.2025 15:09, Daniel P. Smith wrote:
On 4/9/25 02:24, Jan Beulich wrote:
> On 08.04.2025 18:07, Alejandro Vallejo wrote:
>> From: "Daniel P. Smith"
On 4/10/25 16:56, Jason Andryuk wrote:
On 2025-04-10 11:01, Jan Beulich wrote:
On 10.04.2025 15:09, Daniel P. Smith wrote:
On 4/9/25 02:24, Jan Beulich wrote:
On 08.04.2025 18:07, Alejandro Vallejo wrote:
From: "Daniel P. Smith"
To begin moving toward allowing the hypervisor to construct mo
On 2025-04-10 11:01, Jan Beulich wrote:
On 10.04.2025 15:09, Daniel P. Smith wrote:
On 4/9/25 02:24, Jan Beulich wrote:
On 08.04.2025 18:07, Alejandro Vallejo wrote:
From: "Daniel P. Smith"
To begin moving toward allowing the hypervisor to construct more than one
domain at boot, a container
On 2025-04-10 09:13, Daniel P. Smith wrote:
On 4/9/25 06:28, Alejandro Vallejo wrote:
On Wed Apr 9, 2025 at 7:24 AM BST, Jan Beulich wrote:
On 08.04.2025 18:07, Alejandro Vallejo wrote:
--- /dev/null
+++ b/xen/arch/x86/include/asm/boot-domain.h
@@ -0,0 +1,28 @@
+/* SPDX-License-Identifier: GPL
On 10.04.2025 15:09, Daniel P. Smith wrote:
> On 4/9/25 02:24, Jan Beulich wrote:
>> On 08.04.2025 18:07, Alejandro Vallejo wrote:
>>> From: "Daniel P. Smith"
>>>
>>> To begin moving toward allowing the hypervisor to construct more than one
>>> domain at boot, a container is needed for a domain's
On 4/9/25 06:28, Alejandro Vallejo wrote:
On Wed Apr 9, 2025 at 7:24 AM BST, Jan Beulich wrote:
On 08.04.2025 18:07, Alejandro Vallejo wrote:
From: "Daniel P. Smith"
To begin moving toward allowing the hypervisor to construct more than one
domain at boot, a container is needed for a domain's
On 4/9/25 02:24, Jan Beulich wrote:
On 08.04.2025 18:07, Alejandro Vallejo wrote:
From: "Daniel P. Smith"
To begin moving toward allowing the hypervisor to construct more than one
domain at boot, a container is needed for a domain's build information.
Introduce a new header, , that contains th
On 08.04.2025 18:07, Alejandro Vallejo wrote:
> From: "Daniel P. Smith"
>
> To begin moving toward allowing the hypervisor to construct more than one
> domain at boot, a container is needed for a domain's build information.
> Introduce a new header, , that contains the initial
> struct boot_domai
On Wed Apr 9, 2025 at 7:24 AM BST, Jan Beulich wrote:
> On 08.04.2025 18:07, Alejandro Vallejo wrote:
>> From: "Daniel P. Smith"
>>
>> To begin moving toward allowing the hypervisor to construct more than one
>> domain at boot, a container is needed for a domain's build information.
>> Introduce
12 matches
Mail list logo