Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-25 Thread Eduardo Habkost
On Fri, Mar 01, 2013 at 11:56:00PM +0100, Jiri Denemark wrote: [...] = Getting information about CPU models = Requirement: libvirt uses the predefined CPU models from QEMU, but it needs to be able to query for CPU model details, to find out how it can create a VM that

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-04 Thread Daniel P. Berrange
On Fri, Mar 01, 2013 at 03:58:18PM -0300, Eduardo Habkost wrote: On Fri, Mar 01, 2013 at 07:31:46PM +0100, Andreas Färber wrote: Am 01.03.2013 14:12, schrieb Jiri Denemark: On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: = Listing CPU models = Requirement: libvirt

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Jiri Denemark
On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: Hi, After a long time trying to figure out the proper modelling inside QEMU, I believe the plans are now clearer in QEMU, so it's time to coordinate more closely with libvirt to try to make use of the new stuff. I tried to

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Jiri Denemark
On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: = Querying host capabilities = Requirement: libvirt needs to know which feature can really be enabled, before it tries to start a VM, and before it tries to start a live-migration process. The set of available capabilities

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Eduardo Habkost
On Fri, Mar 01, 2013 at 02:12:38PM +0100, Jiri Denemark wrote: On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: Hi, After a long time trying to figure out the proper modelling inside QEMU, I believe the plans are now clearer in QEMU, so it's time to coordinate more

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Eduardo Habkost
On Fri, Mar 01, 2013 at 02:28:37PM +0100, Jiri Denemark wrote: On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: = Querying host capabilities = Requirement: libvirt needs to know which feature can really be enabled, before it tries to start a VM, and before it tries to

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Andreas Färber
Am 01.03.2013 14:12, schrieb Jiri Denemark: On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: = Listing CPU models = Requirement: libvirt needs to know which CPU models are available to be used with the -cpu option. Current problem: libvirt relies on help output parsing for

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Daniel P. Berrange
On Fri, Mar 01, 2013 at 07:31:46PM +0100, Andreas Färber wrote: Am 01.03.2013 14:12, schrieb Jiri Denemark: On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: = Listing CPU models = Requirement: libvirt needs to know which CPU models are available to be used with the -cpu

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Eduardo Habkost
On Fri, Mar 01, 2013 at 07:31:46PM +0100, Andreas Färber wrote: Am 01.03.2013 14:12, schrieb Jiri Denemark: On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: = Listing CPU models = Requirement: libvirt needs to know which CPU models are available to be used with the -cpu

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Eduardo Habkost
On Fri, Mar 01, 2013 at 06:34:31PM +, Daniel P. Berrange wrote: On Fri, Mar 01, 2013 at 07:31:46PM +0100, Andreas Färber wrote: Am 01.03.2013 14:12, schrieb Jiri Denemark: On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote: = Listing CPU models = Requirement: libvirt

Re: [Qemu-devel] libvirt-QEMU interfaces for CPU models

2013-03-01 Thread Jiri Denemark
On Fri, Mar 01, 2013 at 12:02:07 -0300, Eduardo Habkost wrote: On Fri, Mar 01, 2013 at 02:12:38PM +0100, Jiri Denemark wrote: Definitely, we plan to start using enforce flag as soon as we have better CPU probing interface with QEMU. Since libvirt does not currently consult CPU specs with