search for: vnc_display

...g_image.append([a, vals.__dict__[a]]) @@ -847,17 +853,20 @@ """If vnc was specified, spawn a vncviewer in listen mode and pass its address to the domain on the kernel command line. """ - if not (vals.vnc and vals.vncviewer) or vals.dryrun: return - vnc_display = choose_vnc_display() - if not vnc_display: - warn("No free vnc display") - return - print ''VNC='', vnc_display - vnc_port = spawn_vnc(vnc_display) - if vnc_port > 0: - vnc_host = get_host_addr() - vnc = ''VNC_VIEWER=%s:...

...0 - - return VNC_BASE_PORT + display - -def preprocess_vnc(vals): - """If vnc was specified, spawn a vncviewer in listen mode - and pass its address to the domain on the kernel command line. - """ - if vals.dryrun: return - if vals.vncviewer: - vnc_display = choose_vnc_display() - if not vnc_display: - warn("No free vnc display") - return - print ''VNC='', vnc_display - vnc_port = spawn_vnc(vnc_display) - if vnc_port > 0: - vnc_host = get_host_addr() -...

...OM if (xenfb_pv_display_init(ds) == 0) { } else @@ -10042,33 +10058,35 @@ fprintf(stderr, "fatal: -nographic can''t be used with -curses\n"); exit(1); } - /* nearly nothing to do */ - dumb_display_init(ds); - } else if (vnc_display != NULL || vncunused != 0) { - int vnc_display_port; - char password[20]; - vnc_display_init(ds); - xenstore_read_vncpasswd(domid, password, sizeof(password)); - vnc_display_password(ds, password); - vnc_display_port = vnc_display_open(ds, vnc_display, vncunused);...

...*argv) } } - /* Now send logs to our named config */ - sprintf(qemu_dm_logfilename, "/var/log/xen/qemu-dm-%d.log", domid); - cpu_set_log_filename(qemu_dm_logfilename); + cpu_set_log(0); #ifndef NO_DAEMONIZE if (daemonize && !nographic && vnc_display == NULL && vncunused == 0) { diff -r 2a8eaba24bf0 tools/python/xen/xend/image.py --- a/tools/python/xen/xend/image.py Tue Feb 26 15:11:51 2008 +0000 +++ b/tools/python/xen/xend/image.py Wed Feb 27 15:26:53 2008 -0500 @@ -296,7 +296,34 @@ class ImageHandler: { '&...

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine*. There are a few items on my todo list but this works well. New since last send: - live migration support** - write path in the guest

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine*. There are a few items on my todo list but this works well. New since last send: - live migration support** - write path in the guest

Hello all, This are the latest version of the patches. Lots of things have changed since the last submission. A few of which I remember: - VNC copy / paste works* (* conditions apply) - client vnc copies get propagated to guest port 3 (/dev/vmch3) - guest writes to port 3 (/dev/vmch3) go straight to client's clipboard - sysfs hooks to autodiscover ports - support for 64 ports in this

Hello all, This are the latest version of the patches. Lots of things have changed since the last submission. A few of which I remember: - VNC copy / paste works* (* conditions apply) - client vnc copies get propagated to guest port 3 (/dev/vmch3) - guest writes to port 3 (/dev/vmch3) go straight to client's clipboard - sysfs hooks to autodiscover ports - support for 64 ports in this

> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.