Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The guest failed to start when having a file image disk created on host disk with 4096 sector
Version-Release number of selected component (if applicable):
libvirt-1.0.4-1.1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Find the test machine with 4096 sector in Beaker:dell-per300-01.rhts.eng.bos.redhat.com
2. Confirm it has a disk of 4096 sector.
[root@dell-per300-01 ~]# fdisk -l /dev/sda
Disk /dev/sda: 160.0 GB, 160000000000 bytes, 312500000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
......................
[root@dell-per300-01 ~]# fdisk -l /dev/sdb
Disk /dev/sdb: 162.8 GB, 162842222592 bytes, 39756402 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0008e73a
Device Boot Start End Blocks Id System
/dev/sdb1 63 2622611 10490196 83 Linux
/dev/sdb2 2622720 3622720 4000004 83 Linux
3. create a guest named kvm-rhel6.4 on default dir pool backed on sda
4. create a image backed on sdb
# mount /dev/sdb2/ /var/lib/libvirt/test/
# #qemu-img create -f qcow2 /var/lib/libvirt/test/test.qcow2 5G
5. add test.qcow2 to guest, make below configurations
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source file='/var/lib/libvirt/test/test.qcow2'/>
<blockio logical_block_size='4096' physical_block_size='4096'/>
<target dev='vdb' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</disk>
7. start guest
# virsh start kvm-rhel6.4
error: Failed to start domain kvm-rhel6.4
error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1 (label charserial0)
qemu-kvm: -drive file=/var/lib/libvirt/test/test.qcow2,if=none,id=drive-virtio-disk1,format=qcow2,cache=none: could not open disk image /var/lib/libvirt/test/test.qcow2: Invalid argument
Actual results:
Expected results:
Additional info:
Description of problem: The guest failed to start when having a file image disk created on host disk with 4096 sector Version-Release number of selected component (if applicable): libvirt-1.0.4-1.1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Find the test machine with 4096 sector in Beaker:dell-per300-01.rhts.eng.bos.redhat.com 2. Confirm it has a disk of 4096 sector. [root@dell-per300-01 ~]# fdisk -l /dev/sda Disk /dev/sda: 160.0 GB, 160000000000 bytes, 312500000 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes ...................... [root@dell-per300-01 ~]# fdisk -l /dev/sdb Disk /dev/sdb: 162.8 GB, 162842222592 bytes, 39756402 sectors Units = sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0008e73a Device Boot Start End Blocks Id System /dev/sdb1 63 2622611 10490196 83 Linux /dev/sdb2 2622720 3622720 4000004 83 Linux 3. create a guest named kvm-rhel6.4 on default dir pool backed on sda 4. create a image backed on sdb # mount /dev/sdb2/ /var/lib/libvirt/test/ # #qemu-img create -f qcow2 /var/lib/libvirt/test/test.qcow2 5G 5. add test.qcow2 to guest, make below configurations <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/var/lib/libvirt/test/test.qcow2'/> <blockio logical_block_size='4096' physical_block_size='4096'/> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> 7. start guest # virsh start kvm-rhel6.4 error: Failed to start domain kvm-rhel6.4 error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1 (label charserial0) qemu-kvm: -drive file=/var/lib/libvirt/test/test.qcow2,if=none,id=drive-virtio-disk1,format=qcow2,cache=none: could not open disk image /var/lib/libvirt/test/test.qcow2: Invalid argument Actual results: Expected results: Additional info: