Displaying 20 results from an estimated 500 matches similar to: "Dedicate PCI Devices to DomU?"
2010 Feb 17
1
CentOS 5.3 host not seeing storage device
Maybe one of you has experienced something like this before.
I have a host running CentOS5.3, x86_64 version with the standard
qla2xxx driver. Both ports are recognized and show output in dmesg
but they never find my storage device:
qla2xxx 0000:07:00.1: LIP reset occured (f700).
qla2xxx 0000:07:00.1: LIP occured (f700).
qla2xxx 0000:07:00.1: LIP reset occured (f7f7).
qla2xxx 0000:07:00.0: LOOP
2018 Jun 12
2
[PATCH 1/2] Convert target drivers to use sbitmap
On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote:
> diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c
> index 025dc2d3f3de..cdf671c2af61 100644
> --- a/drivers/scsi/qla2xxx/qla_target.c
> +++ b/drivers/scsi/qla2xxx/qla_target.c
> @@ -3719,7 +3719,8 @@ void qlt_free_cmd(struct qla_tgt_cmd *cmd)
> return;
> }
>
2018 Jun 12
2
[PATCH 1/2] Convert target drivers to use sbitmap
On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote:
> diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c
> index 025dc2d3f3de..cdf671c2af61 100644
> --- a/drivers/scsi/qla2xxx/qla_target.c
> +++ b/drivers/scsi/qla2xxx/qla_target.c
> @@ -3719,7 +3719,8 @@ void qlt_free_cmd(struct qla_tgt_cmd *cmd)
> return;
> }
>
2016 Dec 08
3
[PATCH] linux/types.h: enable endian checks for all sparse builds
On 12/07/16 21:54, Michael S. Tsirkin wrote:
> On Thu, Dec 08, 2016 at 05:21:47AM +0000, Bart Van Assche wrote:
>> Additionally, there are notable exceptions to the rule that most drivers
>> are endian-clean, e.g. drivers/scsi/qla2xxx. I would appreciate it if it
>> would remain possible to check such drivers with sparse without enabling
>> endianness checks. Have you
2016 Dec 08
3
[PATCH] linux/types.h: enable endian checks for all sparse builds
On 12/07/16 21:54, Michael S. Tsirkin wrote:
> On Thu, Dec 08, 2016 at 05:21:47AM +0000, Bart Van Assche wrote:
>> Additionally, there are notable exceptions to the rule that most drivers
>> are endian-clean, e.g. drivers/scsi/qla2xxx. I would appreciate it if it
>> would remain possible to check such drivers with sparse without enabling
>> endianness checks. Have you
2007 Sep 23
3
ext3 file system becoming read only
Hi
In our office environment few servers mostly database servers and yesterday it
happened
for one application server(first time) the partion is getting "read only".
I was checking the archives, found may be similar kind of issues in the
2007-July archives.
But how it has been solved if someone describes me that will be really helpful.
In our case, just at the problem started found
2009 Feb 27
2
Stability
I''m wondering if anyone might have any suggestions...
We''ve installed CentOS5.2 on 3 servers and have an FC switch, dual-port cards, and FC RAID device. We configured the RAID as two separate logical RAIDs. One is RAID-10 for speed and it hosts Xen VM images as LVs. The rest of the drive is RAID-5 to maximize space and houses a lot of lighter access data on a GFS2 filesystem.
2009 Sep 15
1
SUMMARY : Repair Filesystem prompt , after inode has illegal blocks ; qla2xxx message on reboot
hi All,
thanks for the responses.
After being dropped into the
# Filesystem repair
prompt,
( on account of "inode 27344909 has illegal blocks" )
following warm reboot (via "reboot") after finding (SAN ) filesystem in read-only
mode yesterday morning (possibly because of HBA fault on SAN) , I ran
fsck -r /data
(Linux version 2.6.18-92.1.18.el5 , Red Hat 4.1.2-42 , ext3
2016 Dec 08
1
[PATCH] linux/types.h: enable endian checks for all sparse builds
On 12/07/16 18:29, Michael S. Tsirkin wrote:
> By now, linux is mostly endian-clean. Enabling endian-ness
> checks for everyone produces about 200 new sparse warnings for me -
> less than 10% over the 2000 sparse warnings already there.
>
> Not a big deal, OTOH enabling this helps people notice
> they are introducing new bugs.
>
> So let's just drop __CHECK_ENDIAN__.
2009 Sep 14
1
qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.
hi All,
Re below - thanks for the replies to the fsck question.
I have run fsck -r /data and this eventually completed with several changes made.
Now I am getting the following error from the qla2xxx driver on boot
.
.
.
qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.
qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.
.
etc
.
It looks
2018 Jun 12
1
[PATCH 1/2] Convert target drivers to use sbitmap
On Tue, 2018-06-12 at 09:15 -0700, Matthew Wilcox wrote:
> On Tue, Jun 12, 2018 at 03:22:42PM +0000, Bart Van Assche wrote:
> > On Tue, 2018-05-15 at 09:00 -0700, Matthew Wilcox wrote:
> > > diff --git a/drivers/scsi/qla2xxx/qla_target.c b/drivers/scsi/qla2xxx/qla_target.c
> > > index 025dc2d3f3de..cdf671c2af61 100644
> > > ---
2005 Sep 30
2
boot errors
I''ve compiled the 3.0-devel version on SUSE Linux 9.3. The ony problem is the qla2300 driver, which will not start all correctly on boot. So i cannot see other partitions than sda.
---------------------------------------------------------------------------------
QLogic Fibre Channel HBA Driver
ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 24 (level, low) -> IRQ 185
qla2300
2006 Jul 14
0
qla2xxx driver failed in dom0 - invalid opcode: 0000 [1] SMP
I wanted to post this in case there is a real bug here.
The system this is on is running Debian Etch with the Xen packages from
Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged
software so this is probably slightly out of date.
This is on an HP DL320 G4 with a Pentium D 930 processor. I tried unloading
and reloading the qla2xxx module, but rmmod reported it in use, however
2006 Jul 14
0
RE: qla2xxx driver failed in dom0 - invalid opcode: 0000[1] SMP
> I wanted to post this in case there is a real bug here.
>
> The system this is on is running Debian Etch with the Xen packages
from
> Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged
> software so this is probably slightly out of date.
It would be interesting to see if this can be repro''ed on a tree built
from a recent xen-unstable.hg.
2006 Jan 04
1
AW: QLA2xxx URGEND
2008 Feb 12
7
san fibrechannel device in HVM domU
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
2007 May 08
1
kernel: kernel BUG at include/asm/spinlock.h:109!
Hi,
We are running a server as an nfs head connect to a clariion, every
couple of days we have our box fall over with the following msg in
syslog.
Has anyone had this happen to there boxen?
rhel4 u4
May 8 12:23:52 ruchba kernel: Assertion failure in
log_do_checkpoint() at fs/jbd/checkpoint.c:363: "drop_count != 0 ||
cleanup_ret != 0"
May 8 12:23:52 ruchba kernel: ------------[ cut
2018 Jun 12
8
[PATCH 0/3] Use sbitmap instead of percpu_ida
Removing the percpu_ida code nets over 400 lines of removal. It's not
as spectacular as deleting an entire architecture, but it's still a
worthy reduction in lines of code.
Untested due to lack of hardware and not understanding how to set up a
target platform.
Changes from v1:
- Fixed bugs pointed out by Jens in iscsit_wait_for_tag()
- Abstracted out tag freeing as requested by Bart
2018 Jun 12
8
[PATCH 0/3] Use sbitmap instead of percpu_ida
Removing the percpu_ida code nets over 400 lines of removal. It's not
as spectacular as deleting an entire architecture, but it's still a
worthy reduction in lines of code.
Untested due to lack of hardware and not understanding how to set up a
target platform.
Changes from v1:
- Fixed bugs pointed out by Jens in iscsit_wait_for_tag()
- Abstracted out tag freeing as requested by Bart
2019 Jan 11
1
CentOS 7 as a Fibre Channel SAN Target
For quite some time I?ve been using FreeNAS to provide services as a NAS over ethernet and SAN over Fibre Channel to CentOS 7 servers each using their own export, not sharing the same one.
It?s time for me to replace my hardware and I have a new R720XD that I?d like to use in the same capacity but configure CentOS 7 as a Fibre Channel target rather than use FreeNAS any further.
I?m doing