search for: new_slot

...04:01.0 > /sys/bus/pci/drivers/ohci_hcd/unbind echo -n 0000:04:01.1 > /sys/bus/pci/drivers/ohci_hcd/unbind echo -n 0000:04:01.2 > /sys/bus/pci/drivers/ohci_hcd/unbind echo -n 0000:04:01.3 > /sys/bus/pci/drivers/ehci_hcd/unbind echo -n 0000:04:01.0 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:04:01.1 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:04:01.2 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:04:01.3 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:04:01.0 > /sys/bus/pci/drivers/pciback/bind echo -n 0000:04:01.1 > /sys/bus/pci/dr...

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

...------------------------------------ after trying to load pciback as module: -------------------------------------------------------------------------------------- echo -n 0000:02:05.0 > /sys/bus/pci/drivers/8139too/unbind modprobe pciback echo -n 0000:02:05.0 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:02:05.0 > /sys/bus/pci/drivers/pciback/bind echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/bind echo -n 0000:02:07.0 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:02:07.0 > /sys/bus/pci/drivers/pcib...

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 > /sys/bus/pci/drivers/pciback/bind echo -n bind 0000:2:0.1 > /sys/bus/pci/drivers/pciback/bind It fails in one of two ways. If there is a driver present for that device, the driver symlink has a value...

...5) 02:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) and here is the script to bind/unbind: #!/bin/sh # ifdown eth0 ifdown dev1804289383 echo -n 0000:02:02.0 > /sys/bus/pci/drivers/sundance/unbind echo -n 0000:02:02.0 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:02:02.0 > /sys/bus/pci/drivers/pciback/bind echo -n 0000:02:01.0 > /sys/bus/pci/drivers/8139too/unbind echo -n 0000:02:01.0 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:02:01.0 > /sys/bus/pci/drivers/pciback/bind Here is the domU configuration (the first pci/mac,...

...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 script containing "modprobe pciback" and the necessary unbind, new_slot, and bind commands. I also modified the configuration file for my IPCop domU by inserting the line pci=(´03:02.0´, ´03:03.0´, ´03:05.0´) and by removing the vif=... statement. When I start my IPCop domU I can''t see the three NICs. It''s also impossible to install the appropriate dr...

...so I used this script before the startup of xendomains: #!/bin/bash /sbin/modprobe pciback SLOT=0000:06:00.1 # Unbind a PCI network card from its network driver echo -n $SLOT > /sys/bus/pci/drivers/e1000/unbind # And now bind it to the PCI Backend echo -n $SLOT > /sys/bus/pci/drivers/pciback/new_slot echo -n $SLOT > /sys/bus/pci/drivers/pciback/bind I can see that after executing the script above the adapter is bind to pciback correctly. When I start the DomU I can´t see the Adapter with lspci. I use XEN 3.1.0 with Kernel 2.6.18 (Source-Package) under Debian Etch. The frontend-Driver is c...

...3 16:07 0000:03:08.0 -> ../../../../devices/pci0000:00/0000:00:1e.0/0000:03:08.0 --w------- 1 root root 4096 Dec 3 16:07 bind lrwxrwxrwx 1 root root 0 Dec 3 16:07 module -> ../../../../module/pciback --w------- 1 root root 4096 Dec 3 16:07 new_id --w------- 1 root root 4096 Dec 3 16:07 new_slot -rw------- 1 root root 4096 Dec 3 16:07 permissive -rw------- 1 root root 4096 Dec 3 16:07 quirks --w------- 1 root root 4096 Dec 3 16:07 remove_slot -r-------- 1 root root 4096 Dec 3 16:07 slots --w------- 1 root root 4096 Dec 3 16:07 unbindsys/bus/pci/drivers/pciback/ This is the domU confg...

Hi all, This has, i''m sure, been told a lot of time but i haven''t found any things to solve my problems. Here is it: I wan''t to export a usb port on DomU (CentOS 5) from my Dom0 (Debian Etch). I have only succeded with the pci export but with the next command: "xm create machine pci=00:1d.0" With having many differents syntaxes in the machine

