search for: scsi_level

...(111, ''Connection refused'') tail -f xend-debug.log cat: /sys/bus/scsi/devices/host5/model: No such file or directory cat: /sys/bus/scsi/devices/host5/type: No such file or directory cat: /sys/bus/scsi/devices/host5/rev: No such file or directory cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file...

...cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target0:2:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target0:2:0/model: No such file or directory cat: /sys/bus/scsi/devices/target0:2:0/type: No such file or directory cat: /sys/bus/scsi/devices/target0:2:0/rev: No such...

...si: cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory cat: /sys/bus/scsi/devices/host6/model: No such file or directory cat: /sys/bus/scsi/devices/host6/type: No such file or directory cat: /sys/bus/scsi/devices/host6/rev: No such file or directory cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/vendor: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/model: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/type: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/rev: No such file...

...011. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/...

...h0: Operation not supported xenstore-read: couldn''t read path backend/vbd/2/2053/node can''t add vif3.0 to bridge eth0: Operation not supported xenstore-read: couldn''t read path backend/vbd/3/2053/node /var/log/xen/xend-debug.log has this cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/...

...pt2sas0: port enable: SUCCESS Vendor: Dell Model: Virtual Disk Rev: 1028 Type: Direct-Access ANSI SCSI revision: 06 scsi 0:1:0:0: RAID1: handle(0x004f), wwid(0x04adb846d46d5f0a), pd_count(2), type(SSP) scsi 0:1:0:0: qdepth(128), tagged(1), simple(1), ordered(0), scsi_level(7), cmd_que(1) SCSI device sda: 285474816 512-byte hdwr sectors (146163 MB) sda: Write Protect is off sda: Mode Sense: 03 00 00 08 SCSI device sda: drive cache: write through SCSI device sda: 285474816 512-byte hdwr sectors (146163 MB) sda: Write Protect is off sda: Mode Sense: 03 00 00 08 SCSI dev...

...ents_async}=="" looking at parent device '/devices/pci0000:00/0000:00:03.0/virtio0/host0/target0:0:1/0:0:1:0': KERNELS=="0:0:1:0" SUBSYSTEMS=="scsi" DRIVERS=="sd" ATTRS{rev}=="1 " ATTRS{type}=="0" ATTRS{scsi_level}=="7" ATTRS{model}=="PersistentDisk " ATTRS{state}=="running" ATTRS{unpriv_sgio}=="0" ATTRS{queue_type}=="none" ATTRS{iodone_cnt}=="0x478f" ATTRS{iorequest_cnt}=="0x478f" ATTRS{device_busy}=="0&q...

...012. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/...

...nnected, configured in the BIOS before installing the OS. From dmesg: ** scsi 0:1:0:0: Direct-Access LSI Logical Volume 3000 PQ: 0 ANSI: 6 scsi 0:1:0:0: RAID1: handle(0x0143), wwid(0x0dafbe8ecd4f4330), pd_count(2), type(SSP) scsi 0:1:0:0: qdepth(128), tagged(1), simple(1), ordered(0), scsi_level(7), cmd_que(1) ** So, one of these must be true: 1) The machine came from HP with the IR firmware, yet MegaCli64 does not work on the 2308-4i. For the record, it dies because /dev/megaraid_sas_ioctl_node is not created when MegaCli64 is run, as it is on PowerEdge machines. 2) The machine came f...

...s with another terminal. If everything goes well, a SCSI host shows up in your VM (DomainU). clematis:/# cat /sys/class/scsi_host/host0/proc_name scsifront And you can see a disk driver: clematis:/# ls /sys/class/scsi_device/0\:0\:0\:0/device/ block:sda iocounterbits queue_depth scsi_level vendor bus iodone_cnt queue_type state delete ioerr_cnt rescan timeout device_blocked iorequest_cnt rev type driver model scsi_device:0:0:0:0 uevent - Status and TODO I manage to do fdisk, dd with a virt...

Guys, I''ve successfully ran dom0/domU (both Debian) in my local laptop using 2.6.32.15 dom0 with xen-4.0.1-rc3-pre. Great. Now I want to install it into couple of test-machines without compiling from source. So I did following.. a. make dist-xen b. make dist-tools PYTHON_PREFIX_ARG="--install-layout=deb" c. make dist-stubdom This

...ice '/devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/0000:06:00.1/host8/rport-8:0-0/target8:0:0/8:0:0:1': KERNELS=="8:0:0:1" SUBSYSTEMS=="scsi" DRIVERS=="ch" ATTRS{rev}=="190G" ATTRS{type}=="8" ATTRS{scsi_level}=="4" ATTRS{model}=="Scalar i40-i80 " ATTRS{state}=="running" ATTRS{unpriv_sgio}=="0" ATTRS{queue_type}=="none" ATTRS{iodone_cnt}=="0xe2" ATTRS{iorequest_cnt}=="0xe2" ATTRS{queue_ramp_up_period...

Does anyone know what program can be used to query the RAID status from the OS for an on-board LSI SAS 2308-4i? On this page: http://docs.avagotech.com/docs/12351997 there is a curious note on the left that reads: "Integrated MegaRAID support available upon request" After one mostly fruitless round of chatting with LSI/Avago/Broadcom and one completely fruitless round of chatting

...0VLS600 E516 PQ: 0 ANSI: 6 [ 50.239242] scsi 0:0:0:0: SSP: handle(0x000c), sas_addr(0x5000cca00fa20fd1), device_name(0xa0cc0050d30fa20f) [ 50.249120] scsi 0:0:0:0: SSP: enclosure_logical_id(0x5842b2b0512d3300), slot(0) [ 50.256573] scsi 0:0:0:0: qdepth(254), tagged(1), simple(1), ordered(0), scsi_level(7), cmd_que(1) [ 50.266830] scsi 0:0:1:0: Direct-Access HITACHI HUS156060VLS600 E516 PQ: 0 ANSI: 6 [ 50.274824] scsi 0:0:1:0: SSP: handle(0x000a), sas_addr(0x5000cca00fa1ef81), device_name(0xa0cc005083efa10f) [ 50.284702] scsi 0:0:1:0: SSP: enclosure_logical_id(0x5842b2b0512d3300), slot...

...0:0:0:0: Direct-Access SEAGATE ST3300657SS 0006 PQ: 0 ANSI: 5 scsi 0:0:0:0: SSP: handle(0x0009), sas_addr(0x5000c50023bdb4b9), device_name(0x00c50050b8b4bd23) scsi 0:0:0:0: SSP: enclosure_logical_id(0x50030480004a14c0), slot(0) scsi 0:0:0:0: qdepth(254), tagged(1), simple(1), ordered(0), scsi_level(6), cmd_que(1) ata_piix 0000:00:1f.2: version 2.13 ata_piix 0000:00:1f.2: PCI->APIC IRQ transform: INT B -> IRQ 19 ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] ata_piix 0000:00:1f.2: setting latency timer to 64 scsi1 : ata_piix scsi2 : ata_piix ata1: SATA max UDMA/133 cmd 0xbc00 ctl 0xb880 bmd...

Hi everyone, I am very excited to see that dom0 pvops is finally coming close to working, so I wanted to give it a try. >From the description it was not clear to me which kernel to chose as base for the patches.hg, so I took the latest (that was ~ 2 weeks ago) kernel on git.kernel.org I could find (post-2.6.28 git tip at that point). I managed to more or less apply all of the patches in the