All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>,
	qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	Paul Moore <pmoore@redhat.com>,
	peter.maydell@linaro.org
Subject: Fortnightly KVM call for 2023-02-07
Date: Tue, 24 Jan 2023 16:03:05 +0100	[thread overview]
Message-ID: <87o7qof00m.fsf@secure.mitica> (raw)



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

  https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=NWR0NWppODdqNXFyYzAwbzYza3RxN2dob3VfMjAyMjEwMThUMTMwMDAwWiBlZ2VkN2NraTA1bG11MXRuZ3ZrbDN0aGlkc0Bn&tmsrc=eged7cki05lmu1tngvkl3thids%40group.calendar.google.com&scp=ALL

(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.


             reply	other threads:[~2023-01-24 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 15:03 Juan Quintela [this message]
2023-02-01 18:39 ` Fortnightly KVM call for 2023-02-07 Juan Quintela
2023-02-23 22:04 ` Sean Christopherson
2023-02-24  6:28   ` Markus Armbruster
2023-02-28 11:46   ` Juan Quintela
2023-03-07 16:22     ` Sean Christopherson

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=87o7qof00m.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=pmoore@redhat.com \
    --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.