similar to: vncviewer

the man page for vncviewer presents the -via gateway option to use ssh through a gateway. I understand if I want a secure vnc connection to server.foo.com I can use the command: vncviewer localhost -via server.foo.com But I have moved my SSHD services from port 22 to port n. So according to the man pages, I need an environment variable of VNC_VIA_CMD and override the default command with:

On Fri, Feb 21, 2014 at 2:50 AM, Ferenc Wagner <wferi at niif.hu> wrote: > Alexandre Blanchette <blanalex at gmail.com> writes: > > > Is there a way to show some bits of information in the menu, like > > Syslinux version, MAC address and IP address? When the menu is loaded > > at startup, this information is quickly erased and is not easily > > readable.

I''m running snv93. I''m trying to install a windows hvm domU using the virt-install command: /usr/bin/virt-install -n windowsts -r 2048 -s 20 -f /data/domU/windowsts --hvm --vnc -c /dev/dsk/c0t0d0s2 The vncviewer is unable to open a connection to the xend VNC server and is failing with the Connection refused (146) error message. xend is set up with the following properties:

I post this to the mailing list, but perhaps is not the good place. I'm not subscribed, so I don't know if I'm going to get any reply, but please, tell me where to send patches. I attach two patches that correctly describes the new support for F11 and F12 in documentation but I have two more question to update documentation accordingly. In doc/syslinux.txt line 515, talking about

Hi I've got 'WriteOutloud' (talking wordprocessor for dyslexic children) working pretty well on an Asus Eeepc (Xandros) and on an Acer Aspire One (Kuki Linux) I'm using Wine 1.0.1 on both machines. What happens is that the prog starts up normally then immediately minimises to the taskbar. To make it run fullscreen you have to click on it and press Alt+F10 Although not a serious

Unable to connect to my HVM # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3869 2 r----- 368.6 vm00 45 128 1 -b---- 62.3 The vm00 changes state from "r" to "b" after about a minute. (I have a fedora dvd in the drive.) #cat

Hi all, the patch "qemu-vnc-wmvi.patch" adds support for the WMVi pseudoencoding in qemu vnc server. If the client implements it, it is supposed to be able to change colour depth when receiving a WMVi message. Since I didn''t know any client that supports it and I wanted to test the implementation before submitting any patch I also modified vncviewer to support WMVi. The

I'm probably dense - CentOS 4.1 # cat /etc/sysconfig/selinux ..snip... SELINUXTYPE=targeted # su - Alec # tail -n 3 /var/log/messages Aug 31 08:48:26 srv1 su(pam_unix)[31435]: session opened for user Alec by root(uid=0) Aug 31 08:48:26 srv1 su[31435]: Warning! Could not relabel /dev/pts/0 with user_u:object_r:devpts_t, not relabeling.Operation not permitted Aug 31 08:48:27 srv1

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

Hello, is there a way to start automatically the vncviewer when a domU starts? When I was using the xm toolstack I could use "xm create domain.cfg -vncviewer" or something similar (if I''m not wrong), but I don''t know how to do it with the xl toolstack. At the moment, I have to create the domain using xl create domU.cfg, then xl list to see the domU id and then xl

On Thursday 07 February 2008 05:19:26 pm Hamid Majidy wrote: > When I start guest with "xm create clientdom", I get: > xm create clientdom > Using config file "./clientdom". > VNC= 3 > Started domain clientdom >   > But when I try to connect to it with "vncviewer 192.168.122.1:5900" I get: > VNC Viewer Free Edition 4.1.2 for X - built Mar 14

Hi. I found this issue with IA64 box while looking at the c/s of 18204:21dd1fdb73d8, but I believe the things is same with x86 box. I''m not sure whether this patch coexist with the old ioemu which is to be removed soon. So it might be desirable to apply this patch after deleting the internal ioemu tree. thanks, xm: Don''t spawn vncviewer twice. Without this patch, vncviewer

To anybody who can help me I want to acess the VM(Virtual manchine ) in IE brower, the URL is http://localhost:5831 。31 is the vnc display of the VM. I failed to acess the VM , but I can acess the dom0 in the IE brower. How could I acess the VM domU in the IE brower ？ Could the VM be acessed through IE Brower? Thanks PS: Xen 3.0 _______________________________________________ Xen-users

I''ve attached the preliminary patch to add vncviewer options to the ''xl create''. It applies cleanly against c/s 4e1d091d10d8. All feedback is welcome. Goncalo # HG changeset patch # User Goncalo Gomes <goncalo.gomes@eu.citrix.com> # Date 1332257809 0 # Node ID 46f8afe643dee8de2c592c65204567fbad657616 # Parent 4e1d091d10d83130842170cd61f1194e5459f2aa Add

Hi, I''ve been posting this question to lots of lists and not getting good answers. I have a Ubuntu Hardy laptop. With a ssh connection to a RHEL5 xen dom0. Running cobbler/koan on the dom0 Koan --virt --nogfx ... starts a new domU on the xen box and starts up the RHEL5 installer the installer attempts to configure its network interface using DHCP and gets stuck If this was an install

Is there a way to show some bits of information in the menu, like Syslinux version, MAC address and IP address? When the menu is loaded at startup, this information is quickly erased and is not easily readable. -- Alexandre Blanchette <blanalex at gmail.com>

Changes since v1: - Removed libxl vncviewer related dependencies - The vncviewer function was modified to accept a domid instead of domspec; - main_vncviewer was updated to reflect the new use. - A domain_create structure is now passed to the parse_config_data where required/feasible (NULL otherwise) - xl restore now have long options for vncviewer/vncviewer-autopass; docs updated. - Updated

Hi My original message and problem is in http://lists.xenproject.org/archives/html/xen-users/2013-06/msg00422.html, but I couldn''t reply to that, so I''m sending an update in the form of a new message. I have changed the memory parameter in /etc/xen/win.cfg, from 1024 to 4096 and now the domU stays active, or at least on the list before: memory=1024

Hi, i have a strange problem since pxelinux 3.62 with the F10 help key. I configured this: DISPLAY pxelinux.cfg/schlunix_new.txt F1 pxelinux.cfg/helps/schlunix F2 pxelinux.cfg/helps/schlunix64 F3 pxelinux.cfg/helps/rescue F4 pxelinux.cfg/helps/rescue64 F5 pxelinux.cfg/helps/stress F6 pxelinux.cfg/helps/stress64 F7 pxelinux.cfg/helps/dosimages F8 pxelinux.cfg/helps/mailsystem F9

Hello fellow syslinux/extlinux users! Please forgive the long post, but I believe my problem warrants the background info to understand the issue. I've developed a specialized spin of Fedora that runs off CompactFlash. The spin is actually produced by the livecd-tools package and is then transferred to the CF card -- which has been formatted with ext3 -- using livecd-tools'