similar to: Bug#763102: xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains

Hi, I migrate Xen4.0 to XEN4.1, and found XEN4.1 performance is not as good as 4.0.2. xm shutdown takes longer time, control thru libvirt take longer time, and since I''m testing PCI/VGA passthru, the "createdevice: pci" also take around 5~8 seconds comparing to 1 second in XEN4.0.2. below is my configuration, do you have any suggestions to make the performance better?

On Sat, 2015-08-22 at 00:24 +0200, Volker Klasen wrote: > Hi Ian, > > you can use the patch I posted in the original report, Uh, how on earth did I miss it! > there are two > places that need to be fixed. I'm using it since November. Thanks. Since loads is a classmethod I think the right fix for that issue is to s/self/cls/ in the body rather than s/cls/self/ in the

Control: tag -1 +moreinfo Hello, It seems this was incorrectly closed as xend only since this code can be used on upgrade (as part of rebooting from xend into a new system). I don't have any systems to test but I think the fix is trivially the following: @@ -51,7 +51,7 @@ class DataJSON(Data): class DataSXP(Data): def __init__(self, p): - s = SXPParser()(p) + s =

Package: xen-utils-common Version: 4.4.1-9 Severity: important This bug was already reported as #763102 and was brushed off because maintainer says it implicates xend which is not there in 4.4 anymore. However, this problem is present during upgrade from wheezy to jessie and means that reboots are not possible without physical interventions. As noted in #763102, during shutdown, we can see this

Hi All, Please help me. I am now installing the XEN on my PC and trying to config the pci pass through. My motherboard is intel DQ45CB which is vtd enabled. I downloaded the latest xen4.0 source from xen.org which is the latest release. I downloaded stable-2.6.32-x dom0 kernel source from jeremy''s repository. After compiling the xen and dom0 kernel, I could play it. I could create

Hi All, Please help me. I am now installing the XEN on my PC and trying to config the pci pass through. My motherboard is intel DQ45CB which is vtd enabled. I downloaded the latest xen4.0 source from xen.org which is the latest release. I downloaded stable-2.6.32-x dom0 kernel source from jeremy''s repository. After compiling the xen and dom0 kernel, I could play it. I could create

Sorry to duplicate my issues onto the list - I thought I had looked through this thread before and seen a different error, but apparently Adam and I are running into much the same thing. I'm seeing exactly the same "Failed to assign device to IOMMU" along with the "Device not owned by PCI Back End or pci-stub" in these scenarios. I have not gone back to previous versions,

Changes since v1: - Fix a double-free bug introduced by v1, pointed out by Stefano where internal pointer was being passed back to caller from libxl_create_stubdom() 8<---------------------------------------------------------------------- Currently scratch variables allocated by libxl have the same lifetime as the context. While this is suitable for one off invocations of xl. It is not

Signed-off-by: Vincent Hanquez <vincent.hanquez@eu.citrix.com> --- tools/ocaml/Makefile | 2 +- tools/ocaml/common.make | 2 +- tools/ocaml/libs/xl/xl.ml | 209 ++++++++++++ tools/ocaml/libs/xl/xl.mli | 209 ++++++++++++ tools/ocaml/libs/xl/xl_stubs.c | 706 ++++++++++++++++++++++++++++++++++++++++ 5 files changed, 1126 insertions(+), 2 deletions(-)

Hi, I''m running a machine with: - Hypervisor: xen-unstable - Dom0: xen/next-2.6.32.17 commit c3f5aba942c7516a5c76c47345ff0a473daf2542 Hardware: -MSI 890FXA-GD70 with AMD IOMMU -Phenom X6 I''m trying to do PCI passthrough to a HVM, this fails with: Error: Failed to assign device to IOMMU (0000:04:00.0@100,msitranslate=1,power_mgmt=0) Error: pci: to avoid potential security

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I've updated the feature/bug763102 with the following extra patch: With both your patches applied, xen-init-list works. Cheers, Volker -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlXZ2cgACgkQgKD4KXUzSrhELACg2CCtFNUPtHxNz7XgpQjaYH6b Gn4An26yNob9A7vhz1L8RTWTMCrfc6RY =M2dx -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ian, you can use the patch I posted in the original report, there are two places that need to be fixed. I'm using it since November. Cheers, Volker -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlXXpS8ACgkQgKD4KXUzSriihQCgidnLz9Lx475uQ4dzWz4jDrzM nsUAn3Z/Sy3tA2yquXvyAXnY04pxgOop =GYjR -----END PGP SIGNATURE-----

Hi, all I''m trying SRIOV with Xen but failed to pass through virtual function of SRIOV to dom-U. My platform: Xen-unstable 4.2 Pvops Dom-0 kernel 2.6.32.35 CentOS 5.4 Dom-0 CentOS 5.4 HVM Dom-U And follow VtdHowto wiki page, my steps are: First, bind the virtual function to pci-stub. After that, check the assignable virtual function devices: [root@localhost ~]# xm

Hello all I''ve just installed xen 4.1.1 on my server and was tryoing to tweak xendomains script to work with new xl schema but I can´t get it to save domains. It does start them with some changes I made to it but when I issue service xendomains stop I just get [ OK ] but domains stay running. Has xendomains script been ported to work with 4.1.1 or is there another alternative to it.

I''m running xen 3.1.2 as bastardized by RedHat on a redhat clone operating system. I''m using the xendomains script as it came out of the box to start my domU''s at boot and stop them at shutdown. There are three problems right now: 1) left to its own devices, service xendomains stop attempts to do "xm save" on each of the domU''s. that takes quite a

Source: xen Severity: wishlist Hi, xendomains init and default files in debian folder is not updated from upstream onesfor some years. Some parameters are missed. The more useful parameters when mainly windows domUs are used is XENDOMAINS_CREATE_USLEEP that I setted to 30 or 40 seconds on my systems to decrease the "overload" caused by windows startup (even if pv drivers are installed).

Hello, for everybody who develops or uses the script /etc/init.d/xendomains, there is a serious error in this script. If the given variable XEN_DOMAINS_AUTO_ONLY is set to true in /etc/sysconfig/xendomains, then the saving of the domains always fails - the domains are shut down instead of the saving. This is very bad especially for some HVM domains which MUST be saved instead of shut

Hello, for everybody who develops or uses the script /etc/init.d/xendomains, there is a serious error in this script. If the given variable XEN_DOMAINS_AUTO_ONLY is set to true in /etc/sysconfig/xendomains, then the saving of the domains always fails - the domains are shut down instead of the saving. This is very bad especially for some HVM domains which MUST be saved instead of shut

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: important Dear Maintainer, After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto fails with errors like this Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus:

Processing commands for control at bugs.debian.org: > unarchive 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains Unarchived Bug 763102 > reopen 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common: