Re: [libvirt] [PATCH] Set sensible defaults for cpu match and feature policy

2010-09-23 Thread Daniel Veillard
On Wed, Sep 22, 2010 at 05:50:10PM +0100, Daniel P. Berrange wrote: > To enable the CPU XML from the capabilities to be pasted directly > into the guest XML with no editing, pick a sensible default for > match and feature policy. The CPU match will be exact and the > feature policy will be require.

Re: [libvirt] [PATCH] Set sensible defaults for cpu match and feature policy

2010-09-22 Thread Eric Blake
On 09/22/2010 10:50 AM, Daniel P. Berrange wrote: To enable the CPU XML from the capabilities to be pasted directly into the guest XML with no editing, pick a sensible default for match and feature policy. The CPU match will be exact and the feature policy will be require. This should ensure safe

[libvirt] [PATCH] Set sensible defaults for cpu match and feature policy

2010-09-22 Thread Daniel P. Berrange
To enable the CPU XML from the capabilities to be pasted directly into the guest XML with no editing, pick a sensible default for match and feature policy. The CPU match will be exact and the feature policy will be require. This should ensure safety for migration and give DWIM semantics for users

Re: [libvirt] [PATCH] Set sensible defaults for cpu match and feature policy

2010-09-22 Thread Jiri Denemark
> To enable the CPU XML from the capabilities to be pasted directly > into the guest XML with no editing, pick a sensible default for > match and feature policy. The CPU match will be exact and the > feature policy will be require. This should ensure safety for > migration and give DWIM semantics f

[libvirt] [PATCH] Set sensible defaults for cpu match and feature policy

2010-09-22 Thread Daniel P. Berrange
To enable the CPU XML from the capabilities to be pasted directly into the guest XML with no editing, pick a sensible default for match and feature policy. The CPU match will be exact and the feature policy will be require. This should ensure safety for migration and give DWIM semantics for users