similar to: vncviewer via gateway option question

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:

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

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

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

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

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

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

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

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

Folks: I am unable to get my opensolaris sn-b85 domU to start up in an opensolaris sn-b85 dom0. I am booted to xvm. Other systems, such as Fedora 8, WinXP Pro, W2k3 server, W2k8 server and Windows Vista startup normally. I have used the following to build the domU: # mkfile -n 25g /solhvm/solhvm.img # ls -l /solhvm total 269 -rw------T 1 root root 26843545600 Jul 7 10:37 solhvm.img

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

sorry i figured this out after deleting the other parts of the thread. just run vino-preferences as the user who runs the main x display. it will have various options to enable and as soon as you do that you can get to hostname:0 via vnc. works quite well.

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

root@boris-P5Q-E:/mnt/usr/tmp# losetup -f ubuntu11.04.iso root@boris-P5Q-E:/mnt/usr/tmp# losetup -a /dev/loop0: [0809]:406494 (/mnt/usr/tmp/ubuntu11.04.iso) root@boris-P5Q-E:~/vms/natty# cat natty.hvm name = "NattyHVM" builder = "hvm" memory = "2048" disk = [''phy:/dev/sda5,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r''] vif = [

root@boris-P5Q-E:/mnt/usr/tmp# losetup -f ubuntu11.04.iso root@boris-P5Q-E:/mnt/usr/tmp# losetup -a /dev/loop0: [0809]:406494 (/mnt/usr/tmp/ubuntu11.04.iso) root@boris-P5Q-E:~/vms/natty# cat natty.hvm name = "NattyHVM" builder = "hvm" memory = "2048" disk = [''phy:/dev/sda5,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r''] vif = [

I''m trying to get linux domU going with opensolaris ''130. The CPU is a plain P4 3.2Ghz (no hardware Virt) but all I''m trying is --paravirt Here''s the command line I''m trying..... virt-install --paravirt --name=dom1 --ram=1024 --vnc \ --os-type=linux --os-variant=fedora8 \ --network bridge \ --file /dev/zvol/dsk/rpool/dom1 \ --location

I have the vncserver running on CentOS 4, but when I log in using vncviewer from another box, I don't see my gnome desktop, just a fancy terminal. I suspect I need to edit the ~/.vnc "xstartup file, but what do I add to fix this. On all other distros I have tried, the vncserver serves up my gnome desktop by default. -- Lee Parmeter Emperor, linXos - The Flying Penguin

http://bugs.freedesktop.org/show_bug.cgi?id=13257 Summary: using nouveau on NV17 kills the KDE VNC server Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at