similar to: [PATCH 0/4] megaraid_sas HBA emulation

Hi Alex, I've been playing around with VFIO and megasas (of course). What I did now was switching between VFIO and 'normal' operation, ie emulated access. megasas is happily running under VFIO, but when I do an emergency stop like killing the Qemu session the PCI device is not properly reset. IE when I load 'megaraid_sas' after unbinding the vfio_pci module the driver

Hi Alex, I've been playing around with VFIO and megasas (of course). What I did now was switching between VFIO and 'normal' operation, ie emulated access. megasas is happily running under VFIO, but when I do an emergency stop like killing the Qemu session the PCI device is not properly reset. IE when I load 'megaraid_sas' after unbinding the vfio_pci module the driver

This patch add an emulation for the LSI MegaRAID SAS HBA. It is using SG_IO to forward / pass through SCSI commands to the underlying block driver, so no emulation is done currently. Signed-off-by: Hannes Reinecke <hare at suse.de> --- Makefile.hw | 2 +- hw/megasas.c | 1134 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/pci_ids.h | 2 + 3 files changed, 1137

This patch add an emulation for the LSI MegaRAID SAS HBA. It is using SG_IO to forward / pass through SCSI commands to the underlying block driver, so no emulation is done currently. Signed-off-by: Hannes Reinecke <hare at suse.de> --- Makefile.hw | 2 +- hw/megasas.c | 1134 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/pci_ids.h | 2 + 3 files changed, 1137

Hello, I noticed the default megaraid_sas driver version in upstream Linux 2.6.32.25 is pretty old, version 4.01, and it seems to be very buggy. It fails to bring up disks and boot fails. Many people have reported this issue on various hardware using LSI RAID adapters, and on various Dell servers (R310/R410/R510/R710) using Dell PERC H700 RAID adapters (which are rebranded LSI adapters).

Hello, I noticed the default megaraid_sas driver version in upstream Linux 2.6.32.25 is pretty old, version 4.01, and it seems to be very buggy. It fails to bring up disks and boot fails. Many people have reported this issue on various hardware using LSI RAID adapters, and on various Dell servers (R310/R410/R510/R710) using Dell PERC H700 RAID adapters (which are rebranded LSI adapters).

Hi all, I got bored and implemented SCSI passthrough for the virtio-blk driver. Principle is quite simple, just put the missing fields (cdb, sense and status header) on the virtio queue and then call the SG_IO ioctl on the host. So when using '-drive file=/dev/sgXX,if=virtio,format=host_device' you can happily call any sg_XX command on the resulting vdX device. Quite neat, methinks. And

Hi all, I got bored and implemented SCSI passthrough for the virtio-blk driver. Principle is quite simple, just put the missing fields (cdb, sense and status header) on the virtio queue and then call the SG_IO ioctl on the host. So when using '-drive file=/dev/sgXX,if=virtio,format=host_device' you can happily call any sg_XX command on the resulting vdX device. Quite neat, methinks. And

On 08/21/2013 12:48 PM, Michael S. Tsirkin wrote: > Hey guys, > I've put up a wiki page with a kvm PCI todo list, > mainly to avoid effort duplication, but also in the hope > to draw attention to what I think we should try addressing > in KVM: > > http://www.linux-kvm.org/page/PCITodo > > This page could cover all PCI related activity in KVM, > it is very

On 09/17/2015 07:33 AM, Michael S. Tsirkin wrote: > On Wed, Sep 16, 2015 at 07:29:17PM -0500, Suman Anna wrote: >> The virtio core uses a static ida named virtio_index_ida for >> assigning index numbers to virtio devices during registration. >> The ida core may allocate some internal idr cache layers and >> an ida bitmap upon any ida allocation, and all these layers are

On 01/16/2017 05:04 PM, Fam Zheng wrote: > This series implements the proposed fc_host feature of virtio-scsi. > > The first patch updates the data structure changes according to the spec > proposal; the second patch actually implements the operations. > > Fam Zheng (2): > virtio_scsi: Add fc_host definitions > virtio_scsi: Implement fc_host > >

Hi List, I''ve testet a bunch of kernel- and module versions with megaraid_sas and xen for months now. With 2.6.18.8 kernel and v00.00.03.01 megaraid_sas module there seem to be sometimes strange and unreproduceable segmentation faults up to kernel panics under heave i/o load. With 2.6.24-19-xen kernel from Ubuntu and v00.00.03.10 megaraid_sas it seemed stable. But I was able to

CentOS Errata and Enhancement Advisory 2014:0893 Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-0893.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ba8d66aa82c1aabaf23f0635284306d4715a9580baea9ceded32ba4887cb882e kmod-megaraid_sas-06.803.01.00_rh1-1.el6_5.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2016:1780 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1780.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3f942683663a5acf3ec76fbc4da33363451ff5778ea1da2dec382806510af15f kmod-megaraid_sas-06.811.02.00-1.el7_2.x86_64.rpm Source:

CentOS Errata and Enhancement Advisory 2017:0518 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-0518.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ed979c3e0264765971802dcf126c98649e278f5c5fddd224d72e80b461826169 kmod-redhat-megaraid_sas-07.700.00.00-rh1.el7_3.x86_64.rpm Source:

CentOS Errata and Enhancement Advisory 2018:1670 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1670 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a795c66044e67414a963d7531c1ce960850b788b1cb1fe63db95ed1159f18a9c kmod-redhat-megaraid_sas-07.702.06.00_rh2_dup7.5-1.el7_5.x86_64.rpm Source:

CentOS Errata and Enhancement Advisory 2018:1670 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1670 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) Source: b243c283592e002f31d604f12edbbfdd26a188f335f2751b92ad129045e79172 kmod-redhat-megaraid_sas-07.702.06.00_rh2_dup7.5-1.el7_5.src.rpm -- Johnny Hughes

Hi Everyone I am looking at setting up a File Server that uses ISCSI storage. It is the first time I have done this, so I am wanting to get peoples thoughts on whether for CentOS systems you should use Hardware based ISCSI HBA's? If so do I need to be careful about what HBA I use ? Currently I am looking at purchasing a Dell System using Broadcom ethernet cards/ ISCSI HBA. From

On 06/20/2013 11:07 AM, Dennis Chen wrote: > Hi, > > When I want to use NPIV for a FC HBA in my Linux machine, I got the below > error msg in virsh: > > virsh # nodedev-create /home/kvm/vHBA.xml > error: Failed to create node device from /home/kvm/vHBA.xml > error: internal error Parent device scsi_host20 is not capable of vport > operations > > I checked the

Hi. I'm looking at a qlogic qle2462 hba for my dl360 g5. The thread http://www.mail-archive.com/freebsd-stable@freebsd.org/msg99497.html mentions a deadlock when system is loaded. Has this issue been resolved? Are there other PCI Express hba's which are known to work with freebsd stable and dl360 g5? -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is