From: Juan Quintela <quintela@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>
Cc: qemu-devel@nongnu.org
Subject: Re: KVM call minutes for 2022-01-25
Date: Tue, 25 Jan 2022 17:41:00 +0100 [thread overview]
Message-ID: <87a6fjrco3.fsf@secure.mitica> (raw)
In-Reply-To: <87k0enrcr0.fsf@secure.mitica> (Juan Quintela's message of "Tue, 25 Jan 2022 17:39:15 +0100")
Juan Quintela <quintela@redhat.com> 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
>
> As the discussion is quite complicated, here is the recording of it.
>
> Later, Juan.
>
>
> https://redhat.bluejeans.com/m/TFyaUsLqt3T/?share=True
And now the link that works without a login.
https://bluejeans.com/s/KetOlwoxLa3
Later, Juan.
next prev parent reply other threads:[~2022-01-25 16:44 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 [this message]
2022-01-27 11:34 ` Markus Armbruster
2022-01-25 16:54 ` Philippe Mathieu-Daudé
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=87a6fjrco3.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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.