search for: vdevfn

...INFO (XendDomainInfo:2357) createDevice: pci : {''devs'': [{''slot'': ''0x02'', ''domain'': ''0x0000'', ''key'': ''00:02.0'', ''bus'': ''0x00'', ''vdevfn'': ''0x10'', ''func'': ''0x0'', ''opts'': [[''msitranslate'', ''1''], [''power_mgmt'', ''0'']], ''uuid'': ''16d91793-5fe2-e409-9a8c-1bae56a...

...9;t be expected to do so IMO. Clients should not be bothered with xend''s internal representation of a PCI device. This patch populates the ''key'' field within xend if it is uninitialized, similar to current initialization of ''uuid'' field. The ''vdevfn'' field suffers a similar problem if not (optionally) specified by user. AFAICT, the xm client initializes ''vdevfn'' to 0x100 if not specified so I''ve done the same here. Signed-off-by: Jim Fehlig <jfehlig@novell.com> diff -r 28a160746815 -r 461b9d3a643...

...(vnc 1) (uuid b9b91105-4738-b6d6-8b7e-bfb645bb55db) (location 127.0.0.1:5900) ) ) (device (pci (dev (slot 0x1d) (domain 0x0000) (key 0000:00:1d.0) (bus 0x00) (vdevfn 0x28) (func 0x0) (opts (msitranslate 1)) (opts (power_mgmt 0)) (uuid 420c4d30-dd05-25d0-eb25-d013c846b6ef) ) (dev (slot 0x00) (domain 0x0000) (key 0000:01:00.0)...

...ain, pcidev->bus, pcidev->dev, pcidev->func)); + flexarray_set(back, boffset++, libxl_sprintf(gc, "dev-%d", i)); + flexarray_set(back, boffset++, libxl_sprintf(gc, PCI_BDF, pcidev->domain, pcidev->bus, pcidev->dev, pcidev->func)); if (pcidev->vdevfn) { - flexarray_set(back, boffset++, libxl_sprintf(ctx, "vdevfn-%d", i)); - flexarray_set(back, boffset++, libxl_sprintf(ctx, "%x", pcidev->vdevfn)); + flexarray_set(back, boffset++, libxl_sprintf(gc, "vdevfn-%d", i)); + fl...

...configure: [''pci'', [''dev'', [''slot'', ''0x00''], [''domain'', ''0x0000''], [''key'', ''0000:02:00.0''], [''bus'', ''0x02''], [''vdevfn'', ''0x100''], [''func'', ''0x0'']], [''state'', ''Initialising'']] [2010-05-07 17:01:13 4154] DEBUG (XendDomainInfo:675) XendDomainInfo.hvm_pci_device_create: {''devs'': [{''slot'...

...configure: [''pci'', [''dev'', [''slot'', ''0x00''], [''domain'', ''0x0000''], [''key'', ''0000:02:00.0''], [''bus'', ''0x02''], [''vdevfn'', ''0x100''], [''func'', ''0x0'']], [''state'', ''Initialising'']] [2010-05-07 17:01:13 4154] DEBUG (XendDomainInfo:675) XendDomainInfo.hvm_pci_device_create: {''devs'': [{''slot'...

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

...d 1) (keymap en-us) (vnc 1) (uuid c8f2de24-0fc3-dc03-1141-29d7074bdbb6) ) ) (device (pci (dev (slot 0x00) (domain 0x0000) (key 03:00.0) (bus 0x03) (vdevfn 0x20) (func 0x0) (uuid 83e7e9d0-9a6c-228d-e69c-3c6715dabdfc) ) (dev (slot 0x00) (domain 0x0000) (key 03:00.1) (bus 0x03) (vdevfn 0x28) (func 0x1)...

Hi, One of the I noticed during migration from XM toolchain to XL in PCI Pass-through was that we used to specify target bdf in HVM guest as pci = [ ''0000:07:11.6=0@1a'' ] However with XL, it now seems like this is the correct syntax: pci = [ ''0000:07:11.6@1a'' ] Is that correct? I''ve verified that it works but what about zero in

...it shows up in "xm pci-list-assignable-devices" I''ve tried assigning the function to my domU using both the xen config: ... (dev (slot 0x10) (domain 0x0000) (key 0000:09:10.1) (bus 0x09) (vdevfn 0x100) (func 0x1) (uuid c8d37aaf-d175-4792-d67b-dd0bcf9526e8) ) ... and simply doing a "xm pci-attach <domU> 0000:09:10.1" In both cases, I get the message [ 1.001725] pcifront pci-0: Installing PCI frontend [ 1.001853] pcifront pci...

...])), - ]) - ), + ("reg", uint8), + ("func", uint8), + ("dev", uint8), + ("bus", uint8), + ("enable", bool), ("domain", unsigned_integer), ("vdevfn", unsigned_integer), ("vfunc_mask", unsigned_integer), diff -r b19856f6dd76 tools/libxl/libxl_pci.c --- a/tools/libxl/libxl_pci.c Thu Sep 09 09:24:24 2010 +0100 +++ b/tools/libxl/libxl_pci.c Thu Sep 09 12:06:50 2010 +0100 @@ -41,6 +41,15 @@ #define PCI_BDF_SHORT "...

...vid : int; + vnc : bool; + vnclisten : string; + vncpasswd : string; + vncdisplay : int; + vncunused : bool; + keymap : string; + sdl : bool; + opengl : bool; + display : string; + xauthority : string; +} + +type pci_info = +{ + v : int; (* domain * bus * dev * func multiplexed *) + domain : int; + vdevfn : int; + msitranslate : bool; + power_mgmt : bool; +} + +type physinfo = +{ + threads_per_core: int; + cores_per_socket: int; + max_cpu_id: int; + nr_cpus: int; + cpu_khz: int; + total_pages: int64; + free_pages: int64; + scrub_pages: int64; + nr_nodes: int; + hwcap: int32 array; + physcap: int32;...

...XL_LOG(ctx, XL_LOG_ERROR, "Device Model didn''t respond in time\n"); + XL_LOG(ctx, XL_LOG_ERROR, "Device Model didn''t respond in time"); snprintf(path, sizeof(path), "/local/domain/0/device-model/%d/parameter", domid); vdevfn = libxl_xs_read(ctx, XBT_NULL, path); sscanf(vdevfn + 2, "%x", &pcidev->vdevfn); @@ -1211,22 +1222,22 @@ int libxl_device_pci_add(struct libxl_ctx *ctx, uint32_t domid, libxl_device_pci int i; if (f == NULL) { - XL_LOG(ctx, XL_LOG_ERROR, &quo...

...6/site-packages/xen/xend/XendDomainInfo.py", line > 641, in pci_device_configure_boot > self.pci_device_configure(dev_sxp, first_dev = first) > File > "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line > 934, in pci_device_configure > vdevfn = self.hvm_pci_device_insert(dev_config) > File > "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line > 800, in hvm_pci_device_insert > return self.hvm_pci_device_insert_dev(new_dev) > File > "/usr/lib64/python2.6/site-packages/xen/xend/...

The series introduces auto-generation of the type definitions used in the libxl interface followed by auto-generation of a destructor function for each type. In the future it may be possible to use the related data structures for other purposes, for example auto-generation of the functions to marshal between C and language binding data types. tools/_libxl_types.h should be identical both before

Hello, I''m hoping someone may be able to push us in the right direction. I''m trying to get one of our products to work with the current branch of Xen (4.0/4.0.0) but I''m hitting a problem. We are currently using Xen 3.3.2 on a Sun Blade 600 chassis (with x6270 blades) this works great. But when we upgrade to Xen 4.0/4.0.1 we get the following message when

Hi, All the reviews for the AMD 890fx chipset reported that it supports IOMMU v1.2. But I cannot find any mention of that on AMD site. Does 890fx support IOMMU? Do 890fx motherboards with IOMMU exist? Does Xen support 890fx? Regards, Leonardo _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This patch supports basic gfx passthrough on QEMU: - disable emulated VGA adpater if there is passthroughed gfx - register/unregister legacy VGA I/O ports and MMIOs for passthroughed gfx Signed-off-by: Ben Lin <ben.y.lin@intel.com> Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list