similar to: [PATCH]: Don''t ask for a VNC password after HVM live migrate

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,

Hi, Sorry, I should not have removed infomation on xend. image.py, line 399, in configVNC config.remove([''vncpasswd'', vncpasswd_vmconfig]) When vncpasswd is removed, qemu-dm cannot be started in reboot of hvm domain. Because necessary information disappears. It cannot be helped though information in config list remains in xenstore. This patch corrects above. Regards,

I''ve set xend service properties as follows: config/vnc-listen astring \''0.0.0.0\'' config/vncpasswd astring \''vnc\'' config/default-nic astring ''nge1'' but I get an authentication error whenever I try to connect to the console with ''vncviewer :0'' - I''m on the xvm host itself. other relevant data: SunOS

Hello all I am using open source xen v 3.0.4. When network-nat and vif-nat is activated in the config file, modified guests boot ok but hvm guests does not have network connection. Here is the config files: xend-config.sxp ------------------------------------- #(network-script network-bridge) #(vif-script vif-bridge) (network-script network-nat) (vif-script vif-nat)

(sent to the kvm list erroneously) -------------- next part -------------- An embedded message was scrubbed... From: Chris Lalancette <clalance at redhat.com> Subject: [PATCH]: Fix silly output for virtio devices in /proc/interrupts Date: Wed, 21 May 2008 14:51:45 +0200 Size: 4582 Url: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20080521/38a29f92/attachment.eml

(sent to the kvm list erroneously) -------------- next part -------------- An embedded message was scrubbed... From: Chris Lalancette <clalance at redhat.com> Subject: [PATCH]: Fix silly output for virtio devices in /proc/interrupts Date: Wed, 21 May 2008 14:51:45 +0200 Size: 4582 Url: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20080521/38a29f92/attachment.eml

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"

Hi All, Im getting the following error when I run virt-install: bash-3.2# virt-install -n winxp-01 --hvm -r 384 --vnc -f /etc/opt/vms/winxp-01.img -s 16 -c /etc/opt/images/windowsXP_SP2.iso Starting install... libvir: Xen Daemon error : POST operation failed: (xend.err ''Error creating domain: vncpasswd is not set up in VMconfig and xend-config.'') Traceback (most recent call

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

Attached is a simple patch to fix the return value from the 64-bit kernel when you call with a bad system call number with tracing enabled (for either ptrace or audit). What should happen is that the user process gets a -ENOSYS return call from the syscall; what actually happens (only in the 64-bit kernel) is that you get back the system call number. The 32-bit kernel does not suffer from this

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

All, Long ago Xen added code to the device model to basically do an fsync() after every data write if the user in the guest specified that IDE write caching should be disabled. This works fine, except in the case where you are doing O_DIRECT writes inside the guest (ala dd if=/dev/zero of=/dev/hdb oflag=direct). This is because you can get out of ide_write_dma_cb() in the middle of the loop

Unable to connect to my HVM # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3869 2 r----- 368.6 vm00 45 128 1 -b---- 62.3 The vm00 changes state from "r" to "b" after about a minute. (I have a fedora dvd in the drive.) #cat

Hello, I have now shfited to Centos 5.5, and I am testing live migration between 2 physical hosts with XEN 3.1.2. XEN 3.1.2 (virtualization) is included in centOS 5.5 during the installation phase, so everything is handled by default. A third host with Ubuntu OS serves as the network file system. The three hosts are connected by one D-link gigabit switch (DGS-2205). The downtime of live

Hi, i''m a little bit stuck here with creating a HVM-Windows (w2k3) Guest under Xen 3.1. I''m using ubuntu 7,10 with a 2.6.22.16-xen-patched kernel which seems to be stable for single cpu-linux guests. Cpu is a Q6600 and XD,VT and VT-d is enabled in the bios. When i create the windows guest with ''xm create w2k3 -c" (conf below) I get: "Started domain

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

Hi. I found this issue with IA64 box while looking at the c/s of 18204:21dd1fdb73d8, but I believe the things is same with x86 box. I''m not sure whether this patch coexist with the old ioemu which is to be removed soon. So it might be desirable to apply this patch after deleting the internal ioemu tree. thanks, xm: Don''t spawn vncviewer twice. Without this patch, vncviewer

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

Hello, When I start an HVM domU qemu return me the error "xs_read(): vncpasswd get error..." I''m running Xen 3.1 fedora patch + 2.6.20 + ubuntu feisty. Xen Packages come from Cedric Gabriello ( http://cedric.gabriello.fr/ ) <http://cedric.gabriello.fr/> It''s very strange because the VM seems to start ... but qemu process appear as [ defunc ] and of course

Hello, This is my first post in this list. I''m running Debian Squeeze as Dom0 on a bi-xeon 64 bits : root@sd-29499:/etc/xen# uname -a Linux sd-29499 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux I''m trying to install a Squeeze DomU but there is no network card, even during install wich doesn''t show any network card with lspci (but when I