Xen devel - Jul 2006 - [PATCH] VNC enhancement in new qemu-dm

Keir,
Qemu 0.8.1 uses a written-from-scratch VNC implementation, which lacks
of some original features. One thing is that it doesn''t recognize
ctrl+alt+1/2/3 to switch among screens. Another issue is VNC client may
reset color depth after connection, so if we don''t re-calculate
color_table, monitor/console''s background is abnormal. I made a patch
to
add them. In addition, it sets VNC window title with domain-name.

Thanks,
Xiaowei


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Are you sure you want to expose the monitor interface via VNC?  Most of
the commands aren''t functional for Xen.  It also exposes an asymmetry
between VT domains and PV domains with a framebuffer.

For debugging purposes, it would seem easier to just start with -monitor
pty and have something akin to xm console to connect to the monitor''s
pty.

In fact, the monitor may make more sense as the default target of xm
console...

Right now, xm console goes to ttyS0 but presumably a user would want to be
able to connect to any of the four virtual serial ports.  Perhaps all four
should be stored in xenstore and a new xm command should be introduced?

Regards,

Anthony Liguori

On Tue, 25 Jul 2006 13:41:38 +0800, Yang, Xiaowei wrote:
> Keir,
> Qemu 0.8.1 uses a written-from-scratch VNC implementation, which lacks
> of some original features. One thing is that it doesn''t recognize
> ctrl+alt+1/2/3 to switch among screens. Another issue is VNC client may
> reset color depth after connection, so if we don''t re-calculate
> color_table, monitor/console''s background is abnormal. I made a
patch to
> add them. In addition, it sets VNC window title with domain-name.
> 
> Thanks,
> Xiaowei
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

>Are you sure you want to expose the monitor interface via VNC?  Most of
>the commands aren''t functional for Xen.  It also exposes an
asymmetry
>between VT domains and PV domains with a framebuffer.
>
Hi Anthony, 
To me, this asymmetry between VT and PV domains should not be a problem.
After all, VT depends on Qemu while PV doesn''t. People can accept some
different usage between these two. Monitor screen is ready in Qemu and
SDL can display it. So if users find they can use it with SDL while not
with VNC, this kind of asymmetry may be more unfriendly:-)

Thanks,
Xiaowei

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 7/25/06, Yang, Xiaowei <xiaowei.yang@intel.com>
wrote:
> Keir,
> Qemu 0.8.1 uses a written-from-scratch VNC implementation, which lacks
> of some original features. One thing is that it doesn''t recognize
> ctrl+alt+1/2/3 to switch among screens. Another issue is VNC client may
> reset color depth after connection, so if we don''t re-calculate
> color_table, monitor/console''s background is abnormal. I made a
patch to
> add them. In addition, it sets VNC window title with domain-name.
Xiaowei,

I''ve applied these now.

The screen switching has one issue though, it will pass the numeric
keypress to the terminal, i.e. if you switch from the monitor back to
the 1st display, it will emit a 1 keypress to the monitor, the same
for switch from 1st display to 2nd.  Could you have a look at fixing
this?

Also, please send separate patches in the future.

Thanks!

    christian

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel