On Thu, Jan 11, 2018 at 4:58 AM, Eduardo Habkost wrote:
> On Thu, Jan 11, 2018 at 11:25:08AM +0100, Igor Mammedov wrote:
>> On Wed, 10 Jan 2018 19:48:00 -0200
>> Eduardo Habkost wrote:
>>
>> > On Wed, Jan 10, 2018 at 01:30:29PM -0800, Alistair Francis
On Thu, Jan 11, 2018 at 11:25:08AM +0100, Igor Mammedov wrote:
> On Wed, 10 Jan 2018 19:48:00 -0200
> Eduardo Habkost wrote:
>
> > On Wed, Jan 10, 2018 at 01:30:29PM -0800, Alistair Francis wrote:
> > > On Thu, Dec 28, 2017 at 6:59 AM, Eduardo Habkost
On Wed, 10 Jan 2018 19:48:00 -0200
Eduardo Habkost wrote:
> On Wed, Jan 10, 2018 at 01:30:29PM -0800, Alistair Francis wrote:
> > On Thu, Dec 28, 2017 at 6:59 AM, Eduardo Habkost
> > wrote:
> > > On Thu, Dec 28, 2017 at 02:39:31PM +0100, Igor
On Wed, Jan 10, 2018 at 01:30:29PM -0800, Alistair Francis wrote:
> On Thu, Dec 28, 2017 at 6:59 AM, Eduardo Habkost wrote:
> > On Thu, Dec 28, 2017 at 02:39:31PM +0100, Igor Mammedov wrote:
> >> On Fri, 22 Dec 2017 11:47:00 -0800
> >> Alistair Francis
On Thu, Dec 28, 2017 at 6:59 AM, Eduardo Habkost wrote:
> On Thu, Dec 28, 2017 at 02:39:31PM +0100, Igor Mammedov wrote:
>> On Fri, 22 Dec 2017 11:47:00 -0800
>> Alistair Francis wrote:
>>
>> > On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
On Thu, Dec 28, 2017 at 02:39:31PM +0100, Igor Mammedov wrote:
> On Fri, 22 Dec 2017 11:47:00 -0800
> Alistair Francis wrote:
>
> > On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
> > wrote:
> > > On Wed, Dec 20, 2017 at 2:06 PM,
On Fri, 22 Dec 2017 11:47:00 -0800
Alistair Francis wrote:
> On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
> wrote:
> > On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost
> > wrote:
> >> On Tue, Dec 19, 2017 at
On Fri, Dec 22, 2017 at 11:47:00AM -0800, Alistair Francis wrote:
> On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
> wrote:
> > On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost
> > wrote:
> >> On Tue, Dec 19, 2017 at 05:03:59PM -0800,
On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
wrote:
> On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost wrote:
>> On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote:
>>> On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis
>>>
On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost wrote:
> On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote:
>> On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis
>> wrote:
>> > On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell
On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote:
> On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis
> wrote:
> > On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell
> > wrote:
> >> On 20 December 2017 at 00:27, Alistair Francis
On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis
wrote:
> On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell
> wrote:
>> On 20 December 2017 at 00:27, Alistair Francis
>> wrote:
>>> There are numorous QEMU
On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell wrote:
> On 20 December 2017 at 00:27, Alistair Francis
> wrote:
>> There are numorous QEMU machines that only have a single or a handful of
>> valid CPU options. To simplyfy the management of
On 20 December 2017 at 00:27, Alistair Francis
wrote:
> There are numorous QEMU machines that only have a single or a handful of
> valid CPU options. To simplyfy the management of specificying which CPU
> is/isn't valid let's create a property that can be set in the
There are numorous QEMU machines that only have a single or a handful of
valid CPU options. To simplyfy the management of specificying which CPU
is/isn't valid let's create a property that can be set in the machine
init. We can then check to see if the user supplied CPU is in that list
or not.
I
15 matches
Mail list logo