On Tue, Jul 20, 2010 at 11:04:01AM +0200, Jiri Denemark wrote:
> > > > > And how about adding policy='disable' attribute, so that I can ask
> > > > > virConnectCompareCPU to ignore this particular incompatibility, as I
> > > > > do
> > > > > with items?
> > > >
> > > > Just don't use tag in you
> > > > And how about adding policy='disable' attribute, so that I can ask
> > > > virConnectCompareCPU to ignore this particular incompatibility, as I do
> > > > with items?
> > >
> > > Just don't use tag in your XML.
> > >
> > > In other words, if you specify in domain XML (or it's cpu
> >
On Mon, Jul 19, 2010 at 09:58:35PM +0300, Dan Kenigsberg wrote:
> On Mon, Jul 19, 2010 at 02:40:40PM +0200, Jiri Denemark wrote:
> > > > By specifying element in CPU requirements a guest can be
> > > > restricted to run only on CPUs by a given vendor. Host CPU vendor is
> > > > also specified in c
On Mon, Jul 19, 2010 at 02:40:40PM +0200, Jiri Denemark wrote:
> > > By specifying element in CPU requirements a guest can be
> > > restricted to run only on CPUs by a given vendor. Host CPU vendor is
> > > also specified in capabilities XML.
> > >
> > > The vendor is checked when migrating a gue
> > By specifying element in CPU requirements a guest can be
> > restricted to run only on CPUs by a given vendor. Host CPU vendor is
> > also specified in capabilities XML.
> >
> > The vendor is checked when migrating a guest but it's not forced, i.e.,
> > a guest configured without element can
On Fri, Jul 02, 2010 at 11:16:22PM +0200, Jiri Denemark wrote:
> By specifying element in CPU requirements a guest can be
> restricted to run only on CPUs by a given vendor. Host CPU vendor is
> also specified in capabilities XML.
>
> The vendor is checked when migrating a guest but it's not forc
> > By specifying element in CPU requirements a guest can be
> > restricted to run only on CPUs by a given vendor. Host CPU vendor is
> > also specified in capabilities XML.
> >
> > The vendor is checked when migrating a guest but it's not forced, i.e.,
> > a guest configured without element can
On Fri, Jul 02, 2010 at 11:16:22PM +0200, Jiri Denemark wrote:
> By specifying element in CPU requirements a guest can be
> restricted to run only on CPUs by a given vendor. Host CPU vendor is
> also specified in capabilities XML.
>
> The vendor is checked when migrating a guest but it's not forc
By specifying element in CPU requirements a guest can be
restricted to run only on CPUs by a given vendor. Host CPU vendor is
also specified in capabilities XML.
The vendor is checked when migrating a guest but it's not forced, i.e.,
a guest configured without element can be freely migrated.
---
