similar to: The problem about xen pci passthrough

-----Original Message-----From: John R Pierce <pierce at hogranch.com> Reply-to: CentOS mailing list <centos at centos.org> To: centos at centos.org Subject: Re: [CentOS] SCSI drives and Centos 7 Date: Sat, 29 Apr 2017 13:31:11 -0700 On 4/29/2017 12:42 PM, Gregory P. Ennis wrote: > what does `lspci` have to say about this raid card ? > > John, > > Thanks for the prompt

-----Original Message-----From: John R Pierce <pierce at hogranch.com> Reply-to: CentOS mailing list <centos at centos.org> To: centos at centos.org Subject: Re: [CentOS] SCSI drives and Centos 7 Date: Sat, 29 Apr 2017 11:19:38 -0700 On 4/29/2017 10:49 AM, Gregory P. Ennis wrote: > I am remote from the unit today, and do not have a good way to look at > the board today, but the

On 4/29/2017 12:42 PM, Gregory P. Ennis wrote: > what does `lspci` have to say about this raid card ? > > John, > > Thanks for the prompt : > > lspci demonstrates : > > 02:01.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID (rev 01) > 02:02.0 SCSI storage controller: Adaptec AIC-7902B U320 (rev 10) > 02:02.1 SCSI storage controller: Adaptec AIC-7902B U320

On Sun, Apr 30, 2017 at 1:03 PM, Gregory P. Ennis <PoMec at pomec.net> wrote: > Thanks for your help. I did not want to replace this machine with new > equipment, but it looks like I may need to do just that. > > Here are the results with respect to the lsi raid board for : > > lspci -nn > > > 02:01.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID

Hello, I am desperately trying to get pci-passthrough to working. I want to pass a tg3 nic to domU. when booting domU I get a lot of messages: pcifront pci-0: pciback not responding!!! in domU, "ifconfig eth... adress up" hangs for 2 minutes, finally ifconfig -a shows a correct setting with no data transmitted rx/tx The IP Adress is being assigned, but there is no data transmission

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 gurus, I used xen 4.1.0 (64bit) + dom0 kernel 2.6.32.39 (32bit) + domu kernel 2.6.32.39 (32bit) environment. I was trying to passthru Broadcom NIC to domu. The NIC can be UP but not RUNNING, on domu #ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:10:18:95:25:90 inet addr:10.0.0.3 Bcast:10.0.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

When destroying pcifront/pciback, the following message appears in the guest linux kernel log. WARNING: g.e. still in use! WARNING: leaking g.e. and page still in use! This is caused by the wrong disconnect procedure that pcifront terminates the gnttab foreign access before pciback unmaps the ring. This patch corrects the handling of pcifront/pciback destruction sequence. Firstly pcifront

Following 7 patches are for PCIE AER (Advanced Error Reporting) support for XEN. --------------------------------------------------------------------------- Patches 1~4 back port from Linux Kernel which enables kernel support to AER. Those patches enable DOM0 PCIE error handling capability. When a device sends a PCIE error message to the root port, it will trigger an interrupt. The irq handler

Hi, It seems that destroying pcifront/pciback always fails on current xen. This patch fixes the problem, making pciback switch to "Closed" state after pcifront switched to "Closing" state. Regards, ------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Dear All, The production server supports Intel Virtualization Technology. Processor is an Intel Xeon 1.86 GHz Quad Core. 8 GB DDR2 memory. There is also an Emulex LightPulse Fiber Channel HBA adapter. The host operating system (Dom 0) is RHEL 5 x86 with Xen Virtualization technology. Dom 0 kernel is 2.6.18-8.el5xen. I have recompiled the Dom 0 kernel so that pciback

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

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

On Wed, Jan 27, 2016 at 01:30:05PM -0500, Konrad Rzeszutek Wilk wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. I have very similar (the same?) problem with USB 3.0 controller. But on different software versions. > >

include/xen/xenbus.h nicely declares struct xenbus_driver''s ''ids'' member as pointer to const... As usual, written and tested on 2.6.25-rc3 and made apply to the 2.6.18 tree without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2008-02-26/drivers/xen/blkback/xenbus.c

Patch 6 pciback_err_handler.patch: Implementation for enabling PCIE_AER support in XEN This patch is the main implementation for enabling PCIE_AER handling, adding related pci error handler in pciback and pcifront. When a device sends a PCIE error message to the root port, it will triger an interrupt. The irq handler will then collect roor error status register, then schedule a work to process

Hi, I have a question about the bug: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1632 This is marked as fixed in the pv-ops kernel. I am working for a company developing a xen based virtualisation solution. Unfortunately the design is tied to CentOS and there is resistance to upgrade to > 2.6.31 kernel. My question is whether it is possible for me to try to backport the fixes for

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