Bug 1154116 - Unable to boot with virtio-scsi from qcow2 image
Summary: Unable to boot with virtio-scsi from qcow2 image
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-17 15:10 UTC by Frank Büttner
Modified: 2015-05-31 19:19 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-31 19:19:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The boot menu (5.17 KB, image/png)
2014-10-17 15:10 UTC, Frank Büttner
no flags Details

Description Frank Büttner 2014-10-17 15:10:29 UTC
Created attachment 947932 [details]
The boot menu

Description of problem:
When an VM use SCSI as the disc bus an the virtio-scsi as the SCSI controller, it can't boot.

Version-Release number of selected component (if applicable):
libvirt-1.1.3.6-1.fc20.x86_64

How reproducible:
every time

Steps to Reproduce:
1. create an vm (for example with virt-manager)
2. use SCSI as the bus and qcow2 for the disc image
3. use virtio-scsi as the scsi controller
4. use SCSI as the bus for the CD-ROM drive

Actual results:
the vm don't boot, because the virtual BIOS don't see the disc.

Expected results:
An booting vm.

Additional info:
See the picture of the boot process.
Both the CD-ROM and the disc use virtio-scsi.
Booting from the CD-ROM an iso image work.
Switching back to virtio as the bus for the disc, will result in an booting vm from disc.

Comment 1 Fedora End Of Life 2015-05-29 13:06:37 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Cole Robinson 2015-05-31 19:19:50 UTC
This works fine for me on F22, so closing. If you can still reproduce on F21+, please reopen


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