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 Spec: Domain: Cpu: Cores: 4 Sockets: 1 Threads: 1 Devices: Disks: Boot Order: 1 Disk: Bus: virtio Name: rootdisk Cdrom: 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): cnv-2.2 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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.
I was testing it with cirros/fedora, if the CDROM driver is virtio, the VMI cannot be scheduled due to the error.
Created attachment 1662623 [details] vm yaml
Could it be that we need to limit the bus for cdroms to SATA? Michal, what does RHV do?
(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.
No, no i440fx support. We are starting with q35. This means that limiting and defaulting CDROM to SATA sounds sane.
Created attachment 1665285 [details] virtio is recommended disk type for windows tools on UI
Stu, when moving to POST, please ensure that you link to the relevant PR.
My mistake. I thought I had. https://github.com/kubevirt/kubevirt/pull/3107
*** Bug 1800638 has been marked as a duplicate of this bug. ***
Stu, better use the proper field for it. It makes it easier to find.
verify with build hco-bundle-registry-container-v2.3.0-7 virt-operator-container-v2.3.0-36 $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"} step: 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.
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. https://access.redhat.com/errata/RHEA-2020:2011