From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: quintela@redhat.com, kvm-devel <kvm@vger.kernel.org>,
qemu-devel@nongnu.org
Cc: Mirela Grujic <mirela.grujic@greensocs.com>
Subject: Re: KVM call minutes for 2022-01-25
Date: Tue, 25 Jan 2022 17:54:43 +0100 [thread overview]
Message-ID: <6ba8efb0-b4e0-dbda-e1f1-fac9dfa847fd@amsat.org> (raw)
In-Reply-To: <87k0enrcr0.fsf@secure.mitica>
On 25/1/22 17:39, Juan Quintela wrote:
>
> Hi
>
> Today we have the KVM devel call. We discussed how to create machines
> from QMP without needing to recompile QEMU.
>
>
> Three different problems:
> - startup QMP (*)
> not discussed today
> - one binary or two
> not discussed today
> - being able to create machines dynamically.
> everybody agrees that we want this. Problem is how.
> - current greensocs approach
> - interested for all architectures, they need a couple of them
>
> what greensocs have:
> - python program that is able to read a blob that have a device tree from the blob
> - basically the machine type is empty and is configured from there
> - 100 machines around 400 devices models
> - Need to do the configuration before the machine construction happens
> - different hotplug/coldplug
> - How to describe devices that have multiple connections
- problem realizing objects that have inter-dependent link properties
Mirela, you mention an issue with TYPE_CPU_CLUSTER / TYPE_CPU, is that
an example of this qom inter-link problem?
> As the discussion is quite complicated, here is the recording of it.
>
> Later, Juan.
>
>
> https://redhat.bluejeans.com/m/TFyaUsLqt3T/?share=True
>
> *: We will talk about this on the next call
>
>
next prev parent reply other threads:[~2022-01-25 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 16:39 KVM call minutes for 2022-01-25 Juan Quintela
2022-01-25 16:41 ` Juan Quintela
2022-01-27 11:34 ` Markus Armbruster
2022-01-25 16:54 ` Philippe Mathieu-Daudé [this message]
2022-01-26 16:21 ` Mirela Grujic
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=6ba8efb0-b4e0-dbda-e1f1-fac9dfa847fd@amsat.org \
--to=f4bug@amsat.org \
--cc=kvm@vger.kernel.org \
--cc=mirela.grujic@greensocs.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox