RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1707693 - Guest can't boot successfully when there are two bootable disk in guest
Summary: Guest can't boot successfully when there are two bootable disk in guest
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 1687348
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-08 06:07 UTC by Meina Li
Modified: 2021-03-15 07:35 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1687348
Environment:
Last Closed: 2021-03-15 07:35:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Meina Li 2019-05-08 06:07:17 UTC 
+++ This bug was initially created as a clone of Bug #1687348 +++

Description of problem:
Guest can't boot successfully when there are two bootable disk in guest

Version-Release number of selected component (if applicable):
libvirt-5.0.0-5.virtcov.el8.x86_64
qemu-kvm-3.1.0-18.module+el8+2834+fa8bb6e2.x86_64
kernel-4.18.0-74.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a guest with two bootable disk.
# virsh edit guest
...
 <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/lmn.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/rhel76.qcow2'/>
      <target dev='vdb' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
    </disk>
...

2. Start guest and check the status.
# virsh start guest
Domain guest started
# virsh list --all
 Id    Name   State
-----------------------
 256   guest    running

3. Check the console of the guest by virt-manager and find the guest will hang.
...
[    4.373732] ata2: SATA link down (SStatus 0 SControl 300)
[    4.373982] ata1: SATA link down (SStatus 0 SControl 300)
[    4.381651] ata4: SATA link down (SStatus 0 SControl 300)
[    4.381896] ata3: SATA link down (SStatus 0 SControl 300)
[    4.397653] ata6: SATA link down (SStatus 0 SControl 300)
[    4.397898] ata5: SATA link down (SStatus 0 SControl 300)
..

Actual results:
Can't boot successfully when there are two bootable disk in guest

Expected results:
Should boot the guest successfully

Additional info:
1) Please refer to the boot.log in attachment.
2) The UUID of vg, lv are different and the following are fstab file for two images:
For lmn.qcow2:
/dev/mapper/rhel-root   /                       xfs     defaults        0 0
UUID=d6423e79-98a9-4ff9-b5fc-a6ca2356f9b5 /boot                   xfs     defaults        0 0
/dev/mapper/rhel-swap   swap                    swap    defaults        0 0

For rhel76.qcow2:
/dev/mapper/rhel-root   /                       xfs     defaults        0 0
UUID=bd8118d2-aa31-4045-bcf5-fec6c7792e2a /boot                   xfs     defaults        0 0
/dev/mapper/rhel-swap   swap                    swap    defaults        0 0
3) Change both the path of rhel-root and rhel-swap to UUID and start guest, it can also reproduce.
Comment 2 Han Han 2019-05-08 06:57:56 UTC 
I find that the rootfs LVs are duplicated to /dev/mapper/rhel-root. So as the SWAPs /dev/mapper/rhel-swap.
Could you please replace all the path as UUID format in fstab of os image. I think the mount process cannot tell the LVs from each other.
Comment 3 Meina Li 2019-05-08 07:19:37 UTC 
Has already test by uuid in 3) in Additional info part.
Comment 7 RHEL Program Management 2021-03-15 07:35:54 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.