Bug 1802001 - CD-ROM does not support disk type "VirtIO"
Summary: CD-ROM does not support disk type "VirtIO"
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 2.3.0
Assignee: sgott
QA Contact: zhe peng
: 1800638 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2020-02-12 05:59 UTC by Guohua Ouyang
Modified: 2020-05-04 19:10 UTC (History)
9 users (show)

Fixed In Version: hco-bundle-registry-container-v2.3.0-70 virt-operator-container-v2.3.0-36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-05-04 19:10:37 UTC
Target Upstream Version:

Attachments (Terms of Use)
vm yaml (2.34 KB, text/plain)
2020-02-12 09:53 UTC, Guohua Ouyang
no flags Details
virtio is recommended disk type for windows tools on UI (51.04 KB, image/png)
2020-02-24 03:27 UTC, Guohua Ouyang
no flags Details

System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 3107 0 None closed Reject CD-ROM devices that use the virtio bus 2020-05-20 09:19:04 UTC
Github kubevirt kubevirt pull 3145 0 None closed [release-0.26] Reject CD-ROM devices that use the virtio bus 2020-05-20 09:19:04 UTC
Red Hat Product Errata RHEA-2020:2011 0 None None None 2020-05-04 19:10:49 UTC

Description Guohua Ouyang 2020-02-12 05:59:42 UTC
Description of problem:
Create a VM with CD-ROM driver is virtio, the VMI cannot be started because "disk type 'virtio' of 'vdb' does not support ejectable media".

$ oc describe vmi vm1

      Cores:    4
      Sockets:  1
      Threads:  1
        Boot Order:  1
          Bus:  virtio
        Name:   rootdisk
          Bus:       virtio
          Readonly:  true
          Tray:      closed
        Name:        cd-drive-1

" Normal   SuccessfulCreate  78s                 disruptionbudget-controller     Created PodDisruptionBudget kubevirt-disruption-budget-lw6fr
  Normal   SuccessfulCreate  78s                 virtualmachine-controller       Created virtual machine pod virt-launcher-vm1-5j45r
  Warning  SyncFailed        64s (x25 over 66s)  virt-handler, host-172-16-0-15  server error. command SyncVMI failed: "LibvirtError(Code=67, Domain=10, Message='unsupported configuration: disk type 'virtio' of 'vdb' does not support ejectable media')"

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Petr Kotas 2020-02-12 09:22:25 UTC
Hi, if you are installing the virtio-win during windows install, the SATA bus has to be used.

When installing windows, the virtio drivers are not present and therefore the virtio bus can not be used.
When installing Linux, the drivers should be present in the kernel for most of current Linux distributions and the installation will be fine.

Comment 2 Guohua Ouyang 2020-02-12 09:48:04 UTC
I was testing it with cirros/fedora, if the CDROM driver is virtio, the VMI cannot be scheduled due to the error.

Comment 3 Guohua Ouyang 2020-02-12 09:53:37 UTC
Created attachment 1662623 [details]
vm yaml

Comment 4 Fabian Deutsch 2020-02-18 15:52:00 UTC
Could it be that we need to limit the bus for cdroms to SATA?

Michal, what does RHV do?

Comment 5 Michal Skrivanek 2020-02-19 13:45:36 UTC
(In reply to Fabian Deutsch from comment #4)
> Could it be that we need to limit the bus for cdroms to SATA?
> Michal, what does RHV do?

do you support i440fx at all? if yes it needs to be machine type dependent. Which it should be in any case since you definitely want to support other architectures where SATA may not necessarily be available.
For q35 on x86 yeah, use SATA.

Comment 6 Fabian Deutsch 2020-02-19 13:47:25 UTC
No, no i440fx support.
We are starting with q35.

This means that limiting and defaulting CDROM to SATA sounds sane.

Comment 8 Guohua Ouyang 2020-02-24 03:27:39 UTC
Created attachment 1665285 [details]
virtio is recommended disk type for windows tools on UI

Comment 9 Dan Kenigsberg 2020-03-08 12:56:37 UTC
Stu, when moving to POST, please ensure that you link to the relevant PR.

Comment 10 sgott 2020-03-10 13:13:43 UTC
My mistake. I thought I had. https://github.com/kubevirt/kubevirt/pull/3107

Comment 11 sgott 2020-03-12 19:44:59 UTC
*** Bug 1800638 has been marked as a duplicate of this bug. ***

Comment 12 Dan Kenigsberg 2020-03-13 14:19:03 UTC
Stu, better use the proper field for it. It makes it easier to find.

Comment 14 zhe peng 2020-04-02 07:31:44 UTC
verify with build 
$virtctl version
Server Version: version.Info{GitVersion:"v0.26.4", GitCommit:"9e5318e9a784a14bd18db682ec7a137ea65eb986", GitTreeState:"clean", BuildDate:"2020-03-31T14:58:56Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

 create a vm with cd-rom with virtio bus
$cat vm.yaml
 - cdrom:
     bus: virtio
   name: cd-drive-1

$ oc create -f test.yaml
The request is invalid: spec.template.spec.domain.devices.disks[1].cdrom.bus: Bus type virtio is invalid for CD-ROM device

test with UI:
use wizard to create a vm
add a virtio bus cdrom, will get error when create vm:
Error "Bus type virtio is invalid for CD-ROM device" for field "spec.template.spec.domain.devices.disks[1].cdrom.bus".

move to verified.

Comment 17 errata-xmlrpc 2020-05-04 19:10:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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