similar to: Enabling qemu-dm log

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

hi thereguys today when i create a hvm domain, but it failed. so i see the /var/log/xen/qemu-dm-*.log: domid: 16 -append only allowed with -kernel option as a fresh man of xen , i really can not understand what''s the meaning. best regards _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

hi, I want to pass through "01:00.0",declared as pci=['01:00.0'] in cfg file. but found error log "pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0". in qemu-dm-example.hvm.log In fact, /dev/xen/pci_iomul does not exist. So where /dev/xen/pci_iomul implemented ? I have searched xen and linux code,

Hello, I''ve tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can''t support SPICE, so I installed upstream qemu. ( http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and

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

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

Hi, I''m kinda new to XEN stuff, and I''ve been trying to create a fully virtualized guest on CentOS 5.3 for almost 3 months and no luck yet. I approached this process through several methods, one with virt-install and creating config file manually. Following is what happens when I try to create a guest, and I have included qemu-dm and last part of xend.log logs below too.

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

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/

Package: xcp-xapi Version: 1.3.2-14 Severity: important I imported a HVM from a legacy xm environment. It is attached to one vif, the xenapi management vif It fails to start: # xe vm-start uuid=f2ba4767-7b4f-b416-3da6-3fe059ebfc37 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: device model

Hi, John Can you try the attached patch ? This issue can be reproduced on SMP platform, while the domain 0 is UP. The reason is, after finishing a dma request, the dma thread will trigger the interrupt and then clear the call back function. When guest get the interrupt , it will try to check the call back function, if it is set, then it will trigger a dma request again. So if the checking for

Hi, I''m trying to build a xen-qemu-dm-4.0 package to support the HVM part of the Xen 4.0 package that will be soon in Debian experimental. When I start an HVM domain, I have the following subject line of this thread in my /var/log/xen/qemu-dm-XXXX.log file, and then it stops here. Any idea what I should do to fix? Thomas P.S: my build is using a clone of

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

So how do I set up an HVM with Debian? I tried with device_model_version="qemu-xen", and I got this: libxl: error: libxl_dm.c:1086:libxl__spawn_local_dm: device model /usr/lib/xen-4.2/bin/qemu-system-i386 is not executable: No such file or directory I also tried device_model_version="qemu-xen-traditional", and I got this: libxl: error: libxl_dm.c:1086:libxl__spawn_local_dm:

Package: xen-utils-4.3 Version: 4.3.0-3+b1 Severity: normal When I try to create an HVW withDevian/xen, I run into trouble. It used to work, maybe with xen 4.1, but it has never worked since. Bug 688311 was filed, with the same exact problem. That bug was somehow closed and no resolution or explanation was provided. I have seen posts mentioning "traditional" and "upstream"

Hi: I''ve confronted one of my HVM domain frequently crash due to qemu-dm quit abnormally. Xend.log [2011-05-18 14:32:44 24651 1301875008] INFO (XendDomain:1259) Domain 322-2.vhd (2645) unpaused. [2011-05-18 14:38:26 24651 1201162560] WARNING (image:552) domain 322-2.vhd: device model failure: pid 8637: died due to signal 7; see /var/log/xen/qemu-dm-322-2.vhd.log [2011-05-18

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

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-hypervisor-4.1-amd64 Version: 4.1.4-2 This is related to Bug#699237: Huawei E220 does not work under Debian Wheezy Mainboard Gigabyte Z77X-D3H, 32GB RAM Xen dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux - affected 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux - affected Bus 001 Device 004: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA

This function (introduced quite a long time ago in e7911109f4321e9ba0cc56a253b653600aa46bea - "disable qemu PCI devices in HVM domains") appears to be completely broken, causing the regression reported in http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1805 (due to the newly added caller of it in 56d7747a3cf811910c4cf865e1ebcb8b82502005 - "qemu: clean up MSI-X table