>>> On 06.04.17 at 10:52, wrote:
> On 05/04/17 18:41, Tamas K Lengyel wrote:
>> On Wed, Apr 5, 2017 at 9:04 AM, George Dunlap
>> wrote:
>>> On Tue, Apr 4, 2017 at 4:24 PM, Tamas K Lengyel
>>> wrote:
>>> "mixed"
>>>
>>> Both external domains and the guest itself have full access to altp2m
>>> fu
On 05/04/17 18:41, Tamas K Lengyel wrote:
> On Wed, Apr 5, 2017 at 9:04 AM, George Dunlap
> wrote:
>> On Tue, Apr 4, 2017 at 4:24 PM, Tamas K Lengyel
>> wrote:
>> "mixed"
>>
>> Both external domains and the guest itself have full access to altp2m
>> functionality
>>
>> "limited"
>>
>> External
On Wed, Apr 5, 2017 at 9:04 AM, George Dunlap wrote:
> On Tue, Apr 4, 2017 at 4:24 PM, Tamas K Lengyel
> wrote:
>> Currently setting altp2mhvm=1 in the domain configuration allows access to
>> the
>> altp2m interface for both in-guest and external privileged tools. This poses
>> a problem for us
On Tue, Apr 4, 2017 at 4:24 PM, Tamas K Lengyel
wrote:
> Currently setting altp2mhvm=1 in the domain configuration allows access to the
> altp2m interface for both in-guest and external privileged tools. This poses
> a problem for use-cases where only external access should be allowed,
> requirin
>>> On 04.04.17 at 17:24, wrote:
> Currently setting altp2mhvm=1 in the domain configuration allows access to the
> altp2m interface for both in-guest and external privileged tools. This poses
> a problem for use-cases where only external access should be allowed,
> requiring
> the user to compil
>>> On 04.04.17 at 17:24, wrote:
> Currently setting altp2mhvm=1 in the domain configuration allows access to the
> altp2m interface for both in-guest and external privileged tools. This poses
> a problem for use-cases where only external access should be allowed,
> requiring
> the user to compil
On 04/04/2017 11:24 AM, Tamas K Lengyel wrote:
Currently setting altp2mhvm=1 in the domain configuration allows access to the
altp2m interface for both in-guest and external privileged tools. This poses
a problem for use-cases where only external access should be allowed, requiring
the user to co
Currently setting altp2mhvm=1 in the domain configuration allows access to the
altp2m interface for both in-guest and external privileged tools. This poses
a problem for use-cases where only external access should be allowed, requiring
the user to compile Xen with XSM enabled to be able to appropri
