KVM call minutes for 2022-01-25
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
*: We will talk about this on the next call
Quoted 24 lines · Juan Quintela
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 themwhat 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
Quoted 6 lines
As the discussion is quite complicated, here is the recording of it.
Later, Juan.
And now the link that works without a login.
https://bluejeans.com/s/KetOlwoxLa3
Later, Juan.
Quoted 17 lines · Juan Quintela
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
Quoted 7 lines
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?
Quoted 10 lines
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
Quoted 27 lines · Philippe Mathieu-Daudé
Quoted 17 lines · Juan Quintela
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 themQuoted 8 lines
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
Quoted 5 lines
- 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?
Yes, for cluster/cpu specifically it is the parent-child relationship between objects.
Quoted 11 lines
Quoted 10 lines
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
Quoted 17 lines · Juan Quintela
Quoted 16 lines · Juan Quintela
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
Quoted 7 lines
Quoted 7 lines
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
Nice demo, by the way! I assume you're going to post patches. Feel free to post as RFC when the work isn't ready for merge, but could use review, or could make our discussions more productive.
[...]