Summary: | The spapr vscsi disks for lun id '9-31' and channel id '4-7' could not be recognized inside a power pc guest | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Gu Nini <ngu> |
Component: | qemu-kvm-rhev | Assignee: | David Gibson <dgibson> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | dgibson, knoel, lmiksik, lvivier, mrezanin, qzhang, shuyu, virt-maint, xuhan, xuma, zhengtli |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.3.0-23.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-04 16:56:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: |
Description
Gu Nini
2015-09-07 01:49:37 UTC
This result is normal as the default values for ibmvscsi module are: # cat /sys/module/ibmvscsi/parameters/max_channel 3 And the maximum number of LUN is hardcoded in the driver: linux/drivers/scsi/ibmvscsi/ibmvscsi.c ... 2298 2299 host->max_lun = 8; 2300 host->max_id = max_id; 2301 host->max_channel = max_channel; 2302 host->max_cmd_len = 16; ... The spapr-vscsi paravirtual interface isn't really designed to handle multiple SCSI targets, although it can to a limited extent. Under PowerVM the interface only ever has a single target per controller. For the LUNs we should probably reduce the advertised number of LUNs in the qemu side to 8 (currently 31). Max channels sounds like jut a guest configuration problem, not a bug. Thanks Laurent and David. Hello, David Based on your comment, do you want to move the bug to POST status? Regards, Qunfang I already did. So we do want to fix this so it's handled more gracefully, but there are some questions about whether it's best address in qemu or the guest. In any case this is essentially a cosmetic problem (poor error reporting) so I'm deferring to RHEL 7.3. Fix included in qemu-kvm-rhev-2.3.0-23.el7 Verify the bug on following sw versions: Host kernel: 3.10.0-313.el7.ppc64le Qemu-kvm-rhev: qemu-kvm-rhev-2.3.0-23.el7.ppc64le Guest kernel: 3.10.0-306.0.1.el7.ppc64le Now, the spapr-vscsi lun with id 8 or larger could not be initialized with following error prompt: (qemu) device_add scsi-hd,bus=scsi0.0,drive=s63-l8-c1,scsi-id=63,lun=8,channel=1,id=hds63-l8-c1 2015-09-18T10:45:58.288290Z bad scsi device lun: 8 2015-09-18T10:45:58.288399Z Device 'scsi-hd' could not be initialized Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2546.html |