similar to: vncunused always allocating port 0

"vncunused" is documented to default to 1. Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r 71a0257ed7d2 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Mon May 10 15:51:49 2010 -0700 +++ b/tools/libxl/xl_cmdimpl.c Mon May 10 16:02:27 2010 -0700 @@ -209,7 +209,7 @@ dm_info->vnc = 1; dm_info->vnclisten = "127.0.0.1";

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, In case of someone else is trying to do the same configuration as mine, I stated below the steps to configure HVM and PV''s domains to use FIXED VNC Ports (instead of having Xen automatically assign one unused port based on domain id): For HVM''s: vnc=1 # Enable VNC vncconsole=0 # Don''t start vncviewer after "create" the

Hello, It looks like xen 4.1.2* has some problems with solaris 11 iso images too (s. further below log messages) hvm-solaris11.born2b3.net.cfg # --- kernel = ''/usr/lib64/xen-default/boot/hvmloader'' builder = ''hvm'' device_model= ''/usr/lib64/xen-4.1/bin/qemu-dm'' name = ''solaris11hvm.born2b3.net'' acpi =

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)

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

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

''vncdisplay=N'' in hvm config file is ignored when building qemu-dm arguments. xm create or xm new -> xm start with hvm config file containing vnc=1 vncdisplay=5 results in ''-vncunused'' being passed to qemu-dm. There are several approaches for a fix - this patch defaults vncdisplay to None in xm options. It currently defaults to 1 and is always included in

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

Hi, I''m trying so give all my guests a static vnc display my Configfile looks like this. 1 ostype = "opensuse" 2 name = "suse-10.3-testcups" 3 builder = "linux" 4 memory = 512 5 vcpus = 1 6 uuid = "c6d9aa20-06c4-46f5-81e8-7906f7cfb642" 7 on_crash = "destroy" 8 on_poweroff =

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

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.

Next question:- eth0            8000.001c2596e32b       no              peth0 pan0            8000.000000000000       no virbr0          8000.000000000000       yes Presence virbr0 in report seems strange. Direct port  Xen 3.4.2  to F11 doesn''t install daemon libvirtd ( bridge virbr0 ) , unless you wrote xen-3.4.2-(x).fc12.src.rpm  yourself. So , from where bridge virbr0 comes 

Greetings, I would like to know how one can identify if a DomU is PV or HVM? Any docs which may indicate a way to find out? I have a CentOS 5.5 64bit DomU which might be HVM - how can this DomU can be made PV? Just stop the DomU, and then delete it using Virtual Machine Manager and the create another config file for a PV DomU and use xm new and then xm start? Let''s say I have a config

Hi, In continuation with my previous mail, I changed the vif entry in the config file as, vif = ["mac=00:16:3e:43:b7:99,bridge=xenbr0"] and I was able to boot into the guest, but I was not able to ping any system from the guest. I have attached the snapshot of the boot error messages. Thank you Regards Ananth -----Original Message----- From: CB, Anantha Padmanabhan Sent: Wednesday,

Hi everyone, I'm wondering how one adds a new drive to a Windows domu... I'm running Centos 5.1 x86_64 on a Xeon server and have a Windows 2003 R2 64 bit domu. The Windows system was installed from a CD onto this server so it is a brand new VM. All working fine. So then I wish to add another drive to the Windows domu for a data drive. I added the drive to the Xen configuration, but it

Hi I cant start a hvm domU with more than 3 nic's configured... why? it is a bug? With previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2