On Thu, Aug 28, 2008 at 5:33 PM, Daniel P. Berrange <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 28, 2008 at 02:39:57PM +0900, Nguyen Anh Quynh wrote:
>> Hi,
>>
>> Though libvirt tries very hard to hide the difference between
>> hypervisors behind an abstraction layer, there are still differences
>> th
On Thu, Aug 28, 2008 at 02:39:57PM +0900, Nguyen Anh Quynh wrote:
> Hi,
>
> Though libvirt tries very hard to hide the difference between
> hypervisors behind an abstraction layer, there are still differences
> that we might want to expose to the users. For example, QEMU has the
> monitor interfac
Hi, Quynh
Thank you for your comment.
I am clearified your question.
But I have no good idea to solve.
Someone may have a good idea.
Thanks
Atsushi SAKAI
"Nguyen Anh Quynh" <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 28, 2008 at 2:52 PM, Atsushi SAKAI <[EMAIL PROTECTED]> wrote:
> > Hi, Quynh
> >
On Thu, Aug 28, 2008 at 2:52 PM, Atsushi SAKAI <[EMAIL PROTECTED]> wrote:
> Hi, Quynh
>
> Did you see the libvirt access control feature?
> http://libvirt.org/auth.html
> You mean current access control feature is not enough for your use.
But that access control is about authenticating/authorizing
Hi, Quynh
Did you see the libvirt access control feature?
http://libvirt.org/auth.html
You mean current access control feature is not enough for your use.
Thanks
Atsushi SAKAI
"Nguyen Anh Quynh" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Though libvirt tries very hard to hide the difference bet
Hi,
Though libvirt tries very hard to hide the difference between
hypervisors behind an abstraction layer, there are still differences
that we might want to expose to the users. For example, QEMU has the
monitor interface, which provides some unique functions. Users might
want to have access to th
