Re: Should we keep the original vnc behavior even if the underlying qemu changes?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/01/2013 08:43 AM, Guan Nan Ren wrote:
>         Since qemu v1.1.0 upstream commit 8cf364, qemu implemented shared-flag handling
>         the default qemu vnc server behavior from mode 'ignore' to 'allow-exclusive'.
>         The direct effect is as follows for libvirt user:
>         vncviwer client:
>           before: all client could share desktop without any option
>           after: all client need -Shared options for desktop sharing. One client without
>                  -Shared option breaks others's connection
>         virt-viewer:
>           before: virt-viewer could support multiple desktop sharing
>           after: only one active connection
> 
>         If we need to keep the original vnc behavior at libvirt level, the '-vnc :1,share=ignore'
>         need to add into qemu commandline.
> 
>         Any ideas about this?

It sounds like we need an XML attribute, with several states (exclusive,
allow-share, force-share, ignore), and then specify that omitting the
attribute allows the hypervisor to pick its own default.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]