similar to: [PATCH] Xend: Fix PCI Device Configuration

This is a small fix of the error handling in device_create(). Signed-off-by: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com> Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

When destroying pcifront/pciback, the following message appears in the guest linux kernel log. WARNING: g.e. still in use! WARNING: leaking g.e. and page still in use! This is caused by the wrong disconnect procedure that pcifront terminates the gnttab foreign access before pciback unmaps the ring. This patch corrects the handling of pcifront/pciback destruction sequence. Firstly pcifront

Currently console class''s "other_config" parameters (such as "vnclisten" and "vncpasswd") are not passed to xend when creating a domain by xm command through xen-api. The attached patch fixes this problem. Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list

This patch enables ''xm pci-attach/detach'' commands to be executed via xen-api. Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Add direct pci device assignment support. This patch depends on the previous patch (1/3). ----------------------------------------- Fields for DPCI class: (RO_inst) VM PPCI hotplug_slot <- same as vslot param of pci-attach/detach. (RO_run) virtual_domain virtual_bus virtual_slot virtual_func virtual_name <- domain:bus:slot:func

Hi, It seems that destroying pcifront/pciback always fails on current xen. This patch fixes the problem, making pciback switch to "Closed" state after pcifront switched to "Closing" state. Regards, ------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi all, I am trying the pci-passthrough on xen 3.3.0. I binded the pci slot to pciback using late binding. But xend fails to allocate this slot to domU. linux-242:/home/xen-3.3.0 # xm create -c pci=08:01.0 /etc/xen/xen3.3_guest1 Using config file "/etc/xen/xen3.3_guest1". Error: [Errno 2] No such file or directory: ''/sys/bus/pci/devices/0000:06:00.0/config''

Hey everyone, I realize that people asking about PCI passthrough has been thoroughly beaten to death many a time, however I couldn''t find the answer to these questions anywhere (and I''d really like to know :P) so please just bare with me. I know the GART built into AMD chipsets can act as a "mini IOMMU" and do DMA translation but not protection/isolation. However,

In current xend, we can not assign co-assignment devices to different guests, even for pv guests. This patch loosens the policy for pv guest: if none of the co-assignment devices have been assigned to hvm guest, we can assign the devices to different pv guests. The patch also adds a detection: if a device has been assigned to guest, we can't try to "xm pci-attach" it to the same

I had an issue late yesterday where some windows domU''s were down. The person who "owns" those domUs let windows updates install and then restart, which they failed to restart. When I tried to manually restart them I was getting can''t allocate memory errors. In the past I''ve had can''t allocate memory errors when trying to bring up a new domU.

# HG changeset patch # User Jim Fehlig <jfehlig@novell.com> # Date 1288301229 21600 # Branch xend-pci # Node ID 461b9d3a643a2c67c961d9fc468a804891f3770d # Parent 28a16074681582f1209c9077f870ccf44927133e Fix pci passthru in xend interface used by libvirt Attempting to define or create a domain whose XML config contains a passthru PCI device fails with libvirt xen84: # cat win2k8r2.xml ...

[2005-09-19 16:40:21 xend] ERROR (process:37) [block-file] ioctl: LOOP_SET_FD: Device or resource busy [2005-09-19 16:40:21 xend] ERROR (process:37) [block-file] ioctl: LOOP_SET_FD: Device or resource busy [2005-09-19 16:40:21 xend] ERROR (process:37) [block-file] ioctl: LOOP_SET_FD: Device or resource busy [2005-09-19 16:40:21 xend] ERROR (process:37) [block-file] ioctl: LOOP_SET_FD: Device

hi guys My OS is centos 5.4 uname -a : Linux localhost.localdomain 2.6.18-prep #1 SMP Mon Jul 12 20:03:46 CST 2010 x86_64 x86_64 x86_64 GNU/Linux and my xen version is 3.3.1, I install xen from souce code. The xen dom0 and xend is ok but I can''t use virt-install to install a domU. The error is below:

Package: xen-utils-common Version: 3.2.0-1~bpo4+1 Severity: minor I use the version from backports, but it's still present in sid. In /etc/xen/xend-config-sxp : #(xen-tcp-xmlrpc-server-address 'localhost') #(xen-tcp-xmlrpc-server-port 8006) should be #(xend-tcp-xmlrpc-server-address 'localhost') #(xend-tcp-xmlrpc-server-port 8006) Small typo in a commented line, but

I rebooted my machine and now when trying to run a "vm ... virsh create /etc/xen/vm1.xml" I am getting the following error: libvirtError: virDomainCreate() failed POST operation failed: (xend.err ''Device 0 (vkbd) could not be connected. Hotplug scripts not working.'') I tried restaring xend and even mounting and unmounting the partition that holds the vm and still no

Error:Unable to connect to xend:No such file or directory.Is xend running ?" When i tried to start up  xend i am getting the  error message like this "Error:Unable to connect to xend:No such file or directory.Is xend running ?" When i check the file /var/log/xen/xend.log i am getting the  follwing log messages. How should i fix this problem ? ExpatError: no element found: line

Comparing my last know working configuration with the current one, it appears to be gagging on the new localhost\.localdomain that is in the configuration file. I don''t know if this got added by my machine when compiling. diff -ur xen-3.0-testing.hg/install/etc/xen/xend-config.sxp xen-unstable.hg/install/etc/xen/xend-config.sxp --- xen-3.0-testing.hg/install/etc/xen/xend-config.sxp

Hi, I am posting this message because past 36 hours have been nightmare for me. I finally have solved the problem I by temporarily moving put the xml files from /var/lib/xend directories reboot then xend started. And DomU''s were failing to start the above xml files I kept back and got all DomU''s back. I am very very surprised.I do not have any logical answer to this some one

Resent of mail sent on 28.04. xend: fix bug in option parsing If you enable legacy tcp xmlrpc in xend''s config but omit to enable ssl the following backtrace is generated when starting xend: [2010-04-28 16:09:04 15754] ERROR (SrvDaemon:349) Exception starting xend (''NoneType'' object has no attribute ''rfind'') Traceback (most recent call last): File

Hi I tried building xen on my IA64 machine. It builds and installs smoothly. But I have not been able to start xend. I get the error in /var/log/xen/xend.log as below: [2007-06-14 05:02:01 xend 26504] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. [2007-06-14 05:02:01 xend 26520] INFO (SrvDaemon:322) Xend Daemon started [2007-06-14 05:02:01 xend 26520] INFO