similar to: xen networking and pci late binding

Hi, I am trying to set up a Xen server using two 4-port NIC cards. The exact type: D-Link DFE 580TX. There are no problems using this cards under plain linux. The driver is called ''sundance''. But when I use pciback.hide the DomU can''t access this card. I have had the same task when using the NIC BCM 5708 (NetXtreme II). I had found a message in

Hi I have an Asus M2N32 WS Pro, 4G Ram, AthlonX264 4600+. I Installed SuSE 10.3 (64bit) on Dom0, LVM on Raid 5. All domU''s boot off LVM, using same Suse 10.3. I have a firewall (fw) domU running shorewall and a domU name-dhcp-server (nds). Somewhere in between 10 and 16 hours the network stalls. In dns, I can see dhcp queries and offers, but these never make it to the clients in the

Hi, once again, Problems with pciback and pci passthrough the system -------------------------------------------------------------------------------- DOMAIN0:~# lspci -tv -[0000:00]-+-00.0 nVidia Corporation nForce3 250Gb Host Bridge +-01.0 nVidia Corporation nForce3 250Gb LPC Bridge +-01.1 nVidia Corporation nForce 250Gb PCI System Management +-02.0

I am a bit confused on the PCI stuff. PASSTHRU-- does this mean that pcifront is not needed? Or only that the PCI is not limited as it is with slot. In general, none of the docs are getting me anywhere with xen 3.0.3. Example: I run this: echo -n 0000:2:0.1>/sys/bus/pci/drivers/pciback/new_slot echo -n 0000:2:0.0>/sys/bus/pci/drivers/pciback/new_slot echo -n bind 0000:2:0.0 >

Hi, how would I make it so that a particular virtual network interface of dom0 is attached to a particular bridge created for a particular VM? When I start the VM with 'virsh start <domU>', I get interfaces vif1.0, vif1.1 and vif1.2. After shutting down domU with 'virsh shutdown <domU>' and starting it again as before, the virtual network interfaces are vif2.0,

I have a OpenSuse 10.3 with xen 3.1.0 running and it''s been running fine for a few months. This past weekend it suddenly started to act up and after some troubleshooting I can now say that it seems like the guests(domU) loose the outgoing network pipe, from the console I can see that the TX counter is stuck at the same value but it''s no errors. It behaves as if whatever I try to

Hello everybody, for just one week I try to install three servers on an OpenSuSE 10.3 dom0 equipped with 4 NICs. One server is an OX using the onboard NIC via xenbr0. This server runs!! For my IPCop server I intended to use the three remaining NICs (Intel Pro100/S, 3Com 3C590, Realtek RTL-8139). These three NICs should be used natively by my IPCop. So I tried to use the pciback driver. I wrote a

Hello, I´m trying to map one network interface of a Dual-Port e1000 Server Adapter to a DomU (firewall). In Dom0 the adaper is seen with lspci as: 06:00.0 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) 06:00.1 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) My goal is to map only 06:00.1 to DomU so I used this

Hi! I''ve 5 DSL routers and a linux router in a switch. The linux router is doing NAT for a LAN network, but it freezes when I set up load balancing with this command: ip route add default proto static\ nexthop via 192.168.1.10 dev eth1\ nexthop via 192.168.1.20 dev eth1\ nexthop via 192.168.1.30 dev eth1\ nexthop via 192.168.1.40 dev eth1\ nexthop

I have this cheap "ENCORE 10/100Mbps Fast Ethernet PCI Adapter" which comes with its own driver that compiles to 'sundance.ko' and performs bad (30% packet loss) on a fully updated CentOS 4.4 box. This brand, model and driver have worked OK for me on some other CentOS installations, none of which are 4.4. Short of replacing the board, which you can bet I will do, can anybody

Despite what Keir said on your timing requirements, I guess you get the famous co-assignment message. See at the end of this: http://www.nabble.com/xen-3.3.0-pv-pci-passthrough-co-assigned-problem-td20008460.html BR, Carsten. ----- Originalnachricht ----- Von: mdlabriola@yahoo.com Gesendet: Mit, 15.4.2009 13:56 An: xen-devel <xen-devel@lists.xensource.com> Betreff: [Xen-devel] 3rd party

Hello everone, I am new to this mailing list. I am regarding problems while trying to load an additional driver module. The module is sundance.o, used for D-Link DFE 550 nics. I downloaded this driver tarball from the D-Links website. I am using Syslinux 1.52 which is based on the 2.4.18 kernel. My syslinux is embedded on three floppy disks and all works pretty well and boots up without any

Hi. Im faced with a little problem when trying to give an Ali USB 2.0 controller to a guest system: when i try to start my domu, it says that the backend device could not be found. Im using Debian etch both as dom0 and as domU. Im using the standard binary installation from the Debian etch repositority tree (kernel, hypervisor, ...). Im running xen 3.0.3-1 and both use a 2.6.18 kernel. In

I am using the latest xen unstable and trying to install this 00:19.0 Ethernet controller: Intel Corporation 82562V 10/100 Network Connection (rev 02) since xen uses 2.6.16.29 it does not support it yet, someone said (on google) that 2.6.18.3 supports it. So I want to boot 2.6.18.3 in domU and enable it with the pciback thing. my seize commands are: echo -n 0000:00:19.0 >

Hello, I''m trying to do a pci passthrough for a perc 5/i raid controller and i have 2 problems (i haven''t used linux systems recently so i may be a bit rusty) : On the hardware part i''m using an ASUS M4A89TD PRO motherboard with iommu enabled in bios (and i can see with "xm dmesg" that I/O Virtualization seems enabled by xen). On the software part i

Trying to set up PCI pass through with xen 3.2.1 on Debian Lenny, with xen Kernel 2.6.26... having no luck. I have the following configured... i) Virtualization and vt-d are both enabled in the bios, I have power cycled after making these changes. ii) I have these option in grub menu; iommu=1 pciback.permissive pciback.hide=(07:01.0)(01:00.0) vtd=1 iii) I have this in my cfg file

Hi! As dom0 I''m running Ubuntu Hardy withe xen 3.3 from backports. Reason to using xen 3.3 is that I could get Intrepid stock kernel to work as domu with xen 3.2. Now the problem I have is that I can''t passthrough PCI-devices to my domu. If I run lspci in the domu nothing is returned. I''ve tried to use the kernel from Hardy (2.6.24-21-xen) and stock kernel from

I''ve been trying to set up a VGA-passthrough on my Ubuntu 12.04 box to run Windows (for gaming) while leaving my RAID-5 array available (managed by Linux). First, here are the machine specs: CPU: AMD A8-3870K 3.4GHz Quad-Core APU GPU: APU-integrated AMD Radeon 6550 (shared memory) Mobo: ASUS F1A75-V EVO with AMD-virtualization enabled in UEFI-BIOS RAM: 8GB DDR3 1866 G-Skill Sniper

Hi all! I want to assign a physical network card (e100) to a domU: I think Dom0 is ok but domU does not recognize the pci nic. into DomU I don''t know wath should I see: I have nothing in dmesg nor in messages... Into Dom0 I have this modules.conf: options pciback hide=(0000:03: 08.0) install e100 /sbin/modprobe pciback; /sbin/modprobe --ignore-install e100 This is dmesg: pciback

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned: