From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Luigi Leonardi <leonardi@redhat.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH] igvm: add command line parameter support
Date: Thu, 1 Oct 2026 09:12:06 +0100 [thread overview]
Message-ID: <ar4V1i54Czo45lQh@redhat.com> (raw)
In-Reply-To: <87qzi9alml.fsf@pond.sub.org>
On Thu, Oct 01, 2026 at 10:08:34AM +0200, Markus Armbruster wrote:
> Luigi Leonardi <leonardi@redhat.com> writes:
>
> > Add a "cmdline" property to the igvm-cfg object and a handler for the
> > IGVM_VHT_COMMAND_LINE directive, which copies the string into the
> > parameter area the directive points at.
> >
> > This command line is intended for the component running at VMPL0, such
> > as SVSM, rather than for the guest OS, whose own command line still
> > comes from -append. SVSM can use it to select the serial port it logs
> > to, for example.
> >
> > Signed-off-by: Luigi Leonardi <leonardi@redhat.com>
>
> [...]
>
> > diff --git a/qapi/qom.json b/qapi/qom.json
> > index 5895c97750..d56bdef561 100644
> > --- a/qapi/qom.json
> > +++ b/qapi/qom.json
> > @@ -1004,11 +1004,15 @@
> > #
> > # @file: IGVM file to use to configure guest
> > #
> > +# @cmdline: command line for the software loaded from the IGVM file,
> > +# rather than for the guest OS. Ignored if the IGVM file does
> > +# not ask for one. (since 11.2)
> > +#
> > # Since: 10.1
> > ##
> > { 'struct': 'IgvmCfgProperties',
> > 'if': 'CONFIG_IGVM',
> > - 'data': { 'file': 'str' } }
> > + 'data': { 'file': 'str', '*cmdline': 'str' } }
> >
> > ##
> > # @SevCommonProperties:
>
> How is @cmdline going to be parsed? By a shell?
This is something passed to the guest workflow. ie a kernel command
line string.
> For what it's worth, MigrationExecCommand uses ['str']. Such values can
> be passed to exec()-like functions without parsing.
In this case we should treat 'cmdline' as an opaque strnig and not
try to place any semantics on its expected syntax.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-10-01 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 14:35 [PATCH] igvm: add command line parameter support Luigi Leonardi
2026-10-01 8:08 ` Markus Armbruster
2026-10-01 8:12 ` Daniel P. Berrangé [this message]
2026-10-01 8:27 ` Markus Armbruster
2026-10-06 14:13 ` Luigi Leonardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ar4V1i54Czo45lQh@redhat.com \
--to=berrange@redhat.com \
--cc=anisinha@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=leonardi@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.