All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: KVM call agenda for 2013-08-06
Date: Tue, 06 Aug 2013 15:30:55 +0200	[thread overview]
Message-ID: <874nb3hrow.fsf@elfo.elfo> (raw)



Hi

This is the agenda for today call:


* libvirt requirements for (eduardo)
   * Checking which CPU features are exposed/required by each CPU model
     + machine-type
   * Checking which CPU features are available on a given host
     (considering QEMU + kernel + host CPU capabilities)

Which option to use to remove the pvpanic device? (mst)
 -nodefaults
 -device
 -ioport



PD:  Remember that the conference code of the call has changed.  If you
haven't receive an invite,  let me know.

Thanks,  Juan.

WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] KVM call agenda for 2013-08-06
Date: Tue, 06 Aug 2013 15:30:55 +0200	[thread overview]
Message-ID: <874nb3hrow.fsf@elfo.elfo> (raw)



Hi

This is the agenda for today call:


* libvirt requirements for (eduardo)
   * Checking which CPU features are exposed/required by each CPU model
     + machine-type
   * Checking which CPU features are available on a given host
     (considering QEMU + kernel + host CPU capabilities)

Which option to use to remove the pvpanic device? (mst)
 -nodefaults
 -device
 -ioport



PD:  Remember that the conference code of the call has changed.  If you
haven't receive an invite,  let me know.

Thanks,  Juan.

             reply	other threads:[~2013-08-06 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 13:30 Juan Quintela [this message]
2013-08-06 13:30 ` [Qemu-devel] KVM call agenda for 2013-08-06 Juan Quintela
  -- strict thread matches above, loose matches on Subject: below --
2013-07-23 16:31 Juan Quintela
2013-08-06 10:07 ` Michael S. Tsirkin
2013-08-06 10:22   ` Mauro Sanna
2013-08-06 10:25     ` Michael S. Tsirkin

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=874nb3hrow.fsf@elfo.elfo \
    --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.