...vices/pci0000:00/0000:00:1e.0/0000:04:04.0 > --w------- 1 root root 4096 2008-11-16 20:53 bind > lrwxrwxrwx 1 root root 0 2008-11-16 20:53 module -> > ../../../../module/pciback > --w------- 1 root root 4096 2008-11-16 20:53 new_id > --w------- 1 root root 4096 2008-11-16 20:53 new_slot > -rw------- 1 root root 4096 2008-11-16 20:53 permissive > -rw------- 1 root root 4096 2008-11-16 20:53 quirks > --w------- 1 root root 4096 2008-11-16 20:53 remove_slot > -r-------- 1 root root 4096 2008-11-16 20:53 slots > --w------- 1 root root 4096 2008-11-16 20:53 uevent > -...

...n run where 1 second''s worth of data is taking around 1.03 seconds, if I remember correctly, and our spec only allows us to be .008 seconds late. I tried to hide the PCI cards from dom0, to see what the behavior is like in a domU, but I can''t get that to work either. The pciback new_slot/bind stuff appears to work (I don''t get errors), but when I try to create my domU, I get errors listing other devices that must also be sent to domU (looks like everything on that PCI bus) Do you guys think there''s a better chance of getting these boards working on domU or dom0?...

...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:00:01.0 > /sys/bus/pci/drivers/pciback/new_slot # echo 0000:00:01.0 > /sys/bus/pci/drivers/pciback/bind # xl pci-list-assignable-devices 0000:00:01.0 where 0000:00:01.0 is the location of the graphics card. I''m not sure what else there is to try at this point. Is this a bug, a problem with Ubuntu''s repository version, or...

Hi, I''m on a HP DL365, amd64, running SLES10sp1, but with kernel and xen of SLES10sp2, therefore using Xen 3.2. The domU shall be a Windows HVM guest. I want use the Qlogic SAN card in a domU. I''m following these instructions: http://www.novell.com/communities/node/2880/assign-dedicated-network-card-or-pci-device-xen-virtual-machine well, there is written that this only

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

All, I would like to run the following issue past the list to confirm that my problem analysis makes sense or whether I missed something: We have a HP ML370G6 server with VT-x and VT-d enabled in the BIOS. It is equipped with two Smart Array HBAs - one connected to the HDD array (SmartArray P800) and one connected to an LTO tape drive (SmartArray P212). Both controllers use the same driver

...ler (rev 03) 00:0a.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 00:0a.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 00:0a.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01) then i echoed ''0000:00:0a.3'' into /sys/bus/pci/drivers/pciback/new_slot and into /sys/bus/pci/drivers/pciback/bind when i do this, i get PCI: Enabling device 0000:00:0a.3 ACPI: PCI Interrupt 0000:00:0a.3 -> GSI18 (level,low) -> IRQ 16 ACPI: PCI interrupt for device 0000:00:0a.3 disabled What to do now? How could i tell him to find this device in domu? THANKS...

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

...2562V 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 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:00:19.0 > /sys/bus/pci/drivers/pciback/bind (results from dmesg) pciback: wants to seize 0000:00:19.0 pciback 0000:00:19.0: probing... pciback 0000:00:19.0: seizing device pciback 0000:00:19.0: pcistub_device_alloc pciback 0000:00:19.0: initializing... pciback 0000:00:19.0: initia...

...doesn''t seem to do anything (i have also tried 0000:03:0e.0 as pci function but still nothing). i can do the binding at runtime using this commands : echo "0000:03:0e.0" >/sys/bus/pci/drivers/megaraid_sas/unbind echo "0000:03:0e.0" >/sys/bus/pci/drivers/pciback/new_slot echo "0000:03:0e.0" >/sys/bus/pci/drivers/pciback/bind and it works, i can check that the device is available to pass-through with "xm pci-list-assignable-devices" (i also see "pciback seizing device message" in log), and i can start my vm. But i would like to do...

..../../../../devices/pci0000:00/0000:00:1e.0/0000:07:01.0 0 --w------- 1 root root 4096 2009-01-24 00:21 bind 0 lrwxrwxrwx 1 root root 0 2009-01-24 00:21 module -> ../../../../module/pciback 0 --w------- 1 root root 4096 2009-01-24 00:21 new_id 0 --w------- 1 root root 4096 2009-01-24 00:21 new_slot 0 -rw------- 1 root root 4096 2009-01-24 00:21 permissive 0 -rw------- 1 root root 4096 2009-01-24 00:21 quirks 0 --w------- 1 root root 4096 2009-01-24 00:21 remove_slot 0 -r-------- 1 root root 4096 2009-01-24 00:21 slots 0 --w------- 1 root root 4096 2009-01-24 00:05 uevent 0 --w------- 1...