similar to: PCI passthrough - pci interrupt gets disabled

Hello List, I'm hoping someone else out there has an Asus DSBF-DE server board, and can tell me if anything special needs to be done to get ports 5 and 6 of the onboard SATA to work under Centos 5.1 x64. I have drives on 1 through 4 that are detected and working properly, however, a drive on 5 is not detected, from what i can tell, the kernel doesn't even see phy's for ports 5 and 6.

(lspci-output added at the end of this mail!) Hi specialists, I''m trying to pass an HP Surestore USB-drive to a domU. I''m hiding the pci-device in the dom0, and capturing it in the domU. Although this works fine I receive the following lines in /var/log/syslog of the dom0 after a reboot ======================================================================= Aug 8

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, We are having a problem on several Supermicro servers (I'll include more details on the configuration later) : when booting Linux 3.2 linux-image-3.2.0-4-amd64 (Wheezy) as a DOM0 on Xen 4.1 (xen-hypervisor-4.1-amd64 from Wheezy), the system hangs after : [ 3.716174] scsi1 : ata_piix [

Dear folks, We are installing a large diskless cluster using CentOS 5.1. The hardware is pretty new - Supermicro X7DWT boards with Harpertown CPUs. Unfortunately we have some PXE-related problems described by the following scenario: 1) Set up DHCP, TFTP and NFS on a server, prepare PXE kernel and initrd - fine. 2) Start up the node using PXE for the first time - fine. 3) Reboot the node - PXE

Hi ,Guys I installed CentOS5.2-x86_64 on my Dell PowerEndger 1950 with virtualization component ,when reboot the system halted at: /////////////////////////////////////////////////////////// Red Hat nash version 5.1.19.6 usb 1-5: device not accepting address 4 ,error -110 usb 1-5: device not accepting address 5, error -110 usb 1-5: device not accepting address 6,error -110 usb 1-5: device not

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

# lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 22) 00:05.0 PCI bridge [0604]: Intel Corporation 5520/X58 I/O Hub PCI

On 7/30/2016 6:56 AM, Fawzy Ibrhim wrote: > # lspci -nn > 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) > 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) > 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 22) >

On 01/25/2014 06:54 PM, Ivan Kabaivanov wrote: > Hi all > > I have a very weird case of pci passthrough. > > I have a machine with 7 network interfaces, all of them intel. Four of them are on one quad giga ethernet device. If I manually unbind the devices and allow qemu to use them, with intel IOMMU working, everything works like a charm. Here's how I do it manually: >

On 7/28/2016 3:41 PM, Fawzy Ibrahim wrote: > LSI SATA MEGARAID 95Q9 afaik, the megaraid cards are mostly all SAS, which support SATA drives, except very old ones were SCSI. Ok, I do see they had a series of MegaRAID SATA 150-xx and 300-xx cards, these were 64 bit PCI or PCI-X cards. 95Q9 does not appear to be a valid card number, 9240, 9260, 9280 are some pci-express SAS MegaRaid

I obtain this error when booting (xen/stable-2.6.31.x|xen/master) on Xen 3.4.2 x86_64 xen_major : 3 xen_minor : 4 xen_extra : .2 I had no errors with the same kernel, version of the day 2010-03-03 To compile the kernel i use this configuration " http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 "

Hi all I have a very weird case of pci passthrough. I have a machine with 7 network interfaces, all of them intel. Four of them are on one quad giga ethernet device. If I manually unbind the devices and allow qemu to use them, with intel IOMMU working, everything works like a charm. Here's how I do it manually: root@kybrat (x86_64) ~]$ lspci -nn | grep net 00:19.0 Ethernet controller

Hello all, I recently bought a brand new Dell Precision 7540 laptop.? Before buying I checked the specifications from the RedHat hardware list and they said that it was "fully RedHat 8 Certified" and listed all the hardware that was "certified" to work with that laptop. https://access.redhat.com/ecosystem/hardware/3979771 I have had good results the last few years with

I installed a 2 port serial PCI card on a system running CentOS 4.3, but I can't get the additional serial ports to work. The card I used is from StarTech (http://www.startech.com/Product/ItemDetail.aspx? productid=PCI2S550&c=US). When it is detected by kudzu, it shows up as a "NetMos Technologies PCI 9835 Multi I/O Controller". I've included the output of

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important I already posted this on the xen-devel-mailinglist but no one seems to have an answer. I'm posting it here because perhaps someone using Debian and Virtualization might have an idea about this? Since Debian 8 I observe that live migrating a PVM on XEN 4.4.1 (also 4.5.1) and Linux Kernel 4.1.0 (also 3.18) requires

[big snip] > There is a sysfs attribute called "d3cold_allowed" which can be used > for "blocking" D3cold, so can you please retest using that? > Hey-this is almost certainly not the right place in this thread to respond, but this thread has gotten so deep evolution can't push the subject further to the right, heh. So I'll just respond here. I've been

Hi, I using on all server (FSC RX100S5) xen 3.3.1 and kernel 2.6.26-1 or 2.6.26-2,evrything it works good. Now I try using xen 3.4.0 with the same kernel but the system not up only go to the initramfs. I suspect that the kernel did not load the driver for the controller. The question just why it works on a Xen 3.3.1 does not work on 3.4 with the same versions of the kernel . Below I put

Hi, Here it is... 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary)

Dear List, After some googling around without any results, I'm quite puzzled. Since some past update I can't precise, kernel 2.6.164 works fine, however 2.6.194 has some sound problem in my somewhat old and beaten Toshiba laptop. -Audacious plays OK but other applications have problems. -For instance, mplayer acts quirky: when I pause a playing video, sound keeps stuttering endlessly. The

https://bugs.freedesktop.org/show_bug.cgi?id=68488 Priority: medium Bug ID: 68488 Assignee: nouveau at lists.freedesktop.org Summary: Lockup and reboot on T61 with nouveau driver/exa QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: All Reporter: a9016009 at gmx.de