On Thu, 2024-11-07 at 18:50 +0000, Jeremy Stanley wrote:
> On 2024-11-07 19:16:09 +0100 (+0100), Bastian Blank wrote:
> [...]
> > No, actually CD-ROM works fine, if you happen to use virtio to
> > access
> > it. What not works is AHCI.
>
> Ah, good point, if the cloud is selecting AHCI by default, it should
> be possible in OpenStack environments for a user to override that to
> virtio at server instance creation time by setting custom properties
> (depending on what hypervisor is in use on the backend). For other
> cloud providers/platforms, there may be similar options.
Does anybody on here know what I would need to specify on the virt-
install command to change the behavior of the CD-ROM?
This is what I am using:
```
virt-install \
--name {{ NewVirtualMachineName }} \
--memory {{ NewVirtualMachineRAM }} \
--cpu host \
--vcpus={{ NewVirtualMachineCPUs }} \
--import \
--disk "path={{ GuestDiskPath }}" \
--cloud-init meta-data="{{ CloudInitMetaDataFile.path }}",user-data="{{
CloudInitUserDataTempFile.path }}",network-config="{{
CloudInitNetworkConfigTempFile.path }}" \
--arch x86_64 \
--machine q35 \
--osinfo detect=on,name=debiantesting \
--network bridge=br0 \
--graphics spice \
--clock offset=utc \
--noautoconsole \
--autostart
```
