Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1687348 - 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: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dracut
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-11 10:46 UTC by Meina Li
Modified: 2019-03-11 12:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)
boot.log (deleted)
2019-03-11 10:46 UTC, Meina Li
no flags Details

Description Meina Li 2019-03-11 10:46:31 UTC
Created attachment 1542826 [details]
boot.log

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.


Note You need to log in before you can comment on or make changes to this bug.