similar to: [PATCH] libxl: When checking BDF of existing slots, function should be decimal, not hex

Add commands to automatically prep devices for pass-through The current method for passing through devices requires users to either modify cryptic Linux boot parameters and reboot, or do a lot of manual reads and writes into sysfs nodes. This set of patches introduces commands to make this easier. It expands on the concept of "assignable" (from the list_assignable_devices command).

To remove a pci passthough device from QEMU (upstream). Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- tools/libxl/libxl_internal.h | 2 ++ tools/libxl/libxl_qmp.c | 35 +++++++++++++++++++++++++++++++++++ 2 files changed, 37 insertions(+), 0 deletions(-) diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h index 1dff211..84da6b1 100644 ---

Fix a xl/libxl segfault when assigning a device to the guest (bug http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1713). Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r b05892ff0fce tools/libxl/libxl_pci.c --- a/tools/libxl/libxl_pci.c Tue Jan 25 15:14:52 2011 +0000 +++

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1323432076 0 # Node ID 9c1b223e152eaaa3861f9b6132590de0b4f6cb7e # Parent d8c390192ad1147d7202cf04be090478f1810a5d libxl: fix cold plugged PCI devices with stubdomains Since 23565:72eafe80ebc1 the xenstore entries for the stubdomain''s PCI were never created and therefore the stubdom ends up waiting forever

Changes since last time: - split auto-generated code in to c and h files - un-break the build system - fix ocaml binding due to libxl API change - lot''s of tidy-ups too numerous to mention Please consider and apply :) -----8<--------------------------------------------------------------- Introduce python binding for libxl. The binding is not yet complete but list_domains,

* Introduce new variants of the logging functions which include errno values (converted using strerror) in the messages passed to the application''s logging callback. * Use the new errno-including logging functions everywhere where appropriate. In general, xc_... functions return errno values or 0; xs_... functions return 0 or -1 (or some such) setting errno. * When

Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl:

The e820_sanitize() function in libxl_pci.c expects one of its arguments to be non-zero; but since a recent changeset, it can typically expect *to be* zero. Since the zero case is handled properly, just remove the check. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> diff -r d35a117afa2f -r f9ce45c9f984 tools/libxl/libxl_pci.c --- a/tools/libxl/libxl_pci.c Tue Mar 27 15:25:07

From 18344216b432648605726b137b348f28ef64a4ef Mon Sep 17 00:00:00 2001 From: Liu Jinsong <jinsong.liu@intel.com> Date: Fri, 23 Aug 2013 23:30:23 +0800 Subject: [PATCH V3] xl: HVM domain S3 bugfix Currently Xen hvm s3 has a bug coming from the difference between qemu-traditioanl and qemu-xen. For qemu-traditional, the way to resume from hvm s3 is via ''xl trigger'' command.

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

I am running Xen 4.6 on CentOS 7 in a Dell Poweredge T430 I need PCI Passthrough to get USB working. I am following the Xenproject Wiki I have enabled the Virtulasation in the BIOS. I have xen_pciback as a module I have issued the command: xl pci-assignable-add 00:1a0.0 and it shows up fine when I issue this xl pci-assignable-list I have pci=['00:1a.0'] on the DomU config file I

I have a system with several reserved ranges low in the e820 map which cause problems when starting PV domains with PCI devices. The machine memory map looks like: (XEN) 0000000000000000 - 0000000000060000 (usable) (XEN) 0000000000060000 - 0000000000068000 (reserved) (XEN) 0000000000068000 - 000000000009ac00 (usable) (XEN) 000000000009ac00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000

I always failed to build the xen in my enironment, with following error (my gcc version is 4.1.2): > gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value > -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD > -MF .libxenlight.so.1.0.0.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -Werror

I have a USB controller I wish to pass to a HVM guest. More specifically a WindowsXP HVM guest if that matters. I have iommu=1 on the hypervisor line in grub.cfg as well as xen-pciback.hide=(00:12.2). In the VMs config file I have the following: pci= [''00:12.2''] Whenever the VM is started it gives the following error: libxl: error: libxl_pci.c:794:libxl__device_pci_add PCI

Hi, unfortunatly your latest change "AMD,IOMMU: Clean up old entries in remapping tables when creating new one" (Changeset 26517 in xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at boot for me. When i tried to boot latest versions of xen unstable or xen-testing, my dom0 gives me the message: (XEN) ************************************* (XEN) Panic on CPU 0: (XEN)

I think this is a bug in the xl toolchain. lspci -s 0000:12:0.* 12:00.0 Display controller: ATI Technologies Inc Device 671d 12:00.1 Audio device: ATI Technologies Inc Device aa80 sudo xm pci-list-assignable-devices 0000:13:00.0 0000:13:00.1 0000:12:00.0 0000:12:00.1 So there is a multi-function device (actually one ASIC of a AMD Radeon 6990 card). It has two function addresses 0 = Display

I''ve just had my first attempt at getting VGA passthrough to work, and it crashed the machine. I''m trying to understand whether this is a problem with my hardware, configuration or a software problem. I''m running Xen 4.1.2 with Linux 3.1.2 The CPU is an Intel Core i5-650 http://ark.intel.com/products/43546/Intel-Core-i5-650-Processor-%284M-Cache-3_20-GHz%29 The Video

Hi all, I am having problems to get the SeaLevel IO card to work with CentOS distro. Basically the card is being recognised and shown by lspci BUT /proc/devices file is not updated with the new devices does anyone know why. ? Could someone tell me what/where infos are needed to get /proc/devices to be updated. The reason I require the /proc/devices infos is because I want to run a mknod

PXE-On-A-Disk from (ftp://ftp.scyld.com/private/jlehan/pxe-on-a-disk.html) was posted on syslinux mailing list: http://syslinux.zytor.com/archives/2005-December/006222.html. It is being mentioned by syslinux wiki, or some other documentation of syslinux that I currently can't find. I tried etherboot2ethersel.pl from PXE-On-A-Disk (ftp://ftp.scyld.com/private/jlehan/pxe-on-a-disk.html)

I have RTFM but it is limited on offering help when a problem crops up for a noob who is not a programmer. I DL and installed the WINE program on my Ubuntu 7.10 and can see it on the Applications. Selecting 'Configure Wine' brings up the 'grey' screen but nothing I do to it seems to function. I opened the terminal and typed 'winecfg' and stuff happens like: 'bob at