similar to: VNC problem in qemu-dm

Hi all, thanks to Mats I managed to compile a custom Linux kernel (2.6.16.29) and Xen 3.0.3. I then did "apt-get bcc" (to be able to build "hvmloader") cd /usr/src/xen...src/tools/ make install Then I could launch Windows XP but I wouldn''t see the SDL window... because qemu-dm has a compile time dependency on SDL devel. "apt-get libsdl1.2-dev" I

Hello, i have 2 problems with the virtualization of windows on a xen- domain. The first one is the vnc connection. I''ve set everything up, but if i try to do a xm console XX, it says something about xenconsole tty file not found, and if i look up the qemu-dm-XXXX.log there is just one line that says : "/path/to/xen/bin/qemu-dm invalid option -- ''-

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,

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

Hi all, In xen-4.1.2 src/tools/libxl/libxl_dm.c, there is a function called `libxl_build_device_model_args_old`, the func will build qemu-dm cmdline args according to the xl-formated configuration file specified by xl create domid: 2 -videoram option does not work with cirrus vga device model. Videoram set to 4M. Strip off blktap sub-type prefix to /home/malei/c2.delta.img (drv

Hi. I can''t use the vnc option (VNC=1 in my xmexample.hvm file), when I use RedHat or Fedora on 64 bits. The qemu log, say /usr/lib64/xen/bin/qemu-dm: invalid option -- ''-vncconnect'' But when I use RedHat or Fedora 32 bits, works fine. There is a problem or incompatibility in the 64 bits Xen kernel and the VNC option ? Best regards Luis

I was looking at vnc.c to see what would be involved in making a reverse VNC connection (vnc server connects to the client), and it looks possible but I also wondered if there was any reason why libvncserver couldn''t be used instead? Both qemu-dm and libvncserver appear to be licensed under GPL although I haven''t checked what version. I''ve never figured out whether

Package: xen-utils-3.1-1 Version: 3.1.0-2 Severity: normal Hi, When running an HVM domain with qemu-dm, I get the following in the logs: /usr/lib/xen-3.1-1/bin/qemu-dm.debug: line 10: /usr/lib/xen/bin/qemu-dm: No such file or directory /usr/lib/xen-3.1-1/bin/qemu-dm.debug: line 10: exec: /usr/lib/xen/bin/qemu-dm: cannot execute: No such file or directory And indeed there is no xen/

I tried using http://ftparchive.gplhost.com/debian/pool/lenny/main/x/xen-qemu-dm-3.4/xen-qemu-dm-3.4_3.4.2-1_amd64.deb But my hvm instance wouldn't start. I got this in the qemu-dm log domid: 22 qemu: the number of cpus is 2 Watching /local/domain/0/device-model/22/logdirty/next-active Watching /local/domain/0/device-model/22/command char device redirected to /dev/pts/0

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

Hi, first of all, my name is Karsten and I am fairly new to xen. A former colleague of mine has set up a xen dom0 with 4 virtual machines runnig on it. A few months ago this colleague left the company. Last week our office Building has been hit by a lightning wich resulted in an power blackout. After the power went back again, the system booted and all but one of the virtual machines went

Package: xen-utils-3.1-1 Version: 3.1.0-2 Severity: wishlist File: xen-utils-3.1 qemu-dm currently is built with OSS support. This occours /dev/dsp locking once a HVM guest is started. If you have /dev/dsp already open by other applications, sound won't work within guest VM, otherwise qemu-dm will lock and won't be available to the host OS. Would be nice to see qemu-dm built with alsa

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information

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,

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

Package: xen-utils-3.4 Version: 3.4.2-2 # cat qemu-dm-openfiler.log failed to set up fds or execute dm /usr/lib/xen-3.4/bin/qemu-dm: ['OSError: [Errno 2] No such file or directory\n'] -- Jiann-Ming Su "I have to decide between two equally frightening options. If I wanted to do that, I'd vote." --Duckman "The system's broke, Hank. The election baby has peed in

I have a headless CentOS 5.3 box running Xen 3.3.1. The DomU (domcont) is running off a DRBD device and the network bridge (br0) is running over a bonded ethernet link. All network interfaces are running fine and the DRBD devices replicate over their respective links. The DRBD device that I am trying to boot off is /dev/drbd1 and is set to Primary on the Dom0 that is running this DomU.

Hello, I want to install a 2003 guest on a Debian Etch with xen binary packages (apt-get install), but through a vnc console (no graphical interface). So I launch the xm create in an ssh connection, and want to connect through vnc to complete the installation of windows. So the domain gets created with xm create but no VNC port is displayed: ----- Using config file "2003.hvm". VNC= 1

When I try to create a PV domU, the VM starts up and I can access it through "xm console <id>", but when I try to connect to it through VNC, the port just hangs. I''ve tried using RealVNC and TightVNC, and also tried on Linux and Windows. All that happens on the client is that it says that the connection has established, and hangs there. I''ve tried running

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