similar to: [PATCH] Update new qemu-dm to spawn vncviewer

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

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

Ben- I like the idea but I don''t understand how this patch can work: 1) You never put a name into `serial_devices[]'' for the summa port. The loop in `main'' that initializes the serial devices only calls `qemu_chr_open'' if there''s a string name in `serial_devices''. How did you get this to work? 2) Minor point, I don''t see the need

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

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:

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:

How do you send special keystrokes in vncviewer? I need to send Shift-F10... Searching the net showed nothing and realvnc's webpage yielded nothing either. Thanks! jlc

Hi! Some vnc clients has '-via ssh_gateway' option to simplify the setup of ssh port forwarding. Basically the option implements the following 3 steps: 1. Find local port available for listening. 2. Fork/exec ssh -L found_port:vnc_host:vnc_port ssh_gateway sleep some_delay 3. Connect to the found_port Although convenient the setup has its problems. First, it exposes the remote vnc

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 can''t use the vnc option (VNC=1 in my xmexample.hvm file), when I use RedHat or Fedora on 64 bits. The qemu log, say /usr/lib64/xen/bin/qemu-dm: invalid option -- ''-vncconnect'' But when I use RedHat or Fedora 32 bits, works fine. There is a problem or incompatibility in the 64 bits Xen kernel and the VNC option ? Best regards Luis

Hello, I want to install a 2003 guest on a Debian Etch with xen binary packages (apt-get install), but through a vnc console (no graphical interface). So I launch the xm create in an ssh connection, and want to connect through vnc to complete the installation of windows. So the domain gets created with xm create but no VNC port is displayed: ----- Using config file "2003.hvm". VNC= 1

I have xkeybindings running just fine on centos 5. I have vncviewer running in full screen mode showing another PC. When vncviewer is running is running it seems to override my xkeybindings. Is there a way to tell vncviewer to not bind to any keys?? The only keys I am binding is on the Keypad 3,4,6, 9 and Enter. Nothing that vncviewer uses anyway. How can I still have my xkeybindings active

I have a host that I have been accessing with vncviewer via its fqdn that had only an IPv4 A record. I just added a AAAA IPv6 record, and vncviewer via fqdn stopped working. But worked when I provided the IPv4 address instead. It LOOKS like vncviewer is trying the IPv6 address, eventhough all documentation indicates that it does not support IPv6. Definitely my server is only listening on

Anybody out there running Windows XP, Windows XP SP2 or Windows 2003 server with the default XEN 3.0.3 on Ubuntu Feisty ? Have Ubuntu Feisty Dom0 with a number of Ubuntu 6.1/7.04, Debian and FC6 DomUs all working lovely. But it will not work for any windows versions. The install gets as far as the blue "Setup is Starting Windows" screen. Intel VT extensions are enabled and the F5 trick

Hello, if I start a unmodified Guest Already working on A SLES Installation now I get under gentoo: VNC= 1 vncviewer: ListenAtTcpPort: bind: Address already in use vncviewer: ListenAtTcpPort: bind: Address already in use The config: disk = [ ''file:/var/lib/xen/images/win/hda,ioemu:hda,w'' ] memory = 512 vcpus = 1 builder = ''hvm'' device_model =

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

Hi, Does the current tree implement Rotate 180? I can see 0, 90 and 270, but not 180. This feature might sound silly at first glance, but it happens to be highly useful for my convertible tablet laptop. I've browsed the current nv code and nouveau implementations, and it's pretty clear that the older xrandr implementation did not do this. Is there some secret in xrandr1.2 that I'm

Hello, I set up a Windows as Guest System. But now I can''t reconnect to the VM with vncviewer. But the Session is running I can Connect with rdesktop. How can I connect to this again? R. R. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users