similar to: pciback and pci passtrought problems

Hi, next step, # dmesg | grep pciback Bootdata ok (command line is root=/dev/sda2 ro console=tty0 pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0) ) Kernel command line: root=/dev/sda2 ro console=tty0 pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0) Unknown boot option

Hi, i updated from 3.2.1 to 3.3.0 and now i can''t start a vm Error: (38, ''Function not implemented'') ------------------------------------------------------------------------- title Xen 3.3.0 / Debian GNU/Linux, kernel 2.6.18-6-xen-amd64 root (hd0,1) kernel /boot/xen-3.3.0.gz module /boot/vmlinuz-2.6.18-6-xen-amd64 root=/dev/sda2

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

Hi, new day, new Problem and i don''t know what it means.... --------------------------------------------------------- DOMAIN0:~# xm create auto/fli4l Using config file "/etc/xen/auto/fli4l". Error: unsupported format character '':'' (0x3a) at index 6 --------------------------------------------------------- kernel = "/HDD250/vm_images/fli4l/KERNEL"

Hello, I''m running 6.26-2-xen-amd64 with xen-hypervisor-3.2-1-amd64. Now I try to pass through a controller card to WHS, at the moment without success because the card isn''t present in DomU. At the first moment I guess it''s a windows problem ;) so I''d tried to boot a Knoppix .iso but same problem there, the passed through device isn''t present in DomU.

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 >

Hi, I've got some weird sound artifacts happening during calls, they're very hard to describe, so I have a 122kb recording: http://openprojects.rarcoa.com/~miztic/artifact.wav normally the artifacts are just short blips, not quite as long as the one above, but they sound the same. When using the aggressive echo suppressor, it seems like those artifacts cause a really loud buzzing sound to

Greetings Xen user community, I am interested in using Mellanox ConnectX cards with SR-IOV capabilities to passthrough pci-e Virtual Functions (VFs) to Xen guests. The hope is to allow for the use of InfiniBand directly within virtual machines and thereby enable a plethora of high performance computing applications that already leverage InfiniBand interconnects. However, I have run into some

On 3/22/23 04:23, nospam at godawa.de wrote: > Jim Fehlig schrieb: >> >> What is the libvirt version? > > It's the "latest and greatest" I get from this source: > > [root at xen1 ~]# virsh --version > 6.6.0 > > [root at xen1 ~]# libvirtd --version > libvirtd (libvirt) 6.6.0 > > [root at xengfs1f ~]# yum list | grep libvirt >

Hi, i tried a complete new installation with Debian 5.0.0 Lenny. Standard Installation works fine, Xen Install from Sources also. But after reboot the startup stops with the kernel panic, that it doesn''t find the modules folder.... its an Asrock AM2NF3-VSTA Board with nForce3 250 chipset, and the HDD is on Sata I compiled my own kernel, and tried with the AMD and Nvidia IDE Driver

Sorry to duplicate my issues onto the list - I thought I had looked through this thread before and seen a different error, but apparently Adam and I are running into much the same thing. I'm seeing exactly the same "Failed to assign device to IOMMU" along with the "Device not owned by PCI Back End or pci-stub" in these scenarios. I have not gone back to previous versions,

Hi all, I am trying the pci-passthrough on xen 3.3.0. I binded the pci slot to pciback using late binding. But xend fails to allocate this slot to domU. linux-242:/home/xen-3.3.0 # xm create -c pci=08:01.0 /etc/xen/xen3.3_guest1 Using config file "/etc/xen/xen3.3_guest1". Error: [Errno 2] No such file or directory: ''/sys/bus/pci/devices/0000:06:00.0/config''

Thanks Anna, this was also quite interesting for me. Did you mean that I just have to eliminate the else branch or raise arround "All devices behind the uppermost PCI/PCI-X bridge must be co-assigned to the same guest." or do I have to eliminate more in order to prevent an FLR (whatever that is). For my board it''s definitely necessary to move PCI devices in different guests,

Hi, I am still trying to assign pci or usbs to a domU. I get to the point where pciback seizes the devices (5 usb and 2 pci). I modified the configuration of the domU with pci = [ ''00:1d.0'' , ''00:1d.1'' , ''00:1d.2'' , ''00:1d.3'' , ''00:1d.7'', ''02:01.0'' , ''02:02.0'' ] but

Remove duplicated #include('s) in drivers/xen/xen-pciback/xenbus.c Signed-off-by: Huang Weiyi <weiyi.huang at gmail.com> --- drivers/xen/xen-pciback/xenbus.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/xen-pciback/xenbus.c b/drivers/xen/xen-pciback/xenbus.c index 206c4ce..978d2c6 100644 --- a/drivers/xen/xen-pciback/xenbus.c +++

Remove duplicated #include('s) in drivers/xen/xen-pciback/xenbus.c Signed-off-by: Huang Weiyi <weiyi.huang at gmail.com> --- drivers/xen/xen-pciback/xenbus.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/xen-pciback/xenbus.c b/drivers/xen/xen-pciback/xenbus.c index 206c4ce..978d2c6 100644 --- a/drivers/xen/xen-pciback/xenbus.c +++

Good morning, I need to use pciback.hide to hide a pci card because I want to pci passthrough that card to a domU. My hardware neither supports Intel-Vt-d nor AMD's IOMMU. Unfortunately this doesn't seem to work in Centos 54 anymore. I guess it doesn't work because it is not compiled into the kernel, but as a module. I got the following error in dmesg and the pci device is still

Hello, I''m attempting to run Windows XP in a domU using the PCs actual graphics card. I believe I''ve set everything up correctly, including the pciback module etc. I''ve set pciback to grab the graphics card and all the USB hosts as well: (from dmesg) pciback 0000:00:02.0: seizing device pciback 0000:00:02.1: seizing device pciback 0000:00:1a.0: seizing device pciback

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Fix to return -ENOENT in the pcistub_device_find() and pci_get_drvdata() error handling case instead of 0(overwrite to 0 by str_to_slot()), as done elsewhere in this function. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- drivers/xen/xen-pciback/pci_stub.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Fix to return -ENOENT in the pcistub_device_find() and pci_get_drvdata() error handling case instead of 0(overwrite to 0 by str_to_slot()), as done elsewhere in this function. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- drivers/xen/xen-pciback/pci_stub.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3