similar to: the log of qemu-dm-*.log

stubdom: rename the ioemu-dm domain config file to domainname-dm, which is shorter, makes more sense, and sorts better. diff -r c9b516a77927 stubdom/README --- a/stubdom/README Mon Aug 04 11:29:45 2008 +0100 +++ b/stubdom/README Mon Aug 04 12:51:31 2008 +0100 @@ -10,6 +10,9 @@ of video memory for the HVM domain, you of video memory for the HVM domain, you need to avoid the need for ballooning,

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

errors from /var/log/xcp-xapi.log: 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xapi] creating device emulator 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] Device.Dm.start domid=10 661Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] qemu-dm: should be running in the background (stdout redirected to syslog) 661Z|debug||1227 UNIX

Dear xen-users. First of all, I''m not a linux-guru and a beginner with xen and completly new in this mailinglist. I''ve installed Xen on debian 6 and I was successful creating two machines: one for tests and "fogserver" (to test speed of writing computer images), both para-virtualisations.

Hi- I trying to debug a HVM vncdisplay problem, but there is no qemu-dm.loggenerated out in the /var/log/xen driectory. Can someone tell me how I can enable the qemu-dm log. Thanks, -Yung _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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,

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

hi there guys recently, i am studying the qemu , so i have a idea , using the qemu to emulate a winxp in hvm domian(the system is debian). But when i install the winxp , the installtion interface appearing, some seconds later , the hvm domian restart anybody experienced the same problem? Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

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

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"

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/

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:

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

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''m using xen to run real linux system. I''ve configured partition for my system. When I''m installing Debian Etch everything is fine but when I''m starting installed system I get a hang. My xen disk conf is: disk = [ ''phy:/dev/root/node1,ioemu:hda,w'' ] device_model =

On Wed, 2014-01-01 at 09:52 -0600, Marc F. Clemente wrote: > I have seen posts mentioning "traditional" and "upstream" qemu-dm. > But it is not clear to me what the difference is between "traditional" > and "upstream", or how to select either one. This is explained in the xl.cfg(5) man page. http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html

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