similar to: [Xen-ia64-devel] [PATCH] xm: Don''t spawn vncviewer twice.

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 everybody, i have a problem setting up a DomU with Windows XP. I get the following error: xen:/etc/xen# xm create windows.hvm Using config file "./windows.hvm". VNC= 1 Unexpected error: exceptions.OSError Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-3.1-1/bin/xm", line 7, in ? main.main(sys.argv) File

Right now xm will return 1 if you run `xm list non_existant_domain` Wouldnt it be a better idea to have a specific error code for this error so that scripts wrapping around xm can better determine if the domain does not exist or if xm just failed for whatever reason? ~Shaun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Xen patchbot -unstable wrote: > # HG changeset patch > # User emellor@leeni.uk.xensource.com > # Node ID da24df1ea484cf72dc9d367d52e828777e0e20cd > # Parent c1bb4eb565296bdb00aed84fcc877befbcebd8e9 > Improve error handling, in particular fixing the ProtocolError that is thrown > when a domain is specified by the user that does not exist. Added a few > error codes -- many

We have an old 2000 machine with some data that we can''t get rid of yet. the machine is taking up way too much space for the amount of data it holds and the frequency in which the data is accessed. so, i want to do a p2v migration. using knoppix i have dd''d the whole hda drive and moved the data to an image file on the xen server. then i created a lvm volume that is large

Hi I`m trying to start win2k3R2 in XEN with this config # grep -v ^# /etc/xen/win2k3.hwm | grep -xv '''' import os, re arch = os.uname()[4] if re.search(''64'', arch):     arch_libdir = ''lib64'' else:     arch_libdir = ''lib'' kernel = "/usr/lib/xen-3.2-1/boot/hvmloader" builder=''hvm'' memory = 1024 name =

stubdom: rename the ioemu-dm domain config file to domainname-dm, which is shorter, makes more sense, and sorts better. diff -r c9b516a77927 stubdom/README --- a/stubdom/README Mon Aug 04 11:29:45 2008 +0100 +++ b/stubdom/README Mon Aug 04 12:51:31 2008 +0100 @@ -10,6 +10,9 @@ of video memory for the HVM domain, you of video memory for the HVM domain, you need to avoid the need for ballooning,

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

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

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 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

Using an 8-way ES7000 with 32GB of ram, I''m running xen at changset 11217 with dom0_mem=3092M as a kernel parameter on a x86_64 hyperviser. It appears that qemu is adding too much overhead to virtual machines to display graphics. If I boot a sles9sp3 domVT in runlevel 5 with vga=0x314 for a graphicalboot, and immediately use vncviewer simply to watch the virtual machine as it boots,

I''ve recently installed Debian Lenny witch Xen (xen-utils, xen.tools and xen-linux-system-2.6.26-2-xen-amd64). I want to virtualize some windows servers, but I''m unable to connect to localhost VNC when I start the vm (xm create) to proceed with windows instalation. The VM config is: import os, re arch = os.uname()[4] if re.search(''64'', arch):

HI all, i am configuring VNC server in CentOS 5.1. i have enables this two lines in /etc/sysconfig/vncserver file VNCSERVERS="2:vnc" VNCSERVERARGS[2]="-geometry 1024x768 -depth 24" here i have created a user vnc and set the password using vncpasswd cmd. then i started the vncserver # vncserver New 'localhost.localdomain:1 (gopinath)' desktop is

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 noticed only one connection at a time is supported.Is it possible to make it accept multiple viewer sessions simultaneously ? Thanks. -- This message posted from opensolaris.org

Hi, all I was trying to install Xen on CentOS5.4. The OS has a "virtualization" option, and I choose to install, so I get the 3.0 version of Xen. When I trying to install a higher version 3.4.1, the make world and make install process went ok, and the "xm list" command could show the domain 0. So I created a guest OS in virtual machine manager and wanted to install a guest

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

Hi: Sorry for the basic NOOB question but I managed to create a VM but now I am stuck. On page 26 of the XCP Virtual Machine Installation Guide it says "VNC and perform the OS installation". I tried everything I could find (listed below) but I am stuck. Any help would be greatly appreciated. Thanks in advance. Here are two questions whose answers would really help: 1.

Hi, I''m trying to get copy/paste/cut working between my Xen host (FC8 64) and guest OSs (Centos 5.1, Windows 2000). I''ve tried the viewer in virt-manager, virt-viewer, and vncviewer. None of them seem to transfer clipboard contents between host and guest, even with both clipboard checkboxes selected in vncviewer options. Does anyone know how to get this working? Thanks.