Bug 21995 – Von paravirtualisierten CD-ROM-Laufwerken kann nicht gebootet werden (KVM)

Bug 21995 - Von paravirtualisierten CD-ROM-Laufwerken kann nicht gebootet werden (KVM)


Summary:	Von paravirtualisierten CD-ROM-Laufwerken kann nicht gebootet werden (KVM)

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - KVM
Version:	UCS 2.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Bugzilla Mailingliste
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-03-25 15:26 CET by Alexander Kläser
Modified:	2023-06-28 10:46 CEST (History)
CC List:	2 users (show)

See Also:	36269
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Alexander Kläser

2011-03-25 15:26:38 CET

Wird unter KVM eine Maschine aufgesetzt nur mit paravirtualisiertem CD-Rom-Laufwerk und einer Boot-fähigen CD/DVD, dann kann nicht von der CD gebootet werden. Fehlermeldung:

> Boot failed: Could not read from CDROM (code 0001)
> No bootable device

Comment 1 Philipp Hahn

2013-06-06 09:47:13 CEST

Das ist mit SeaBios 1.7.2 und qemu-1.5 immer noch so.

Comment 2 Philipp Hahn

2013-06-07 11:15:07 CEST

Booting from VirtIO-*blk* CDROM is not supported: <https://lists.gnu.org/archive/html/qemu-devel/2013-06/msg01046.html>

VirtIO-*scsi* works with qemu-kmv-1.1.2 and libvirt-0.9.12
<http://wiki.qemu.org/Features/VirtioSCSI>
<http://www.redhat.com/archives/libvir-list/2012-January/msg00539.html>

    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/UCS_3.1-1-amd64+phahn.iso'/>
      <target dev='sda' bus='scsi'/>
      <readonly/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='scsi' index='0' model='virtio-scsi'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>

GRUB: OK
Installer: OK
UCS: OK
Windows XP: FAIL
  Scheitert während der Installation mit
  STOP: 0x0000007B (0XF7C7D63C,0xC0000034,0x00000000,0x00000000)
Windows 7: FAIL
  Scheitert an fehlenden Treibern während der Installation, d.h. man müsste dazu die VirtIO-Treiber als zusätzliches IDE-CDROM oder Floppy einbinden

Comment 3 Philipp Hahn

2014-11-10 11:12:43 CET

This is still an issue with UCS-4.0.

We should add "virtio-scsi" as an alternative or switch to it by default as "virtio" only supports disk block devices, which leads to CD-ROMs being not fully functional: an UCS "DVD" only works as it is a "Hybrid-ISO" image, which contains a disk partition table and as such is mountable via /dev/vdX1.

The device is not recognized as a CD-ROM drive by udev, which runs "/lib/udev/cdrom_id /dev/vdX". As such it isn't accessible via /dev/sr0, which is used in /etc/fstab as the device for /cdrom. (Running "univention-repository-create" fails because it tries to mount /cdrom.)

virtio-blk also doesn't support TRIM, which the newer QEMU can use to free allocates space in QCOW2 and QED files.

Comment 4 Philipp Hahn

2015-01-14 19:59:48 CET

Again: Ticket #2014112821000255

Comment 5 Stefan Gohmann

2016-04-25 07:52:48 CEST

This issue has been filed against UCS 2.4.

UCS 2.4 is out of maintenance and many UCS components have vastly changed in
later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug".
In this case please provide detailed information on how this issue is affecting
you.