Hi, Daniel Would you give me a comment on this model? If not, please apply this patch.
> About virsh connect, I think as follows. > > ========================================================================== > //Authorization model of a general user of now// > > *Local connection* *Remote connection* > > HV | Xen | QEmu/KVM/etc HV | Xen | QEmu/KVM/etc > --------------------------------- --------------------------------- > authority | R/W | R/W authority | R/O | R/W > > > //Authorization model of a general user of mine// > > *Local connection* *Remote connection* > > HV | Xen | QEmu/KVM/etc HV | Xen | QEmu/KVM/etc > --------------------------------- --------------------------------- > authority | R/O | R/W authority | R/O | R/W > > # R/W=Read Write R/O=Read Only > ========================================================================== > > In the same way as connection local at the time of remote connection, > this revision is the contents which only Xen cannot full control. Thanks, Shigeki Sakamoto. -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
