similar to: static vnc port

How does this setting work? I was hoping to use it to make connections predictable. I have vncunused = 1 as well, but xen never starts the server on the expected port (dom-u id). Thanks! jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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)

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

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 following error. I tried doing googling but none of suggested solution is working for me. Please guide me through my first experience with xen.for more details please see

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 

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

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 there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

I am needing to explicitly assign VNC ports to my virtual guests so that I can connect to them externally via a VNC client, and not virt-viewer. Since I will have multiple KVM Hosts with access to the same shared storage (to facilitate migrations) I need to ensure I have unique VNC ports assigned to each guest so that I don't overlap somehow. I had planned to use a range of ports starting at

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

Hello all, I have a PowerEdge 2950 that I am using to host Windows XP VM's under CentOS. I am experiencing poor performance in the Xen VM's. Any time I try to do something, the CPU usage (as reported by the Windows task manager) hits 100% for a few and then drops back down. This is causing the VM's to run sluggish and be quite annoying to use. Example.. I click IE.. cpu hits

Hi all, These days I installed xen 4.3 unstable from source and recompiled qemu upstream with spice support. After xl create , the windows domU started successfully and spice client can visit the VDI. However, it display blue screen before entering the windows welcome screen. Is it a bug in current upstream qemu support? My domU configuration file is: builder =

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

I''m trying to install OpenSuSE 10.3 as a domU on a CentOS 5.6 system running xen 3.0.3. It starts to load and then hangs: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20480 MBytes) ata0 slave: Unknown device ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom ata1 slave: Unknown device Booting from CD-Rom... ISOLINUX 3.31 0x46f43c1e Copyright (C) 1994-2005 H. Peter Anvin Loading... In

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