search for: libxl_pci

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

...77dd60a2418324580297e # Parent 69c3ae25bb1ddcb0ea44b7566d36d34e9d6a70aa libxl: When checking BDF of existing slots, function should be decimal, not hex Spotted-by: Konrad Wilk <konrad.wilk@oracle.com> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> diff --git a/tools/libxl/libxl_pci.c b/tools/libxl/libxl_pci.c --- a/tools/libxl/libxl_pci.c +++ b/tools/libxl/libxl_pci.c @@ -480,7 +480,7 @@ static int pciback_dev_has_slot(libxl__g return ERROR_FAIL; } - while(fscanf(f, "%x:%x:%x.%x\n", &dom, &bus, &dev, &func)==4) { + while(fscanf(...

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)

...x 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 +++ b/tools/libxl/libxl_pci.c Tue Jan 25 15:34:43 2011 +0000 @@ -268,7 +268,7 @@ static int libxl_create_pci_backend(libx for (i = 0; i < num; i++, pcidev++) libxl_create_pci_backend_device(gc, back, i, pcidev); -...

...been asked to insert to show up. Since the stubdomain is already running when we call the libxl_device_pci_add loop in do_domain_create we should treat it as if "starting == 0". Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r d8c390192ad1 -r 9c1b223e152e tools/libxl/libxl_pci.c --- a/tools/libxl/libxl_pci.c Thu Dec 08 17:43:29 2011 +0000 +++ b/tools/libxl/libxl_pci.c Fri Dec 09 12:01:16 2011 +0000 @@ -819,7 +819,8 @@ int libxl__device_pci_add(libxl__gc *gc, stubdomid = libxl_get_stubdom_id(ctx, domid); if (stubdomid != 0) { libxl_device_pci pcidev_s =...

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/lib...

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

...hows up fine when I issue this xl pci-assignable-list I have pci=['00:1a.0'] on the DomU config file I have added this iommu=soft and swiotlb=force both together and separately to the kernel command line in the DomU (running Debian 8), but I get the same error each time. libxl: error: libxl_pci.c:999:do_pci_add: xc_assign_device failed: Operation not permitted libxl: error: libxl_create.c:1424:domcreate_attach_pci: libxl_device_pci_add failed: -3 Can anyone suggest a cure for this? Many thanks Francis -------------- next part -------------- An HTML attachment was scrubbed... URL:...

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

...c -I../../tools/include > -I../../tools/libxc -I../../tools/include -I../../tools/xenstore -I../../tools/include > -I../../tools/blktap2/control -I../../tools/blktap2/include -I../../tools/include > -Wl,-soname -Wl,libxenlight.so.1.0 -shared -o libxenlight.so.1.0.0 flexarray.o > libxl.o libxl_pci.o libxl_dom.o libxl_exec.o libxl_xshelp.o libxl_device.o > libxl_internal.o xenguest.o libxl_utils.o osdeps.o libxl_paths.o > libxl_bootloader.o libxl_blktap2.o > /usr/bin/ld: libxl_dom.o: relocation R_X86_64_PC32 against > `hvm_build_set_params'' can not be used when making a s...

...ore 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 device 0:0:12.2 is not assignable My CPU(Opteron 6128) is iommu capable. I am using kernel 2.6.32.43 from jeremy''s source with pciback compiled into the kernel. What am I not doing that sets 00:12.2 as an assignable device? _____________________________...

...GEMENT: Loader: 0000000000100000->00000000001795d0 TOTAL: 0000000000000000->000000003e000000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001ef 1GB PAGES: 0x0000000000000000 libxl: error: libxl_pci.c:712:do_pci_add xc_assign_device failed Daemon running with PID 2050

...GEMENT: Loader: 0000000000100000->0000000000179830 TOTAL: 0000000000000000->000000007f800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000000 libxl: error: libxl_pci.c:790:libxl__device_pci_add PCI device 0:12:0.70 is not assignable There is no function 70 on that device. In relation to that, the BDF documentation (http://wiki.xensource.com/xenwiki/BDFNotation) seems to imply that you can specify the extended BDF notation on your kernel boot line in grub. i....

Hello, I hope that I am posting the correct list with this question. I have been trying to get VGA passthrough working on my system for some time now without success. I do not have the system with me right now, so I will not be able to provide any logs or error messages right now. I will be able to to do so in a couple of hours. I have a VT-d enabled system (Motherboard and CPU) on which I wish

Hello, I hope that I am posting the correct list with this question. I have been trying to get VGA passthrough working on my system for some time now without success. I do not have the system with me right now, so I will not be able to provide any logs or error messages right now. I will be able to to do so in a couple of hours. I have a VT-d enabled system (Motherboard and CPU) on which I wish

On Mon, Oct 17, 2011 at 05:36:27PM +0200, Dario Faggioli wrote: > Hi everyone, > > I''m trying to setup PCI-passthrough for a network card on a testbox. > With HVM, everything seems to work, while if I try with a pv-guest the > domain crashes! > > Here''s the thing: > -- > # xl pci-list-assignable-devices > 0000:07:00.0 > 0000:07:00.1 > >

...GEMENT: Loader: 0000000000100000->000000000017c510 TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 00000000001015a0 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000005fb 1GB PAGES: 0x0000000000000001 libxl: error: libxl_pci.c:712:do_pci_add xc_assign_device failed Daemon running with PID 11389 Leading up to this error, I have done the following to put the device into what is supposedly an assignable state: # stop lightdm # echo 0000:00:01.0 > /sys/bus/pci/drivers/radeon/unbind # modprobe xen-pciback # echo 0000:0...

..._backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl: don''t leak output vcpu info on error in libxl_list_vcpu libxl: don''t leak ptr in libxl_list_vm error case libxl: don''t leak pcidevs in libxl_pcidev_assignable libxl: don''t try to fclose file twice on error in libxl_userdata_store libxl: use pipe instead of temporary file for VNC viewer --autopass libxl: don''t leak buf in libxl_xen_console_read_start error handling libxl: replace for loop with more idiomatic do-...

...> pci-assignable-list > > I have pci=['00:1a.0'] on the DomU config file > I have added this iommu=soft and swiotlb=force both together and separately > to the kernel command line > in the DomU (running Debian 8), but I get the same error each time. > > libxl: error: libxl_pci.c:999:do_pci_add: xc_assign_device failed: Operation > not permitted > libxl: error: libxl_create.c:1424:domcreate_attach_pci: libxl_device_pci_add > failed: -3 Can you please attach the following: 1. The complete domU config file 2. A complete log of the command and all the output 3. The...

...ened gentoo as Dom0 on Xen 4.2, with several DomUs, also running hardened gentoo. I have PCI passthrough working for a DomU (3 network cards, 2 wired, 1 wireless), but when i try to pass it my usb root hub, i get the following error, during xl create (or when i use xl pci-attach): libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn''t support reset from sysfs for PCI device 0000:00:0f.2 After that, the system (both Dom0 and the DomUs) are terribly slow, sometimes completely inaccessible (took me several minutes to get the dmesg output (see attached for full output)...