On Thu, Jul 10, 2025 at 08:39:18 +0200, Enrique Llorente Pastora wrote:
> On Thu, Jul 10, 2025 at 7:55 AM Peter Krempa wrote:
> >
> > On Wed, Jul 09, 2025 at 15:44:15 +0200, Enrique Llorente Pastora wrote:
> > > I have pushed a v3 with all the fixes for v2, clearly v2 was kind of
> > > half baked,
On Thu, Jul 10, 2025 at 7:55 AM Peter Krempa wrote:
>
> On Wed, Jul 09, 2025 at 15:44:15 +0200, Enrique Llorente Pastora wrote:
> > I have pushed a v3 with all the fixes for v2, clearly v2 was kind of
> > half baked, sorry about that.
>
> Before I reply to v3 I still want you to reply at least to
On Wed, Jul 09, 2025 at 15:44:15 +0200, Enrique Llorente Pastora wrote:
> I have pushed a v3 with all the fixes for v2, clearly v2 was kind of
> half baked, sorry about that.
Before I reply to v3 I still want you to reply at least to my question
about how the test result (.args) file ended up refe
>-Original Message-
>From: Daniel P. Berrangé
>Subject: Re: [PATCH v3 07/21] conf: Add tdx as launch security type
>
>On Mon, Jun 30, 2025 at 02:17:18PM +0800, Zhenzhong Duan wrote:
>> When 'tdx' is used, the VM will be launched with Intel TDX feature enabled.
>> TDX feature supports run
I have pushed a v3 with all the fixes for v2, clearly v2 was kind of
half baked, sorry about that.
On Mon, Jul 7, 2025 at 5:02 PM Peter Krempa wrote:
>
> On Mon, Jul 07, 2025 at 15:51:51 +0200, Peter Krempa via Devel wrote:
> > On Mon, Jul 07, 2025 at 14:52:09 +0200, Enrique Llorente via Devel wr
On Wed, Jul 09, 2025 at 01:42:20PM +0100, Mark Cave-Ayland wrote:
> On 09/07/2025 12:10, Daniel P. Berrangé wrote:
>
> > On Wed, Jul 09, 2025 at 11:27:45AM +0100, Daniel P. Berrangé via Devel
> > wrote:
> > > On Mon, Jul 07, 2025 at 02:19:10PM +0100, Mark Cave-Ayland wrote:
> > > > Hi all,
> > >
On 09/07/2025 12:10, Daniel P. Berrangé wrote:
On Wed, Jul 09, 2025 at 11:27:45AM +0100, Daniel P. Berrangé via Devel wrote:
On Mon, Jul 07, 2025 at 02:19:10PM +0100, Mark Cave-Ayland wrote:
Hi all,
I'm currently looking at how libvirt can be used to clone a saved VM, and
have been focusing o
This adds support for custom command line arguments for the passt
backend, similar to qemu:commandline. The feature allows passing
additional arguments to the passt process for development and testing
purposes.
The implementation:
- Adds a passt XML namespace for custom arguments
- Properly taints
On Wed, Jul 09, 2025 at 11:27:45AM +0100, Daniel P. Berrangé via Devel wrote:
> On Mon, Jul 07, 2025 at 02:19:10PM +0100, Mark Cave-Ayland wrote:
> > Hi all,
> >
> > I'm currently looking at how libvirt can be used to clone a saved VM, and
> > have been focusing on the previous thread on this topi
>-Original Message-
>From: Daniel P. Berrangé
>Subject: Re: [PATCH v3 14/21] qemu: Add FakeReboot support for TDX guest
>
>On Wed, Jul 09, 2025 at 09:44:42AM +, Duan, Zhenzhong wrote:
>>
>>
>> >-Original Message-
>> >From: Daniel P. Berrangé
>> >Subject: Re: [PATCH v3 14/21]
On Mon, Jul 07, 2025 at 02:19:10PM +0100, Mark Cave-Ayland wrote:
> Hi all,
>
> I'm currently looking at how libvirt can be used to clone a saved VM, and
> have been focusing on the previous thread on this topic at
> https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/YXN2L2PYL
>-Original Message-
>From: Daniel P. Berrangé
>Subject: Re: [PATCH v3 12/21] conf: Add Intel TDX Quote Generation
>Service(QGS) support
>
>On Wed, Jul 09, 2025 at 02:52:05AM +, Duan, Zhenzhong wrote:
>>
>>
>> >-Original Message-
>> >From: Daniel P. Berrangé
>> >Subject: Re:
>-Original Message-
>From: Daniel P. Berrangé
>Subject: Re: [PATCH v3 21/21] docs: domain: Add documentation for Intel
>TDX guest
>
>On Mon, Jun 30, 2025 at 02:17:32PM +0800, Zhenzhong Duan wrote:
>> Signed-off-by: Zhenzhong Duan
>> ---
>> docs/formatdomain.rst | 63
>++
On Mon, Jun 30, 2025 at 02:17:18PM +0800, Zhenzhong Duan wrote:
> When 'tdx' is used, the VM will be launched with Intel TDX feature enabled.
> TDX feature supports running encrypted VM (Trust Domain, TD) under the
> control of KVM. A TD runs in a CPU model which protects the confidentiality
> of i
On Wed, Jul 09, 2025 at 05:58:03AM -0400, Andrea Bolognani wrote:
> On Wed, Jul 09, 2025 at 09:53:40AM +0100, Daniel P. Berrangé via Devel wrote:
> > On Wed, Jul 09, 2025 at 10:29:32AM +0200, Hector Cao wrote:
> > > > >3. if that fails too, load the msr module and try again;
> > > >
> > > > It
On Wed, Jul 09, 2025 at 09:53:40AM +0100, Daniel P. Berrangé via Devel wrote:
> On Wed, Jul 09, 2025 at 10:29:32AM +0200, Hector Cao wrote:
> > > >3. if that fails too, load the msr module and try again;
> > >
> > > It seems like a modules-load file is simpler than having this manual
> > > kmod
On Wed, Jul 09, 2025 at 09:44:42AM +, Duan, Zhenzhong wrote:
>
>
> >-Original Message-
> >From: Daniel P. Berrangé
> >Subject: Re: [PATCH v3 14/21] qemu: Add FakeReboot support for TDX guest
> >
> >On Mon, Jun 30, 2025 at 02:17:25PM +0800, Zhenzhong Duan wrote:
> >> Utilize the exist
>-Original Message-
>From: Daniel P. Berrangé
>Subject: Re: [PATCH v3 14/21] qemu: Add FakeReboot support for TDX guest
>
>On Mon, Jun 30, 2025 at 02:17:25PM +0800, Zhenzhong Duan wrote:
>> Utilize the existing fake reboot mechanism to do reboot for TDX guest.
>>
>> Different from normal
On Wed, Jul 09, 2025 at 09:35:02AM +, Duan, Zhenzhong wrote:
>
>
> >-Original Message-
> >From: Daniel P. Berrangé
> >Subject: Re: [PATCH v3 00/21] LIBVIRT: X86: TDX support
> >
> >On Wed, Jul 09, 2025 at 08:55:48AM +, Duan, Zhenzhong wrote:
> >>
> >>
> >> >-Original Message-
>-Original Message-
>From: Daniel P. Berrangé
>Subject: Re: [PATCH v3 00/21] LIBVIRT: X86: TDX support
>
>On Wed, Jul 09, 2025 at 08:55:48AM +, Duan, Zhenzhong wrote:
>>
>>
>> >-Original Message-
>> >From: Daniel P. Berrangé
>> >Subject: Re: [PATCH v3 00/21] LIBVIRT: X86: TD
From: Hector Cao
Add documentation on the way libvirt displays the Host CPU
model and capabilities (features). There is an implicit
expection from users to get the CPU model name matching the
CPU model they are running on, however, this does not happen
most of the time. As a consequence, having a
Hello,
This is a follow-up of the submission:
https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/EZBLO5CIGC3FTI5J72WNVAKWPSNQFLCY/
Based on Jiri's feedback, it is better to tackle this situation by
documentation. You can find here a proposal for the documentation.
The section
On Wed, Jul 09, 2025 at 08:55:48AM +, Duan, Zhenzhong wrote:
>
>
> >-Original Message-
> >From: Daniel P. Berrangé
> >Subject: Re: [PATCH v3 00/21] LIBVIRT: X86: TDX support
> >
> >On Mon, Jun 30, 2025 at 02:17:11PM +0800, Zhenzhong Duan wrote:
> >> Hi,
> >>
> >> This series brings l
>-Original Message-
>From: Daniel P. Berrangé
>Subject: Re: [PATCH v3 00/21] LIBVIRT: X86: TDX support
>
>On Mon, Jun 30, 2025 at 02:17:11PM +0800, Zhenzhong Duan wrote:
>> Hi,
>>
>> This series brings libvirt the x86 TDX support.
>>
>> * What's TDX?
>> TDX stands for Trust Domain Extens
On Wed, Jul 09, 2025 at 10:29:32AM +0200, Hector Cao wrote:
> > >3. if that fails too, load the msr module and try again;
> >
> > It seems like a modules-load file is simpler than having this manual
> > kmod load + repeat.
> >
> >
> Is this modules-load file deployed by libvirt itself or are yo
Thanks Daniel,
On Wed, Jul 9, 2025 at 10:17 AM Daniel P. Berrangé
wrote:
> On Wed, Jul 09, 2025 at 10:03:26AM +0200, Hector Cao wrote:
> > Hello,
> >
> > This mail is a Request for Comment.
> >
> > On recent Intel CPUs, some of the CPU features (mostly vmx-* subfeatures)
> > are listed and contr
On Wed, Jul 09, 2025 at 10:03:26AM +0200, Hector Cao wrote:
> Hello,
>
> This mail is a Request for Comment.
>
> On recent Intel CPUs, some of the CPU features (mostly vmx-* subfeatures)
> are listed and controlled
> via the MSRs (Model Specific Registers) instead of the traditional CPUID
> instr
Hello,
This mail is a Request for Comment.
On recent Intel CPUs, some of the CPU features (mostly vmx-* subfeatures)
are listed and controlled
via the MSRs (Model Specific Registers) instead of the traditional CPUID
instruction method.
Right now, libvirt reads the MSR's values via /dev/cpu/*/cpu
On Wed, Jul 09, 2025 at 03:13:11PM +0800, Xiaoyao Li wrote:
> On 7/9/2025 2:58 PM, Daniel P. Berrangé wrote:
> > > > Could we rename "policy" to "attributes", or more precisely
> > > > "tdAttributes"? It's not intuitive for users to connect "policy" with
> > > > "TD attributes".
> > > Will use "att
On 7/9/2025 2:58 PM, Daniel P. Berrangé wrote:
Could we rename "policy" to "attributes", or more precisely
"tdAttributes"? It's not intuitive for users to connect "policy" with
"TD attributes".
Will use "attributes" as QAPI exposes "attributes".
IMHO 'policy' is preferrable as it is consistent
30 matches
Mail list logo
