search for: xenpcipassthrough

Hi. link for ''XenPCIPassthrough <http://wiki.xen.org/xenwiki/XenPCIPassthrough> - PCI passthru to assign a PCI device to a guest'' on '' http://wiki.xen.org/xenwiki/XenDevHome'' not works. need to change from ''http://wiki.xen.org/xenwiki/XenPCIPassthrough'' to '' http://wiki...

I''m using Xen 4.01 and jeremy''s pvops kernel, the kernel version is 2.6.32.18. At first I want to test the performance of pci passthrough when it comes to the network card 82571EB I''m using the Jeremy''s kernel 2.6.32.18 as DomU kernel too. And I found if the interface is not connected, I mean the network card receives no packet, ( the network card

I''m using Xen 4.01 and jeremy''s pvops kernel, the kernel version is 2.6.32.18. At first I want to test the performance of pci passthrough when it comes to the network card 82571EB I''m using the Jeremy''s kernel 2.6.32.18 as DomU kernel too. And I found if the interface is not connected, I mean the network card receives no packet, ( the network card

hi, I want to know if there is any particular linux kernel version on DomU that is required for PCI pass through to work ? It is not clear from the link here http://wiki.xensource.com/xenwiki/XenPCIpassthrough. I want to use linux kernel 2.6.27.39 as my DomU. Can that be used for PCI pass through ? thanks and I appreciate any help. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi experts I use xen-4.0.0 and dom0 is 2.6.33 and domU is 2.6.34 #lspci ............... 01:00.0 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 01:00.1 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit

...iommu, but pci passthrough is widely common. xm dmesg shows: (XEN) I/O virtualisation disabled Also, a friend told me, on its (pci passthrough working) machine the same message appears. AND, any documantation regarding this feature dosn''t mention vt-d at all: http://www.wlug.org.nz/XenPciPassthrough http://www.google.de/search?q=xen+pci+passthrough So, what does the error mentioned in my subject mean? Is it a wrong interpreted issue by the kernel, or do I really need vt-d, which my board obviously does not support? (ECS G31T-M with core 2 quad q6600) OR, is there another (more easy) solu...

I see that by default Xen seems to emulate a Realtek 8139 in my hvm''s. I have a quad port Intel PCIe nic available and wondered if I remove the network line altogether from the config and pass the nic in will I have near native performance without pv drivers? Also, is it possible to pass in one of each of the 4 ports into 4 different hvms? I don''t exactly know how the NIC

...____ Frédéric Abel| RTS France BeNeLux | Quantum Corporation ________________________________ From: Frederic Abel Sent: jeudi 5 mai 2011 16:28 To: xen-users@lists.xensource.com Subject: PCI passthrough on PV domU crashes with iommu=soft Hello , Following the http://wiki.xen.org/xenwiki/XenPCIpassthrough doc. I get several issues to perform pci passthrough The config file is in Addendum 0 I''m using the debian XEN 4 and kernel 2.6.32-5 for xen on squeeze dom0 and domu (see addendum 1) I managed to pci hide the 2 ports (see addendum 2) If not using the iommu=soft I get a FW issue...

Hi all, I'm just curios and would like some input from the community on this one. We're busy budgeting for a couple of new servers and I thought it would be good to try out the Core i7 CPU's, but see the majority of them don't offer VT-d, but just VT-x. Looking at the LGA1366 range, only the "Intel lga1366 i7 980XE" (from the list of what our suppliers stock) have VT-d,

Hi guys, i have 4 Xen servers, two with Xen 3.2.1 and the other two with Xen 4. All four servers with 3 network card attached to different networks, 3 of these interfaces are bridges (configured in the ''/etc/network/interfaces'' config file, NOT in xend-config.sxp file) and one is used for the ISCSI service, where the virtual machines are loaded. The problem is,

Hello I am new in XEN and Linux. I am trying the VGA passthru. I can xen-pciback.hide EtherNet, Serial Com port. But when I xen-pciback.hide my VGA. I can no longer login to the Linux(Fedora 12). Then how can I xm create a XP DomU guest? Can anyone help? I am using Intel Q35 MB with Intel Core2 CPU. _______________________________________________ Xen-users mailing list

Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don''t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the

Xen Community: As many of you are aware, the Xen 4.0 hypervisor is due to ship tomorrow (shhhh, don''t tell anyone) and I wanted to get submissions underway for Xen 4.1 features. I have updated the Roadmap Wiki page (http://wiki.xensource.com/xenwiki/XenRoadMap) with a new section for Xen 4.1 features to be added. Feel free to add your ideas or send me your features and I will update the

So yesterday I got was able to get a domU successfully using a PCI SCSI card. This morning I restarted the host server. When I try to start up the same domU I get this error: Error: pci: improper device assignment specified: pci: 0000:0e:04.0 must be co-assigned to the same guest with 0000:0e:04.0, but it is not owned by pciback. How do I make this card owned by pciback on reboot. Do I need to

Hello all, I''m trying to pass my PCI device through to an HVM. I''m following the steps on the xen pci passthrough wiki. First I check my pci devices #lspci - 03:00.0 VGA compatible controller: ATI Technologies Inc Device 671d 03:00.1 Audio device: ATI Technologies Inc Device aa80 04:00.0 Display controller: ATI Technologies Inc Device 671d 04:00.1 Audio device: ATI

...hwinge> [ 0.401609] pcifront pci-0: Creating PCI Frontend Bus 0000:00 <tschwinge> Yet, staying with that kernel won't be the solution. :-) <bwh^> tschwinge: No indeed If I use the ``iommu=soft swiotlb=force'' switches as given on <http://wiki.xensource.com/xenwiki/XenPCIpassthrough>, nothing changes, apart from an additional ``PCI-DMA: Using software bounce buffering for IO (SWIOTLB)'' line in the dmesg. Any ideas? Regards, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Si...

...hwinge> [ 0.401609] pcifront pci-0: Creating PCI Frontend Bus 0000:00 <tschwinge> Yet, staying with that kernel won't be the solution. :-) <bwh^> tschwinge: No indeed If I use the ``iommu=soft swiotlb=force'' switches as given on <http://wiki.xensource.com/xenwiki/XenPCIpassthrough>, nothing changes, apart from an additional ``PCI-DMA: Using software bounce buffering for IO (SWIOTLB)'' line in the dmesg. Any ideas? Regards, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Si...

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Hello, I''m facing a strange issue with network card PCI passthrough on my openwrt test domU. - With network PCI passthrough, DNS lookup failed for some domains (exemple, google.com) but not for other (free.fr my ISP, or my domain jbfavre.org). I can ping an IP address without any problem. - Starting domU as a "normal" (ie without PCI passthrough), no problem. As far as I can