similar to: Password unused in vnc console

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

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

Dear All, I have a problem with my VPS machine ...I used Centos OS and xen application : - I created domU called vps1 with this configuration : # more /etc/xen/vps1 kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' memory = 1536 name = "vps1" vif = [ ''bridge=xenbr0,ip=202.162.218.236,mac=00:16:3E:12:18:36'' ] disk = [

stubdom: add example config file Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r e69570f85e85 tools/examples/stubdom-ExampleHVMDomain --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tools/examples/stubdom-ExampleHVMDomain Thu Jul 17 19:31:13 2008 +0100 @@ -0,0 +1,21 @@ +# Not to be started directly, +# See xmexample.hvm-stubdom and stubdom/README for more details

On ia64 we have a desire to know the guest OS the user plans to run in an HVM domain. With this information we can make certain optimizations, for instance knowing if a guest identity maps a memory region can change how we handle page faults. In the past we''ve tried to do this via the guest firmware detecting the guest type, but this is error prone and doesn''t allow the user to

Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting error. I tried doing googling but none of suggested solution is working for me. For more details please see below, I have highlighted few details in bold color just for

Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting error. I tried doing googling but none of suggested solution is working for me. For more details please see below, I have highlighted few details in bold color just for

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

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"

I installed a 32 bit Windows 2003 enterprise edtion domU. xm list shows the domU has 7G RAM. But Windows 2003 shows only 3.75G RAM. I do not know what''s wrong. Anyone knows? [root@sjd-hot w2k3e]# xm info host : sjd-hot.rashost.com release : 2.6.18.8-xen version : #1 SMP Fri Nov 27 03:53:01 UTC 2009 machine : x86_64 nr_cpus

This patch provide the code to set the VNC password to QEMU upstream through VNC. The password is still stored in xenstore but will not be used by QEMU upstream. Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- tools/libxl/libxl_create.c | 3 +++ tools/libxl/libxl_dm.c | 21 ++++++++++++--------- tools/libxl/libxl_internal.h | 1 + tools/libxl/libxl_qmp.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''m getting the error: xend (12, ''Cannot allocate memory'') From the command line after the Dom-0 goes through a period of heavy memory usage. I don''t have any hard numbers on how to duplicate it, but I''ll give you the steps I''ve gone through to duplicate the problem. First, some information about my setup. It''s a new setup, and

All, Attached is a simple patch to fix the VNC server in the qemu device model after an HVM save/restore/migrate, if you don''t have a vncpasswd specified. The basic problem was that the "image" section of the sxp had a "None" in it, which means that on the restore (either on the local machine or remote machine), the vnc server in the qemu device model literally

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

Hallo, I have an installed Windows 7 on one partition and running Debain Squeeze on the other. Both are 64 bit. I want to use Xen to run Windows as virtual guest from a physical disk. Once I get this working the Window will never be booted directly. When I try to create the virtual machine by "xm create -c win.xen" it hangs. The versions I use Xen 4.0.1-4 Kernel 2.6.32-5-xen-amd64