Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2001808

Summary:	Add Attach Windows guest tools CD
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Martin Necas <mnecas>
Component:	ovirt-engine	Assignee:	Liran Rotenberg <lrotenbe>
Status:	CLOSED DEFERRED	QA Contact:	Guilherme Santos <gdeolive>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.8	CC:	abpatil, ahadas, bugs, lrotenbe, mavital, michal.skrivanek, shipatil, usurse
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-19 08:23:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1996098

Description Martin Necas 2021-09-07 08:54:02 UTC

Description of problem:
Allow starting VM with guest tools CD enabled.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Arik 2021-09-13 11:27:43 UTC

Liran, how about adding that option also to REST-API (maybe not only for run-once but also for ordinary run-vm via REST-API)?

Comment 2 Liran Rotenberg 2021-09-13 11:49:04 UTC

We have the option to add this in the UI when using Run-Once on a Windows VM and that VM is set with the CD to something(suppose to be windows installation disk). Then the user can select on attach the drivers disk and it will run with it.
The idea of having it in Run-Once only is that it suppose to be only when the user is installing Windows OS on a VM and it is expected to be done once. AFAIK, there are manual steps in that flow, as such, having it only in the UI (as this is non-automated) does make sense.
For users to install it later on when the OS installed and the VM is running they need to change disk on that VM and install it. In the Windows installation it is done manually, also on a installed Windows OS, as the APT it gone and the user is required to manually install it from the disk.

The auto-attaching dropped in favor of Windows updates(store), only the initial setup should be done manually, or in the OS installation to recognize virtio disks for example.
Is it for the OS installation? How it is automated?

Comment 3 Arik 2021-09-13 11:57:26 UTC

(In reply to Liran Rotenberg from comment #2)
> Is it for the OS installation? How it is automated?

That's a question you can ask in bz 1996098
It seems the user likes to automate create-vm and then run-vm via Ansible, I don't know what they do once the VM is up and how they interact with the installer
OK, let's talk about ordinary (not run-once) run operations once separately, I suspect that it would be trivial to achieve if we enable it for run-once via the API
So is there a reason not to enable it the same way we do via the UI also via the API?

Comment 4 Liran Rotenberg 2021-09-13 14:06:30 UTC

It might work only if we have a CD-ROM attached already, but we can test it. Apart from that, we can add it to the API.

Comment 10 Michal Skrivanek 2022-04-27 14:32:30 UTC

you can attach virtio-win the same way as any other CD. I don't think we need a special option for this.

Comment 12 Michal Skrivanek 2022-05-19 08:23:39 UTC

Unfortunately this request was not prioritized and didn't make it into RHV 4.4SP1. There are no further major RHV releases planned to implement this in(see https://access.redhat.com/support/policy/updates/rhev for RHV lifecycle information)