[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0
- From: Cole Robinson <crobinso redhat com>
- To: "Jan ONDREJ (SAL)" <ondrejj salstar sk>
- Cc: fedora-virt redhat com
- Subject: Re: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0
- Date: Fri, 13 Mar 2009 14:06:37 -0400
Jan ONDREJ (SAL) wrote:
> Hello,
>
> thank you for positive reply.
>
> On Fri, Mar 13, 2009 at 12:45:56PM -0400, Cole Robinson wrote:
>> Jan ONDREJ (SAL) wrote:
>>> Starting an domain starts my serial console owned by root and is not
>>> accesssible from virt-manager (virt-viewer). After changing ownership it's
>>> immediatelly available. Is it possible to change this in time of virtual
>>> machine creation? (in libvirt or where?)
>>>
>> Yes, this is one of the drawbacks of not running virt-manager as root:
>> since the qemu:///system libvirt connection will launch your guests as
>> root, a regular user won't be able to access ptys.
>>
>> I don't know of a proper solution to it all, other then running the app
>> as root or changing the the pty permissions as you did.
>
> Is it known to libvirt, who is user which is starting virtual machine? Can
> libvirt change ownership of this pty back to user? Root do not need to be
> owner of this file to access it, he can access any file, but user needs.
>
I'm pretty sure libvirt doesn't know the actual user who is connecting
via PolicyKit: it all looks like root after the authentication.
> Another solution can be to change permissions on pty to 660, leave group to
> tty or change it to a value defined in libvirtd.conf.
>
This doesn't sound unreasonable, you'd probably want to bring it up on
libvir-list or file a bug though.
Thanks,
Cole
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]