>>> On 11.02.15 at 18:04, wrote:
> On 11/02/15 07:56, Jan Beulich wrote:
> On 10.02.15 at 20:30, wrote:
>>> While coding this is up I have hit issues that I need input on:
>>>
>>> As a HVM_PARAM_ item, I would assume I should be following
>>> what HVM_PARAM_VIRIDIAN does. It has this comment
On 11/02/15 07:56, Jan Beulich wrote:
On 10.02.15 at 20:30, wrote:
>> While coding this is up I have hit issues that I need input on:
>>
>> As a HVM_PARAM_ item, I would assume I should be following
>> what HVM_PARAM_VIRIDIAN does. It has this comment:
>>
>> case HVM_PARAM_VIRIDI
>>> On 10.02.15 at 20:30, wrote:
> While coding this is up I have hit issues that I need input on:
>
> As a HVM_PARAM_ item, I would assume I should be following
> what HVM_PARAM_VIRIDIAN does. It has this comment:
>
> case HVM_PARAM_VIRIDIAN:
> /* This should only e
On 01/26/15 10:58, Don Slutz wrote:
> On 01/22/15 03:32, Jan Beulich wrote:
> On 21.01.15 at 18:52, wrote:
>>> On 01/16/15 05:09, Jan Beulich wrote:
>>> On 03.10.14 at 00:40, wrote:
> This is a new domain_create() flag, DOMCRF_vmware_port. It is
> passed to domctl as XEN_DOMCTL_C
