similar to: How to setup the keyboard map in the VNC server?

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Switching to the xl toolstack I expected my configuration to work unmodified, but it doesn't, and I couldn't find any documentation regarding this, since xl.cfg(5) is missing. Original version, used with xm: vfb = ['type=vnc,vnclisten=0.0.0.0:6369,vncdisplay=6369,vncpasswd=x'] Working xl version: vnclisten="0.0.0.0:6369"

vfb: Add opengl option (and replace bogus vncpasswd copy in xenapi_create in the SDL case) Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 2ad29c586d49 tools/python/xen/xend/XendConfig.py --- a/tools/python/xen/xend/XendConfig.py Tue Mar 18 14:36:27 2008 +0000 +++ b/tools/python/xen/xend/XendConfig.py Tue Mar 18 15:16:47 2008 +0000 @@ -165,7 +165,7 @@ # Xen API

the contexts are as follows, looking forward to your reply, thanks [1]enviromention : xen3.4.2+CentOS-5.5 [2]config file: xp.hvm, as follows _s_name = 'xp-101' _s_vnc_display = 5310 _s_vm_id = 101 _s_vm_mac = '00:16:3e:eb:ca:65' _s_memory = 512 _s_allow_destroy = False _s_use_vnc = True # -*- mode: python; -*-

Changes since v1: - Include nic,net2,vkb,vfb init functions --- This allows libxl users to get some sane default values for this complex set of structures. This is purely code movement and there are no functional changes except for a trivial error handling change in nic device init. Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> diff -r efe2d3ea22ae tools/libxl/libxl.c ---

Hi, I''m using VNC to show vm''s linux boot. I see lines like [ 1.053298] EXT3-fs: INFO: recovery required on readonly filesystem. [ 1.053686] EXT3-fs: write access will be enabled during recovery. [ 1.494490] kjournald starting. Commit interval 5 seconds etc. But à the end of booting, it stop. No prompt login. With "xm console vm" I have the boot login. I

I''ve been using Xen strictly for PV for a while now, but I recently upgraded to hardware capable of HVM domUs. I''m trying to get a really basic HVM instance going so I can get my hands around making them work, in anticipation of using one to run a BSD to act as a firewall for other domUs on the machine. (I like PF.) Also, I might need run windows at some point, I suppose.

Hi, I wanted to ask it on elli_dbergs''s thread ''problem with xm create'', but it seems that my message was never gonna be published (waited for 24 hours til i figured it was taking way too much time). So i''m working with Xen unstable, installed dom0 over Ubuntu 8.10, no problem so far apparently, reboot on Xen, then I go to /etc/xen to get some example config

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

Hi   Below is what i get while creating a guest domain, please someone help me.   [root@xenserver xen]# uname -a Linux xenserver 2.6.21-2950.fc8xen #1 SMP Tue Oct 23 12:24:34 EDT 2007 i686 i686 i386 GNU/Linux [root@xenserver xen]# [root@xenserver xen]# xm list Name                                      ID   Mem VCPUs      State   Time(s) Domain-0                                   0   930     2    

Hi folks, I''m updating my xen server from a dom0 on debian sarge, using a self compiled xen 3.0.4 and a kernel 2.6.16, to a standard debian etch using the deb packages xen 3.0.3 and kernel 2.6.18. On the old server, all my hvm machines use vnc console and a password is set into xend-config.sxp and it works nice. On the new etch server, with the same hvms and configuration files,

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains

Hello all, I have a problem getting a working VNC console for HVM guests on Xen 4.1. When I start the DomU with xm create everything is fine the DomU runs and in xm list it has the running state but when I try to connect to the VNC console to install an operating system (Ubuntu and Debian I have tested) the VNC viewer only shows a black screen. So I searched in the logs and found a log entry

We are running a 2-node cluster with Debian Squeeze (2.6.32-5-xen-amd64) and Xen 4.0.1 on the dom0 and Ubuntu lucid domUs. We are now using fully virtualized (HVM) vms. In our configuration the dom0 administers to domUs created and run on a SAN box accessed via private network (192.168...). A sample configuration file is pasted below. We have had little or no IO problem with HVMs created and

Hi all, I try xen 4.1, but in my domU''s HVM don''t appear vnc port. I used in my domU.cfg the parameter ''vncunused=1''. How to get vnc port specified domU? In another Xen (4.0.2), I get vnc port with ''xm list --long domU''. (vfb (vncunused 1) (vnc 1) (uuid cb20995f-55ae-55ce-143d-dd6a2ecc5969)

Hi , I have installed Xen 4.0.1 oon to my Debain Lenny. I have successfully got the Dom0 kernel to boot up. Now when I try to start my first hvm guest I get an error Error: Domain ''hvmguest'' does not exist. My /etc/xen/hvmguest.cfg file is as given below import os, re arch_libdir = ''lib64'' arch = os.uname()[4] kernel =

I found that the example HVM config doesn't work at all on amd64 I used the following, based on various postings I found through Google. Could you include a working example in the package? I think that specifying the full kernel and device_model paths makes a difference on amd64 # Enable hardware virtualisation using HVM kernel = '/usr/lib64/xen-3.2-1/boot/hvmloader' device_model =

Changes since v1: - Fix a double-free bug introduced by v1, pointed out by Stefano where internal pointer was being passed back to caller from libxl_create_stubdom() 8<---------------------------------------------------------------------- Currently scratch variables allocated by libxl have the same lifetime as the context. While this is suitable for one off invocations of xl. It is not

I think it has to be something trivial, but I cannot start 2 windows servers at the same time on the same dom0. If I start server 2008 first I can''t start 2012, if I start 2012, I can''t start 2008. The failure is: libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model not ready xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup

Hi all, I installed xen-3.3.1 and configured two DomU with 2.6.18.8-xen kernel. Now the DomU1 and DomU2 could work and the network is ok. But I used the filesystem image from jailtime, so the X-Window mode can''t work. Thus, I tried two ways to make the GUI-mode work: (1) yum install X-Window in Guest OS, and the GUI configuration Wizard shows up. When done with the configuration, the