similar to: Bug#744157: VNC parameters can be set only globally using xl

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: normal It seems to be impossible to save or migrate HVM guest using the xl toolstack. Trying to do so hangs the process initiating the action, and the domU can't be shut down with the 'xl shutdown' command after this. 'xl destroy' works. The domain keeps running during the save operation, doesn't get paused for any

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: minor In the file /etc/xen/xl.conf there's a suggestion that vif scripts should be named relative to the /etc/xen/scripts directory, which is not the case, since absolute paths have to be used. The manual page xl.conf(5) is also missing. Relevant snippet: # default vif script #vifscript="vif-bridge"

Processing commands for control at bugs.debian.org: > tags 744157 +fixed-upstream Bug #744157 [xen-utils-4.1] VNC parameters can be set only globally using xl Added tag(s) fixed-upstream. > tags 744159 +fixed-upstream Bug #744159 [xen-utils-4.1] HVM guest can't be saved/migrated with xl Added tag(s) fixed-upstream. > tags 744160 +fixed-upstream Bug #744160 [xen-utils-common] xl.conf

I'm afraid this still doesn't work even after upgrading to jessie (xen-utils-4.3 4.3.0-3+b1). Should I open a new bug against xen-utils-4.3 or can this bug somehow be applied to that package as well?

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,

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

Hello. This is my first experience with Xen. I set up a machine to server as a Xen host, and am now in the process of installing a Windows XP guest. When I get to typing the Windows XP license key, my keyboard keys are all mangled (I have a french keyboard, but it seems to be in QWERTY in the VNC server, though some keys are not in the place they should be on a american keyboard). I

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

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

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

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

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important Tags: security patch When you use xl toolstack, you can't reboot domUs. When you switch back to xm toolstack, than reboot works again. I think the problem with the debian packaged version is the same as in this thread: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html I also think it's a security issue,

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 All, I am confused by a type conversion happening against my intent. In an R script I allocate a matrix X, and I pass it to a C function by using tmp -< .C(..., as.double(X),...). I use as.double() because I read that it makes sure that the parameter passing is correct. I return the matrix from the R script using: return (list(..., X = tmp$X, ...)) The returned value is not a matrix

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

I have NAT routing working perfectly with gentoo dom0s but winxp guests it doesn''t seem to work. This is my working config for a gentoo machine: #general name = "test-gentoo"; memory = 256; #booting kernel = "/boot/gentoo-domU"; #virtual disks disk = [ "file:/xen/gentoo/gentoo.img,xvda,w", "file:/xen/gentoo/swap,xvdb,w" ]; root =

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

Hello, everybody! Does anyone have experience of running win7/winxp with xl? As for me, I got HAL_INITIALIZATION_FAILED BSOD on win7 booting and guest hanging in case of winxp. When i run these guests (with the same configs) with xm, everything is ok. The guests boot perfectly. Did anyone run into it too? I use the lattest xen-unstable, but i saw the problem several months ago too. My

Hello, I have Ubuntu installed as a domU and can connect to it over VNC running in dom0. However I cannot increase the resolution above 800x600. I would really like 1024x786. In the Ubuntu guest it says there graphics card is a VESA compatible, and only has 600x400 and 800x600 screen resolutions. My domU config is shown below. I have stdvga=0 I searched the mailing lists, and it said stdvga=1