Fortnightly KVM call for 2023-02-07
Hi
Please, send any topic that you are interested in covering in the next call in 2 weeks.
We have already topics:
- single qemu binary
People on previous call (today) asked if Markus, Paolo and Peter could be there on next one to further discuss the topic.
- Huge Memory guests
Will send a separate email with the questions that we want to discuss later during the week.
After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics.
Call details:
By popular demand, a google calendar public entry with it
(Let me know if you have any problems with the calendar entry. I just gave up about getting right at the same time CEST, CET, EDT and DST).
If you need phone number details, contact me privately
Thanks, Juan.
Quoted 10 lines · Juan Quintela
Hi
Please, send any topic that you are interested in covering in the next call in 2 weeks.
We have already topics:
- single qemu binary
People on previous call (today) asked if Markus, Paolo and Peter could be there on next one to further discuss the topic.
Quoted 4 lines
- Huge Memory guests
Will send a separate email with the questions that we want to discuss later during the week.
Hi folks
Just one addition for next call.
"Wang, Wei W" <[email protected]> has asked to give a presentation about a new feature:
TDX Live Migration
He wanted 1h, but I told him that we already have two topics for next call. So we leave it in half an hour and will do the rest of the presentation in a following call.
Later, Juan.
Quoted 16 lines
After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics.
Call details:
By popular demand, a google calendar public entry with it
(Let me know if you have any problems with the calendar entry. I just gave up about getting right at the same time CEST, CET, EDT and DST).
If you need phone number details, contact me privately
Thanks, Juan.
Sean Christopherson
reviewerQuoted 8 lines · Juan Quintela
Please, send any topic that you are interested in covering in the next call in 2 weeks.
We have already topics:
- single qemu binary
People on previous call (today) asked if Markus, Paolo and Peter could be there on next one to further discuss the topic.
Quoted 7 lines
- Huge Memory guests
Will send a separate email with the questions that we want to discuss later during the week.
After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics.
Hi Juan!
I have a somewhat odd request: can I convince you to rename "KVM call" to something like "QEMU+KVM call"?
I would like to kickstart a recurring public meeting/forum that (almost) exclusively targets internal KVM development, but I don't to cause confusion and definitely don't want to usurp your meeting. The goal/purpose of the KVM-specific meeting would be to do design reviews, syncs, etc. on KVM internals and things like KVM selftests, while, IIUC, the current "KVM call" is aimed at at the entire KVM+QEMU+VFIO ecosystem.
Thanks!
Quoted 22 lines · Sean Christopherson
Quoted 8 lines · Juan Quintela
Please, send any topic that you are interested in covering in the next call in 2 weeks.
We have already topics:
- single qemu binary
People on previous call (today) asked if Markus, Paolo and Peter could be there on next one to further discuss the topic.Quoted 7 lines
- Huge Memory guests
Will send a separate email with the questions that we want to discuss later during the week.
After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics.
Hi Juan!
I have a somewhat odd request: can I convince you to rename "KVM call" to something like "QEMU+KVM call"?
Quoted 7 lines
I would like to kickstart a recurring public meeting/forum that (almost) exclusively targets internal KVM development, but I don't to cause confusion and definitely don't want to usurp your meeting. The goal/purpose of the KVM-specific meeting would be to do design reviews, syncs, etc. on KVM internals and things like KVM selftests, while, IIUC, the current "KVM call" is aimed at at the entire KVM+QEMU+VFIO ecosystem.
Thanks!
Sounds fair to me.
Quoted 19 lines · Sean Christopherson
Quoted 8 lines · Juan Quintela
Please, send any topic that you are interested in covering in the next call in 2 weeks.
We have already topics:
- single qemu binary
People on previous call (today) asked if Markus, Paolo and Peter could be there on next one to further discuss the topic.Quoted 7 lines
- Huge Memory guests
Will send a separate email with the questions that we want to discuss later during the week.
After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics.
Hi Juan!
Quoted 8 lines
I have a somewhat odd request: can I convince you to rename "KVM call" to something like "QEMU+KVM call"?
I would like to kickstart a recurring public meeting/forum that (almost) exclusively targets internal KVM development, but I don't to cause confusion and definitely don't want to usurp your meeting. The goal/purpose of the KVM-specific meeting would be to do design reviews, syncs, etc. on KVM internals and things like KVM selftests, while, IIUC, the current "KVM call" is aimed at at the entire KVM+QEMU+VFIO ecosystem.
I can do that.
I would have told you that you could use our slots, but right now we are quite low on slots.
If nobody objects, I will change that for the next call.
Later, Juan.
Sean Christopherson
reviewerQuoted 29 lines · Juan Quintela
Quoted 19 lines · Sean Christopherson
Quoted 8 lines · Juan Quintela
Please, send any topic that you are interested in covering in the next call in 2 weeks.
We have already topics:
- single qemu binary
People on previous call (today) asked if Markus, Paolo and Peter could be there on next one to further discuss the topic.Quoted 7 lines
- Huge Memory guests
Will send a separate email with the questions that we want to discuss later during the week.
After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics.
Hi Juan!
Quoted 8 lines
I have a somewhat odd request: can I convince you to rename "KVM call" to something like "QEMU+KVM call"?
I would like to kickstart a recurring public meeting/forum that (almost) exclusively targets internal KVM development, but I don't to cause confusion and definitely don't want to usurp your meeting. The goal/purpose of the KVM-specific meeting would be to do design reviews, syncs, etc. on KVM internals and things like KVM selftests, while, IIUC, the current "KVM call" is aimed at at the entire KVM+QEMU+VFIO ecosystem.
Quoted 5 lines
I can do that.
I would have told you that you could use our slots, but right now we are quite low on slots.If nobody objects, I will change that for the next call.
Thanks, much appreciated!