Bug 1350413
| Summary: | Hypervisor can't boot from iscsi lun on UEFI machine. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | cshao <cshao> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | amureini, bmcclain, bugs, cshao, fdeutsch, huzhao, jstodola, leiwang, lsurette, qiyuan, rbarry, rvykydal, sbueno, snagar, weiwang, yaniwang, ycui, ykaul |
| Target Milestone: | pre-dev-freeze | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-12 07:31:50 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: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1329957 | ||
| Attachments: | |||
Created attachment 1172860 [details]
UEFI_iscsi_VS_local
This looks like it's on legacy RHEV-H. iSCSI+EFI on legacy RHEV-H will probably get nacked due to capacity unless there's a customer case. I can't set the flag, though, unfortunately... Chen, we encountered this bug on RHVH 4.0 as well, right? (In reply to Ying Cui from comment #3) > Chen, we encountered this bug on RHVH 4.0 as well, right? Yes, we encountered this bug on RHVH 4.0 as well. Version info: RHEV-H-7.2-20160701.2-RHVH-x86_64-dvd1.iso redhat-release-rhev-hypervisor-4.0-0.9.el7.x86_64 imgbased-0.7.1-0.1.el7ev.noarch If this is also reproducible on NGN, can we file a separate bug for that targeted against anaconda (or re-target this bug against anaconda), please? Please attach the logs from the installation to this bug as individual, text/plain attachments. The logs are available in /tmp in the installer environment and copied to /var/log/anaconda in the installed system. Created attachment 1177188 [details]
new-log-ngn-uefi-iscsi-boot
Created attachment 1177303 [details]
ifcfg.log extracted from uefi-iscsi.tar.gz
Created attachment 1177304 [details]
X.log extracted from uefi-iscsi.tar.gz
Created attachment 1177305 [details]
packaging.log extracted from uefi-iscsi.tar.gz
Created attachment 1177306 [details]
ks-script-SWhS2k.log extracted from uefi-iscsi.tar.gz
Created attachment 1177307 [details]
ks-script-o23gan.log extracted from uefi-iscsi.tar.gz
Created attachment 1177308 [details]
anaconda.log extracted from uefi-iscsi.tar.gz
Created attachment 1177309 [details]
storage.log extracted from uefi-iscsi.tar.gz
Created attachment 1177310 [details]
syslog extracted from uefi-iscsi.tar.gz
Created attachment 1177311 [details]
program.log extracted from uefi-iscsi.tar.gz
Does iscsi boot work if you add 'ip=ibft' to the boot parameters? This is necessary for the iBFT interface to be available to anaconda to be configured. (In reply to David Shea from comment #18) > Does iscsi boot work if you add 'ip=ibft' to the boot parameters? This is > necessary for the iBFT interface to be available to anaconda to be > configured. Still not work after add 'ip=ibft' to the boot parameters. The bootloader is installed on a partition of a multipath disk with two offload iscsi devices. Either the UEFI firmware is not configured (or not able) to handle such a disk or the bootloader is not installed in proper way, but given it works on a local disk I'd think the former is the case. (In reply to Radek Vykydal from comment #21) > The bootloader is installed on a partition of a multipath disk with two > offload iscsi devices. Either the UEFI firmware is not configured (or not > able) to handle such a disk or the bootloader is not installed in proper > way, but given it works on a local disk I'd think the former is the case. Hi shaochen, Could you take a look at Radek's comment and check whether your UEFI firmware is configured properly? Or check whether it can handle such a disk? (Maybe attempt the same steps on a different machine that is known to have firmware which supports such a configuration?) The current firmware of our servers don't have the iscsi configuration item, so I can’t confirm whether this issue is caused by firmware configuration or not, we have to upgrade the firmware, and that will take some time. I also found if choose one iscsi lun to install bootloader, anaconda can't configure the /boot/efi and /boot on that iscsi lun, but put them on the local disk, and this will make the system unbootable. What's more, this issue occurred on UEFI FC server as well. I'm not sure the anaconda's behaviour is caused by firmware configuration or it can't configure /boot/efi on iscsi lun. In conclusion, 1. we have to wait until the firmware is upgrade to confirm this issue. 2. there is a bug in anaconda that it shouldn't configure the /boot/efi on other disks except the disk to install bootloader. I'll file a bug for this later. Our iSCSI UEFI machine is Dell PowerEdge R515, it's the Dell 11th generation of PowerEdge server, it can't support boot from iSCSI lun on UEFI mode, Dell 13th generation PowerEdge servers can support this feature, but we don't have the test enviroment yet. I tested RHVH 4.0 install and RHEL 7.3 install on Dell PowerEdge R515 UEFI mode, the behaviours are similar: 1. Choose only one iSCSI lun to install, RHVH 4.0 will pop up an error when partitioning, and installation can't go further. As to RHEL 7.3, it can finish installation, but can't boot. 2. Choose a local disk and one iSCSI lun to install, both RHVH 4.0 and RHEL 7.3 will put /boot and /boot/efi on the local disk, even set the iSCSI lun as boot device, intallation succeed, and the system will boot from local disk. Test versions: RHVH-4.0-20161116.0-RHVH-x86_64-dvd1.iso RHEL-7.3-20160923.0-Server-x86_64-dvd1.iso Qin, to summarize: This bug appeared on an 11th generation server, which is known to not support boot from iSCSI in UEFI mode, is this correct? Fabian, yes, you are right. Thanks Qin. Then I'm closing this bug - because of comment 28 - because it appeared on aa host which is known to not support that feature. Please file a new bug in case that this bug reappears on a Dell 13th gen server. |
Created attachment 1172859 [details] all log info Description of problem: Hypervisor can't to boot from iscsi lun on UEFI machine. Version-Release number of selected component (if applicable): rhev-hypervisor7-7.2-20160624.1 ovirt-node-3.6.1-13.0.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Prepare a UEFI machine. 2. Set the iscsi lun as boot lun. 3. Install RHEV-H on iscsi lun. 4. Reboot and try to login rhevh. Actual results: Hypervisor can't boot from iscsi lun on UEFI machine. Expected results: Hypervisor can boot from iscsi lun on UEFI machine. Additional info: 1. No such issue during boot from local disk on uefi machine. 2. No such issue during boot from iscsi lun on legney mode.